企业信息化基础架构详解研讨.pptVIP

* Let’s take a look at how SMS 2003 works. It should be noted that in contrast to SUS which uses a ‘pull’ model, SMS uses a ‘push’ model to distribute patches to the target systems and then relies on the SMS clients on these systems to complete the installation. The SMS administrator, in a one-time event, downloads the Security Update Inventory Tool and/or the Microsoft Office Inventory Tool from the Download Center Web site. The administrator, in a one-time event, runs the inventory tool installer program on the SMS site server, which creates the necessary packages, collections, and advertisements for distributing the software update scan tools to the clients. Simultaneously, the installer program creates the program for the synchronization component on the synchronization host. The software update scan component packages replicate to distribution points in the SMS site, and from there to the target client computers. The scan component analyzes the installed and applicable software updates on the client computer. The information is converted to SMS hardware inventory data, and it propagates up the hierarchy along with the rest of the hardware inventory data. Note that the time it takes for the information to reach the site server depends on the scan component configuration, hardware inventory agent schedule settings, and site server load. The SMS administrator runs the Distribute Software Updates Wizard to view, evaluate, and authorize applicable software updates from the software update inventory data. The Distribute Software Updates Wizard downloads the source files for the specified software update from the Microsoft Download Center Web site, stores the source file in the specified package source shared folder, and creates or updates the necessary packages, programs, and advertisements for distributing the software updates to SMS clients. To every package the Wizard creates or updates, it appends an SMS program that contains commands to run the Software Update