We've had issues with security breaches. The main problem is that if we are using this with the individual computer and using a remote desktop, there are some loopholes there. When I implemented this on an individual computer within two or three days it got captured.

There is a problem with the printing and sharing of this program. There is a lot of customized software leaving the market due to this. If somebody wants to run a specific program with the specific settings, they don't want full access to the computer. Then there are some problems that have to be resolved.

We'd like to have an additional control panel available in order o more easily give resources to the computers. There are a lot of restrictions and having a program panel would make things easier. It would help us set up the right access and permissions.  

It would be helpful if there was a feature that notifies you when the internet is down so you're not working for nothing, it should be something that pops right up where you can see it. The internet is always going to go down and the product seems to notice that it's down before my VPN notifies me that it's gone down. You're working and nothing's happening and it takes time to get the notification. 

For an additional feature, I'd like to see Remote Desktop specify which computer Zoom meetings will run on. I've joined a couple of sessions from home, and when I turn on my video, all you see is my empty desk chair at the office.

It's not as reliable a protocol as, for example, Citrix.

The training profiles could be better.

I'd like to have more granular remote profiles.

We'd like to see on-site multi-fact authentification.

The solution is under the Microsoft infrastructure and therefore does not allow for service under other operating systems. We'd like, in the future, if it would work with Linux or Unix-based operating systems or even Mac.

I've sometimes had trouble setting up an RDS connection if I want a specific user to be able to log in with their credentials and have the RDS element retain those settings so that the password isn't required each time. There can be issues with that. 

We've had a few occasions when the application has crashed suddenly, possibly due to updates. Microsoft updates should not directly impact the application and rather than releasing post hotfixes, it would be better to carry out testing before releasing it to the environment. It's a challenge for us; the new application is upgraded, but there's an incompatibility. It should be the other way around - testing in the lab environment and then commercially released.

An additional feature we'd like to see would be cross-platform support. With more OSs in the market whether Microsoft, iMac or Android applications, it would be good to have a smooth transition between cross-platform support both in terms of operating system and in terms of devices. Moving from tabs to mobiles to desktops to laptops to notebooks - the transition between multiple OSs and multiple hardwares.

It could be made simpler from a management perspective.

It should be easier to set it up for desktop printing.

Its look and feel could be updated.

In Azure Remote Desktop Services (RDS), which is a VDI solution, we would like to see linked clones. It is a Hyper-V solution, and it doesn't support linked clones and uses a lot of storage. That's why we don't use it. VMware has a similar solution that supports linked clones for the master image.

From the perspective of an IT professional, Microsoft Remote Desktop is very easy to use. However, it could be made easier to use for the end user, especially when it comes to activating it.

Microsoft could also improve the sustainability of this product, especially in terms of account redundancy. They could also add something like a log to make more easy to use so that they can easily prevent some of the failures. I think Microsoft can do better.

The user interface needs improvement.

While it's not expensive, the pricing could always be better.

I would like to see a web-based interface, instead of client installation to refresh the UI through HTML.

When comparing with other vendors offering applications not with a client module, but through the web through HTML, this should be the next step for Microsoft.

I would like to be able to access the remote desktop using a web-based interface, rather than having to use the client.

In a future release, they could improve by providing more advanced technology and better buffering for if the connection is degraded or lost. For example, if I am connected on my LAN or WAN, and there is any latency in the network while I am connected it will stay connected for one or two minutes. Without any buffering, the connection will be disconnected, and the work is lost.

Microsoft Remote Desktop Services could improve by having graphical acceleration.

There could be some improvement in the integration of the solution.

The solution should have better security. 

It is overpriced.

Microsoft Remote Desktop Services is only available for the professional version of the Windows operating system. This restricts a lot of users. The feature should be available for all versions.

There are times I get disconnected from the service and when one or two attempts to establish a remote connection. Microsoft should show where the problem is, I have to find it by myself.

Microsoft Desktop Services is stable but it takes up a lot of resources in the CPU. It's a bit heavier than some solutions.