A Story of Windows Server
No photo available
April 26, 2019

A Story of Windows Server

Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Windows Server

As a software company, we develop our products and do integration projects for our customers. Since MS technologies are mostly used by the developers, MS infrastructure has to be used to test the builts. My company also is a software reseller and a solution partner. The vendors some of the modules require the Windows Server platform. Thus, we have to use Windows Server for self-study, tests, and experiments for pre-deployment and pre-implementation tasks. Briefly, the selected development and software infrastructure drove us to use Windows Server.
  • Having an integrated GUI eases management.
  • Windows Servers' uptime is fairly well.
  • There are many third-party management tools where there is no solution brought by Microsoft.
  • The requirement to restart after updates is the worst thing about Windows Server.
  • Windows Service infrastructure sometimes has issues to start an application as a service.
  • There is an event and troubleshooting mechanism which doesn't help much mostly. Also, IDs which were given for a problem are not user-friendly.
  • Some configurations require deep diving into the registry and sometimes it feels like it doesn't work due to complicated documentation.
  • After Investing in Windows Server (or Microsoft technologies) it feels like it grabs you as time passes. As usual, such systems get mature and develops in time. You may find your self stuck in MS technologies and can't move to another platform.
  • If you have moderate knowledge on Windows Server it is easy to have a well-managed server. The learning curve may be lower than alternatives.
  • Since it is very popular and widely used, it is also popular among attackers. Don't forget to use an antivirus and keep the server hotfixes up to date. Keeping it up to date may require frequent restarts which means a decrease in uptime duration.
Choosing a server technology actually means what platform will the software product that your company uses, require.
Say that:
- you use MS office, It is well integrated with Outlook.
- Since the enterprise messaging solution is very important, Outlook is the only excellent client of Exchange
- Exchange must run on a Windows Server.

What brought us to use Windows Server.:
- the infrastructure that my companies' customers chose
- the software development platform that my company chose
- the infrastructure that the software vendor (which we resell) chose
Red Hat Enterprise Linux (RHEL)
If you prefer MS technologies for development, Windows Server is very well. MS development SDKs bring many tools that ease integrations, there are many companies that are well integrated with MS and there are many talented developers experienced on MS technologies. On the other side, if you need just a server for open technologies and you think Windows Server has a GUI and that makes it easy to manage, consider this again. Even Windows Server has a complete GUI, it still requires a high level of experience to have a well-managed server.