Microsoft Remote Desktop Services Reviews

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. 

I'm a technical manager and we are customers of Microsoft.

The solution has very smooth connectivity and is a very user friendly product. An additional advantage is that it works with very low bandwidth. 

We've had a few occasions when the application has crashed suddenly, possibly due to updates. Microsoft updates should not directly impact the application and rather than releasing post hotfixes, it would be better to carry out testing before releasing it to the environment. It's a challenge for us; the new application is upgraded, but there's an incompatibility. It should be the other way around - testing in the lab environment and then commercially released.

An additional feature we'd like to see would be cross-platform support. With more OSs in the market whether Microsoft, iMac or Android applications, it would be good to have a smooth transition between cross-platform support both in terms of operating system and in terms of devices. Moving from tabs to mobiles to desktops to laptops to notebooks - the transition between multiple OSs and multiple hardwares.

I've been using this solution for the last five years. 

The solution is stable. 

The product is scalable, we have over 500 users. 

The quality of the technical support is quite good although it's often dependent on the quality of the Microsoft partner. If the partner is good, then support is good but if not, there can be issues. 

The pricing in comparison to similar products is quite good.

I would suggest a UAT test on a smaller group or pilot deployment. Once you do a test run on the pilot deployment, then it should be rolled out for a larger base of users.

In terms of overall experience, I rate the solution eight out of 10. 

My main use case for Microsoft Remote Desktop Services is to connect to remote servers in the cloud that I use in my back-end application.

The best features Microsoft Remote Desktop Services offers is that it's easy to use.

Both the interface and the setup process make it feel easy to use for me.

Microsoft Remote Desktop Services positively impacts my organization because it makes the job and work easier for all.

It makes the work easier for everyone because it's easy to use and we can save time when connecting to our back-end servers.

Microsoft Remote Desktop Services are adequate for now and can be improved.

I have been using Microsoft Remote Desktop Services for about 15 years.

My advice to others looking into using Microsoft Remote Desktop Services is to use it because it's a good tool. I would rate this product a 10.

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. 

If any of our clients using the internet are facing an issue, we connect Microsoft Remote Desktop Services and troubleshoot the exact issue.

Things can be made easier if someone is not with us or at a long distance since we can connect easily with those people. So, it's easy for us to use such features.

There have been some network issues in the solution. So, when we used to connect it, the solution suddenly got disconnected. So the network part needs to be improved. Also, for a long duration, if we share Microsoft Remote Desktop Services, then network issues come up, so I suggest improvements in the aforementioned areas. Also, the pricing could be better.

I have been using Microsoft Remote Desktop Services for one or two months. Also, I am using the solution's latest version.

The network issue is something that causes us to invest longer time duration in connecting, after which it gets disconnected. Hence, I rate the solution's stability nine and a half out of ten.

It is a scalable solution. Scalability-wise, I rate the solution a ten out of ten. Around five to ten of our clients are users using the solution. Also, the solution is being used extensively.

I do have plans to increase the usage of the solution. The number of users is increasing. In the last month, we have had two or three potential clients in the pipeline. In the near future, its usage will increase.

I have never contacted technical support.

The solution's initial setup process was straightforward. The deployment process took around a week.

Deployment steps are followed. For every network deployment, it is necessary to generate a single token. Once this token is generated, payment will be required. Once we obtain the UI connector, it is essential to verify that everything is running smoothly. Only then can it be directly connected, ensuring that the deployment process takes place without any issues.

Regarding the deployment of one server, if done by someone knowledgeable with Microsoft products, then it can be done directly. Else it will take a month since we need time to learn all these things. An engineer looks into a few things.

The implementation can be done in-house.

The solution is expensive. Since things are made to be a bit easier in the solution, the solution's cost is a bit on the higher side.

I will recommend it to others when I think it's quite an easy tool, especially if its implementation is easy. We should also be able to connect and solve our problems through troubleshooting issues remotely. For long-distance purposes, the tool gets quite easier for its users. I will recommend that everyone should use it.

Overall, I rate the solution a ten out of ten.

We use the solution for remote access. I use Microsoft Remote Desktop Services to troubleshoot or reboot the service of my mobile or tablet applications.

The most valuable feature of Microsoft Remote Desktop Services is managing the remote desktop end user or remote server. It is much easier to transfer a file between your desktop and remote site using Microsoft Remote Desktop Services.

The solution should introduce a chat feature for end users.

I have been working with Microsoft Remote Desktop Services for more than ten years.

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

More than 30 people use Microsoft Remote Desktop Services in our company.

The initial setup is straightforward.

The solution has a pretty comparable pricing.

I do recommend Microsoft Remote Desktop Services for my clients. It would be good if we could manage client-server applications through the remote interface.

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

The most valuable features of Microsoft Remote Desktop Services are unification, central management, and accessibility.

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

The stability of Microsoft Remote Desktop Services is scalable if you have reasonably good hardware. Overall the reliability is good.

Microsoft Remote Desktop Services is scalable. You can add nodes, remove nodes, and there is load balancing embedded into the solution too.

We have approximately 30 to 50 users using this solution in my organization.

I am in contact with support from Microsoft Remote Desktop Services approximately twice or three times a year for a particular topic. They typically have been able to resolve our issues, but it is sometimes difficult to be passed over to someone who understands the issue we are facing through the different levels of support.

