Microsoft Remote Desktop Services Reviews

I use RDS to connect our servers.

The most valuable part of RDS is that it allows you to work from any location and check the server through a VPN connection.

Users have to re-enter their ID and password every time they log on, which is tedious and repetitive. It would be better if the system could save users' passwords between sessions.

I've been using RDS for around ten years.

The cloud version's scalability is better than on-prem.

Microsoft's technical support is helpful, but its speed could be better.

The initial setup is very simple.

I would rate RDS eight out of ten.

As an internal Microsoft product, we find it very trustworthy. It's quite secure. It connects easily to Windows operating systems on devices. 

The performance meets our requirements and the stability is good.

The solution scales well.

The setup process is easy.

The solution is under the Microsoft infrastructure and therefore does not allow for service under other operating systems. We'd like, in the future, if it would work with Linux or Unix-based operating systems or even Mac.

Although I don't use it consistently, I have used it for ten to 15 years. It's a pretty old solution. 

The solution is stable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. It's very reliable. 

The scalability is okay. Sometimes we deploy a server-client scenario, so many clients can connect to the same server and they can log in at the same time simultaneously. There's no issue with scalability in that sense.

We have 50 users on the product currently.

We've never had any real issues. I haven't dealt with technical support.

In terms of the initial setup, the implementation process is simple and straightforward. It's not difficult. 

Since it is not a new solution, most of the engineers know how to deploy and how to operate it; we are not waiting for further technical documents for assistance.

Since it was quite easy to deploy, we did not need any outside assistance from integrators or consultants. 

While it's connected to the cloud, it's a solution that is currently on-premises. 

I'm not sure if we are using a specific version. Whatever options that come with Microsoft, we use that. Since they upgraded Microsoft (for example, earlier it was Microsoft XP, and Windows 7, 8, 9, 10, et cetera), the options come up throughout those operating systems. We use whatever they offer.

I would recommend the solution to others. I'd rate it at a nine out of ten. We've had a good experience with it over a number of years. 

We predominantly use RDS to connect up to a computer and a LAN. We are non-profit and help other non-profits with their technology. We are customers of Microsoft. 

This is a user-friendly solution and I'm very pleased that RDS now includes multi-screen. If you're remotely controlling a system that has two monitors, you can split and have your own, it's a nice feature. I like the ubiquity of the product, the fact that it's around as a protocol, and that it can be utilized at the admin level to look at any console that one might need. You don't need to think about it very much. Of course, the fact that it uses an active directory for security and authentication is pretty nice. It helps secure a network to a large extent because you can really restrict the number of users and accessibility if needed. Those are all good things.

I've sometimes had trouble setting up an RDS connection if I want a specific user to be able to log in with their credentials and have the RDS element retain those settings so that the password isn't required each time. There can be issues with that. 

I've been using this solution for many, many years. 

I've got no issues with the stability of RDS. 

I don't have much to offer regarding scalability. We use RDS predominantly for admin connection to other servers in a network. I might log into one computer in a remote network and then use RDS to get from that server to a different server but that's as far as it goes.

The initial setup is relatively straightforward, especially if you're familiar with the solution. Most organizations we deal with have a technician, or at least a network administrator who deals with any day-to-day issues. We generally maintain the operating system for these organizations and we run updates on them all the time.

There's nothing to be afraid of with this solution. I don't have any problems with it, it's great for me. 

I rate this solution 10 out of 10. 

It allows me to remotely take control of a desktop if my wife or son has a problem.

I have been using the solution for one or two years. 

The solution is stable.

It doesn't need to be scalable in my case as I only implement the solution on a few desktops at home. 

I've had good experiences with Microsoft customer support. 

It was easy for me, but I have experience working in this field.

I would say it's expensive as there similar products available for free. 

I rate this solution a seven out of ten.

We use Microsoft Remote Desktop if we want, for example, to help a user that has a problem. We can also use it to take the control of a computer on a remote location.

The simplicity of the product has been most valuable to me. This is especially true if you use a Microsoft product to connect to Microsoft Remote Desktop. There is no broker in between. Microsoft Remote Desktop is something that comes with Windows at no cost unless you use a Microsoft server.

For me, it boils down to simplicity. There is no cost and the setup is easy. 

From the perspective of an IT professional, Microsoft Remote Desktop is very easy to use. However, it could be made easier to use for the end user, especially when it comes to activating it.

