Network Solution for Windows – Windows system, Linux system, Ubuntu server configuration tip

Use sus: on client: To configure Windows XP to use sus first you must enable Automatic Updates feature. In Windows XP, you open Control Panel, select System, select the next Automatic Updates. In Windows 2000 you open Control Panel, click Next to Automatic Updates.

You will see in the Properties of this feature. You will be the administrator, choose to update and download and install, assign them to users on specific machines. If you log into the system by the administrator you will see a notice at the bottom right of the screen display system to show you are download or install if you configure the update automatically, or automatically download and installation that you must perform after it failed and has been fully downloaded.

Update Download and installation: The process can be downloaded under the two bits are the number was about or to download displayed as bar drag shows% download system is. Number of Bits inspected on a network connection used to download from the site providing the patches, and this feature allows you to pause or stop, so after you perform the download again, then the system will check the number of bits have to download and continue to be, not download from the beginning because a lot of patches as a service pack to download such a long time and may in time that the system is turned off and boot Again, this is a feature in the Windows Automatic Update.

Installation process will start when the download is complete, if in the process of configuring the Automatic Update mode to you automatically install the system will inform the installation process is started if you choose not the installer will notify you need to install after the installation the system will require you need to restart the computer or not, this is an option you need to set up in Part 1 of this article.

Basic errors and how to overcome.

Use the settings in the Policy can control the process from download to install, as well as setting up the computer need to reboot or not. Also an important issue that you must configure exactly the sus server to ensure only the update package is provided for system clients only. On the other hand you must also ensure that the sus always update the latest patches from Microsoft.

A common problem is the sus your standing behind a firewall system and synchronize data with Microsoft’s server is not achieved, so you need to know any open ports and the site is so necessary to synchronize data between servers and server sus supply of patches by Microsoft.

You need to open port 80 to the following addresses:

1. http://www.msus.windowsupdate.com
2. http://download.windowsupdate.com
3. http://cdm.microsoft.com

You can also have an error due to access bandwidth, such as access bandwidth is too low to download a large Service Pack (SP1 Windows Server 2003 – nearly 400MB). Then, the synchronized data will fail and this case you do not select the download that update.

If you are trying to overcome the errors between the client-side and sus server, you need to pay attention to edit the Registry you put in the parameters in the following key:

1. HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \
   CurrentVersion \ WindowsUpdate \ Auto Update \ DetectionStartTime
2. HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \
   CurrentVersion \ WindowsUpdate \ Auto Update \ LastWaitTimeout

You can also query the Windows Automatic Update Servie environment from command line by using the following command you can refresh this service is: not

1. Net stop wuauserv
2. Net start wuauserv

With the refresh will fix the error service not be provided to the client machine.

Monitoring system Client-Side.

Sus Automatic Update client and provided a few events are available in the system, for if the event say that the system will save the system event log, you can use it to analyze errors related to sus as well as Automatic Update clients. Here are the event and analyze the event.

Table 1: sus / AU Client Event Log Messages

Logs: Sus server will record the entire process synchronization as well as the servers try to connect to the servers providing the patches. The whole log can be accessed by the administrator in the sus through Web environment in the web environment as it is in

Autoupdate \ administration \ history-sync.xml

This log file records the synchronized data of times before, as well as the schedule of the next time, or the synchronization is complete or error occurred during the , as well as scheduled or can be made synchronous by the administrator.

On the client machine, necessary that all clients can use HTTP protocol to request from sus server with a file called wutrack.bin, including more information about the status of your client. with the following:

2004-02-09 09:09:41 192.168.0.121 – 80 GET / wutrack.bin
V = 1 & U = 63a9dfd44a7aca47ade26684ed5fe66a & C = iu & A = n & I
= & D = & P = 5.1.1677.2.0.1.
0 & L = en-US & S = s & E = 00000000 & M = & X = 031101050105756200 Whistler Control + + + Update Pack

In addition the system will also record the status of the update on the client system in the event introduced above, from which you can use multiple parameters in the log files to analyze errors can occurred, as well as how to overcome it quickly.

In part 3 of article I will introduce versions of its Windows Software Update Service and the superiority of the new version of WSUS.