All the other products I have used in the past OS2 servers, Novell Netware, Banyan Vines etc don't show up in the search list, which i guess goes to show that the best wins.
I've worked with several network device vendors in my 10+ years of being in the industry and my favorite continues to be Cisco IOS. Overall, Cisco IOS tends to be the most stable, the most intuitive, has the best TAC support, and has the best knowledge base articles and white papers.
Windows is well-suited for environments where caretakers are not as technical as they are in larger environments. It is also well-suited for small environments where a small number of server instances can provide a complete enterprise management solution, including directory services (AD), networking services (DHCP, DNS), file server services, printing, and hosting of applications that the enterprise relies on. It is also fairly good at providing hybrid-cloud support (most especially with Azure).
By this point, there are several "flavors" of the Cisco IOS such as XE, XR, and the standard Cisco IOS. While they are all fairly similar, there does exist syntax differences between them. It would be ideal if at some point in the future, Cisco is able to unify all of them into one standard operating system which would use the same syntax across all platforms.
While overall Cisco does a great job of QA'ing their IOS, no matter the release, there's always some minor bugs. I think it's important that Cisco continue to pour resources into their QA team to test their software.
While I'm very familiar with the graphical readouts of "show processes cpu history" I would love for Cisco to eventually find a more intuitive way to display this data. I can't begin to count how many times I've had to teach more entry level (and even mid level) engineers how this graph is interpreted.
I do wish that Cisco had something similar to Juniper's "commit check" or "commit confirmed". This helps validate the changes you're about to apply, and catch errors, so that you have a better idea of the impact of the change.
Microsoft needs to minimize the update frequency by making the product more secure. It can become very exhausting trying to keep updated if you don't have a dedicated support team. It can become challenging where the business is unable to allow downtime for reboots as part of the update process.
Prone to security and audit vulnerabilities.
The operating system needs more CPU and memory resources compared to other options such as Linux.
Understanding the licensing model can be abit confusing.
Comes with a standard firewall, but not the most secured one available. Would suggest using a more secured firewall as part of your antivirus software.
Due to the number of vulnerabilities and the operating system being a target for hackers, anti-virus software is a must.
I've carefully reviewed the servers and services currently running on Windows Server 2012, and given the opportunity would renew them as is going forward. There are two systems I currently have in place, one is a very large Linux implementation for a large ecommerce site, and one is a very large backup solution front ended by FTP servers running Linux. Neither are well suited for Windows, but the overall network infrastructure is and will be Windows Server for the foreseeable future.
The data that Cisco IOS is able to provide is extremely relevant, it's fast, and it's intuitive. I also love that you're able to leverage things like macros or EEM scrips to run multiple commands at once. This is especially useful when you have more junior or entry level engineers in your environment and you want to provide them with a "shortcut" by having them type a single command to execute multiple commands.
There are simply too many different parts of Windows Server to make it a cohesive piece of software. While some of the newer features found in Windows Server 2012 and 2016 have nice UIs that are logically laid out, there are enough parts of the system that is still based on old code with clunky UIs and confusing options to make Windows Server a particularly user-friendly experience.
Microsoft's support is hugely wide-ranging from articles online to having to contact them directly for the more serious issues. In recent years when I have contacted them directly, I have found the support o be excellent as I have found myself connected to very knowledgeable people in the field in which I needed the support. The online support available is vast and I tend to find most of the time that there is always someone out there who has had the same issue as me in the past and knows something about how to resolve it! This is the advantage of using industry standard and long-established systems such as Windows Server.
Make sure that you have detailed processes in place for every server instance you plan to install/upgrade, if possible get the base OS loaded and Windows Updates applied ahead of time, and if using a VM take a snapshot prior to installing each role, as well as along the way.
We have found other Cisco software to be filled with added functionalities as compared to iOS. New NCS software has certain programmability features that are advantageous to legacy iOS software but are more complex to use for some users. Hence, we still have most areas of the network that functions using iOS software.
I didn't use any other system which gives the same functionality and I am not aware of any. The full integration between all components and especially the ability to integrate mail via Exchange or even via a hybrid setup with the Ofice365 cloud, including the ability to directly manage the cloud from the server, using Power Shell, is something I didn't see anywhere else.
