Server Configuration > Service Packs and HotFixes > Service Pack Policies
 
Service Pack Policies
Policies controlling service pack distribution are found in:
installdir/config/policies/servicepack.policy
These policies specify the minimum and maximum version of the client that is allowed to connect to this server. The default behavior is to follow the published client/server compatibilities.
As administrator, you can make service packs mandatory for connecting clients by specifying the minimum version of the Integrity Lifecycle Manager client that is allowed to connect to the Integrity Lifecycle Manager server. A client that meets or exceeds the specified minimum (and maximum) is allowed to connect to the server.
Users with clients that do not meet the specified version are prompted to download the required service pack before they can continue with any other operations. Users with clients that meet the minimum allowed service pack, but exceed the maximum, are prompted to roll back the latest service pack before they can continue with any other operations.
* 
The client Help > About dialog box displays the current service pack level. Service packs are downloaded to the client ICServicePack directory located in the user’s home directory.
The following table outlines all available policy options (configurable and non-configurable) in the servicepack.policy file:
* 
Starting with Integrity 10.1, to determine the correct version number to use in the service pack policies, see the Service Pack Policy Properties section in the server, client or agent log file.
Service Pack Policy Option
Description
mksis.servicepack.minClientBase=
Specifies the minimum base version of the Integrity Lifecycle Manager client that can connect to the Integrity Lifecycle Manager server. Follows the format: <major>.<minor>.<subminor>
For example, 10.0.0 means that to connect to the Integrity Lifecycle Manager server, users must have at least client 10 installed.
* 
The base version number is identified in the Agent/ClientBase property in the server, client or agent log file.
mksis.servicepack.minClientSP.<major>. <minor>.<subminor>=
Specifies the minimum service pack version of the Integrity Lifecycle Manager client that can connect to the server. Follows the format:
<major>.<minor>.<subminor>=<servicepack>
For example, 10.0.0=001 means that to connect to the Integrity Lifecycle Manager server, users must have at least Integrity Lifecycle Manager server 10 SP1 installed.
* 
• The <major>.<minor>.<subminor> version number is identified in the Agent/ClientBase property in the server, client or agent log file.
• The <servicepack> version number is identified in the Agent/ClientSP property in the server, client or agent log file.
mksis.servicepack.maxClientBase=
Specifies the maximum base version of the Integrity Lifecycle Manager client that can connect to the server. Follows the format: <major>.<minor>.<subminor>
For example, 10.0.0 means that to connect to the Integrity server, users cannot have a base version higher than Integrity server 10 installed.
* 
The base version number is identified in the Agent/ClientBase property in the server, client or agent log file.
mksis.servicepack.maxClientSP.<major>. <minor>.<subminor>=
Specifies the maximum service pack version of the Integrity Lifecycle Manager client that can connect to the Integrity Lifecycle Manager server. Follows the format:
<major>.<minor>.<subminor>=<servicepack>
For example, 10.0.0=001 means that to connect to the Integrity Lifecycle Manager server, users cannot have a service pack version higher than Integrity client 10 SP1 installed.
* 
• The <major>.<minor>.<subminor> version number is identified in the Agent/ClientBase property in the server, client or agent log file.
• The <servicepack> version number is identified in the Agent/ClientSP property in the server, client or agent log file.