|
|
From the web UI, you can deploy patches to a single machine or to a number of machines. Before commencing the actual deployment, PatchQuest checks if the patches selected are already downloaded and available locally in the PatchQuest server. If not, a download request is first initiated and the patches in question are downloaded from the vendor websites via the internet. Once the patches are available locally, they are then copied to the remote systems and executed. The transfer of the patches from the PatchQuest server to the remote systems is via secure means (https). Therefore tampering of patches and installation of inappropriate hotfixes is completely eliminated.
Note for Red Hat Linux : Deployment of Red Hat Linux patches is not supported currently. You will only be able to add and scan the Red Hat systems.
After you have added and scanned the system, you can deploy all the missing patches in the selected systems, from Systems tab and System Groups tab. Choose system from the list and click on the 'Deploy All Missing Patches' button. This will take you to a view which will display all the missing patches for the systems selected. from here, click on the 'Deploy Selected Patches' at the bottom of the screen.
After you have added and scanned the system, you will be able to see the available and missing patches in the Scan Result view. You can select the missing patches and click on the 'Deploy' button.
Installation of patches on multiple systems, can be done from the Patch Information view. Select the patches you wish to install and click on the 'Deploy' button. This will display a screen wherein you will be able to see a list of systems, in which a selected patch is missing and another list in which it is installed. Note that this list is based on the latest scan results in PatchQuest.
On clicking the Deploy button, you will be led to a patch deployment configuration screen. From here you can opt for :
This option comes up in the Patch Deployment configuration screen only when there are some MS Office patches in your selected patch deployment list. There are 2 options to deploy MS Office patches, that you can choose from namely, using a CD or synching with an AIP . Refer to 'Deploying MS Office Patches' for more details.
Rebooting
PatchQuest automatically determines if rebooting the system is required after patch deployment, for the installation to complete successfully. The radio button in the rebooting options is set accordingly. You have the provision to change the options, but it is best advised to let the configurations remain.
If the reboot after deployment option is selected, you further have options to configure the time interval to wait before the system reboots itself. You can also force the applications to close automatically.
If you wish to bring the system to a halt after patch deployment has been completed, you can choose the 'Shutdown after deployment' option.
If the shutdown after deployment option is selected, you further have options to configure the time interval to wait before the system shuts down. You can also force the applications to close automatically before shutting down.
Custom Message Display
After the deployment is complete, you can configure a custom message to be displayed in the affected system. The newly configured message is persisted in this screen and the same message is available when you revisit this Patch Deployment configuration screen.
E-mailing Deployment Status
The status of the deployment can be intimated by e-mail to any e-mail address (ideally the administrator's e-mail ID) that is configured here. Enter any number of e-mail addresses in the text-field provided; separated by comma. A report will be sent to those IDs when the deployment task is completed.
|
|