Microsoft Remote Desktop Services Reviews

My main use case for Microsoft Remote Desktop Services is remoting into computers that I don't have physical access to in order to assist or perform configurations, or remoting into our servers to do day-to-day work.

The best features Microsoft Remote Desktop Services offers include easy connection to the devices on the same network and easy connection to the devices over VPN.

The easy connection over VPN in Microsoft Remote Desktop Services helps my team significantly, especially when they are working from home and need to remote connect to our servers. Using remote desktop services and connecting to a VPN allows us to connect without having to use third-party tools.

Microsoft Remote Desktop Services has positively impacted my organization by helping us function efficiently when we're not physically at certain machines.

Microsoft Remote Desktop Services could be improved by providing a way to make it configurable without using VPN from the actual service itself.

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

In my experience, Microsoft Remote Desktop Services is stable.

The scalability of Microsoft Remote Desktop Services for my organization is fine. It is used more so for back-end machines and for very specific support, so as we grow, we still use it the same amount.

I previously used TeamViewer before switching to Microsoft Remote Desktop Services.

My experience with pricing, setup cost, and licensing for Microsoft Remote Desktop Services has been easy. I don't think there was any cost, as this was built into our experience with Windows and Azure.

I have seen a return on investment with Microsoft Remote Desktop Services, as it has sped up a lot of our support.

Microsoft Remote Desktop Services has saved us considerable time because we don't have to be on-site for support and have more accessibility to the machines.

My experience with pricing, setup cost, and licensing for Microsoft Remote Desktop Services has been easy. I don't think there was any cost, as this was built into our experience with Windows and Azure.

I switched from TeamViewer to Microsoft Remote Desktop Services because Microsoft's integrated products are easier to use and support.

My advice to others looking into using Microsoft Remote Desktop Services is that it's an easy piece of software that's integrated with Windows and other services offered by Microsoft, making the cost of entry and support straightforward. I would rate this product an eight out of ten.

In a way, we have some virtual solutions, at least RDS from Microsoft Hyper V. That's what we're using today, but not for everyone. Some people do use it. It's more like remote desktop. It's been a long time, at least since Windows Services 2008 or around 2010. 

Today, most of our users, among three or four companies sharing software like the ERP system, work on individual workstations or laptops. That's really the main use across the companies today, however, it would sometimes make sense to look at remote Desktop or VDI. My impression is that most solutions, especially today, make sense for large corporations with two thousand seats or more. 

So far, we have not used anything besides remote Desktop for, for example, accountants working from various locations or not based in our offices. That's really how we do it today.

The main benefit, is that it's easy for us to get the same desktop and do things in the same way regardless of our location. However, it would sometimes make sense to look at remote Desktop or VDI. My impression is that most of the solutions, especially today, make sense for large corporations with 2000 seats or more. So far, we have not used anything besides remote Desktop.

We would like configuration to be automatic and the price to be close to zero, however, that's not realistic. Everyone wants to join some kind of cloud service today. We have decided to keep our ERP software on our own servers. For users, it should be easier to create a template and duplicate users. We have done it in an old-fashioned way. 

It would be easier to set up, and upgrades should be easier.

The cost we have today is quite low, to be honest. However, if we want to hire a lot of people, it would require quite a lot of work. As long as we have a small number of installations and users, it's manageable.

It would sometimes make sense to look at remote Desktop or VDI. My impression is that most of the solutions, especially today, make sense for large corporations with 2000 seats or more. So far, we have not used anything besides remote Desktop, mainly for accountants or those working from different locations or not based in our offices.

We have not used a different solution for a long time, to be honest. We have used Microsoft. Whenever I looked at competing solutions like Citrix or VMware, the benefit is great if we have many users, however, the cost would be too high for a few users. That's been my conclusion so far. We have not worked with other solutions in this configuration of companies.

When it comes to users, it should be easier to create a template and duplicate users. We have done it in an old-fashioned way. If setting up a new user, it usually takes about two or three hours, not days.

With Citrix or VMware, the benefit is great if we have many users, however, the cost would be too high for a few users. We have not worked with other solutions in this configuration of companies. 

Mostly we are quite happy with it. However, some of us want a more powerful desktop. When not present, we use a remote tool called Splashtop, which is a good solution for some users. We have about ten licenses for those who need a powerful workstation at the office. 

We have not used many different tools. We are never in contact with Microsoft. These are quite basic configurations, to be honest. It's not complicated. AI is coming to or is already in some applications we are using. Not system-wise, however, it might be good. 

I'd rate the solution seven out of ten. It's quite good, yet certainly not perfect. 

