The most common method of distributing updates is to have one server receive updates from the Microsoft HTTP server and then share those updates among the rest of the servers (the "spoke" servers) in your environment. After one server receives an engine update, it can share that update with any other server whose network update path points to it.
Configuring servers to distribute and receive updates
You must configure both the hub and the spoke servers before distributing updates.
To prepare a server to act as an update hub, you first need to establish a Windows® share for the Engines directory (which is usually in the Antigen installation directory).
Next, enable the Redistribution Server option in the Scanner Updates section of General Options on the chosen hub server. This configures Antigen to save the two most recent engine update packages in the engine package folder instead of the usual single engine package. Antigen will also download the full update package rather than performing an incremental update. The multiple engine packages allow the spoke servers to continue pulling updates from the redistribution server while a new update is being downloaded.
Then, enter the UNC credentials.
To configure UNC credentials
-
Select General Options from the SETTINGS shuttle.
-
Select Use UNC Credentials in the Scanner Updates section.
-
In the UNC Username field, enter the name of a user with access rights to the UNC path. Also enter the UNC Password.
-
Click Save.
After the hub server has been set up, configure the spoke servers to point to the shared directory by entering the hub's UNC path (\\ServerName\ShareName), in the Primary Network Update Path field of each of the spoke servers.
Note: |
|---|
|
The use of static IP addresses within the update path is neither recommended nor supported.
|
Example: Server Ex1 receives its updates automatically from the Microsoft HTTP server. Ex1 has Antigen installed in C:\Program Files\Microsoft Antigen for Exchange, and you have created a share, called AdminShare, that begins at the Engines directory. Another server, Ex2, will get its updates from Ex1, by using \\Ex1\AdminShare as its primary network update path.