Windows Server Reviews

I administer Windows Server. We have Windows 10 and are migrating to Windows 11 under my organization. The people who work with me are handling the migration right now.

We have several servers, most of them Windows Server. We have a couple of Linux servers, but most of our servers are Windows Server. We maintain the normal infrastructure, including domain controller. We still have a file server and other specific servers. We have an Exchange Server that is only for hybrid purposes as we use Exchange Online. For specific tasks, we need a server to be managed. 

Several years of improvements have been made to the software itself. In the '90s, it was poorly reliable. Now it's very reliable; you can spin up a Windows Server box, and it will run without needing to reboot unless updating. It's quite secure, which wasn't the case previously. They improved security over the years. It's a standard, compatible and backwards compatible with several pieces of software, and it's a standard platform where you can find practically any server software that you need. For me, it's a standard platform right now. They gained the market over the years.

We primarily use the solution for a variety of tasks including active directory servers, exchange servers, hosting applications, running insurance apps, and SQL databases. A whole gamut of things. 

The SQL version of the solution is its most valuable aspect.

The solution is very easy to use and very easy to onboard. 

The solution, for the most part, is stable. The stability is actually pretty good in terms of availability.

The product's performance depends on the use case.

The solution is very scalable.

The initial setup isn't overly difficult.

We are using Windows Server to connect our client software. We use it to access client systems and work on SQL databases.

Rather than purchasing and setting up infrastructure, we are using Windows Server, which obviously saves some costs.

I use Windows Server primarily as an Infra Server and Active Directory domain controller. It acts as a domain controller, chain email server, application server, and file server.

Windows Server offers good operational benefits. It is quite sustained, provides good support, and is quite reliable.

It's very user-friendly, not like technical stuff like Linux or Unix. It is very easy to go and use. That's one reason we like it.

It's easy to manage core applications and deploy engineers. 

Windows engineers are more affordable than Linux or Unix engineers, so that's another advantage. So, the management costs are much lower for the Windows Server. 

Plus, troubleshooting is straightforward with readily available online resources, so we don't need to raise tickets or wait for help. We can easily search on Google and find the solution on the search engine. 

Windows Server is pretty mature already. They're doing a good job with it.

Even though there were changes in my job role or company, I continued to use Windows Server.

In recent times, improvements are required since everything is going to be very granular. If you give access to a particular group or particular user in a particular product line and if you want someone to be a part of that group which has different rights from another team, like an SME, who has more rights compared to an ordinary person, and if a new person or novice person comes in, he will have lesser rights.

Nowadays, everybody wants a user-friendly dashboard and interface. People don't want to know about complex commands and want everything to be available in just a few clicks on the dashboard, where they can see the top trends, what commands are being used, how many logins, and other such related information. The integration process should be smooth if I have Microsoft Active Directory deployed on an on-premises model and I want to connect it to a Microsoft Active Directory on the cloud. Even if you are involved in complex things on the back end, from the front end, the tool should be made easier for users to understand so that they can identify the credentials or keys they use.

If you want to integrate or connect with multiple integration points or ecosystems, then such a process should be something that is easily doable for users. Whether the tool is connected to an API, on-premises model, or cloud, it should be made a process that is easy for users.

We primarily use the solution for our different applications.

We appreciate how many different applications can be on the server at any given time.

The solution is easy to learn. It doesn't take much training.

The implementation is simple.

The graphic interface is very nice.