IBM AIX operating system is advanced with most features and also it's more reliable unlike Redhat Linux, Sun solaris, HP-UX and also we will have well support from the vendor if we run into any issues. IBM AIX is more user-friendly when compared to linux and easy to use so i …
I have been using IBM AIX for a longer time. The kind of confidence I have in IBM AIX as well as its support and super features has always given me many reasons to stick with it to run my business.
Like AIX, Red Hat Enterprise Linux is a very stable operating and designed for companies who don't want to be on the bleeding edge of Linux technology.
The only real comparable competitors to IBM AIX come from the Linux world. Linux is beginning to approach the reliability and stability of IBM AIX and is often a better choice. Linux also has a shorter update cycle with more significant leaps in functionality and feature sets. …
Standard Linux distributions which are used more as commodity servers do not offer the ease of scale and growth that we see with our Aix implementations. IBM owning the HW and SW portions of the stack allows for tighter integrations and better performance windows.
AIX is a more mature operating system than Linux and its stability reflects positively on this. Safe application handling and uptime are great positive features as well.
Windows is not even a choice on the availability front, and patching and there are huge concerns about …
When compared against Red Hat Linux or Microsoft Windows, IBM AIX is much more expensive. The flexibility of the Microsoft and Red Hat offerings give them an extreme advantage over IBM AIX. The TCO for IBM AIX is considerably higher than the other two. The ability to find …
Compared to other Unix-like operating systems, IBM AIX is the one with a solid roadmap into the future and is likely to stay around for a long time (it is over 30 years old and still being updated with new features and components all the time).
It is really all about application support. The only option we really have is Windows Server, and where we can choose we continue to use it for consistency as well as compatibility with the systems where we are forced to use Windows Server).
We've utilized docker and debian for very specific applications and they have been useful - overall Windows Server provides a better package. I would choose VMware ESXi over Windows Server for virtualization as it's far more reliable in our experience. I can't imagine using a …
There are plenty of other server solutions out there which may be better suited for certain tasks, but Windows Server is the way to get a Windows environment going. For simple setups, there are many alternatives, but often there are key features lacking, or a restriction on …
Windows Server is more cost-effective and skills are easier to find to support the products. The deployment and management of the product can be automated with Microsoft SCCM. In my opinion, Linux seems to be more secured but takes more time and effort to learn than Windows …
These are just very different products. They can all have the same functionality but the specific product knowledge with Linux is much higher. This slows down troubleshooting and can leave you with limited options for high end support. There are absolutely good use cases for …
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 …
For our more experienced users and for simple web apps we will go the RHEL route but with Windows Server such an industry standard the the ease of use of the GUI it just makes more sense for most applications that use it. It also generally has a lot more interoperability …
Linux is great, but support is harder to come by. You also need to pay linux admins more as it is a much smaller group of people that can support it. Windows is the industry standard with the most support available. Going with another platform just didn't seem to make sense …
I have some basic experience using various builds of Linux and have always found myself coming back to Windows. Perhaps after years of working with Microsoft products they all have a similar feel and configuration options. Microsoft products are my typical first choice where …
We have various servers or appliances that run on various flavors of Linux that do their jobs well, but we configure and manage them very lightly at the OS level. Most of the admin on these devices is sone inside the applications themselves. We don't shy away from new …
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 have used/administered several servers using systems like Ubuntu, Debian, and CentOS. While these systems are great in their own rights, you are typically using a command-line interface or shell in order to administrate the system. This requires a lot of commands to be …
For our purposes it came down to picking between Windows and Linux and at the end of the day we picked both. We use Windows for 80% of our server needs to run our Web, File, Print, DHCP, Internal DNS, Active Directory, SQL, Web and other windows based servers. We use linux …
Windows Server has become one of the industry standards for providing file and directory services for the majority of users because of the ease with which it interacts with the common desktop OS, as opposed to needing to provide esoteric support for users to be able to work …
About any linux distro can be setup to handle services that a Windows Server can do, except I have not personally found anything nearly as convenient of a replacement for Active Directory, Group Policy, or an RD Gateway. There are alternatives to those services, they just …
Windows Server is by far the easiest server option to get started with because they offer the same kind of interface with windows that most users are already familiar with. Plus, it's the most graphically friendly option, so it is easy to navigate. Lastly, it is the most …
We were comparing Windows Server with Hyper-V to VMware ESXI, and decided on Windows Server as we are primarily a Windows server/workstation shop, and the familiarity allowed us to spin up new Hyper-V servers quickly without much additional training required. We also have a …
We have used various flavors of Linux as it is the only other real competitor in the small to large business world. In most cases it is harder to find technical expertise in the Linux server world verse Windows Server. For this reason Windows has remained our go to operating …
Windows runs some applications better and is easier for junior admins and non-technical users to administer and get started with. It obviously does not run everything better, so other operating systems are preferable in some situations. Compared to OSs like RHEL, they both have …
Windows Server is the only one that has an upfront cost for licensing before hardware is considered. Windows Server is generally better suited for multi-faceted approaches; however, for just backups, TrueNAS and Synology are cheaper and just as good. For standalone services …
Windows Server is the most Enterprise/Business server around, easy to deploy and configure and to co-exist with other servers. Most if not every other server technology is usually very good for a very specific purpose but fail in the coexistence and integration when compared …
IBM AIX is a very powerful and extremely stable operating environment. It is well suited for applications that are business critical and cannot tolerate outages. It is best used to address large enterprise level application needs where stability and scalability are of paramount importance. IBM AIX is less useful for small enterprises.
If you have one user or 1000's of users (especially using Windows), Windows Server is a no-brainer! The only reason I would suggest going with a Linux server is if you have old hardware (Windows Server is more process intensive than Linux). But, Linux is open-source, so anyone can publish updates/security updates, but on the flip side, malicious people also have full access to Linux's codebase allowing for much easier writing of exploitations/viruses/malware/ransomware.
User and device management out of the box. Active directory is a proven system for doing this and works just as well as it always has.
ADFS providing integration into many third-party applications using SAML authentication. We use this heavily to make user experience as simple and straightforward as we can.
Local DHCP. It's another one of these systems that is very easy to setup and use out of the box and requires very little maintenance, if any. The system is almost unchanged throughout the years and so anyone with server experience can manage it.
Windows Server is extremely complex, and while newer versions have eased the initial setup process, setting up a server is still a very time consuming and difficult task.
The complexity of Windows Server also makes troubleshooting any problems that arise extremely difficult, both in tracking down the actual issue and then resolving the issue. Often times a problem can manifest itself in more than one way, making searching for the specific problem also difficult.
Windows Server is also very expensive, with complex and confusing licensing terms. In fact, Microsoft provides a 32-page PDF guide on Windows Server licensing, which is in and of itself dense and confusing to follow. To make matters more complicated, there multiple different version of Windows Server itself - Nano, Essentials, Standard and Datacenter edition, and each edition has different licensing terms. Licensing terms include items such as the physical processor's cores of the server, how many users will be accessing the server (called a CAL - client access license), and a plethora of other items.
Microsoft's support for Windows Server can be extremely frustrating at times. While Microsoft hosts a very active user forum, Microsoft employees who frequent those forums often provide only stock answers to questions (without actually reading the details) or no answers at all. For more in-depth - phone support can be quite expensive.
Upgrading a Windows Server from one major version to another (i.e. 2012 to 2016) is a frustratingly complex and dangerous procedure, as many things can go wrong during the upgrading, essentially breaking the entire setup. In fact, Microsoft doesn't even suggest doing an in-place upgrade, but to perform a backup of the existing server, doing a clean install of the new version, and migrating the information from the older version to the new version. In general, it is not even recommended to upgrade from one version to another as the risk significantly outweigh the benefits.
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.
AIX is robust, helps the systems administrator, is built to prevent easily made mistakes. If you are used to other variants of Unix (in particularly Linux) there is no steep learning curve to get started with AIX. You need to learn the intricacies of the operating system, but that is true for any new operating system. AIX has built-in tools for almost anything you want and has the AIX Toolbox (on the web) for tools that are not included with AIX by default, but can be installed. Installation of AIX is modular, you can select with components and features you want to have installed. Installation of additional components (and usually also removal of installed components) is easy and straight-forward.
Everything can (and should) be done through the easy to use/navigate GUI. There is no need for archaic command prompt use to administer the server. But, it is there if you have very specific needs for batch files, etc. that are not covered in the all extensive GUI.
It has been my experience that unless there is a flaw or bug with Microsoft Windows Server, you will have to pay extra for support beyond the support web site. That said, unofficial support on the thousands of technical websites makes self-help support readily available to any technician with an internet connection. Microsoft's support website is also fairly robust, but I find using a popular search engine often returns knowledgebase articles more quickly that Microsoft's search.
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.
Compared to other Unix-like operating systems, IBM AIX is the one with a solid roadmap into the future and is likely to stay around for a long time (it is over 30 years old and still being updated with new features and components all the time). Compared to many Linux variants, the AIX operating system is more robust, easier to manage and well-supported by its vendor.
Windows Server is more cost-effective and skills are easier to find to support the products. The deployment and management of the product can be automated with Microsoft SCCM. In my opinion, Linux seems to be more secured but takes more time and effort to learn than Windows Server. However, there are more Windows Server skills available in the job market.
