What is our primary use case?
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 is most valuable?
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?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
I found Microsoft Remote Desktop Services stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I have yet to contact Microsoft Remote Desktop Services technical support.
How was the initial setup?
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.
What about the implementation team?
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.
What's my experience with pricing, setup cost, and licensing?
I recall that you don't need to pay for Microsoft Remote Desktop Services because that's included in Windows.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.