Microsoft Remote Desktop Services Reviews

We use it for file repositories, project sharing with Teams, and most of our business intelligence work. We manage around 30 to 40 projects using these resources, mainly on SharePoint.

We use SharePoint here since we're a public university. We have access to all Microsoft platforms. Also, we use Google for email, but they're restricting access for public universities, so we're mostly migrating to Microsoft.

It works well and supports remote work. People can work from home and easily share information. The platform is robust enough for our needs.

We have research projects where students can connect to computers and remotely monitor long experiments, such as charging and recharging cycles of batteries. They don't need to be physically in the lab, which is a good benefit.

It integrates well with existing security and compliance measures

Teams component can be a bit cumbersome to use. It takes some time to get it working as expected, but it's fine once you get used to it.

It is used daily in my university. 

It's scalable enough for our needs and very reliable.

Customer service and support were available whenever we needed them. It was always there. We didn't had any issue. 

Positive

The initial setup is easy. It was easy to set up. 

I would recommend it. The core features are very effective, especially for running an organization with geographically distributed people.

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

We have a lot of Microsoft services configured for different applications. We use the solution to access them.

Since the tool has a graphical user interface, it's easier for us to access the server. It's easier to connect to someone and explain it to them. It is easy to share and explain the features of the solution.

We face frequent disconnections.

I have been using the solution for the past 4 years.

The product is stable enough. I rate the stability an 8 out of 10.

We are quite a large organization with 14,000 employees. Almost everyone uses the product on a daily basis.

The support team takes a long time to get back to us. The team takes almost 2 days to respond to us. The wait time is longer than that of Azure and AWS’s support teams.

The tool is the only way for us to connect to the servers. I will recommend the tool to others. If an organization has a Microsoft ecosystem, Microsoft Remote Desktop Services is the only out-of-the-box solution available. Installing anything else would be a hassle. Overall, I rate the solution an 8 out of 10.

We use the solution for accessing services in our infrastructure, and also, since it's a remote service solution, the desktop infrastructure.

I use the solution as a necessity in order to connect to some servers or to some desktop infrastructure.

The availability is very good. 

It's easy to use. New users especially find it very simple. You just connect and go.

The solution is stable and reliable.   

You can combine the Remote Desktop Services with Citrix in some form, however, not with all of the features of both. It depends on the situation.

We'd like to see more integration with other vendors. 

The solution could offer better, easier scalability. 

Technical support response times could be better. 

We've been using the solution for more than ten years. 

The solution is stable and the performance is good. It's reliable. I haven't had issues with it. There are no bugs or glitches. 

Scalability maybe should be improved. I'm not sure, with the latest version, how scalable it is. We had issues a few years ago and I worked closely with the guys that implemented them. I know that there were better products in the market on the side of scalability. It could scale a lot easier or faster.

Right now, we have about 100 people on-premises using the solution. We are a small firm. 

I don't have much experience with Microsoft services or support.

As far as I've seen, they are there. However, they are kind of slow. That said, it's not something we can generalize and say, "Well, this is Microsoft." In our experience, they are okay. 

Neutral

We use Vendor Desktop Infrastructure. We still use Citrix and we used VMware Horizon as well. 

I wasn't a part of the initial setup and, therefore, can't speak to the process. 

That said, I do not recall the team having any major issues. 

We have a team of two engineers that can handle deployment and maintenance tasks. It's good to have a few people available in case someone goes on holidays or has a day off, et cetera. 

Our team handled the implementation in-house. 

I'm not aware of the exact costs of licensing. You might have to budget a bit for maintenance, however, it's very minimal. 

We test a lot of solutions as we use a lot of different products with clients. We must remain sharp, so we spend some time looking into many options to see what would work best for each customer. 

If it's something new appears in the market, we will install it in order to see if it's okay to recommend to our customers.

We are a Microsft partner. Microsoft product is used in over 90% of the corporate environment here.

This solution is a technology implemented in our company. My position is in the IT department; I also sometimes help troubleshoot.

We tend to use the latest version. We are using both cloud and on-premises deployments.

I'd rate the solution eight out of ten. 

We primarily use the solution for security purposes. For example, blocking copy-paste.

The solution works well as a remote desktop. 