I rate the support from Microsoft Remote Desktop Services a four out of five.

Positive

We are using a mixture of Remote Desktop Services and Citrix solutions. Citrix is more prevalent based on this solution category.

The initial setup of Microsoft Remote Desktop Services is not the easiest. You need to have a certain understanding of how Microsoft is provisioning the solution to be able to set it up and use it.

I rate the price of Microsoft Remote Desktop Services a three out of five.

I would recommend Microsoft Remote Desktop Services for somebody who needs to have centralized control applications, users, or the setup of applications.

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

Our primary use case is for accessing Visual Basic.

The most valuable features are it is fast and cost-effective. I am not aware of a replacement currently on the market.

I would like to see the hard drives work without locking up and integrate the local drives in the next release.

I have been working with Microsoft Remote Desktop Services for the past couple of months.

There is stability but sometimes it does disconnect.

The initial setup was easy and takes usually one or two days.

We did our implementation in-house.

I think that Microsoft Remote Desktop Services is expensive compared to Login solution.

I have used Citrix and Login solution. 

Microsoft Remote Desktop Services is a good solution and I would rate it an eight on a scale of one to ten.

I use Remote Desktop to do a credential swap where it goes from being the explicit user accessing the endpoint to a privileged credential.

What I do is, in the connection process with RDP, the user logs into the PAM tool as first name.last name, which is his normal domain account. However, BeyondTrust, with the remote desktop connection, substitutes the user's first name.last name with a privileged credential that looks like his name. It would be like A-first.last. This is so that we can also perform session recording and keystroke logging, as well as keep a detailed log of who is connected to which desktop and which account.

The most valuable suite feature for us is that it's light. It's built into the operating system and has a command line interface capability to insert credentials, IDs, a password, et cetera.

If anybody who's going to be using this, I’d warn that some of the dependencies that are very helpful when the window servers are running it would be best if they have network-level access enabled. It can speed up authentication. However, it really it also works well with TLS security as well as others on the certificate level. That said, I really don't know if I would start swinging in the dark after that.

Usually, during a privileged session, you don't want the privileged credential password being visible, nor maybe would you want keystrokes or screen scrapes to take place.

One of our first problems was the only time RDP ever gave me a problem was when an organization would build a new server. They would automatically build it. They would name it. They would put the connection settings on it. And then they would also put a certificate on it. Then the engineering team that ordered the server would then rename the server, which would nullify the certificate. That's the only time that RDP or remote desktop ever gave me a problem. And that was not the remote desktop's problem. It was a process flaw.

The only problems that you're going to have with the remote desktop are going to be firewall ports, security, and NLA, which is a net network level access control, or TLS transfer layer security or some other SSL-type of security. Those are the only times you get into any issues. And that's only due to the fact that the originating site is not compatible with the target site. However, that's rare. That said, even then, that's more on the rare side. I'm a PAM architect, a privileged access management architect. I usually knock down those problems before we get to them since I ran it all a hundred times.

I’ve used the solution for 20 to 25 years.

The solution is rock solid. It’s stable and reliable. There are no bugs or glitches, and it doesn’t crash or freeze.

The sky is the limit in terms of scalability. It’s not a problem at all if you need to expand. The only limiting factor is the budget. Obviously, the more you grow, the more you pay.

Tens of thousands of people use the solution. The primary use is to segregate a user from a direct login to a desktop.

The solution is actually built into the larger product. We pretty much just have to secure the connection.

It's actually maintained as part of the standard windows update tools and also could be updated manually with specific patches that might be something more specific to your organization. I've only experienced that once and that was years ago.

I’m implementing the remote desktop for customers.

It’s built-in. It’s free. It doesn’t cost extra.

We are Microsoft partners.

The deployment is both on-prem and cloud. If I was working with an organization that is a monster and they're distributed or maybe even a multinational or multi-state, I would use Azure Cloud and do use the Azure remote desktop solution.

There are so many different types of uses. In my use case, it is so painfully specific for connection brokering. We use it as part of the built-in connection process with our PAM tool. You can actually just sit down at your desktop and then do a start run, and then run MSTSC, which means micro soft terminal services client, which is a remote desktop. You can connect to one of your own computers at home, or you could connect to a server. However, you have to know the ID and password to connect. I circumvent that by doing a command line connection where I insert the credentials and the users connect, not even knowing what ID or password they're using to connect with.

I’d rate the solution ten out of ten. It’s a meat and potatoes product.

Microsoft Remote Desktop Services is used to connect to other systems.

Microsoft Remote Desktop Services has helped our organization because it provides easier access to desktops without having to be physically on-site.

The most valuable feature of Microsoft Remote Desktop Services is the ability to remote into a system that is not on-premises.

Microsoft Remote Desktop Services could improve by having a better application for managing multiple sessions. There used to be one but they stopped supporting it.

I have used Microsoft Remote Desktop Services within the last 12 months.

The stability of Microsoft Remote Desktop Services is very good.

The scalability could improve by having a multi-session manager.

Our IT department uses Microsoft Remote Desktop Services.

The initial setup of Microsoft Remote Desktop Services is simple, it is not complex.

Microsoft Remote Desktop Services comes free as part of Microsoft Windows.

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