Microsoft Remote Desktop Services Reviews

We use Remote Desktop Services for a few things. My experience started with Microsoft Remote Desktop when I tried to reuse really low power desktop machines to turn them from these desktop machines into class remote desktop terminals. That is my initial experience with Microsoft Remote Desktop. My most current experience with Microsoft Remote Desktop is using a specific Microsoft product on the servers where you don't have any chance to administer them using the web browser. SCCM, active directory administration and other Wintel server roles are most handy and the most secure to administer from the Microsoft Management Console. Therefore, you need to do it at least from some instance of the Microsoft windows server.

I like that it works. In most cases, it's predictable. You know what you get.

Microsoft still has some really bad remote desktop appliances for Mac. This is really frustrating because if I'm on windows I can remove the Microsoft remote desktop applied for Windows, but I'm already using windows, I always have an option B. I can still plug directly with Microsoft management console from the windows station and still do something remotely. But on a Mac, I have to rely purely on the Microsoft Remote Desktop. 

If I need to pass second-factor authentication, not a one-time password thing, if I do a Microsoft remote desktop session, I have to reach the first server, which is my best one. From that server, you're actually going inside your protective network. Then on the second spot, you are not able to pass a YubiKey and go any farther. That creates the problem. We have had many support tickets.

With this new company, I have been using this solution for two and a half years, but overall I have 15 years of experience.

It is being used mainly on a Mac platform.

I would say it's stable.

In the last setup, we had 3,000 users. It wasn't the nicest experience.

My experience with support is varied. It really depends. It varies depending on which support line you get. If you say you're a particular engineer then they won't really bother to support you. But if you say you have an enterprise contract and that you're a big company and you have a contract then they offer better support.

We previously used Citrix. Microsoft Remote Desktop Services is a more developed version of Citrix.

I would recommend going for VMware.

Microsoft programs are never easy to install but the installation wasn't something we didn't expect.

We deployed it on our own.

We use enterprise orchestration so it doesn't take too long to deploy. Microsoft products do not really play along with the open-source orchestration platforms. Once you overcome this, it becomes easier.

I would not recommend going with this solution because I wouldn't recommend going for a big enterprise setup. 

I would rate it a four out of ten. 

In the next release, they should develop better support for remote desktops for alternative platforms. It's really lacking consistency. If I have to support terminal server clusters and I have to do change management on the big cluster, then I actually run into a lot of issues both on the Microsoft Remote Desktop as well as Citrix. They should provide a consistent user experience. It's a pain to roll out changes into a different mode of the cluster and to propagate them over multiple modes. I end up in a situation where a portion of my users get the changes and the other portion doesn't.

I was exploring a different feature, particularly trying to deploy active directory domain services. Hence, as an IT administrator, I needed to enable a Remote Desktop Service feature that allows me to connect remotely to the server in just a matter of seconds, so that was my use case for Microsoft Remote Desktop Services.

I was trying to install Microsoft Office on the computer remotely, which means connecting to the server through Microsoft Remote Desktop Services to see if the server has access to the internet or whenever an update needs to be installed.

What I found most valuable in Microsoft Remote Desktop Services is accessibility because the solution lets you take control of your computer remotely, and that's a good feature.

What needs improvement in Microsoft Remote Desktop Services is the connection when I'm outside the network. It should be more accessible. For example, if I use a public network, I want to connect remotely more effortlessly, from my internal network, without much requirement.

I want to connect easily from an external network even when I'm not in my enterprise or company. It should be easy to connect or integrate Microsoft Teams, for example, with Microsoft Remote Desktop Services.

I've used Microsoft Remote Desktop Services twice, and if it's an emergency, I can use it immediately. From time to time, I use the solution.

I found Microsoft Remote Desktop Services stable.

For me, Microsoft Remote Desktop Services doesn't require scaling compared to other services. It works fine, so you won't need to scale it.

I have yet to contact Microsoft Remote Desktop Services technical support.

I found it easy to set up Microsoft Remote Desktop Services. It takes a few seconds to enable your options on your computer, particularly for on-premise deployment. However, it takes about two minutes to deploy if you'd like to deploy the solution for a managed server in the cloud.