The security is good. It can block copy-paste attempts. 

It's a straightforward product.

The user interface is good. It's just a plain Windows interface. It's easy to understand. 

It is very easy to set up.

There isn't any feature missing.

I don't like Windows too much. The whole idea of the remote desktop is nonsense in the Unix world.

The pricing could be better.

I've been using the solution for 20 years. I've used it for two decades or so. It's been used by me for a long time. 

While the solution is stable, it is sometimes slow. I'd rate the stability at eight out of ten. It is mostly reliable.

Windows isn't really scalable. I'd rate it six out of ten in terms of scalability.

We use the solution enterprise-wide. We likely have 100 people using it. We do not have plans to increase usage.

I've never used technical support in the past.

I have used Citrix in the past as well. I used it for different use cases. We like Microsoft for its small-scale simplicity. It is not VDI, per se. It's just a remote desktop.

The initial setup is very simple and straightforward. The product is very simple. 

Its deployment only takes a half-day. The software makes everything very easy. you just buy the license and install it. I'm not very technical and therefore don't know all of the steps. 

One person who is knowledgeable can handle the initial setup. Typically, it doesn't require anyone with high skill levels. 

We can handle the setup ourselves. 

The ROI isn't the best as it is a pretty expensive product. 

You do need to pay for a license and it is expensive. We have a perpetual license. The more users you have the more expensive it can be.

We are using the latest version of the solution. We are using the solution that comes with the Windows Server between 2019 and 2022.

I'd recommend the solution to others. 

I would rate the solution eight out of ten.

I primarily use the solution as a remote desktop. I'm using it over a VPN and SSH too.

I like how it shows the user how you can do things as a help desk service. 

It's part of the Microsoft Operating system and is free. If comes with the larger Microsoft licensing.

It's so insecure, and it's so limited. It became more limited since we cannot use the administration tools. Nothing is really working at this moment. I'm using it over a VPN and SSH too.

I've tried Microsoft's user assistance, and it's limited. 

The administrative functionality is not enough for me. I don't want the user to see what I am doing. I don't want to reveal any authorization keys or passwords. I want to be in the background, managing the desktop and using the Remote Desktop Viewer while handling best practices.

I'd like a chat function so we can talk right there in the app. It would be better than picking up the phone and guiding the users.

I'd like stronger security. 

I'd like to lock the session and take over a session so the user can just watch what I am doing and not interfere.

While the setup looks simple, in the end, it is pretty complex. 

A big upgrade would be if they stepped back from the TCP RDP port they are using and design it after an SSH tunneling and use that port since a tunnel is between two devices, and it is a very secure way to connect. The added benefit is you would also have the possibility to share local and remote resources. 

I've used the solution for a long time. I've used the product for more than seven years. I've likely used it since Windows 7.

The stability is okay, depending on the internet connection. I'd rate it seven out of ten for its general level of stability. 

Basic remote services are not very scalable. I'm trying to use InTune instead, which seems to have more of the functionality I need. 

Right now, usage is limited, and we only have ten people on the solution. It's used mainly by people who are not always in the same location. 

User support is limited. They lack documentation. However, there is a learning center at Microsoft.com, which is pretty good. 

Positive

I've used Log Meln previously. It's a lot better, yet it is quite expensive. There's also TeamViewer, which is well known, and we've used it before. Once again, with the things I do, it is expensive. As a company, you need to pay a big fee. It's not ideal for small teams. 

The solution starts off simple in terms of deployment. However, it gets complex. You have to open locked ports, and that can make your network insecure. 

The pricing is great as it's free in the larger Microsoft system. It's integrated with the operating system. For me, the licensing is a five out of five in terms of useability and affordability.

I'm an end-user. 

The solution is used on-prem with VPN tunneling and SSH. With an Azure AD connection, we can use it on the cloud. 

It's not the best, as the users can always see what you are doing, which is not always ideal. I'd rate it six out of ten.

My company uses Microsoft Remote Desktop Services for our company's accounting software, which doesn't have a cloud solution. In our company, we deployed a server with the help of Microsoft Remote Desktop Services.

