Microsoft Remote Desktop Services Reviews

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. 

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 current role is as an Assistant General Manager in Point Application Services. I am a global administrator for Microsoft 365. We chose this solution based on the requirements we had.

We are using Azure Virtual Desktop, this is the most valuable feature.

The product can be improved by ensuring that people can access it from anywhere and be leveraged on any kind of device virtually. We are leveraging it on some laptops and PCs, but not on mobile devices. I would like to see Virtual Desktop leverage these devices in the future.

Furthermore, I would like to be able to leverage it on other operating systems. Currently, we only leverage it on Microsoft Windows. By being able to access other technologies, companies and users can use multiple technologies.

I have been using Microsoft Remote Desktop Services for less than 3 months.

The solution is stable. We are not leveraging all the applications on Azure Virtual Desktop yet. 

We are able to scale up with Microsoft Remote Desktop. 

The support we receive from Microsoft is great.

Positive

Prior to using Microsoft Remote Desktop, we were using Citrix VDI. We are still using both solutions with different perspectives because on is leveraging on-premise and the other on the cloud.

The initial setup of Microsoft Remote Desktop Services is straightforward. By using Microsoft, you have access to the Wizard, which is helpful.

We used the Microsoft team to deploy the solution.

I am not responsible for licensing and pricing. I am aware that for Azure we do have an extra license because we are leveraging on different tenants. The first tenant is only leveraging on Microsoft 365.

The solution is easy to deploy and there are many features available that you can turn on or off depending on your budget.

I would rate this solution a 10 out of 10.

The users connect to a central server and share the physical or visual server resources. They use the remote desktop environment for office documents, operations, and company-specific programs.

The solution works perfectly. The tool shares computer resources perfectly. It provides the necessary security options.

When we update the environment, we face problems sometimes, and the users cannot use the system.

I have been using the solution for about 10 years.

The tool is stable. Sometimes, the updates break the system.

The tool is very scalable. We can add and delete objects from the environment easily. We have approximately 500 users.

The setup is straightforward. It is easy to deploy. Microsoft provides the necessary documentation, including detailed steps to install and configure the servers. The deployment process can be improved. It can be made more easier.

The tool must be cheaper. It should provide an option to pay the license fee once in a year or once in two years.

We don't use any support because we can easily find online documents to solve our issues. I recommend that everybody use the product. If any company wants to share one computer’s resources with many users, they can choose Microsoft Remote Desktop Services. Overall, I rate the product an eight 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 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.

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.

We have many customers that are using Microsoft Remote Desktop Services for publishing internal applications through the services. The process involves virtualizing applications for internal and external users and making them accessible through Microsoft Remote Desktop Services and reverse proxy services. By doing so, users can indirectly access the applications without logging into the server directly. The solution is used mostly for external company users.

Microsoft Remote Desktop Services has helped the security posture of the organization by not exposing its internal applications. instead of giving internal direct access to their internal apps. They give access to only a secondary server with limited access to internal applications.

The most valuable feature of Microsoft Remote Desktop Services is its security and simple configuration.

The solution can improve the policies of the solution.

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

The stability of Microsoft Remote Desktop Services is good.

Microsoft Remote Desktop Services is scalable, we are able to have more licenses or increase the load if needed.

The solution is straightforward and we have not had any problems needing to contact support.

I have not used a similar solution to Microsoft Remote Desktop Services.

The initial setup of Microsoft Remote Desktop Services is simple. It only takes a few clicks of the mouse to complete.

The price of Microsoft Remote Desktop Services is reasonable. The solution can come for free for some clients with certain agreements.

For customers who already have the Microsoft EA framework, the license for enhancing internal security when publishing web and internal applications to both internal and external users is readily available. By using this feature, customers can ensure that their applications remain secure without compromising access to their users. This eliminates the need for direct access, thereby enhancing the overall security of their systems.

I would recommend this solution to others.

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

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.