Windows Server Reviews

It's a platform, so it brings on a system for the servers themselves. I have multiple services running over Microsoft Servers, for example.SAP, Exchange . All of my services already running are running over this platform.

I also using it occasionally for application access.

The most valuable aspect of the solution is its operating system. It's just like Linux or UNIX. 

I'm using all the features within it and find them all quite helpful.

I love using it for the DHCP server, DNS services, and using a computer to map sites on our domain.

The security should be improved, specifically from port security & Allowed protocols,The improvement should retire all marked ports & protocols as a security breach to enhance platform risks & stability . 

Overall, from a security perspective, Microsoft needs to improve.

The Server platform GUI seems to take up a lot of resources unnecessarily.

I've been using the solution for twenty plus years for now.

While the solution hasn't always been stable, starting from the 2012 version, it's increasingly gotten more stable.

Since the 2012 version, we find it to be quite stable. The OS between the resources, between applicators, technical support, etc., is all very easy to handle. We don't have issues with it; it seems to be quite reliable.

The company here is using this solution. Sometimes it's for remote access, however, even if they don't use it for that, they already using is as it's implemented over the Windows Server.

I'm not sure if we'll be scaling any more as everyone is using it.

Registration is very easy, so we didn't need technical support for that aspect of the solution. However, it still requires continual study in order to use everything properly. In terms of speaking with someone directly, I don't have any information about that, and therefore can't comment on the quality of their service.

The initial implementation was not complex. I'd describe the setup as straightforward.

You have to sign off the approach of the planned service, make a timeline, and start to implement a POC. Once you're done with that, you can apply for it online. 

For Microsoft platforms, we have not needed any outside assistance. For the other services, like ERP,  we are already using consultants for implementation.

We're just a customers. We've been using multiple versions of the solution up to the 2016 version.

I would recommend the Microsoft platform and Windows Servers in particular. It's great for implementation into any environment and is easy to use. They have enhanced some security, however, there needs more done in that respect.

That said, from an efficiency, performance, business continuity, and integration standpoint, I'd highly recommend the Microsoft platform. While Linux has a better security layer, if that is your concern, be aware it will require investment in a lot of resources, training. 

I'd rate the solution seven out of ten. To get higher marks, the solution really needs to do something about the GUI & its security, which currently consumes a lot of resources & allowing breaching. 

The solution is mainly used for personal tasks. A lot of the customers are working with Microsoft solutions. This product works well with Microsoft. That's why we provide the Microsoft Windows Server solution to a lot of our customers.

The solution is very stable.

The scalability has been good.

We find the initial implementation process to be quick and easy.

The interface is good.

We've found the level of security to be fine.

The technical support needs to be improved. 

I've been using the solution for eight years. It's been a while. I've used it for almost a decade. 

The solution is stable. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

The solution is very scalable. If a company needs to expand it, it can do so. It's not a problem. 

We only have about 14 people on the solution currently.

Microsoft technical support isn't ideal. They could improve their services. We're not 100% satisfied. 

They could be faster, more knowledgeable, and more customer-friendly. They need to provide more direct answers. 

The installation process isn't too difficult. It's fairly straightforward. 

The deployment is fast and only takes about three or four hours or so. It doesn't take long.

In my organization, we have eight people that can handle deployment or maintenance tasks.

As integrators, we can set up the solution for our clients. I can handle a deployment myself. It's not overly complex. 

Customers do need to pay a yearly licensing fee.

I work with both the on-premises and cloud deployment models.

We're an integrator.

I'd rate the solution at an eight out of ten. We're pretty happy with its capabilities. 

That said, in Thailand, they do not sell many Windows Servers, so it's difficult to use the product, Windows Server, a lot.

We are using Windows Server on virtual machines running off-premise.

This operating system for business can be useful for personal documents or any daily or routine stuff.

The features that I have found most valuable are its ease of use and the compatibility with most other products.

I would definitely like to see bolting monitoring tools. To monitor the server you usually have to install third party tools. I would like to be less reliant on third-party tools. They always create some sort of security issue regarding ports that need to be opened, that type of thing. Windows Server has internally monitorable software but remote monitoring software would be a great add-on.

In the next version I would like to see monitoring tools or maybe an easier way to figure out who were the last people that were working on the server, something that gives me better insights into the actions taken by different users who need to access the server. Our server is definitely not for everybody to access, but even if it had logging installed or activated, it's quite difficult to figure out who did what.

I have been using Windows Server for a couple of years.

It is a stable solution.

Windows Server is definitely scalable.

We have 200 users using it in the network.

I was not part of the initial setup, I'm not part of the technical team. But I know from the people who did install it that it was quite easy.

On a scale of one to ten I would give Windows Server a nine.

I would recommend Windows Server for users who want to start using it.

We have an asset management system from a vendor that requires Windows Server. That's where the old content of customers is being stored.

The solution is perfect for Microsoft applications.

The stability is okay.

The solution is scalable.

The installation process is easy.

I don't like it. However, I'm forced to use it, due to the applications, or the vendor supply, that need to run on it. Many of the applications only support Windows Server.

The solution is less stable than Linux.

We've used the solution for a while. We use it constantly.

The solution is pretty stable. There are no bugs or glitches. It doesn't crash or freeze. It's pretty reliable. That said, Linux is even more reliable. 

The solution can scale. If a company needs to expand it, it can do so easily.

We also use Linux. We're 50% Linux, 50% Windows. 

The installation process is very straightforward. It's very easy. It's not too complex. A company shouldn't have any problems handling the process.

We use various versions of the solution, including 2008, 2012, 2016, and 2019.

We're a service provider. I have colleagues who are MSP-certified. They are the consultants to our customers.

