We changed our name from IT Central Station: Here's why
Software Engineer at a comms service provider with 51-200 employees
Real User
Top 5Leaderboard
Easy to deploy, simple to set up and stable
Pros and Cons
  • "The scalability is okay."
  • "The solution should be less expensive."

What is our primary use case?

We are using this solution for some database applications.

What is most valuable?

The solution is mostly stable. 

The scalability is okay. We just need to get the correct edition of the Server.

The initial setup is easy and the deployment is fast.

What needs improvement?

There are some limitations around scalability.

The solution should be less expensive. Linux options are far less costly.

For how long have I used the solution?

I've been using the solution for five years, at least, in this company.

What do I think about the stability of the solution?

The product, for the most part, is stable. I would say the hardware will cause some issues before the operating system.

What do I think about the scalability of the solution?

In terms of hardware, it is scalable, if we can increase the hardware resources. We are not using the data center version of the OS. We're just using the standard version.

We have around 30 people using the solution.

How are customer service and technical support?

I haven't dealt with technical support. So far we haven't escalated anything as our installation is very simple.

How was the initial setup?

The initial setup is not overly complex. It is basically like any other Windows operating system. It's fairly straightforward.

The implementation only takes about 30 minutes. 

We have a team of three in the IT department that can handle deployment and maintenance. 

What about the implementation team?

We did not need any integrator or consultant. it's very easy for a company to handle by itself. 

What's my experience with pricing, setup cost, and licensing?

The pricing could be more competitive.

We only pay a one-time fee and do not have to continuously pay monthly or yearly.

What other advice do I have?

I'm a customer and an end-user.

We are still using 2012, and we're planning to upgrade to 2019.

I'd rate the solution a nine out of ten.

I would recommend the solution to other organizations. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Owner and business consultant at networks srl
Real User
Top 5
A stable solution for file sharing and centralized authentication
Pros and Cons
  • "Compared to other solutions, the ease of administration is great."
  • "If the service could be better integrated with the Azure Cloud, I think it would be a plus for Windows."

What is our primary use case?

We used Windows Server for file sharing and centralized authentication.

We stopped using Microsoft Server in 2012 due to hardware failure and licensing costs. For these reasons, we decided to move to open-source solutions.

What is most valuable?

Compared to other solutions, the ease of administration is great. 

What needs improvement?

In regard to the next release, I would like to see a more scalable solution. I would also like to see any future developments on the market because there was a time when most companies would run away from centralized authentication systems, like Active Directory — they moved to cloud solutions. If the service could be better integrated with the Azure Cloud, I think it would be a plus for Windows.

For how long have I used the solution?

I used Windows Server from 2003 until 2012.

What do I think about the stability of the solution?

Windows Server is absolutely stable.

What do I think about the scalability of the solution?

I can't comment on the scalability as we were only using two to three servers and we never attempted to scale out any further.

How are customer service and technical support?

The technical support is okay. As I have a special relationship with them, It's quite easy for me to get a hold of them. 

Which solution did I use previously and why did I switch?

I started with FreeBSD, then moved to Solaris. Right now I am only using and recommending Linux.

How was the initial setup?

The installation was easy compared to other operating systems, but the documentation part took longer than usual because I typically specialize in Linux-based operations.

What about the implementation team?

I usually handle the implementation myself. If I encounter a specific issue then I may have to apply for a consultant.

What other advice do I have?

Overall, on a scale from one to ten, I would give this solution a rating of eight. If your environment requires it, I would absolutely recommend Windows Server.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
Learn what your peers think about Windows Server. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
564,599 professionals have used our research since 2012.
Senior Solutions Architect at a manufacturing company with 51-200 employees
Real User
Top 5Leaderboard
High performance, scalable, and straightforward installation
Pros and Cons
  • "If everything is configured correctly this solution provides high performance. Building a Failover Cluster is comparatively much easier in Windows Server than any of the Linux-based solutions."
  • "They should release a command-line version of the solution."

What is our primary use case?

Windows Server can be used for various mission-critical applications, such as SAP, web servers, SQL databases, and hosting. Various security applications, for example, Symantec or McAfee, all need Windows Servers as the back end to operate. Additionally, this solution can be used to build up a Failover Cluster.

