How to install WSUS server tips on Hyper-V virtual machines _hyper-v

As many businesses continue to reduce the use of physical servers, a frequently mentioned problem follows: Is it a good idea to virtualize Windows Server Update Service (WSUS) servers? Simple answer: Yes. This article describes how to run WSUS in a Hyper-V virtual machine.

Can WSUS run in a virtual machine?

Word, can run. If you plan to run WSUS virtual machines on Hyper-V, you will not normally be forced to run WSUS on the Windows Server 2008 R2 operating system. To be on the safe side, you need to deploy WSUS 3 SP2. As a general rule, WSUS before SP2 does not work fully with Windows Server 2008 R2, nor does it help manage Windows 7 clients.

What is the easiest way to virtualize a WSUS server?

If you are currently running WSUS 3 on a single physical server, then I would recommend a migration upgrade. To do this, build a virtualized WSUS server and configure it to be exactly the same as your physical WSUS server, and finally synchronize. Once the synchronization process is complete, reconfigure the virtual WSUS server into an autonomous stand-alone machine. Then, you can deactivate the physical WSUS server.

This approach provides two main advantages. First, it makes it easy to upgrade the operating system of a WSUS server if it is necessary to upgrade. Another advantage is that this approach provides a much shorter downtime than a standard physical machine to a virtual machine (P2V) migration, because the physical WSUS server continues to serve the user while your virtual WSUS server is deployed.

What features can I get from a virtualized WSUS server?

A single WSUS server can handle up to 25,000 clients. However, if sufficient resources are configured, and SQL Server is running on a separate server (physical or virtual server). Some enterprises use multiple front-end servers, so they can gain more powerful functionality.

What are the ways to let WSUS have fault-tolerant mechanisms?

In a physical server environment, WSUS ensures fault tolerance by eliminating any single point of failure. You typically need to build a Network Load Balancing (NLB) cluster to provide high availability for WSUS servers. Of course, WSUS relies on SQL Server, and the first way to ensure that SQL Server has a fault-tolerant mechanism is to create an SQL Server cluster with failover mechanisms.

While it is possible to re-establish this high-availability architecture in the Hyper-V infrastructure, it is often considered a better idea to build a Hyper-V cluster. If your host server is clustered, it is unnecessary to implement a cluster of WSUS servers and SQL Servers (at least from the point of view of fault tolerance).

If the Hyper-V host is not using cluster technology (and creating a Hyper-V cluster is not a choice anyway), then I would recommend letting go and building a cluster architecture for virtualized WSUS and SQL Servers. However, you must make sure that you do not put multiple WSUS or SQL Servers on a common Hyper-V server, as this will offset the benefits of clustering technology for WSUS and SQL Servers.

What kind of network bandwidth do I need?

There are no predetermined rules for providing network bandwidth for virtualized WSUS servers. Keep in mind, however, that there are a number of uncommon problems that can arise as a result of insufficient bandwidth. I recommend that you try to have a physical network adapter that is dedicated to your virtual WSUS server. If you are forced to share a single network adapter with multiple virtual servers, use the Network monitoring tool to ensure that the physical network connection is not congested.

If network congestion becomes a problem, remember that WSUS can be restricted at the server level or at the client level by using assembly policy settings. You can find the client restriction policy in the Assembly policy Object Editor (Assemble Policy object Editor), Access computer Configuration (Computer Configuration) > Administrative in turn Templates (Administrative Templates) > Network (Network) > Background Intelligent Conveying Service (Background Intelligent Transfer Service), you can find this setting.

Is there anything special about SQL database?

It is not usually mandatory to run SQL Server on a separate machine (physical machine or virtual machine), so you can assign resources directly to the database server. I also recommend that you run the cleanup Wizard (Cleanup Wizard), defragment the database, and run it once every few months. Doing so can help the database run at its best, which is extremely important in virtualized environments.

Another point to keep in mind is that SQL servers is often an input/output-intensive operation. Therefore, if you are going to virtualize your SQL Server, consider using a dedicated physical storage system so that the input/output load from SQL does not affect other virtual machines.

The above is the entire content of this article, I hope to help you learn, but also hope that we support the cloud habitat community.