I'd rate the solution at a seven out of ten. it's okay. However, it's not my first choice. I find Linux, for example, more stable. 

I would only recommend the solution to a user if they really needed to use it for specific applications. I would not advise it if you needed to install it. I'd only advise it if your application requires Windows. If that's the case, then, of course, you should use it.

We use it for a system that we have in our company. We are using Windows Server 2016.

It is stable and scalable.

It is not easy to use. It can be more user-friendly to make our routine work a bit easy.

It could also be cheaper.

I have been using this solution for four or five years. 

It is stable.

It is scalable. We have around 1,000 users.

Support is handled by another department.

We didn't use any other solution.

I didn't handle its installation, but based on what I know, it was easy to install.

We install and maintain it with the help of another team in our company. They have three engineers for deployment and maintenance.

It could be cheaper. Its licensing is on a yearly basis.

I would recommend this solution. I would rate Windows Server an eight out of ten.

We have the product that my team works on and we need to, for example, deploy the solution on running servers. That way, the client can access it and the QAs in our team could test it.

Also, we have some database servers other than the Windows Server. We use it for servers - indicators for better pages for better performance. We create the databases actually. 

The remote session is really helpful due to the fact that we are using Windows on our machines. You can access the remote session easily on that server. There's also the database management tool that we use to run queries and show a relational database check. If there is some problem with the data we can see it. 

It's good for performance testing on the actual app.

The scalability it offers is great. We can upgrade for the internal services. If we want to increase storage, or our clients do, the solution can accommodate that.

Overall it's really easy to use. It's like using Windows, yet with many other features.

The initial setup is very easy.

Sometimes we face some overload on servers. You need to request one of the IT to assist as there is no way that you can do a remote session on it. They need to intervene directly on the server. It has to be done manually. We also can't intervene ourselves as there is no way to log in remotely to the servers. That's why IT needs to get involved. It's a pain point for us as all you can really do is wait.

In a future release, it would be helpful if there were more tools to help us do some performance testing. The last time we needed to look for tools online and choose some third-party tools to analyze how the application is performing. If they could instead provide us with pre-installed tools, that would be better. There are some but they don't really give you the information that we are looking for. 

We've been using the solution for the last 12 months. We use it pretty much daily.

The stability is good. It's extremely reliable. We are using it in both the development phase and in production whenever we have a release for a client. It doesn't crash or freeze. There are no bugs or glitches.
It also provides multiple metrics that help us supervise the overall performance of the server based on data collected over the lifetime.

For my own team, from our own premise, there are more than a hundred users at any given time on the solution. Sometimes there could be multiple deployments on one server. 

We do have plans to increase usage. It comes with a variety of good features and it's quite useful to us. 

I haven't personally worked with technical support in any capacity. However, I have colleagues that have opened tickets and they don't have any complaints. They are helpful and reliable when dealing with our team.

The initial setup was straightforward. There are some requests from the clients to use HTTPS and therefore we needed to test some certificates. The documentation thing for Amazon or Microsoft is really detailed at the center. It's easy to find the details you need.

We do have a license from Microsoft.

I can't speak to how the subscription works however it's my understanding that it's paid yearly due to the fact that it's a large-scale scheme.

We are just a customer and an end-user.

We have servers deployed within the company's headquarters right here in Tunis which we use for internal purposes. For other clients, it's deployed in other data centers, and they have access to them from our company.

I'd recommend this solution to other companies and users. There are some clients that require this particular server and there are some older solutions that require deployment on a Windows Server. That said, we've moved to .net code to support both Microsoft and Linux.

I'd rate the solution at an eight out of ten.

The main features that we are using are active directory, domain, and DNS. 

They can simplify the utilization and control of the system when you have a lot of setups. They provided something called Windows Center or Control Center in version 2019. It's a free tool that comes with the Windows Server. You can install it on your desktop and use it. 

This tool simplifies the control and monitoring of all servers. If I have 200 servers, I don't need to log in to each one to configure it. I can manage them from this tool. However, this tool needs quite a lot of improvements. It's difficult to use, and they need to improve it. 

I have been using this solution since 1990. Currently, we are using the latest version. We have the cloud and on-premises deployments. 

It is good.

We never contacted them.

The initial setup was straightforward. It took around 15 minutes. Usually, on the server, we don't do the physical installation. When we install initially, we install an image. You just create an image, and that's it. After that, we don't need to do an installation.

There are only two options in the market: Windows and Linux. It depends on your application. If you have an application that requires Windows, you go with Windows Server. Otherwise, you go for Linux. There are not enough choices to choose from and decide. 

They had an issue in version 2016 related to the slowness of update management, but they already solved it in version 2019. It was impacting batch management. The time that Windows required was a lot, but it was fixed in version 2019. That was the only issue we faced in Windows Server. Other than that, it's fine.

I would advise on the version, not on the solution itself, that is, whether to use Windows Server or not. If Windows Server is a required solution, you have to take it. It's not an option. However, I would advise to not use version 2016. 

I would rate Windows Server a ten out of ten. If your application is required on Windows, it's not comparable to any other solution. If an application can work with Windows or Linux, for sure, I'm going with Linux.

We have our applications on the servers.

I like the fact that Windows Server is user friendly.

With Microsoft, there are always bugs, and the stability could be improved.

We have been using Windows Server for a long time. We have different versions: 2016, 2012, and 2008 as well.

It's more or less stable. Sometimes, there are problems with bugs.

It is a scalable solution.

The initial setup is easy. It took about an hour without including configuration. One person handled the deployment. 

We used an in-house team.

I would recommend this solution and rate it at eight on a scale from one to ten.