Upon installation of an RU7 (11.0.7000.975) Symantec Endpoint Protection Manager (SEPM), or following an upgrade of a SEPM to RU7, it is observed that the RU7 client installation packages are listed as version 11.0.7000.0 within the Install Packages section of the SEPM. The expected version number would be 11.0.7000.975. Since 11.0.7000.0 is not listed as an official release version for the Symantec Endpoint Protection (SEP) product, this leads to the question of what version will be installed when using an exported installation created using one of the 11.0.7000.0 packages?
This is a known issue, and represents a
design issue with the LU packages since early days of SEP 11. It unfortunately cannot be changed.
The SEP version 11.0.7000.0 listed in the SEPM means that the SEPM received the client packages via Liveupdate. This had to occur prior to the upgrade of SEPM.
Simply export the 11.0.7000.0 packages and deploy as normal. The end result will be that clients are installed with the 11.0.7000.975 version.
To verify, please export an 11.0.7000.0 package as a non-single.exe. Examining the setup.ini file within the package contents, the correct version of 11.0.7000.975 will be listed in the 'ProductVersion=' field.
Also, there is a note is placed in our readme.html file on the root of the DVD:
"The last number of the client install package update version number appears as a zero in the Symantec Endpoint Protection Manager console when downloaded from a LiveUpdate server
If you configured LiveUpdate settings in the Symantec Endpoint Protection Manager to download client software update packages, you see that the last numeral of the package version number appears as a zero in the Symantec Endpoint Protection Manager console. For example, if the package version number is 11.0.2000.1423, the version number that appears on the Client Install Packages page is 11.0.2000.0. Once the package is deployed to the clients, you can see the package's complete version number in the About box on the clients."
This is scheduled to be fixed in 11.0 RU7 MP2
To reproduce this issue, use with following steps.
1) Install SEPM RU6MP3
2) Run liveupdate, wait for its success, SEPM will download RU7 package (11.0.7000.0) to console
3) Upgrade to SEPM RU7
4) SEPM will have RU7 package (11.0.7000.0) instead of (11.0.7000.975) on console
This is said to be by design.
Imported Document ID: TECH173530
Subscribing will provide email updates when this Article is updated. Login is required.