Microsoft Remote Desktop Services Reviews

We predominantly use Microsoft Remote Desktop Services to access our server. Our team works remotely and needs to log in to perform tasks such as billing. We had two options: either use our existing internal infrastructure or move to the cloud. However, we also required remote printing services so that team members could print from their local desktops. To achieve this, we implemented terminal printing services, VPN, and remote desktop. The purpose was to enable both on-site and remote team members to perform billing tasks, invoicing, and tracking truck movement.

Microsoft Remote Desktop Services meets all our requirements.

We encounter challenges with portability, especially for users of iOS devices. It becomes particularly difficult for us to manage if both ends have iOS devices, whereas having the same infrastructure with Microsoft Windows environments on both ends works seamlessly. The licensing of iOS presents problems for third-party integration and has room for improvement.

I have been using the solution for eight months.

I give the stability a nine out of ten.

I give the scalability an eight out of ten.

The initial setup is straightforward. We activated the solution smoothly and completed the deployment within a day. Beforehand, the distributor's tech team came to discuss our network and gain an understanding of everything. It took them a day to configure the solution. Although everything went smoothly thereafter, we encountered some initial challenges. Specifically, we faced issues connecting to the local and remote printers, as printing services were not functioning properly. To address this, we worked on it for a day and met our requirements within two to three days. It's worth noting that the solution isn't entirely plug-and-play, and there are challenges that require mitigation.

The implementation was completed in-house with the help of the distributor techs.

The cost is fair.

I give the solution a ten out of ten.

We have around 70 people using the solution within our Accounting, Billing, and Sales departments.

I recommend Microsoft Remote Desktop Services to others.

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. 

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.

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 primarily use the solution for online work.

The initial setup is simple. 

It is scalable.

The solution is stable.

I don't really like the solution in general. It's like Microsoft made me use it. I didn't have a choice per se.

The price is too high.

I can use a VPN and get the same results while using an actual desktop.

I'd like to have more courses or training available. 

I've been using the solution for a few years. I've used it since around 2019. It hasn't been an extremely long amount of time.

The solution is really stable. I'd rate it ten out of ten. I've had no issues with reliability. There are no bugs or glitches and it doesn't crash or freeze. 

The scalability is good. You can basically keep adding licenses as needed when you have new users. We have four or five users at this time.

I've never had to use technical support. I can't speak to how helpful or responsive they would be. 

I have used TeamViewer in the past, however, it's quite different from this product. I used the consumer version, not the enterprise version.

I found the initial setup to be quite simple and straightforward. You only have to add a Remote Desktop license. There's no need to call or involve anyone else. 

The solution comes at a high price. It was not cheap. 

I'm a reseller.

I could recommend the solution to others if they need it and it makes sense for their use case. 

I'd rate the solution six out of ten. It's too much of a cost.

The product helps assess our system.

I like the way it can assess our system. 

The features it has already serves or needs.

The initial setup is very simple. 

It is quite stable. 

The product offers good pricing.

Technical support has been helpful. 

I don't need any other new features. It works well as it is. 

We'd like them to continue to improve on security. 

I've been using the solution for quite some time. It's been around ten years or so.

This is a stable product. There are no bugs or glitches. It doesn't crash or freeze. It is reliable. 

I'd rate the stability seven out of ten. 

Our system is on Windows, and we need to scale very little. As far as we're concerned, it scales enough for us. We have about 20 users on the solution currently.

We use Microsoft 365, and if we have any issues, we contact support that covers that. We've been satisfied overall with the level of support we get. I have no complaints. 

Positive

We are also using TeamViewer. It targets different areas from Remote Desktop. For example, it allows others to access your system - not you. They each serve different purposes. 

The initial setup is great it's very simple and straightforward. I do not find it to be complex at all. 

The pricing is good. I'd rate it five out of five in terms of affordability.

I'm a customer and end-user. 

I seldom use the product; however, for me, it works exactly as I need it to. 

I'd rate the solution eight out of ten.

We use it in our bank.

We have some servers, and more than two users go remotely with them. We prepare with the Microsoft engineer servers that take them and the license for the users when they need them.

It has generally improved how our organization functions.

The solution is now stable.

