#Install spiceworks on port 443 install
#Install spiceworks on port 443 license

When you link WSUS servers together, there is an upstream WSUS server and a downstream WSUS server, as shown in the 'WSUS Server Hierarchy' illustration below. Since you can synchronize one WSUS server with another WSUS server instead of with Microsoft Update, you need to have only a single WSUS server that is connected to Microsoft Update. You can create complex hierarchies of WSUS servers.

#Install spiceworks on port 443 license

The WSUS license agreement specifically disallows this. There are instructions for creating custom computer groups in Create the Computer Groups later in this guide.Дo not use WSUS to distribute updates to client computers that are not licensed for your organization. There is no limit to the number of custom groups you can create. If the testing goes well, you can roll out the updates to the Accounting group. Updates are approved first for the Test group. The Test group contains a small number of computers representative of all the computers contained in the Accounting group.

The 'Simple WSUS Deployment with Computer Groups' illustration depicts two custom groups named Test and Accounting, as well as the All Computers group. One benefit of creating computer groups is that it enables you to test updates. The Unassigned Computers group permits you to target only computers that have not yet been assigned group membership. The All Computers group enables you to target updates to every computer on your network regardless of group membership. You cannot remove computers from the All Computers group.

You can move computers from the Unassigned Computers group to a group you create. By default, when each client computer initially contacts the WSUS server, the server adds it to both these groups. There are two default computer groups: All Computers and Unassigned Computers. Computer groups enable you to target updates to specific computers. Using computer groupsД¬omputer groups are an important part of WSUS deployments, even a basic deployment. Other issues to consider when using a custom port for the WSUS Web site are discussed in 'Using the WSUS custom Web site' in Configure IIS later in this guide. If you use the custom Web site, remember to include the port number in the URL when you configure Automatic Updates to point to the WSUS server. If you use the custom Web site, you must also have a Web site set up and running on port 80 to accommodate updating legacy Automatic Updates client software. Alternate port numbers cannot be specified at setup time, but can be configured afterwards.

If you use a custom Web site, WSUS listens on portВ 8530. If you set up WSUS on the default Web site, WSUS listens for Automatic Updates on portВ 80.

#Install spiceworks on port 443 install

If there are no Web sites running on the server where you install WSUS, you can use the default Web site or a custom Web site. Automatic Updates must use the port assigned to the WSUS Web site in Microsoft Internet Information Services (IIS). Chaining WSUS servers together is discussed later in this guide.ДЄutomatic Updates is the client component of WSUS. You can configure multiple WSUS servers to synchronize with a parent WSUS server. If you are planning to use custom ports for this communication, you will have to open those ports instead. If there is a corporate firewall between your network and the Internet, you will have to open these ports on the server that communicates directly to Microsoft Update. All synchronizations after that should be significantly shorter.Д«y default, the WSUS server uses portВ 80 for HTTP protocol and portВ 443 for HTTPS protocol to obtain updates from Microsoft. Initial synchronization can take over an hour.