What is most valuable?

If everything is configured correctly this solution provides high performance. Building a Failover Cluster is comparatively much easier in Windows Server than any of the Linux-based solutions.

What needs improvement?

They should release a command-line version of the solution.

For how long have I used the solution?

I have been using the solution for approximately 15 years.

What do I think about the stability of the solution?

Windows Server is stable. However, there is some maintenance required for smooth operations.

What do I think about the scalability of the solution?

The solution can easily scale.

How was the initial setup?

The installation is straightforward and takes approximately one hour.

What about the implementation team?

If the server environment is large I would advise using an integrator. We have a team that does the maintenance of the solution which is important because it is used for mission-critical applications.

What's my experience with pricing, setup cost, and licensing?

The solution could improve by changing the licensing model. In Windows Server 2008 they provided two versions, one regular and the other was free with no graphics. In Windows 2012 they stopped providing the free version. They should go back to the previous model and let customers have the choice whether they want to opt for a free version or have the Microsoft supported version or the OEM version.

If you choose Windows Server on-premises, you will receive a perpetual license and there is also a subscription license option. For the cloud version, there are several options available, such as a monthly subscription.

What other advice do I have?

I would recommend this solution to others.

I rate Windows Server a nine out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Maan Othman
Senior System Engineer at a comms service provider with 201-500 employees
Real User
Top 5Leaderboard
A server operating system with a valuable user interface
Pros and Cons
  • "I like the views in the user interface."
  • "It would help if Microsoft made it lighter to run on the servers and made troubleshooting much easier."

What is our primary use case?

We use Windows Server to host applications, host files, emails, Windows server emails, and data exchange. But for the most part, we use it to host applications, directory services, and DNS services. 

What is most valuable?

I like the views in the user interface. 

What needs improvement?

It would help if Microsoft made it lighter to run on the servers and made troubleshooting much easier. I have to deal with unexpected errors and faults that happen in Windows. It also crashes. 

When it's a big environment, especially in an industrialized environment, we see unexpected errors. They create instability, or unexpected errors happen in the infrastructure. You need to restart the server or restart the services. You don't know the root cause of these errors.

For how long have I used the solution?

I've been working with Windows Server for about 20 years.

What do I think about the stability of the solution?

Sometimes we have to deal with unexpected errors that create instability.

What do I think about the scalability of the solution?

Windows Server is mostly scalable. However, you run into problems if it's going to be very big. If something happens, troubleshooting it will be very difficult.

How are customer service and technical support?

Microsoft technical support is good.

How was the initial setup?

The initial setup is mostly straightforward. 

What's my experience with pricing, setup cost, and licensing?

The Windows Server standard edition is affordable. But the cost of the data center edition is high, especially compared to some competitors. Some competitors are offering their operating systems for free.

What other advice do I have?

I would tell potential customers of Windows Server that they need to study it. They need to understand their business case very well. If features are available in Windows Server, they can safely go for it, but they need to study the design very well.

On a scale from one to ten, I would give Windows Server an eight.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Lead Solutions Architect - International Projects at a media company with 501-1,000 employees
Real User
Top 20
Scalable, easy to install and best used for Microsoft applications
Pros and Cons
  • "The solution is scalable."
  • "The solution is less stable than Linux."

What is our primary use case?

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

What is most valuable?

The solution is perfect for Microsoft applications.

The stability is okay.

The solution is scalable.

The installation process is easy.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Emmanuel FOMUDE
Senior Oracle Database Administrator at a financial services firm with 51-200 employees
Real User
Top 5
It offers a lot of services, but there are limitations on the number of simultaneous users on the basic license
Pros and Cons
  • "The biggest advantage of Windows Server is the services. It offers the ability to configure services, so your application can run on a Windows Server."
  • "But one issue I have with Windows Server is the limit on the number of concurrent sessions. You cannot have more than three simultaneous users unless you activate a license. You have to install it so that more people can access the applications simultaneously."

What is our primary use case?

Window Server is for the front-end applications. It is on the client-facing side.

What is most valuable?

The biggest advantage of Windows Server is the services. It offers the ability to configure services, so your application can run on a Windows Server. 

For how long have I used the solution?

