Microsoft Remote Desktop Services Reviews

It allows access to the computer from any location.

I can telecommute into the office. Since we have to be on a secure network, it gives me access into my system at work that is more secure than my system at home.

There could be better options and it could be faster. I haven't had too many issues with it, but it's just a very basic program.

I haven't had any issues with the stability of the product.

I haven't experienced any scalability issues. Although, I can see some issues with it but for a small company right now, it's working.

We were using a previous solution. However, I needed ways to telecommute to the office and I came across this solution; it seemed like the best bet.

In my opinion, important factors while selecting a vendor are reliability, support (if needed) and scalability of the solution.

Load balancing: RDS Broker servers divide user sessions evenly among the RDS Host servers that host the applications. You can install multiple RDS Broker servers in an RDS cluster; this is built-in and no extra resources are needed. Optionally, the cluster can be made Highly Available if needed.

High Availability (HA): easy to set up - once the MS SQL database is created and the RDS Broker servers have the needed rights, the database is created automatically and HA is enabled.

Applications are ready for BYOD scenario’s, since RDP is a multi-OS/device technology. No more app testing for client OS migrations.

The valuable features I mentioned assure a stable and highly available environment with maximum uptime for business users. Also, they assure that assigned resources (application RDS hosts) are optimally used, without the need for any extra administrator intervention or monitoring.

Currently, installation of applications on an RDS farm must be performed manually on each server. This should be more controlled and automated.

Also, application sources are mixed on the file system and registry level. They should be in separate ‘containers’.

We did not have any problems with stability.

There are no issues with scalability. At any time, an RDS Host server can be added to any server collection. Also, some additional parameters allow us tocontrol and scale the expected user load (session limit, RDS Host weight).

Technical support is OK if you have MS Premier support.

We did not previously use a different solution.

Installation of the RDS farm was pretty easy. Configuration is a little harder; you need to configure trusted certificates (RDS 2012 allows HTTPS only), add groups and group policies for users, RDS hosts, server collections, etc.

Once configuration is done, management is easy.

There are two choices for RDS CALs (Client Access Licenses). Device CALs are cheap but allow low user mobility and require a high management effort (‘static’ or ‘task station’ scenario). User CALs are 20% more expensive, but offer high mobility and low management cost (‘dynamic’ or ‘mobile’ scenario).

We did not evaluate any other options.

My advice is to start in a lab environment to thoroughly test your infrastructure setup and configuration.

Use User CALs, they give much lower TCO.

Also, for applications you envision to provision on RDS, test whether they install correctly on Windows Server.

Remote desktop services are similar to terminal based settings where multiple terminals connect to a server. A user has the ability to run programs, view files, etc. Each session is independent and secure. All application execution takes place on the server. Allows for IT staff to install all software, databases, etc on the server rather than on individual pc's. Provides centralized management of operating system images.

Network bandwidth may limit a users experience with remote desktop services. If you don't have vpn/terminal access, you cannot use remote desktop. If network or server goes down, you cannot do any work. There may be some lag in running modern development tools.

For all users that love the convenience of being able to work from any location. Provides a secure network connection. There is the potential of lowering developers cost. A great way to get more work from your employees at all times.

I use the solution to connect to different servers.

The solution is really fast. Every company can use it.

When a change is made in Box, it affects all the services, which is annoying.

The performance of Remote Desktop Services could be better.

I have been using the solution for three years.

The stability of the solution is good. I rate the stability a ten out of ten.

I rate the scalability of the solution a ten out of ten. About 1000 employees are using the solution in our organization.

The initial setup is straightforward. We can find the necessary information on the Internet.

We need five employees, including managers, administrators, and engineers, to deploy and maintain the solution.

It is a cloud-based solution. We can use the solution on a local server or the cloud, depending on our organization's needs. I would recommend the solution to others. It is useful and straightforward. Overall, I rate the solution a ten out of ten.

Our primary use case is for accessing Visual Basic.

The most valuable features are it is fast and cost-effective. I am not aware of a replacement currently on the market.

I would like to see the hard drives work without locking up and integrate the local drives in the next release.

I have been working with Microsoft Remote Desktop Services for the past couple of months.

There is stability but sometimes it does disconnect.

The initial setup was easy and takes usually one or two days.

We did our implementation in-house.

I think that Microsoft Remote Desktop Services is expensive compared to Login solution.

I have used Citrix and Login solution. 

Microsoft Remote Desktop Services is a good solution and I would rate it an eight on a scale of one to ten.

On-premises

It's simple and easy to use.

We've been providing Microsoft Remote Desktop Services for about 15 years.

Remote Desktop Services doesn't scale well. 

Microsoft support could be more accessible. They address issues quickly, but it's hard to reach them.

Installing Remote Desktop Services is straightforward. The basic deployment took about one workday. One engineer could handle it.

We have a monthly license.

I rate Microsoft Remote Desktop Services five out of 10. I would recommend it. 

On-premises

The solution is user-friendly and has a good user experience. 

Microsoft should be more compatible with other operating system. 

I have been using Microsoft Remote Desktop Services for a few years. 

Microsoft is a stable solution. I rate the stability a ten out of ten. 

Only one user using the solution. 

Previously we used VMware but Microsoft is easy to deploy. 

The initial setup is straightforward. The deployment takes a few seconds. 

There is a licensing cost. 

Overall, I rate the solution a ten out of ten. 

Private Cloud