My main use case for Microsoft Remote Desktop Services is when data is highly secure and country sensitive, so it needs to stay within one data center and only individuals who have access to that country-only data can use it. Rather than having the data locally on my laptop, which could be insecure, only specific users have the ability to connect to these servers to view the data, so the data can be seen on my local laptop, but it never actually exists on the laptop. It is just the pixels being transmitted to me. I have used it for security reasons.

To view customer data and validate that it was sent correctly to a server, I have used Microsoft Remote Desktop Services, so rather than the data existing on my laptop, I would connect to that server to then validate the data.

Microsoft Remote Desktop Services offers several best features, including the security aspect because sensitive data stays within the server in the data center. It is only really the UI; the pixels are transmitted to myself and other users, making it brilliant for data residency because the data never exists and is never sent to my laptop. I am just viewing it from connecting to the server within a specific place, which is great for data sovereignty.

It is also advantageous for managing lots of users because I can have one massive, powerful server with loads of different users connecting to the same server to share resources, and from a scalability perspective, the IT team managing the application can keep it up to date and maintain it on one server, which is then transmitted to everyone connecting to it, rather than having the application exist on everyone's machines with all of those needing updates.

From the security perspective of using Microsoft Remote Desktop Services, the fact that the data never exists on my laptop and is always centralized in just one place on that one server is great because it means there is a much lower chance of data being leaked, especially if it needs to stay within the country. It highly reduces the risk of the data being sent accidentally to individuals outside of the country, which could break compliance.

Microsoft Remote Desktop Services has positively impacted my organization by increasing our security.

I have noticed the increase in security from using Microsoft Remote Desktop Services through improved compliance, as we are able to confirm 100 percent that data which needs to stay within the country does so because it only exists on the server. Then we connect to the server to view the data, but it never leaves the server, allowing us to hit 100 percent compliance very easily without worrying if someone can accidentally send the data somewhere else.

From the compliance perspective, Microsoft Remote Desktop Services has provided a massive compliance benefit, as we are able to ascertain 100 percent that data stays within the country because it stays on the server.

I understand from the IT team managing Microsoft Remote Desktop Services that it is complex to set up the multiple roles, certificates, and networks required. Networking is quite complicated. Even though on the data center side it is quite simple, maintaining the farm of other connections that connect to that server is the complex piece. I understand there are more modern systems replicating what this solution does, which are easier to use, such as Azure Virtual Desktop within Microsoft Azure Cloud or Amazon WorkSpaces, which I have used before. Rather than having to manage all the complex networking, you could abstract it away a little further in the cloud for easier use. I also understand that this tool is in an end-of-life state now, with Microsoft actively pushing people towards Azure Virtual Desktop or Windows 365.

I do not believe further features will be rolled out due to its end-of-life state, making it a legacy solution now.

I have used Microsoft Remote Desktop Services for around one year.

Microsoft Remote Desktop Services is stable, as I have never had any instability issues.

Microsoft Remote Desktop Services scales very well; I could scale it to however many users I would want. From the functionality perspective, it is fine, but from the cost and operations perspective, it gets quite difficult because I have to purchase numerous licenses and track them. So while it is possible to scale very easily, it is complex to manage that scaling.

I have interacted with Microsoft customer support before; their support is fine, but I would not say it is the best in the industry. I have noticed, along with other team members, that when trying to reach Microsoft for customer support, it has to go through many different teams to reach the right place, leading to delays. In contrast, interacting with Amazon's customer support seems to route the request to the correct team almost immediately, resulting in quicker responses.

In a different organization, I have used Amazon WorkSpaces, which is a good tool that makes it easier to manage because it is within the cloud, with much of the networking and overall management abstracted away. However, I found that there was a big latency issue with WorkSpaces, and if there was a connection error, I could not access my desktop environment, causing significant problems. Therefore, I feel that Microsoft Remote Desktop Services is a bit more reliable.

I did not evaluate other options before choosing Microsoft Remote Desktop Services.

I was not involved in the pricing and licensing perspective, so I cannot speak too much on that. However, I know that two license types are needed: the Windows Server license and another client license. I understand it can get quite expensive and also complex to manage these different licenses.

Microsoft Remote Desktop Services is a good tool that does what it is meant to do, and from a security perspective, it is brilliant. However, there is a lot of overhead with managing it, which modern tools do not have, especially tools that exist in the cloud. Also, it is in an end-of-life state right now, so there probably will not be any new features rolled out, and one issue is that you have to have Windows server licenses to use it, as well as an additional license type for every user or device that connects to the server. This can be expensive and complex to track from the licensing perspective.

I would advise others looking into using Microsoft Remote Desktop Services that it is a good tool to use, but I would not recommend starting to use it nowadays because it is in end-of-life support. Azure Virtual Desktop or Windows 365 is probably the better way to go since they are more modern tools. For what it is, it is a good tool; it is just being phased out as a legacy piece now.

I rate Microsoft Remote Desktop Services an 8 out of 10.

My main use case for Microsoft Remote Desktop Services is to access the server infrastructure of our Customer, which I support in my role as a technical support personnel.

A specific example of how I used Microsoft Remote Desktop Services in that role is that we have some applications running on servers which I need to restart regularly, and I normally use remote desktop to access it and then restart the services on those servers.