My current use case for Microsoft Remote Desktop Services is connecting to services which are specific to a remote location because I am working from India. There are times that I need to connect to those services, so via Microsoft Remote Desktop Services, I access that system because I need to connect to VPN. Some services are specific to a particular location and shouldn't be accessed here, so I connect to that Remote Desktop to use it. It's mainly for support and management activities.

I find the ease of use of Microsoft Remote Desktop Services most valuable, as it allows me to have remote access and connect securely. Another valuable feature is file transfers, as it enables me to move files between local and remote machines efficiently.

The main benefits that Microsoft Remote Desktop Services provide to me include streamlining my working process, ensuring security, and offering flexibility to connect to virtual desktops and apps from multiple devices.

The only problem I see is that when I am connected, there is a certain lag because of the network.

I have been working with Microsoft Remote Desktop Services for five, six years.

For stability, I would rate the product an eight.

I would rate the scalability, or ability to expand, a seven.

Technical support from Microsoft is something I have never used, but I would give them a seven or eight.

Positive

I am not working with products such as Intune, Remote Desktop, or storage solutions such as Azure. Currently, I am using all the Microsoft tools that are available such as Office and Power BI. I have completed some certifications for Azure, but I am not an avid user of Azure. I am not sure if I bought Microsoft Remote Desktop Services on AWS Marketplace or directly from Microsoft because it is provided through my organization. I have experience with virtualization, but I haven't used the session virtualization feature of Microsoft Remote Desktop Services. I do not use the centralized application management function of Microsoft Remote Desktop Services or the centralized dashboard. The solution is cloud-based. I am using multi-factor authentication through Microsoft Remote Desktop Services, and I would rate it a nine. Overall, I rate Microsoft Remote Desktop Services an eight out of ten.

My main use case for Microsoft Remote Desktop Services is to connect to servers from laptops, and sometimes it's even Mac macOS laptops.

For example, in my company, we have MacBook Pro as work computers, and most of our clients have Windows servers, so the best way to connect to the Windows servers is through RDP clients.

The best features Microsoft Remote Desktop Services offers include the fact that it's multi-platform and it's easy to connect from any operating system to a Windows server or a Windows computer.

Microsoft Remote Desktop Services has positively impacted my organization because it's the only way to connect to some servers we have, as we don't have other options; for example, if they were Linux servers, we would just SSH, but on Microsoft, we have to use RDP.

Using Microsoft Remote Desktop Services has helped my team save time and improve productivity because we had Microsoft servers that were impossible to connect from our MacBook Pro laptops, and once we started using RDP, we could connect and move forward to deliver the project.

Microsoft Remote Desktop Services could be improved because we have keyboard compatibility issues with some platforms; on macOS, we sometimes experience keyboard connectivity issues, and it can be problematic when connecting to servers that then need to connect to other servers, as the keyboard layout doesn't match.

I have been using Microsoft Remote Desktop Services for maybe one year.

Microsoft Remote Desktop Services is stable.

I have never personally had to contact customer support.

We previously used native AWS SSM Session Manager, but not all the clients allow it.

I have seen a return on investment from using Microsoft Remote Desktop Services; for example, it has helped in unlocking a locked situation.

By unlocking a locked situation, I mean we couldn't connect to a server in any other way, so we had to use RDP.

My advice to others looking into using Microsoft Remote Desktop Services is to try it and see if it's what you need. I would rate this product an 8 out of 10.

Our main use case for Microsoft Remote Desktop Services is to allow multiple users to remotely access our Windows machine, desktop, or application over the internet and our network.

The best features Microsoft Remote Desktop Services offers include the ability to work remotely or use a virtual desktop, centralized application hosting, and securing access to a machine for internal service and call center or enterprise environments.

We rely mostly on remote work and virtual desktop functionality to access the office environment remotely, along with centralized application hosting to run heavy applications on servers while users access the lightweight Windows machine in a secured way.

Centralizing management and access has helped our team by improving productivity.

Microsoft Remote Desktop Services can be improved in several areas. Currently, it requires a license cost, it has performance limits on shared resources with bottlenecks, the setup is complex, and it is not ideal for graphics-heavy applications.

I have been using Microsoft Remote Desktop Services for about one year.

Microsoft Remote Desktop Services is stable.

The scalability of Microsoft Remote Desktop Services is good.

The customer support for Microsoft Remote Desktop Services is good.

Using Microsoft Remote Desktop Services, we are able to centralize the management of applications and desktops in one place, allowing multiple users to access the same machine. We can also implement gateway and encryption on that and integrate Active Directory.

The experience with pricing, setup cost, and licensing is that the pricing is based on licensing costs and the setup is complex.

What advice I would give to others looking into using Microsoft Remote Desktop Services is to consider its features carefully. I would rate this product an 8.

We use it primarily to provide virtual desktops to our end users, which allow them to access email, word processing, and other essential applications.