The initial setup is simple. It's quick to deploy.

It works well and does what we need it to do.

Sometimes the server stops working, and we don’t know why. Occasionally we’ll get a message to the effect of "There is no remote license."

I’ve been using the solution for about one year.

While we had a problem before, now everything is stable. It’s reliable now. We’ve dealt with our issues and no longer have troubles.

I can’t speak to the scalability. I’ve never attempted to scale. That’s handled by someone else in the company.

Right now, we have 50 licenses available to us. We use the solution quite extensively.

I’ve never dealt with technical support for issues related to the stability problem. I can’t speak to how helpful or responsive they would be. Other team members deal with them. We do have a support contract with Microsoft.

I have dealt with them on Teams on Active Directory and found them to be helpful. I found their help to be excellent.

We already had a license with Microsoft, and therefore, it was natural to use this product as well.

It’s not difficult to set up. It’s pretty straightforward.

The deployment is pretty fast. It only takes about an hour and a half. We only needed to have three people handle the deployment and maintenance.

An engineer worked with us to set up the servers. We have machines joining the domain, and we have workgroup machines.

We handled everything in-house. We didn’t need the help of consultants.

I’m not sure if we have seen an ROI.

I cannot speak to how much the solution costs. My understanding is that it is moderately priced in that it is not cheap or expensive. We ended up getting it when we renewed our license. It’s an extra feature with the broader Microsoft license.

I’m not sure which version of the solution we’re using.

I’d recommend the solution to others. It’s solved problems for us and worked well.

I’d rate the solution nine out of ten.

We have a partnership with Microsoft.

We use Remote Desktop Services for a few things. My experience started with Microsoft Remote Desktop when I tried to reuse really low power desktop machines to turn them from these desktop machines into class remote desktop terminals. That is my initial experience with Microsoft Remote Desktop. My most current experience with Microsoft Remote Desktop is using a specific Microsoft product on the servers where you don't have any chance to administer them using the web browser. SCCM, active directory administration and other Wintel server roles are most handy and the most secure to administer from the Microsoft Management Console. Therefore, you need to do it at least from some instance of the Microsoft windows server.

I like that it works. In most cases, it's predictable. You know what you get.

Microsoft still has some really bad remote desktop appliances for Mac. This is really frustrating because if I'm on windows I can remove the Microsoft remote desktop applied for Windows, but I'm already using windows, I always have an option B. I can still plug directly with Microsoft management console from the windows station and still do something remotely. But on a Mac, I have to rely purely on the Microsoft Remote Desktop. 

If I need to pass second-factor authentication, not a one-time password thing, if I do a Microsoft remote desktop session, I have to reach the first server, which is my best one. From that server, you're actually going inside your protective network. Then on the second spot, you are not able to pass a YubiKey and go any farther. That creates the problem. We have had many support tickets.

With this new company, I have been using this solution for two and a half years, but overall I have 15 years of experience.

It is being used mainly on a Mac platform.

I would say it's stable.

In the last setup, we had 3,000 users. It wasn't the nicest experience.

My experience with support is varied. It really depends. It varies depending on which support line you get. If you say you're a particular engineer then they won't really bother to support you. But if you say you have an enterprise contract and that you're a big company and you have a contract then they offer better support.

We previously used Citrix. Microsoft Remote Desktop Services is a more developed version of Citrix.

I would recommend going for VMware.

Microsoft programs are never easy to install but the installation wasn't something we didn't expect.

We deployed it on our own.

We use enterprise orchestration so it doesn't take too long to deploy. Microsoft products do not really play along with the open-source orchestration platforms. Once you overcome this, it becomes easier.

I would not recommend going with this solution because I wouldn't recommend going for a big enterprise setup. 

I would rate it a four out of ten. 

In the next release, they should develop better support for remote desktops for alternative platforms. It's really lacking consistency. If I have to support terminal server clusters and I have to do change management on the big cluster, then I actually run into a lot of issues both on the Microsoft Remote Desktop as well as Citrix. They should provide a consistent user experience. It's a pain to roll out changes into a different mode of the cluster and to propagate them over multiple modes. I end up in a situation where a portion of my users get the changes and the other portion doesn't.