We use it for file repositories, project sharing with Teams, and most of our business intelligence work. We manage around 30 to 40 projects using these resources, mainly on SharePoint.

We use SharePoint here since we're a public university. We have access to all Microsoft platforms. Also, we use Google for email, but they're restricting access for public universities, so we're mostly migrating to Microsoft.

It works well and supports remote work. People can work from home and easily share information. The platform is robust enough for our needs.

We have research projects where students can connect to computers and remotely monitor long experiments, such as charging and recharging cycles of batteries. They don't need to be physically in the lab, which is a good benefit.

It integrates well with existing security and compliance measures

Teams component can be a bit cumbersome to use. It takes some time to get it working as expected, but it's fine once you get used to it.

It is used daily in my university. 

It's scalable enough for our needs and very reliable.

Customer service and support were available whenever we needed them. It was always there. We didn't had any issue. 

Positive

The initial setup is easy. It was easy to set up. 

I would recommend it. The core features are very effective, especially for running an organization with geographically distributed people.

Overall, I would rate the solution an eight out of ten. 

We have a group of users who work remotely for us, as well as others who connect to our computers from various locations.

The solution works on Microsoft servers. 

Microsoft Remote Desktop Services needs to improve its security. 

I have been using the product for 20 years. 

I rate Microsoft Remote Desktop Services' stability a nine out of ten. 

I rate the tool's scalability a nine out of ten. My company has 80 users. 

We don't use technical support from Microsoft. We have outsourced it to another company. 

We chose Microsoft because it was cheaper. 

Microsoft Remote Desktop Services' deployment is easy. 

The tool's pricing is high in the Slovenian market. I rate it a nine out of ten. 

I rate Microsoft Remote Desktop Services a nine out of ten. 

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. 

My company uses Microsoft Remote Desktop Services for our company's accounting software, which doesn't have a cloud solution. In our company, we deployed a server with the help of Microsoft Remote Desktop Services.

The solution's most valuable feature is that it's a technology that we are familiar with in our company. Microsoft Remote Desktop Services has been around since Windows NT 4 domain, making it a very familiar solution. It was easy to find a lot of clients familiar with the idea of Microsoft Remote Desktop Services since it was not a new concept to them. In general, the solution tends to work well. It is an easy-to-use solution.

The biggest reason we don't use the solution for our company's clients is the solution's prices. In our company, we do our own hosting through a hosting partner since this method offers a much cheaper price. Finding entry-level servers that are limited in the IOPS is frustrating. In our company, we feel quite restricted on the speed that we can get out of the entry-level type of service that we use, making it difficult to sell the solution, especially when clients compare the cloud solution to an on-premises solution.

I have been using Microsoft Remote Desktop Services for five to six years. I work at an IT support company that resells, implements, and offers support for Microsoft products.

My company is happy with the stability of the solution.

I think it's a very scalable product. The product's scalability depends on how big our company's clients are, so it is not an area we need to worry about since you can use its gateway server for different servers.

My company works with small and medium-sized businesses using Microsoft Remote Desktop Services.

The solution's technical support doesn't get covered under Office 365.

My experience with other Microsoft support, apart from Office 365, has not been that fantastic since I remember being quite shocked using the solution.

I haven't used support for Microsoft Remote Desktop Services.

The installation of Microsoft Remote Desktop Services was easy.

The installation of Microsoft Remote Desktop Services takes around four hours.

The solution is deployed on the cloud and on-premises.

A single technician is involved with the deployment part of the product in our company.

In our company, we consider Microsoft Remote Desktop Services as more of an added service than something that generates income for us. We do make a little bit of income with the help of the solution, but most of all, it's just a value-added service that the product provides for our company. Our company won't get rich by selling Microsoft Remote Desktop Services.

The solution is expensive. My company pays toward the monthly licensing costs of the solution, though we also have the option to opt for perpetual licensing offered by Microsoft. Microsoft licensing models are quite complex, so we tend to use a monthly subscription-based model in our company.

The additional cost, apart from the solution's licensing cost, is related to the technical support a user wants.

Though not a lot, some maintenance is required for the solution. One person can do the maintenance of the solution.

I would tell those planning to use the solution not to underspec the server, especially with IOPS, while keeping in mind that the amount of RAM can be more than expected. I would say that the need for a VPN, owing to security reasons, is important.

I rate the overall solution a nine out of ten.

If any of our clients using the internet are facing an issue, we connect Microsoft Remote Desktop Services and troubleshoot the exact issue.

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.

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.

I have been using Microsoft Remote Desktop Services for one or two months. Also, I am using the solution's latest version.

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.

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.

I have never contacted technical support.

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.

The implementation can be done in-house.

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.

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.