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

Create a technical support case if you need further support.

Creating and configuring an MSI OfficeScan (OSCE) client installation package for fresh installations and upgrades

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

This article demonstrates how to create a single MSI OSCE client installation package for OSCE clients' fresh installations and upgrades, then allow users to register these OSCE clients to different specific OSCE servers.

Details
Public

To create and configure a single MSI OSCE client installation package:

  1. Do either of the following:
    • For OSCE 10.6 Service Pack (SP) 3, apply Hot Fix Build 5415 on the server machine where the MSI package will be created.
    • For OSCE 11.0 and later, the feature has been merged, so there is no need to apply the hot fix.
  2. Open the Ofcscan.ini file in the \PCCSRV\ folder of the OSCE server A.
  3. Add the following key under "INI_CLIENT_SETUP_SECTION" and set its value to "1":

    [INI_CLIENT_SETUP_SECTION]
    ForceRefresh=1
    BypassServerChecking=1

    Where:

    ForceRefresh=1 will make the OSCE client register to the new server from which the client package was created.
    BypassServerChecking=1 enables the client to launch a package created from another OSCE server.

  4. Register the OSCE clients to different specific servers by adding the following keys under "INI_CLIENT_SETUP_SECTION" and assigning the correct values:

    [INI_CLIENT_SETUP_SECTION]
    AssignedServerNumber= <total number of Assigned Servers>
    AssignedServer1=[ClientIPRangeStart],[ClientIPRangeEnd], [Server1][:Port][\Domain1\Domain2]
    AssignedServer2=[ClientIPRangeStart],[ClientIPRangeEnd], [Server2][:Port][\Domain1\Domain2]
    ...
    AssignedServerX=[ClientIPRangeStart],[ClientIPRangeEnd], [ServerN][:Port][\Domain1\Domain2]

  5. Save the changes and close Ofcscan.ini.
  6. Create the MSI installation package.

    If you are upgrading clients using the MSI package and the upgraded clients need to be moved to a specified server, manually add the following registry key. Otherwise, proceed to the next step.

    Path:  HKLM\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.\
    Key:   SupportsAssignedServer
    Type:  REG_DWORD
    Value: 1

  7. Install or upgrade the OSCE clients using the MSI package.
 

- The "AssignedServerNumber" key accepts any integer number up to 1000.

- The "AssignedServerX" key allows users to specify a certain IP range of clients that should be registered to the assigned server.

- If the domain is not specified, the client will be registered to the default domain of the server.

- Make sure to put ''[ServerN][:Port][\Domain1\Domain2]'' on the same row with '[ClientIPRangeStart],[ClientIPRangeEnd]'.

- "ServerN" can be assigned an IP address or a hostname of the server.

- If you use the IP address of "ServerN", make sure you can ping the IP address of ''ServerN'' from the OSCE client machine.

- If you use the hostname of "ServerN", make sure you can ping the hostname of ''ServerN'' from the OSCE client machine.

- If the OSCE server A is the 11.0 version or later, Server1, Server2…Server N are also v11.0 or a later version, so make sure they use the same certificate during server installation (OfcNTCer.dat). If not, the client will fail to communicate with the new server.

Premium
Internal
Rating:
Category:
Configure
Solution Id:
1113713
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.