Microsoft could also improve the sustainability of this product, especially in terms of account redundancy. They could also add something like a log to make more easy to use so that they can easily prevent some of the failures. I think Microsoft can do better.

I have been using Microsoft servers for more than 20 years. My first Microsoft server was NT 3.5.

Microsoft Remote Desktop is quite stable product now, particularly if you compare it to previous version.

Microsoft Remote Desktop is scalable. 

The technical support is good. I have had some issues with them, but most of time the technical support is good. Phone support is difficult for me to use but the Microsoft Knowledge Base has been helpful. It is easy to find solutions to problems in the knowledge base. You can also get email support, which is useful. 

We have some of our client applications deployed onto the RDS platform, and we need to test those applications through RDS Web Access. We need to test how external users access these applications from different networks, like the cloud gateway or external locations. As a part of the QA team, I need to check if users can access the applications without any issues.

Basically, I also work with Citrix, and I think the most important thing is getting access to Citrix. Microsoft developed the RDS solution for this purpose, and we don't see any issues accessing applications from Microsoft RDS. It's a good solution.

Users have reported that sometimes when we try to initialize an application, the session disappears one out of ten times. So, maybe it can be one of the areas of improvement. We are still investigating the issue, but we believe it might be due to a network or server issue.

Because this was the only issue I experienced was with the initialization of the session, which affected the stability of the service.

It's a project-based thing for me, so I move into different technologies depending on the project. I worked on Microsoft in June, and now I am into RDS. Currently, I am working on a project for RDS, and once that's done, I may move on to another technology. So, I've been using RDS for around three to four months.

It is stable, but users have reported that sometimes when we try to initialize an application, the session disappears one out of ten times. So we have to download the session file again and re-initiate the session. This issue occurs occasionally, and we must click on the application to reinitialize the session.

We are actually trying to get some insights on the issue with the initial initialization of sessions from the architect, also.

Overall, I would rate the stability a seven out of ten because we still need clarity from the architect. Is it something in the world of technology, or do we have the same issue? Or is it something that we are getting this issue because we moved to a new enrollment? We are just awaiting that.

It is scalable. Currently, we have 19 host servers, and each host is serving around 20 sessions or so.

I would rate the scalability an eight out of ten, where ten is very scalable. I haven't compared it with other solutions, but as an end-user, I believe it is quite scalable.

We have around 600 people, but about 300 to 400 users use the solution concurrently. Nowadays, we are using it regularly due to people working from different locations, but previously it was mainly used when people were working remotely from home.

The customer service and support team is good. 

Positive

The initial setup is not that difficult. I have gone through the RDS initialization steps, which only seem easy.

I would rate the setup around eight because I haven't compared it with other tools yet. But overall, I'm comfortable with the solution.

For the deployment process, in the current scenario, we have this solution from one vendor, and we are migrating it to a new platform. So it's not a complete configuration but rather a lift-and-ship process from one platform to another. We've been working on it for a long time.

We have around four to five people for the deployment and about four to five people for testing the applications after migration. There are a couple of architects who are looking into all the configuration changes in the lift-and-ship process. And there are also a couple of managers and a few quality assurance people.

For maintenance, the client has a partnership with Microsoft for maintenance as part of this deployment.

I would recommend the solution to people, especially for its security aspects and device compatibility.

I would give it a nine, it's good overall.

The solution helps users to access desktops remotely.

The solution performs well and is easy to use.

Microsoft's desktop versions have a limit of only one concurrent session. It needs to be improved. Also, they should enhance the solution's user interface. It could be more intuitive compared to TeamViewer and AnyDesk. 

I rate the solution's stability as a nine.

We have used VNC Viewer, UltraVNC, and TeamViewer before.

The solution is easy to install.

The solution's license is affordable.

I recommend the solution to others and rate it as a nine.

We have a group of users who work remotely for us, as well as others who connect to our computers from various locations.

The solution works on Microsoft servers. 

Microsoft Remote Desktop Services needs to improve its security. 

I have been using the product for 20 years. 

I rate Microsoft Remote Desktop Services' stability a nine out of ten. 

I rate the tool's scalability a nine out of ten. My company has 80 users. 

We don't use technical support from Microsoft. We have outsourced it to another company. 

We chose Microsoft because it was cheaper. 

Microsoft Remote Desktop Services' deployment is easy. 

The tool's pricing is high in the Slovenian market. I rate it a nine out of ten. 

I rate Microsoft Remote Desktop Services a nine out of ten.