instpack
Client Packager creates an installation package that you can send to users using conventional media such as CD-ROM. Users run the package on the client computer to install or upgrade the OfficeScan client and update components.
Client Packager is especially useful when deploying the OfficeScan client or components to endpoints in low-bandwidth remote offices. OfficeScan clients installed using Client Packager report to the server where the package was created.
Client Packager requires the following:
350MB free disk space
Windows Installer 2.0 (to run an MSI package)
To create an installation package using Client Packager:
On the OfficeScan server computer, browse to <Server installation folder>\PCCSRV\Admin\Utility\ClientPackager.
Double-click ClnPack.exe to run the tool. The Client Packager console opens.
Select the type of package you want to create.
|
Client Package Types |
|
Package Type |
Description |
|
Setup |
Select Setup to create the package as an executable file. The package installs the OfficeScan client program with the components currently available on the server. If the target computer has an earlier OfficeScan client version installed, running the executable file upgrades the client. |
|
Update |
Select Update to create a package that contains the components currently available on the server. The package will be created as an executable file. Use this package if there are issues updating components on a client computer. |
|
MSI |
Select MSI to create a package that conforms to the Microsoft Installer Package format. The package also installs the OfficeScan client program with the components currently available on the server. If the target computer has an earlier OfficeScan client version installed, running the MSI file upgrades the client. |
Configure the following settings (some settings are only available if you select a particular package type):
Next to Source file, ensure that the location of the ofcscan.ini file is correct. To modify the path, click 
to browse for the ofcscan.ini file. By default, this file is in the <Server installation folder>\PCCSRV folder of the OfficeScan server.
In Output file, click 
, specify where you want to create the client package, and type the package file name (for example, ClientSetup.exe).
Click Create. After Client Packager creates the package, the message "Package created successfully" appears. Locate the package in the directory that you specified in the previous step.
Deploy the package.
Package deployment guidelines:
Send the package to users and ask them to run the client package on their computers by double-clicking the .exe or .msi file.
Send the package only to users whose OfficeScan client will report to the server where the package was created.
If you have users who will install the .exe package on computers running Windows Vista, Server 2008, or 7, instruct them to right-click the .exe file and select Run as administrator.
If you created an .msi file, deploy the package by performing the following tasks:
Use Active Directory or Microsoft SMS. See Deploying an MSI Package Using Active Directory or Deploying an MSI Package Using Microsoft SMS.
Launch the MSI package from a command prompt window to install the OfficeScan client silently to a remote computer running Windows XP, Vista, or Server 2008.
Select the operating system for which you want to create the package. Deploy the package only to computers that run the operating system type. Create another package to deploy to another operating system type.
Select the scan method for the package. See Scan Methods for details.
The components included in the package depend on the scan method you have selected. For details on the components available for each scan method, see OfficeScan Client Updates.
Before selecting the scan method, take note of the following guidelines to help you deploy the package efficiently:
If you will use the package to upgrade a client to this OfficeScan version, check the domain level scan method on the web console. On the console, go to Networked Computers > Client Management, select the client tree domain to which the client belongs, and click Settings > Scan Settings > Scan Methods. The domain level scan method should be consistent with the scan method for the package.
If you will use the package to perform a fresh installation of the OfficeScan client, check the client grouping setting. On the web console, go to Networked Computers > Client Grouping.
If the client grouping is by NetBIOS, Active Directory, or DNS domain, check the domain to which the target computer belongs. If the domain exists, check the scan method configured for the domain. If the domain does not exist, check the root level scan method (select the root domain icon 
in the client tree and click Settings > Scan Settings > Scan Methods). The domain or root level scan method should be consistent with the scan method for the package.
If the client grouping is by custom client groups, check the Grouping Priority and Source.
Automatic Client Grouping preview pane
If the target computer belongs to a particular source, check the corresponding Destination. The destination is the domain name that appears in the client tree. The client will apply the scan method for that domain after the installation.
If you will use the package to update components on a client using this OfficeScan version, check the scan method configured for the client tree domain to which the client belongs. The domain level scan method should be consistent with the scan method for the package.
This option creates a package that installs on the client computer in the background, unnoticeable to the client and without showing an installation status window. Enable this option if you plan to deploy the package remotely to the target computer.
This option applies only for fresh installations.
If the target computer does not have the OfficeScan client installed, the package first scans the computer for security risks before installing the client. If you are certain that the target computer is not infected with security risks, disable prescan.
If prescan is enabled, Setup scans for virus/malware in the most vulnerable areas of the computer, which include the following:
Boot area and boot directory (for boot viruses)
Windows folder
Program files folder
This option overwrites component versions on the client with the versions currently available on the server. Enable this option to ensure that components on the server and client are synchronized.
This option assigns Update Agent privileges to the client on the target computer. Update Agents help the OfficeScan server deploy components to clients. For details, see Update Agents.
You can allow the Update Agent to perform the following tasks:
Deploy components
Deploy settings
Deploy programs
If you assign Update Agent privileges to a client:
Keep in mind that if the package will be deployed to a pure IPv6 endpoint, the Update Agent can distribute updates only to pure IPv6 or dual-stack clients.
Use the Scheduled Update Configuration Tool to enable and configure scheduled updates for the agent. For details, see Update Methods for Update Agents.
The OfficeScan server that manages the Update Agent will not be able to synchronize or deploy the following settings to the agent:
Update Agent privilege
Client scheduled update
Updates from Trend Micro ActiveUpdate server
Updates from other update sources
Therefore, deploy the client package only to computers that will not be managed by an OfficeScan server. Afterwards, configure the Update Agent to get its updates from an update source other than an OfficeScan server, such as a custom update source. If you want the OfficeScan server to synchronize settings with the Update Agent, do not use Client Packager and choose a different client installation method instead.
This option installs the Outlook Mail Scan program, which scans Microsoft Outlook™ mailboxes for security risks. For details, see Mail Scan Privileges and Other Settings.
This tool adds support for Check Point™ SecureClient™ for Windows XP and Windows Server 2003. SecureClient verifies the Virus Pattern version before allowing connection to the network. For details, see Overview of Check Point Architecture and Configuration.
SecureClient does not verify the virus pattern versions on clients using smart scan.
Select the components and features to include in the package.
For details about components, see OfficeScan Components and Programs.
The Data Protection module will only be available if you install and activate Data Protection. For details about Data Protection, see Data Protection Installation.
See also: