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.
Win Remote Desktop Services SAL
Amazon Web ServicesExternal reviews
External reviews are not included in the AWS star rating for the product.
Remote access has simplified daily server management and saves our team valuable time
What is our primary use case?
What is most valuable?
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.
What needs improvement?
Microsoft Remote Desktop Services are adequate for now and can be improved.
For how long have I used the solution?
I have been using Microsoft Remote Desktop Services for about 15 years.
What other advice do I have?
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.
A platform of choice for building virtualization solutions for every end customer need
What is most valuable?
The solution is user-friendly and has a good user experience.
What needs improvement?
Microsoft should be more compatible with other operating system.
For how long have I used the solution?
I have been using Microsoft Remote Desktop Services for a few years.
What do I think about the stability of the solution?
Microsoft is a stable solution. I rate the stability a ten out of ten.
What do I think about the scalability of the solution?
Only one user using the solution.
Which solution did I use previously and why did I switch?
Previously we used VMware but Microsoft is easy to deploy.
How was the initial setup?
The initial setup is straightforward. The deployment takes a few seconds.
What's my experience with pricing, setup cost, and licensing?
There is a licensing cost.
What other advice do I have?
Overall, I rate the solution a ten out of ten.
An exceptionally scalable tool requiring a straightforward setup phase
What is our primary use case?
If any of our clients using the internet are facing an issue, we connect Microsoft Remote Desktop Services and troubleshoot the exact issue.
What is most valuable?
Things can be made easier if someone is not with us or at a long distance since we can connect easily with those people. So, it's easy for us to use such features.
What needs improvement?
There have been some network issues in the solution. So, when we used to connect it, the solution suddenly got disconnected. So the network part needs to be improved. Also, for a long duration, if we share Microsoft Remote Desktop Services, then network issues come up, so I suggest improvements in the aforementioned areas. Also, the pricing could be better.
For how long have I used the solution?
I have been using Microsoft Remote Desktop Services for one or two months. Also, I am using the solution's latest version.
What do I think about the stability of the solution?
The network issue is something that causes us to invest longer time duration in connecting, after which it gets disconnected. Hence, I rate the solution's stability nine and a half out of ten.
What do I think about the scalability of the solution?
It is a scalable solution. Scalability-wise, I rate the solution a ten out of ten. Around five to ten of our clients are users using the solution. Also, the solution is being used extensively.
I do have plans to increase the usage of the solution. The number of users is increasing. In the last month, we have had two or three potential clients in the pipeline. In the near future, its usage will increase.
How are customer service and support?
I have never contacted technical support.
How was the initial setup?
The solution's initial setup process was straightforward. The deployment process took around a week.
Deployment steps are followed. For every network deployment, it is necessary to generate a single token. Once this token is generated, payment will be required. Once we obtain the UI connector, it is essential to verify that everything is running smoothly. Only then can it be directly connected, ensuring that the deployment process takes place without any issues.
Regarding the deployment of one server, if done by someone knowledgeable with Microsoft products, then it can be done directly. Else it will take a month since we need time to learn all these things. An engineer looks into a few things.
What about the implementation team?
The implementation can be done in-house.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive. Since things are made to be a bit easier in the solution, the solution's cost is a bit on the higher side.
What other advice do I have?
I will recommend it to others when I think it's quite an easy tool, especially if its implementation is easy. We should also be able to connect and solve our problems through troubleshooting issues remotely. For long-distance purposes, the tool gets quite easier for its users. I will recommend that everyone should use it.
Overall, I rate the solution a ten out of ten.