Exporting client installation packages

Article:HOWTO81164  |  Created: 2012-10-24  |  Updated: 2013-10-07  |  Article URL http://www.symantec.com/docs/HOWTO81164
Article Type
How To


Subject


Exporting client installation packages

You might want to export a client install package if you want to use a third-party distribution system, or an unmanaged client with custom policies.

When you export client software packages, you create client installation files for deployment. When you export packages, you must browse to a directory to contain the exported packages. If you specify a directory that does not exist, it is automatically created for you. The export process creates descriptively named subdirectories in this directory and places the installation files in these subdirectories.

For example, if you create an installation package for a group named My Group beneath My Company, a directory named My Company_My Group is created. This directory contains the exported installation package.

Note:

This naming convention does not make a distinction between client installation packages for Symantec Endpoint Protection and Symantec Network Access Control. The exported package name for a single executable is Setup.exe for both Symantec Endpoint Protection and Symantec Network Access Control. Therefore, be sure to create a directory structure that lets you distinguish between Symantec Endpoint Protection and Symantec Network Access Control installation files.

You must decide whether to create an installation package for managed clients or unmanaged clients. Both types of packages have the features, policies, and settings that you assign. If you create a package for managed clients, you can manage them with the Symantec Endpoint Protection Manager console. If you create a package for unmanaged clients, you cannot manage them from the console. You can convert an unmanaged client to a managed client at any time with Communication Update Package Deployment through the Client Deployment Wizard.

Note:

If you export client installation packages from a remote console, the packages are created on the computer from which you run the remote console. Furthermore, if you use multiple domains, you must export the packages for each domain, or they do not appear as available for the domain groups.

After you export one or more installation packages, you deploy the installation package on the client computers.

Note:

You should use silent installations for remote deployment to minimize user disruption. When you use a silent deployment, you must restart the applications that plug into Symantec Endpoint Protection, such as Microsoft Outlook and Lotus Notes. If you use unattended installations (Show progress bar only), Windows may display to users one or more pop-up windows. However, the installation should not fail even if the user does not notice them. You should not use an interactive installation for remote deployment. This installation type fails unless users interact with it. Security features (such as Windows Session 0 isolation) on some operating systems may cause the interactive installation wizard to not appear. You should only use the interactive installation type for local installations. These recommendations apply to both 32- and 64-bit operating systems.

To export client installation packages

  1. In the console, click Admin, and then click Install Packages.

  2. Under Install Packages, click Client Install Package.

  3. In the Client Install Package pane, under Package Name, right-click the package to export and then click Export.

  4. In the Export Package: dialog box, beside the Export folder text box, browse to and select the directory to contain the exported package, and then click OK.

    Note:

    Directories with double-byte or high-ASCII characters are not supported and are blocked.

  5. In the Export Package: dialog box, set the other options according to your installation goals.

    For details about setting other options in this dialog box, click Help.

  6. Click OK.

See Managing client installation packages.

See Deploying clients using a Web link and email.

See Restoring client-server communications with Communication Update Package Deployment.

See Preparing for client installation.


Legacy ID



v8230976_v81626096


Article URL http://www.symantec.com/docs/HOWTO81164


Terms of use for this information are found in Legal Notices