I deployed Microsoft Remote Desktop Services with the help of a consultant because when I was trying to deploy on the cloud, there was a pop-up telling me to wait ten minutes to complete the setup. Then I could get assistance if I had a question, which I did.

I recall that you don't need to pay for Microsoft Remote Desktop Services because that's included in Windows.

The version of Microsoft Remote Desktop Services that I use depends on the environment I'm in. For example, if it's Windows 10, I'll have a different version than Windows Server 2022 or Windows 11. It depends on the system version I want to run the solution on.

Most of the time, the deployment model for Microsoft Remote Desktop Services is on-premises. Still, you can also do a hybrid deployment if you want to connect to a server in another region.

The IT team uses Microsoft Remote Desktop Services.

I recommend the service to others.

My rating for Microsoft Remote Desktop Services is eight out of ten.

The most valuable aspect is it is handy. We just start up the servers, and we can call the remote desktop, and it's connected. And that's it.

The product is stable.

It is easy to set up.

The solution is highly scalable. 

The performance depends on connectivity. The refreshing screen rate is based on the internet and the bandwidth. It can therefore be unstable. 

It would be nice if they had a portable version. This would make it much better. Sometimes we cannot install it on some machines. We just want to use it once and don't need to actually install it anyway, yet we can't. 

I've been using the solution for 20 years. 

The stability depends on the connectivity. If there is terrible connectivity, it will be unstable. In general, if the connectivity is there, I would rate it four out of five in terms of stability.

The scalability has been very good. 

We have about 20 licensed users on the solution right now. 

I've never called technical support. I can't speak to how helpful or responsive they are. 

I'm familiar with TeamViewer and Desktop Anywhere. They are good, however, we are concerned they have issues surrounding security. That's why we prefer this product.

The initial setup is simple. It's not a complex process. 

The solution comes in a bundle, which offers a cost-savings to customers. 

I'm not sure of the exact price. I don't deal with that directly.

I'm just an end-user.

It's on-prem and we have a server or a cluster to form a group of servers to provide. We are our access from other countries as we have some colleagues working in Britain.

I'd rate the solution eight out of ten. 

The solution is primarily for remote desktop services. It's used to start up a desktop service, and we can use a password and a user name to work remotely on other servers.

The product is very easy to use. 

The solution's implementation process is simple. 

It's pretty stable. 

It can scale well.

I can't think of an area that is lacking currently.

We had some instability during the implementation process. This has since been resolved. 

We've used the product for two years now. It was implemented at the beginning of COVID.

The stability is okay in most cases. Sometimes, especially in the beginning, we had some problems. However, that was due to the implementation of this solution. At this moment it's very stable. There are no bugs or glitches. It doesn't crash or freeze. 

The scalability, as far as I know, is not an issue. We moved all employees to this solution. We started with a few, and now almost a thousand colleagues are using this solution. Therefore, for us, in our experience, the solution looks very good if you need to scale.

I've never been in contact with Microsoft technical support. 

Before this solution, we used Citrix.

The solution has a straightforward setup. It's not very complex at all. 

Its deployment took a few weeks. 

The organization, during the start of COVID, had a lot of colleagues started working from home, and it seemed that the Citrix solution was not capable of doing that, so the ICT offices switched to Remote Desktop Services to accommodate people working from home. Our strategy was to have that capability.

The deployment and maintenance are handled by a third party. They aren't necessarily dedicated, however, they are they if something needs to be done. 

We had a third-party integrator that assisted with the implementation. 

I haven't witnessed an ROI. 

We use the solution. We're customers.

We're using the latest version of the solution. 

We use Microsoft Authenticator to log on, which is straightforward. 

I would recommend the solution to others. I suggest they just go for it. It's a very good solution. 

I'd rate the solution eight out of ten.

• Resilience: Has alllowed our 24/7 acute hospital to run electronic prescribing on the wards with limited downtime or post-setup configuration.
• Thin provisioning: Our core applications mean that our WiFi connected devices can drop-off the network without causing patient record locks.

It has enabled our clinical staff to get real-time medicine prescribing information at the patients' bedside with a near 100% service uptime.