The best feature that Microsoft Remote Desktop Services offers is the ability to connect to server infrastructure from anywhere I am; no matter the country I am in, as long as I have an internet connection, I am able to log in to our servers and then carry out my duties.

I appreciate the security features of Microsoft Remote Desktop Services where it ensures that anyone connecting to the server infrastructure is an authenticated individual from a device that is trusted by our systems.

Microsoft Remote Desktop Services has positively impacted my organization by enabling us to work on multiple projects at once; all we need to do is have the login credentials for the different customers we are serving and then we are able to support them remotely.

Microsoft Remote Desktop Services has led to measurable improvements in faster response times and increased productivity for my team as I work in a team that is spread across different time zones, and having access to remote desktop enables us to collaborate across those time zones.

Microsoft Remote Desktop Services helps my team collaborate across projects or locations as we are across multiple time zones; I can pick off where one of my colleagues leaves off, and it enables us to work efficiently across those time zones.

Microsoft Remote Desktop Services could be improved because when I am connected to a larger screen like an external monitor, the window for remote desktop is not able to fill the screen entirely but remains at a section of the screen; I am unsure if it is a setting on my system or a remote desktop-specific issue.

If there were an easier way to save logins so that I do not need to keep entering passwords for different servers every time I need to access a specific server, that would be beneficial.

Regarding the interface, I would rate it a nine mainly because it still looks like an old application, and if it could be modernized, that would be appreciated.

I have been using Microsoft Remote Desktop Services for about fourteen months.

Microsoft Remote Desktop Services is stable.

I cannot provide metrics on the scalability of Microsoft Remote Desktop Services.

I have not had to raise any form of customer support request, so I cannot provide input on that regarding Microsoft Remote Desktop Services.

I have only used Microsoft Remote Desktop Services and did not previously use a different solution.

Before choosing Microsoft Remote Desktop Services, we evaluated other options, but it was a standardized application for us to use in my organization.

We use Microsoft Remote Desktop Services as a standalone application and not integrated into any workflow at the moment.

Microsoft Remote Desktop Services has helped us to be efficient; we are a team of five serving the entire region of Africa and the Middle East, and it has truly improved our overall efficiency as a team.

I do not have a view into the financials as the cost was handled externally regarding Microsoft Remote Desktop Services' pricing, setup cost, and licensing.

My company has a global partnership with Microsoft, and we utilize most of our business systems as Microsoft Enterprise systems, so my company has a business relationship with this vendor other than being a customer.

I would advise others looking into using Microsoft Remote Desktop Services to make sure they have a good network connection and to take security seriously, especially for the local device with which they will connect to servers, because if someone has access to that device without any authentication or security processes, it could lead to a huge security event.

I would give Microsoft Remote Desktop Services a rating of nine out of ten.

My main use case for Microsoft Remote Desktop Services is to log in remotely into a different environment. I have an appliance that we can log in to and be able to get onto different servers and navigate, and we get there through Microsoft Remote Desktop Services.

The best features Microsoft Remote Desktop Services offers include being able to log in and being able to control other machines.

Controlling other machines helps me in my role as it improves our workflow, allowing us to get in rapidly and do our work.

Microsoft Remote Desktop Services has positively impacted my organization by allowing us to remote in rapidly and securely. The secure aspect of Microsoft Remote Desktop Services helps my team stay secure by supporting MFA, which allows us to secure who logs in.

Microsoft Remote Desktop Services helps my team collaborate and work together by allowing us to put everything in one ecosystem with the integration, and it works very well with Windows Server, Active Directory, and Azure.

Microsoft Remote Desktop Services handles updates and maintenance in my environment easily, as it is easy to manage. Microsoft Remote Desktop Services performs very well in terms of reliability and uptime for my organization, and I appreciate this feature.

Microsoft Remote Desktop Services integrates with my existing security tools and policies and is compatible with our security stack, as we are a Microsoft shop, and it works well with us.

When multiple users are logged in at the same time, we have not noticed any issues with Microsoft Remote Desktop Services. The user experience for my team with Microsoft Remote Desktop Services is intuitive and easy to use.

Microsoft Remote Desktop Services can be improved by addressing the single session limitations and also clarifying the licensing, which can be confusing.

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

Microsoft Remote Desktop Services is stable.

The scalability of Microsoft Remote Desktop Services performs well.

Microsoft has good customer support. I would rate the customer support of Microsoft Remote Desktop Services a 10.

I cannot share any metrics on return on investment, but I appreciate the features and the use of it.

My experience with pricing, setup cost, and licensing for Microsoft Remote Desktop Services was that the licensing was acceptable, but I think the cost was fair.

Before choosing Microsoft Remote Desktop Services, I evaluated other options, particularly Citrix.

Microsoft Remote Desktop Services is a good product and I recommend using it. I would rate this product a 9 out of 10.

My main use case for Microsoft Remote Desktop Services is to connect to remote servers in the cloud that I use in my back-end application.

The best features Microsoft Remote Desktop Services offers is that it's easy to use.

Both the interface and the setup process make it feel easy to use for me.

Microsoft Remote Desktop Services positively impacts my organization because it makes the job and work easier for all.

It makes the work easier for everyone because it's easy to use and we can save time when connecting to our back-end servers.

Microsoft Remote Desktop Services are adequate for now and can be improved.

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

My advice to others looking into using Microsoft Remote Desktop Services is to use it because it's a good tool. I would rate this product a 10.

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.

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.

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.

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.

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.