I like its familiarity. If you grew up Office environment, we use Outlook and software and everything, it's just familiar. Other than the initial login through the thin client, you don't even realize that you're on the virtual desktop. So it's just familiarity and ease of use.

It allows employees to log on to corporate resources remotely. But, we don't actually use the application publishing feature.

The current process I have to go through to get a Windows 11 VM up and running is difficult. Windows 10 worked a whole lot better than Windows 11.

Probably about five years in its current form.

I would rate it a nine out of ten. 

I've found it to be very scalable as long as took into consideration the number of users. If there is a sudden surge or drop of users, it might not scale as you like. 

If you plan for your expected user base, it is not a problem. I tend to over-engineer my servers, so I've never run into problems like resource limitations. It's been both scalable and reliable for me.

I would rate the scalability an eight out of ten. My current setup is, again, about 10 to 15, but in my past life, I've deployed it for over 150 people.

The quality of the customer service and support depends upon what day of the week it is. They're very up and down with their support. Some days, I get really great support, and some days, it's not so great. So, on a scale of one to ten, I'd put them at a five.

It also depends upon what you're licensed for... I mean, if you're licensed for the top-level tier, which I was at my last job, the support was really great. But at this current job, we're not leveled at that level. So, I kind of know what's out there, and I'm left like the kid looking in the candy store with my nose against the window. And that's all because of budgeting and pricing. And I understand that.

Again, depending on who you get and what day you get them, you get great support. Or sometimes, if you get the summer intern, not so great support.

Neutral

I would rate my experience with the initial setup an eight out of ten, with ten being the easiest. You do have to have knowledge. You have to know how to apply your licenses, allocate your resources, set up your drives, and everything.

We've built around it, so it integrates very well.

Currently, it's just me, but in my past life, I had a team.

In my particular environment, dealing with classified networks, my biggest return on investment is being able to create a single image and deploy it multiple times rapidly. 

When the updates come in, I only have to deploy them once instead of having to walk around to each machine because we're using them as virtual desktops. To me, that's really valuable because if I had to walk around to everybody's machine to apply a patch, that would be extremely inefficient.

I've never had an issue with it. I've always thought the pricing for RDS was reasonable.

I would recommend it, but depending on the scale of your operation and what you have.

So, like, if you're a small shop, one to two administrators, maybe ten to fifteen users, I would absolutely recommend it. If you start getting outside of that, you might want to start looking at other things because there's just some... well, actually, with the new PowerShell tools and everything, you could probably support up to more than that. But, again, it depends upon your needs and what your environment is going to be. 

If you're going to be supporting thousands of people, I don't think I'd recommend it. But if you're just up to a hundred, I would recommend it.

Overall, I would rate it 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.

It's helped with cutting costs and making access easier. People can work remotely using this product. For remote billing, it's working well. 

The ability to access the computer from a remote location is great. With the Windows Server as a client, we can use more than one computer at a time.

The initial setup is simple. 

It's a stable solution.

You can scale the product.

We've had issues with security breaches. The main problem is that if we are using this with the individual computer and using a remote desktop, there are some loopholes there. When I implemented this on an individual computer within two or three days it got captured.

There is a problem with the printing and sharing of this program. There is a lot of customized software leaving the market due to this. If somebody wants to run a specific program with the specific settings, they don't want full access to the computer. Then there are some problems that have to be resolved.

We'd like to have an additional control panel available in order o more easily give resources to the computers. There are a lot of restrictions and having a program panel would make things easier. It would help us set up the right access and permissions.  

We've been using the solution for 20 years. It's been a long time. 

The solution is stable. If it is configured properly, then it'll not create any problems in between. There are no bugs or glitches. It doesn't crash or freeze. 

The scalability depends on the server size. It does not scale on a personal computer, however. 

The solution can be configured in such a way that you are able to maintain it yourself. We've never had to reach out to technical support for assistance. 

For printer redirection, we are using third-party software.

We've used Citrix and VMware in the past.

The implementation is very straightforward. If there are some problems or if clients have installation issues, that can be solved by the technician and it's very easy.

I'd rate the implementation a three out of five in terms of the ease of the process. 

It does not take too much time due to the remote desktop. You just have to do some settings on the server or computer. We only need about three people to handle deployment tasks. 

I'm a consultant and an integrator. I never call up a third party to help with implementation. 

The solution is not too expensive. It's moderately priced. I'd rate it a three out of five in terms of affordability. 

We are using this and Windows Server and Windows 10 or Windows 9, whatever is available.

Normally this is a private cloud, however, right now, a lot of our customers are on AWS and they're using it from the cloud, also.

I'd advise new users to first gather good knowledge and do some planning before the implementation. 

I'd rate the solution six out of ten.