Rolling Back Client-side Service Packs
Integrity Lifecycle Manager clients are automatically instructed to roll back client-side service packs when the corresponding server-side service pack is rolled back if the client-side service pack exceeds the server’s maximum service pack policy. For more information, see
“Service Pack Policies”.
To allow all connecting clients to roll back without performing a server rollback, you specify an earlier service pack version in the mksis.servicepack.maxClientSP policy. Specifying the earlier service pack version allows the rollback for all connecting clients.
To roll back a service pack on an individual Integrity Lifecycle Manager client, users can run the following command at the root of the Integrity Lifecycle Manager client installation directory:
PatchClient lib/patchrollback/servicepacknumber.zip
where servicepacknumber is the number of the service pack file you want to roll back.
The following are key considerations for rolling back client-side service packs:
• To connect to the Integrity Lifecycle Manager server, the Integrity Lifecycle Manager client must meet both the minimum and maximum directives set in the servicepack.policy file. If the client meets the minimum but not the maximum, users are instructed to roll back.
• Client-side service pack rollbacks are triggered only when a client connects with a service pack that exceeds the maximum allowed by the server's policy, and the user agrees to roll back. You can edit the policy file to trigger client rollbacks independently of server rollbacks.
You should remove the client service pack from the Integrity Lifecycle Manager server download directory so that clients that just rolled back are not prompted to download that service pack again.