Greetings everyone! We have an organization that requires 120 computers to be set up. Here are the objectives we aim to achieve:
(https://i.ytimg.com/vi/XhkfpSQ62RE/maxresdefault.jpg)
1. All computers should be connected to the ActiveDirectory domain
2. We need up to 10 shared folders within the organization, accessible based on AD permission levels
3. Our PHP website needs to run on IIS while the web application will run on ASP.NET
4. We want to distribute the internet through either Kerio or SOUTH
We plan to use Windows Server 2016 as the operating system. However, we are faced with a challenge: our budget is limited to $1K. In light of this, we are considering two options:
Option one is to opt for a regular system unit with core i7, 16GB RAM, and a 2TB HDD. How long will this system unit last?
Option two is to use HP server products, which come with Xeon E5 CPU, 8GB RAM, and a 1TB 3.5" HDD. However, will the 8GB RAM be sufficient for our needs? Which option should we choose?
Considering budget constraints, a regular system unit seems like a more viable option. However, we are concerned about how long it will last. If we eventually have to replace it with a server, the cost of components such as PSU and RAM will be astronomical for our organization.
Server equipment is significantly less performant than alternatives for the same cost, but is more reliable. You don't need to spend money on an i9 if an i7 is sufficient for your purposes. Does your organization permit the purchase of licenses for AD and other software for 100 pieces, both on the server and workstations?
Consider using NAS4Free, a special distribution with web management that offers features like AD via Samba and a file server. You can easily set up the server through the web panel. If you require more advanced features like file deduplication, at least 4GB (preferably 8GB) of RAM is recommended, but 2GB should suffice. An old i5 processor from early generations is also suitable.
It's not advisable to mix a firewall and data storage server. Instead of Kerio, try pfSense - another specialized distribution with web management. Lastly, this server will suffice even for users who find it difficult to use weak and outdated hardware.
With this budget, it's difficult to purchase a server license, but hardware is an option. However, if you require a domain, a server OS is necessary. If the budget only covers hardware and not licenses, it's better to hire two system administrators and use Hyper V or burnt VMware to manage infrastructure.
The critical aspect in this case is having enough memory. Interestingly, we've been running two core i7s with 32GB of RAM for four years without failure (based on the logs). They support AD, files, and PHP sites and cost less than $1k combined.
For hardware, my advice is to go for branded towers that can support added RAM over time. While a regular system technician is acceptable, the hardware's viability decreases significantly with 24/7 use.
When it comes to software, use ESXi on the hardware and create virtual machines within it. This way, you can run a router (e.g. RouterOS or pfSense, and even Kerio) and domain controllers with the servers appearing separate.
If you want a free replacement for ActiveDirectory, consider ClearOS which has AD, email, and file capabilities. However, if this bundle (i.e. ActiveDirectory on Linux) fails, it will be challenging to restore.
The software server is used to accomplish the following tasks: storing public data in one place, facilitating flexible access settings, and enabling the smooth operation of the office. This way, employees can use work information and dоcuments without duplicating them on their computer. In larger companies, it's challenging to provide expensive laptops or desktops for every employee, so purchasing a server is more cost-effective. The server can perform tasks independently, and the system administrator can solve problems remotely.
On the other hand, hardware servers are useful for specialized calculations, setting up access to confidential information, and running programs that require high resources. They are used for continuous processes in large businesses, providing fault tolerance and optimizing work.
When choosing between a PC and a server, consider the size of your business and the tasks that need to be accomplished. For smaller businesses, a PC might suffice, but for larger companies with higher turnover, a server is a better option. Servers have the added advantages of higher fault tolerance, optimized work, and reduced costs. Ultimately, variability allows users to make choices based on their unique needs and goals.
Indeed, a server versus a regular system unit is a difficult choice that depends on many factors. These include budget constraints, performance requirements, server reliability, and longevity. Both options you presented have their advantages and disadvantages.
Option One:
A regular system unit with a core i7, 16GB RAM, and a 2TB HDD will perform well for small to medium-sized workloads and can certainly manage the 120 computers you have. Thanks to the higher memory, it will be better at handling memory-intensive tasks, including running virtual machines or several applications concurrently. The 2TB HDD provides ample storage capacity for your shared folders.
However, the lifespan of such consumer-oriented hardware typically isn't as long as server-grade hardware. Computers, especially those that are running continuously under load, can experience component failure over time. It's hard to estimate exactly how long such a system would last. But under optimal conditions (proper ventilation, regular maintenance, etc.), it might last for 4-6 years.
Option Two:
A server platform with a Xeon E5, 8GB RAM, and a 1TB 3.5" HDD will be more robust and reliable, meant to be used for heavy-duty, continuous server workloads providing higher stability and longevity; they can typically last much longer than consumer-grade hardware. Xeon processors are designed specifically for multi-core tasks, security, and virtualization; therefore, they might increase your PHP site's performance and ASP.NET application over the i7.
However, the 8GB RAM could be a limiting factor depending on how memory-intensive your workloads are. Windows Server 2016 requires a minimum of 2GB to run, and performance improves significantly with more RAM. If you're running multiple applications, you may find that 8GB is insufficient.
One potential solution would be to start with Option Two and upgrade the RAM later if you experience performance issues. This would provide you with the stability and longevity benefits of server hardware while offering a potential workaround for the limited RAM issue. However, keep in mind that upgrading the server later with additional RAM will add up to the costs.
It's also important to note that when distributing internet via Kerio or SOUTH, the server's network card quality and speed will be crucial, and server hardware usually comes with better network cards designed for continuous load.
Considering your budget constraints, the primary decision will depend on how critical it is for your server to be always operational and how intensive your computing tasks are. If possible, seek the assistance of a professional IT consultant to better analyze your specific needs.
If you're expecting to grow more considerable over time, further than 120 computers, it's likely a good idea to tend more towards server-grade hardware as that'll offer much more longevity as well as scalability. While the 8GB RAM HP server would be sufficient for your initial needs, it likely won't be enough if you plan on growth and/or adding more applications/services to the server.
When it comes to costs, even though server hardware is typically more expensive than consumer hardware, in the long run, it may prove to be a more economical decision due to its durability and stability, minimizing downtime and resources spent on maintenance.
As for managing the budget, there are potentially several ways to navigate this tricky area:
Consider buying refurbished/used servers: Refurbished tech can be a great way to get more for your money, especially since server-grade hardware is designed to last.
Leverage virtualization: By using a hypervisor like VMware ESXi or Microsoft's Hyper-V, you can run multiple virtual servers on a single set of hardware, maximizing your use of resources. This could allow you to start with minimal hardware and scale up later as needed - you could even run multiple servers on one machine, for instance, a domain controller, a dedicated file server, etc.
Re-evaluate your needs: Do you really need Windows Server 2016? Linux-based servers could offer a budget-friendly alternative. They are free and many include robust server functionalities.
Cloud-based solutions: Depending on your needs and internet connectivity, it may also be worth considering cloud solutions. Some organizations find that cloud services are a more cost-effective and flexible way to meet their IT needs. Companies such as AWS and Azure offer robust server environments that can be upgraded or downgraded according to your needs, thus providing flexibility and potentially reducing costs.
The information provided about the two options suggests that this choice is not ideal. The main issue seems to be bottlenecks (limited RAM on servers and longevity concerns with consumer-grade hardware) in both alternatives. Given the budget constraints and specific organizational needs, here are some additional recommendations that might be worth considering:
Leasing Hardware:
This can be a cost-effective method for some organizations. By leasing server-grade technology, you avoid the significant upfront costs of buying it outright. While this does essentially add a new ongoing cost, it can be easier to budget for. Furthermore, leasing contracts often come with provisions for regular hardware updates, ensuring your organization is always working with reasonably current technology.
Investment in critical parts:
If you decide to stick with the more consumer-orientated hardware, concentrate on the parts with the largest impact on lifespan and that are hardest to change later. For instance, power supply units (PSUs) in cheaper units can be less reliable. Here, investing in a good quality PSU upfront may extend the life of the system. The same with a good cooling solution—it can significantly improve the systems' longevity.
Split the Load:
If you adopt multiple smaller servers (or consumer-grade systems) rather than one large one, you can split your roles across multiple machines—dedicate one to network and internet management (Kerio or SOUTH), another to Active Directory (AD), one to file storage, and one to your webserver (IIS with PHP and ASP.NET). This way, you evenly distribute your applications, which can lead to smoother operation overall and provides some redundant capability if one part fails.
Upgrading a Server Later
If you opt for the server but find that 8GB RAM isn't sufficient for your needs, you could consider adding more in the future. Though this is an added cost, it's one you can budget for and plan as an upgrade rather than needing it upfront.
Look into cloud or hybrid solutions:
It may be possible to save on initial costs by using a combination of in-house hardware for certain tasks and cloud-based services for others. For example, shared folders and website hosting can be efficiently done in the cloud. In contrast, on-premises servers can handle Active Directory and network management. Cloud solutions generally come with the benefit of easy scalability and off-site redundancy.