Microsoft Remote Desktop Services Reviews

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.

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.

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 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. 

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.

The first use case was related to the development and testing environment. Before COVID, it was also for remote connections for work from home, to have access to a protected environment.

The solution has improved a lot.

It's simple to set up. 

It is stable. 

The solution can scale according to the hardware available. 

The solution isn't as good as the Citrix option.

I used the solution for ten years. 

It's a stable, reliable product. There are no bugs or glitches and it doesn't crash or freeze. 

There are some limitations in terms of the the ability to expand. It's scalable according to the hardware limitation or the virtual environment limitation.

I've also used Citrix. I prefer Citrix to Remote Desktop connections. The management and flow are better.

Hyper-V is also challenging Citrix. However, Citrix has a strong reputation still.

The initial setup was not complex at all. It was very straightforward. 

The connection for the client is embedded in the system. You just need to configure the servers and credentials. 

We did not calculate an ROI, however, it does offer more features than we needed and therefore offers great value for money. 

I'm not sure about the licensing. The licensing policies are changing in the Microsoft environment, so I'm not sure how it's licensed at this time. 

My understanding is that it is expensive. Even if we negotiate, it depends on the business you have and the volumes you run an issue for.

With the rules changing, the licensing can be complex. 

I was a reseller and partner. 

I'm not sure which version of the solution I used. 

We started using the solution on-premises and then deployed it to the Azure cloud. 

I'd rate the solution eight out of ten. It's simple to deploy. Users just need to negotiate a price and handle tasks around their server license. 

We primarily use the solution for remote desktop services. It can be used locally or on the cloud. It's on every single Windows machine. 

If you need a remote desktop for Windows 10, or Windows 2016, you use RDP, which is Remote Desktop Services.

The solution is great for remote into machines. 

It works fine, and it is largely issue-free.

The product is stable. 

If you are deploying it, as a VDI solution, then it is very limited.

The product is not very scalable. 

I've used the solution for 15 years.

It's quite stable and reliable. There are no bugs or glitches, and it doesn't crash or freeze. 

The solution scales minimally. It's not meant for scaling. 

Everyone uses the product to some extent. We do not have plans to decrease usage at this time. 

I try not to contact technical support.

Neutral

We were using Citrix, which I found to be much better.

The solution comes with the Windows Server. You simply enable the feature and begin using it. 

The solution is bundled within Microsoft products. 

I wouldn't necessarily recommend the solution to others unless they had no other choices.

I'd rate the solution five out of ten.