Patch Processing

When you schedule a patch the following occurs:

1. The agent on the managed machine is told to start the update process at the scheduled time.
2. The patch executable is downloaded to the managed machine from where ever the File Source is set for that machine ID.
3. The patch file is executed on the managed machine using the parameters specified in Command Line. You should never have to set these switches yourself, but just in case, this capability is there.
4. After all the patches have been installed the managed machine is rebooted. When reboots occur for a machine ID depends on the Reboot Action assigned to that machine ID. Applies to Machine Update, Patch Update and Automatic Update. Reboots in response to an Initial Update always occur immediately and without warning the user.
5. The managed machine is rescanned automatically. It takes several minutes after the rescan is complete for this data to show up on the VSA. Wait several minutes before checking the patch state after a reboot.

   Note: If you schedule multiple patches for installation on the same machine, all the patches are installed at the same time. After all the patches have been installed the machine reboots once. This technique saves time and reboots.

   Note: Service packs are always installed separately. If you are installing a service pack with other patches you will see a reboot after the service pack install and then another single reboot after all the other patches are installed.