The solution's most valuable feature is that it's a technology that we are familiar with in our company. Microsoft Remote Desktop Services has been around since Windows NT 4 domain, making it a very familiar solution. It was easy to find a lot of clients familiar with the idea of Microsoft Remote Desktop Services since it was not a new concept to them. In general, the solution tends to work well. It is an easy-to-use solution.

The biggest reason we don't use the solution for our company's clients is the solution's prices. In our company, we do our own hosting through a hosting partner since this method offers a much cheaper price. Finding entry-level servers that are limited in the IOPS is frustrating. In our company, we feel quite restricted on the speed that we can get out of the entry-level type of service that we use, making it difficult to sell the solution, especially when clients compare the cloud solution to an on-premises solution.

I have been using Microsoft Remote Desktop Services for five to six years. I work at an IT support company that resells, implements, and offers support for Microsoft products.

My company is happy with the stability of the solution.

I think it's a very scalable product. The product's scalability depends on how big our company's clients are, so it is not an area we need to worry about since you can use its gateway server for different servers.

My company works with small and medium-sized businesses using Microsoft Remote Desktop Services.

The solution's technical support doesn't get covered under Office 365.

My experience with other Microsoft support, apart from Office 365, has not been that fantastic since I remember being quite shocked using the solution.

I haven't used support for Microsoft Remote Desktop Services.

The installation of Microsoft Remote Desktop Services was easy.

The installation of Microsoft Remote Desktop Services takes around four hours.

The solution is deployed on the cloud and on-premises.

A single technician is involved with the deployment part of the product in our company.

In our company, we consider Microsoft Remote Desktop Services as more of an added service than something that generates income for us. We do make a little bit of income with the help of the solution, but most of all, it's just a value-added service that the product provides for our company. Our company won't get rich by selling Microsoft Remote Desktop Services.

The solution is expensive. My company pays toward the monthly licensing costs of the solution, though we also have the option to opt for perpetual licensing offered by Microsoft. Microsoft licensing models are quite complex, so we tend to use a monthly subscription-based model in our company.

The additional cost, apart from the solution's licensing cost, is related to the technical support a user wants.

Though not a lot, some maintenance is required for the solution. One person can do the maintenance of the solution.

I would tell those planning to use the solution not to underspec the server, especially with IOPS, while keeping in mind that the amount of RAM can be more than expected. I would say that the need for a VPN, owing to security reasons, is important.

I rate the overall solution a nine out of ten.

I use the tool to switch to my company’s Windows desktop from my personal system.

The product saves time. It is convenient to use. It is a smart solution. The security is good.

The stability must be improved.

I rate the product’s stability a six out of ten.

We have a bunch of users.

The installation is easy. It took five to seven minutes. The solution is cloud-based.

We can do the deployment ourselves. We install an application and connect to the server. We must provide our credentials to connect to the tool.

People who want to use the product must do a bit of research before making a decision. We faced compatibility issues since some users were using different operating systems. So, our organization asked us to use Microsoft Remote Desktop Services. Windows is a very common operating system used all over the world. Overall, I rate the solution a six out of ten.

We use it on the customer side. We use the product as remote desktop services. 

We've been satisfied with the product overall. 

The remote desktop features are great. It allows users to work remotely. We can take a remote session on the server.

It's largely stable.

The solution is easy to implement. 

We'd like more granular security control of the desktop services. Right now, we have a third-party solution that does this. 

We need to control via group policies. We need to be able to implement these policies in a simpler way in order to control users in a more granular way.

I've used the solution since 2010. I've used it for over ten years. 

The solution is mostly stable. I'd rate the stability five out of ten. We are not able to control or protect without group policies. With a better ability to make policies, it will become stable.

I have not attempted to scale the solution. We're using it for on-premises reasons only. All the customers are here. 

We do not contact technical support directly. We simply rely on Google and seek out our own answers if needed.

We have used different solutions in the past. We found it was easier to centralize control and maintain better security with it. 

For the most part, it is easy to implement. However, the management is dependent on group policies. 

How many people you need to deploy the solution depends on the size of the environment required. 

I'm not aware of the exact pricing. I work on the implementation side. 

We had been working as a partner for Microsoft.

I'd rate the solution five out of ten.

Microsoft needs one centralized console to manage all of its components. That would make it better.