Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

"Unable to upgrade the OfficeScan client…" appears when using the client install package to perform an upgrade

    • Updated:
    • 17 Oct 2016
    • Product/Version:
    • OfficeScan 10.6
    • OfficeScan 10.6
    • OfficeScan 11.0
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • N/A N/A
    • Windows 10
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2003 Compute Cluster Server
    • Windows 2003 Datacenter 64-bit
    • Windows 2003 Datacenter Server
    • Windows 2003 Datacenter Server Edition 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Enterprise Server
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2003 Standard Server Edition
    • Windows 2003 Standard Server Edition 64-bit
    • Windows 2003 Storage Server
    • Windows 2003 Web Server Edition
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2008 Datacenter
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Datacenter Server
    • Windows 2008 Datacenter Server Edition 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Enterprise Server
    • Windows 2008 Enterprise Server Edition 64-bit
    • Windows 2008 Server Core
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Standard Server Edition
    • Windows 2008 Standard Server Edition 64-bit
    • Windows 2008 Storage Server
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012 Datacenter
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Server R2
    • Windows 2012 Standard
    • Windows 2012 Standard R2
    • Windows 2012 Web Server Edition
    • Windows 2016 Server Core
    • Windows 2016 Server Datacenter
    • Windows 2016 Server Standard
    • Windows 7 32-Bit
    • Windows 7 64-bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary

The following error message appears when you use a client install package to perform an upgrade:

Unable to upgrade the OfficeScan client. The installation package was created from an OfficeScan server that does not manage the client installed on this computer.

Details
Public

As the error states, the client package was created using another Officescan Server. By default, the Client Package will run a check to determine if the target client reports to the same server where the package was created. If it does not, the upgrade process will be terminated.

To prevent this, the Server Checking routine must be disabled before creating the client package.

  1. On the OfficeScan server, go to the ..\PCCSRV\ folder and open the ofcscan.ini file using a text editor.
  2. Under [INI_CLIENT_SETUP_SECTION], add the following parameter and value:

    BypassServerChecking=1

  3. Save and close the file.
  4. Create a new Client Package
  5. Use this to new package to upgrade the clients
 
The upgraded clients will still report to their old OfficeScan server.
If you want the upgraded OfficeScan client to report to the new OfficeScan server from where the client package was created:
  1. On the OfficeScan server, go to the ..\PCCSRV\ folder and open the ofcscan.ini file using a text editor.
  2. Under [INI_CLIENT_SETUP_SECTION], add the following parameters and their values:

    ForceRefresh=1
    BypassServerChecking=1

     
    "ForceRefresh=1" will make the OfficeScan client to register to the new server after upgrading.
    "BypassServerChecking=1" will enable client to launch a package from other Officescan server.
  3. Save and close the file.
  4. Recreate the Client Packager setup file and deploy this to the clients.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1056070
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.