I think that the Single Sign-On (SSO) could be improved.

At release time, there was not a lot of information around. We invested some long hours researching. The documentation from Microsoft was difficult to find. Now there are plenty of step-by-step guides around.

I have used it for four years.

Initially, the configuration I setup used DNS round-robin. This was changed to a NLB setup on our session hosts.

This has improved the stability of the clients' Remote Desktop Protocol (RDP) connectivity. It has given us granular control over stopping connections for downtime/maintenance windows.

We did not encounter any scalability issues.

We actioned this with a limited budget. We completed it all in-house with no external technical support other than searching on the internet and testing.

We run Citrix alongside this solution for our internet connected clients. Microsoft Remote Desktop Services (RDS) was used primarily over our LAN/WAN.

The initial setup was a little complex. Like any thin client setup, some applications are trickier than others.

I could not see the benefits of using Citrix as you require RDS CALs regardless. We see this solution as a very good value.

We evaluated Citrix.

• We have found this to be very stable with a quite straightforward setup. However, Single Sign-On (SSO) certificates are a little fiddly.
• Ensure that the underlying infrastructure is fully tested, robust, and scalable.
• Our early problems stemmed from our hypervisor issues. Because clients only heard it was the RDS farm, I took a lot of heat on issues that were out of my control.

We use the solution for support and remote access to servers.

We use Microsoft Remote Desktop Services for its convenience and remote access capabilities.

Using our Active Directory policies, we can connect again and then do remote printing and file copying. We use it on our SAP system.

The solution is unsuitable for direct external internet connections. You must set up a VPN and password handling to use it.

I have been using Microsoft Remote Desktop Services for 10 years.

The product is stable.

I rate the solution’s stability a seven or eight out of ten.

One or two people are using this solution.

The initial setup is simple.

We don't need to buy licenses because we are a Microsoft partner.

We use cloud remote support because we need to assist our customers. It allows them to connect from the web. It's designed to be faster but unsuitable for direct external internet connections. You must set up a VPN and password handling to effectively use it. We primarily work behind the firewall.

Integration is straightforward because it integrates well with Windows Server.

Overall, I rate the solution an eight out of ten.

We use the solution as a remote desktop. It allows us to access Windows services.

The solution offers good access to desktops remotely. It makes work easier. 

The user interface is fine. 

It offers reasonable pricing. Microsoft is very reasonable in its approach to cost.

The solution is stable.

It can scale well.

The initial setup is simple. 

It offers good centralized security features. 

The solution offers many updates. Every week we get updates.

It offers very good functionality.

The solution is not missing any features. 

It could offer better security for enterprises. They are not always on top of security.

I've been using the solution for one year.

The solution is stable If the network k is very stable, you won't have issues. I'd rate the stability eight out of ten. We haven't had any issues. 

The solution is scalable. It extends well. I'd rate it ten out of ten.

We have about five network and system administrators on the solution. If we increase resources, we may increase usage. It's very easy to increase users as necessary.

We have never used Microsoft technical support. 

The initial setup is very straightforward. 

The deployment only takes ten minutes. 

We simply need the remote server parameters in order to make the connection and finalize the setup.

We only need one technical person to deploy and maintain the product. A system admin could easily manage it. 

As long as I have the remote server parameters, I can handle the setup myself. 

We do have to pay a licensing fee. The pricing is not too expensive. It's very reasonable. 

I'd rate the solution eight out of ten. I'd recommend the solution. Microsoft of very reliable, and its remote desktop is great. However, there needs to be more security.

Microsoft Remote Desktop Services could improve by having graphical acceleration.

I have been using Microsoft Remote Desktop Services for approximately two years.

Microsoft Remote Desktop Services is stable and reliable.

The scalability of Microsoft Remote Desktop Services is good.

I have not needed to call the support from Microsoft Remote Desktop Services because the solution is easy to use.

I have previously used other solutions, such as Citrix and VMware. Citrix is the best choice of the ones I have tried.

The initial setup of Microsoft Remote Desktop Services is very easy.

The price of Microsoft Remote Desktop Services is reasonable.

I rate Microsoft Remote Desktop Services an eight out of ten.