We've been using Windows Server for a couple of years. Since the company was founded, we've been using Windows Server and Linux. We're still using Red Hat. When I joined the company, I migrated all the databases over to Linux. Everything on the application side is on Windows Server.

What do I think about the stability of the solution?

Windows Server is stable as far as I know. 

What do I think about the scalability of the solution?

I can't really say that it's scalable. At the application level, we only have about 20 users.

How are customer service and support?

I'm not the one in charge of the platform. The person in charge takes care of things when there is a critical error and there are new updates or patches from the Microsoft site. They're the one who contacts the technical support team if needed.

How was the initial setup?

Installing Windows Server is straightforward. We have a technical team to manage the solution, but I can handle the deployment by itself. 

What's my experience with pricing, setup cost, and licensing?

I think it's a yearly license.

What other advice do I have?

I rate Windows Server six out of 10. I would recommend Windows Server if you are working with .NET applications. But one issue I have with Windows Server is the limit on the number of concurrent sessions. You cannot have more than three simultaneous users unless you activate a license. You have to install it so that more people can access the applications simultaneously.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
ICT and Cyber Security Adviser at a security firm with self employed
Real User
Top 20
Easy to set up and works for any size organization, but needs to be more secure
Pros and Cons
  • "We can scale the solution if we need to."
  • "The performance from time to time can be a bit suspect."

What is our primary use case?

We primarily use the solution for many things. It's an operating system. We use to run many different application servers like SAP exchanges, and applications in our environment.

What is most valuable?

Overall, we've been happy with the solution. 

The initial setup is pretty simple.

We can scale the solution if we need to.

The stability is decent. 

Technical support has been okay.

What needs improvement?

We're concerned about Windows vulnerabilities and how to manage those vulnerabilities ourselves. These are the main things that are tricky in Windows, the environment. 

The performance from time to time can be a bit suspect. 

For how long have I used the solution?

I've used the solution for quite a long time. It's been something like 20 years or so that I have been using this product.

What do I think about the stability of the solution?

To a certain extent, I would say the stability is fine. There aren't bugs or glitches. It doesn't crash or freeze.

What do I think about the scalability of the solution?

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

The size of the company doesn't matter. It works for any size of organization from small to large.

How are customer service and support?

Technical support was okay. We haven't really had any problems with them.

What's my experience with pricing, setup cost, and licensing?

You do have to pay for licensing of the product. 

What other advice do I have?

We are a customer and an end-user of Microsoft. We do not have any special business relationship with them. 

I'd rate the solution at a seven out of ten. We're mostly happy with its capabilities. 

I would advise potential users to secure it well and keep it up to date. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Senior Consultant at a tech services company with 11-50 employees
Real User
Simple to set up, reliable, and has very little downtime
Pros and Cons
  • "The product can scale."
  • "The performance could be a bit better."

What is our primary use case?

The solution helps fulfill customer requirements. We use it for applications.

What is most valuable?

The solution is very stable. There isn't a lot of downtime.

The product can scale. 

The initial setup is very easy.

What needs improvement?

There was one instance in which, during an installation, I got an error I could not easily resolve.

The performance could be a bit better.

For how long have I used the solution?

I've used the solution for around ten years or so.

What do I think about the stability of the solution?

We've found the stability to be reliable. It doesn't crash or freeze. there are no bugs or glitches. 

What do I think about the scalability of the solution?

Scalability is possible. If you need to expand it, you can do so. 

We have about 15 customers on the solution right now. 

How are customer service and support?

I've never really had a problem with the solution, and I've worked with it for many years, I've never had to contact technical support in the past.

How was the initial setup?

With ten years of experience under our belts, we've handled implementations many times over. It's not a problem at all for us. We find the process very straightforward, very simple. 

We have five or six engineers on our team that are able to easily handle deployment and maintenance. 

What about the implementation team?

We can handle the implementation process for our clients. 

What other advice do I have?

We are both a customer and a consultant. 

I'd recommend the solution to others.

I started to work as an engineer and I started working with the server in 2012. I've seen many user requirements met by this server, which is why I can confidently recommend it to others. It helps resolve a lot of issues with the infrastructure.

I'd rate the solution at a nine out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate