Deploying clients by using Save Package

Article:HOWTO81283  |  Created: 2012-10-25  |  Updated: 2013-08-20  |  Article URL http://www.symantec.com/docs/HOWTO81283
Article Type
How To


Subject


Deploying clients by using Save Package

Save Package creates the installation packages that you can install manually or with Windows Group Policy Object.

Save Package performs the following actions:

  • Creates a 32-bit or 64-bit installation package.

    The installation package can comprise one setup.exe file or a collection of files that includes a setup.exe file. Computer users often find one setup.exe file easier to use.

  • Saves the installation package to a directory on the computer that runs Symantec Endpoint Protection Manager.

You must provide the installation package to the computer users. The users run the setup.exe file to install the client software. You or the computer users must restart the computers after installation.

The Mac client install package is automatically exported as a .zip archive file. To expand the package and extract the folder containing the Apple installer file (.pkg) and the Additional Resources folder, you must use either the Mac Archive Utility or the ditto command. You cannot use the Mac unzip command, a third-party application, or any Windows application to expand this file. You must keep the .pkg file and the Additional Resources folder together to complete the installation successfully.

You start the client deployment from the console.

To deploy clients by using Save Package

  1. In the console, on the Home page, in the Common Tasks menu, click Install protection client to computers.

  2. In the Client Deployment Wizard, click New Package Deployment to configure a new installation package, and then click Next.

    Existing Package Deployment lets you deploy the packages that have been exported previously, but you can only use Remote Push with this option.

    Communication Update Package Deployment lets you update client communication settings on the computers that already have the client installed. Use this option to convert an unmanaged client to a managed client. Click Next to select the group of clients on which the package is installed.

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

  3. For a new package, make selections from Install Packages, Group, Install Feature Set, and Content Options. Click Next.

    Note:

    To uninstall third-party security software on the client, click Automatically uninstall existing security software. To see which third-party software the client package removes, see the following knowledge base article: About the Security Software Removal feature in Symantec Endpoint Protection 12.1.

    See Configuring client packages to uninstall existing third-party security software.

  4. Click Save Package, and then click Next.

  5. Click Browse and specify the folder to receive the package, if you do not want to accept the default.

    Check Single .exe file (default) or Separate files (required for .MSI), and then click Next.

    To create a package for computers running on legacy operating systems, click Create a package for clients with systems that are not supported by 12.x packages. Click Next.

    If the default folder does not exist, click Yes in the confirmation dialog box to create it.

    Note:

    If you deploy clients with Windows Group Policy Object, choose Separate files (required for .MSI).

  6. Review the settings summary, click Next, and then click Finish.

  7. Provide the custom installation package to the computer users.

    For example, you can save the installation package to a shared network location, or email the installation package to the computer users. You can also use Windows Group Policy Object to deploy the package.

  8. Confirm that the computer users have received and installed the client software, and confirm the status of the deployed clients.

    Client computers may not appear within the management console until after they are restarted. You or the computer users may need to restart the client computers.

    See Restarting client computers.

    See Viewing the status of deployed client computers.

See Which features should you install on the client?

See About client deployment methods

See Deploying clients by using Remote Push.

See Preparing for client installation.


Legacy ID



v16194723_v81626097


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


Terms of use for this information are found in Legal Notices