Microsoft Remote Desktop Services Reviews

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.

We primarily use the solution as a remote desktop.

The solution's capabilities are great. I like the remote capabilities.

It has a lot of features. We have everything we would need in a remote desktop.

The solution is stable.

It is scalable.  

Technical support is helpful.

The solution offers good value for money.

For Microsoft, maybe bandwidth optimization is one of the areas that need improvement. They also need better support for video applications, like Teams.

I've been using the solution from the beginning. 

The stability is fine. If we have the right bandwidth, I would rate it nine or ten out of ten in terms of reliability. There are no bugs or glitches. It doesn't crash or freeze.

If you have enough bandwidth, yes, it's scalable. However, if the bandwidth is limited, there is a problem. There should be better optimization for bandwidth utilization.

About 50% to 60% of the company uses the solution. 

I've occasionally reached out to technical support. They are helpful and responsive. 

Positive

We used Splashtop solutions, not TeamViewer, and this is also quite a good solution and offers good quality. However, Microsoft's solution offers better support and a more convenient way to optimize support from one administrator to many users. Microsoft's processes are much smoother.

The initial setup's level of difficulty depends. For the administrator, it is simple. For the VDI solutions, it's quite complex.

While the solution is more expensive, it is worth the cost. I'd rate the value you get out of the solution a four or five out of five. 

Usually, at the moment, in Poland, the customers are implementing a hybrid solution. We are looking at this approach as well for our customers. The solution can be implemented on-premise and in the cloud. Certainly, most vendors try to position it as a cloud solution. However, sometimes it's quite challenging to convince the customer that the cloud isn't possible. That's why we are looking at vendors who offer broader implementation options.

We are an end-user and also a Microsoft partner. 

We have the solution on-premise; however, for the VDI solution, which is not a technical remote desktop. We can see the Remote Desktop for administrators or for end users. For the administrator, it certainly is on-premise; for the end user, the VDI solutions, in Poland, we have on-premise and also pure cloud solutions.

I'd rate the solution nine out of ten. I'd recommend the product 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. 

We use it to connect to the legacy system.

It is still in the early stages, and the features are purely for connectivity.

There is a limitation on the number of concurrent users. The limitation is 20, and you have to spin up more than one server, which is not needed at this stage because of customers. So they reduced it to 12 active users. So if you want to deploy more than 12, you should assess other solutions.

We have been using this solution for three months, and it is the latest version. It is deployed on cloud.

We had issues with stability in the beginning, but it is good now. The stability depends on connectivity in terms of the latency of the internet link.

We have not tried to scale it. We have 40 users using this solution.

I rate the technical support a six out of ten. It took them a while to understand the technology.

We chose this solution because it's a Microsoft Cloud and end-to-end all solution, Cloud 365. In addition, it's all Microsoft, so it made sense to stay with the same VDI solution.

The initial setup was straightforward. The deployment was done with BCX, and it took one week.

The licensing came with the product, and the solution had no additional costs.

I rate this solution an eight out of ten. Regarding advice, it depends on the requirements and what you need. In this case, it's just for one legacy system. So if you assess more functionality and scalability, we would look at different products because the customers would be prepared to pay for those products.

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.

We use the solution for support and remote access to servers.

We use Microsoft Remote Desktop Services for its convenience and remote access capabilities.

Using our Active Directory policies, we can connect again and then do remote printing and file copying. We use it on our SAP system.

The solution is unsuitable for direct external internet connections. You must set up a VPN and password handling to use it.

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

The product is stable.

I rate the solution’s stability a seven or eight out of ten.

One or two people are using this solution.

The initial setup is simple.

We don't need to buy licenses because we are a Microsoft partner.

We use cloud remote support because we need to assist our customers. It allows them to connect from the web. It's designed to be faster but unsuitable for direct external internet connections. You must set up a VPN and password handling to effectively use it. We primarily work behind the firewall.

Integration is straightforward because it integrates well with Windows Server.

Overall, I rate the solution an eight 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 the solution as a remote desktop. It allows us to access Windows services.

The solution offers good access to desktops remotely. It makes work easier. 

The user interface is fine. 

It offers reasonable pricing. Microsoft is very reasonable in its approach to cost.

The solution is stable.

It can scale well.

The initial setup is simple. 

It offers good centralized security features. 

The solution offers many updates. Every week we get updates.

It offers very good functionality.

The solution is not missing any features. 

It could offer better security for enterprises. They are not always on top of security.

I've been using the solution for one year.

The solution is stable If the network k is very stable, you won't have issues. I'd rate the stability eight out of ten. We haven't had any issues. 

The solution is scalable. It extends well. I'd rate it ten out of ten.

We have about five network and system administrators on the solution. If we increase resources, we may increase usage. It's very easy to increase users as necessary.

We have never used Microsoft technical support. 

The initial setup is very straightforward. 

The deployment only takes ten minutes. 

We simply need the remote server parameters in order to make the connection and finalize the setup.

We only need one technical person to deploy and maintain the product. A system admin could easily manage it. 

As long as I have the remote server parameters, I can handle the setup myself. 

We do have to pay a licensing fee. The pricing is not too expensive. It's very reasonable. 

I'd rate the solution eight out of ten. I'd recommend the solution. Microsoft of very reliable, and its remote desktop is great. However, there needs to be more security.