Installing clients with Microsoft SMS 2003

Article:HOWTO55425  |  Created: 2011-06-29  |  Updated: 2011-12-17  |  Article URL http://www.symantec.com/docs/HOWTO55425
Article Type
How To

Product(s)

Subject

Languages

Installing clients with Microsoft SMS 2003

You can use Microsoft Systems Management Server (SMS) to install Symantec client software. We assume that system administrators who use SMS have previously installed software with SMS. As a result, we assume that you do not need detailed information about installing Symantec client software with SMS.

Note:

This topic also applies to Microsoft System Center Configuration Manager (SCCM).

Symantec client installation software requires that Microsoft Installer 3.1 run on client computers before the installation. This software is automatically installed if it is not on client computers, but only when you deploy with a single executable setup.exe. This software is not automatically installed if you deploy with the msi file. Computers that run Windows Server 2003 with Service Pack 2, and Windows Vista include Microsoft Installer 3.1 or greater. If necessary, first deploy WindowsInstaller-x86.exe that is contained on the Symantec Endpoint Protection and the Symantec Network Access Control product disc. Upgrading to msi 3.1 also requires a computer restart.

Note:

This note applies to SMS version 2.0 and earlier: If you use SMS, turn off the Show Status Icon On The Toolbar For All System Activity feature on the clients in the Advertised Programs Monitor. In some situations, Setup.exe might need to update a shared file that is in use by the Advertised Programs Monitor. If the file is in use, the installation fails.

Symantec recommends that SMS/SCCM packages launch Setup.exe rather than the MSI directly. This method ensures that the MSI engine can update to the minimum recommended version and also enables installer logging. Use the custom package creation feature in SMS/SCCM to create custom packages instead of the package wizard feature.

Warning:

You must include a Sylink.xml file in client installation packages that you created by using the files on the product disc. You must include a Sylink.xml file that is created after you install and use Symantec Endpoint Protection Manager. The Sylink.xml file identifies the management server to which the clients report. If you do not include this file the client is installed as an unmanaged client. As a result, all clients are installed with default settings and do not communicate with a management server.

Table: Process for installing the client using Microsoft Systems Management Server lists the tasks to create and distribute Symantec client software with SMS 2003.

Table: Process for installing the client using Microsoft Systems Management Server

Step

Description

Step 1

Create a software installation package with Symantec Endpoint Protection Manager that contains the software and policies to install on your client computers. Additionally, this software installation package must contain a file named Sylink.xml, which identifies the server that manages the clients.

Step 2

Create a source directory and copy Symantec client installation files into that source directory. For example, you would create a source directory that contains the installation files for Symantec client software.

Step 3

Create a package, name the package, and identify the source directory as part of the package.

Step 4

Configure the Program dialog box for the package to specify the executable that starts the installation process, and possibly specify the msi with parameters.

Step 5

Distribute the software to specific Collections with Advertising.

For more information on using SMS/SCCM, see the Microsoft documentation that is appropriate for your version.

Legacy ID



v8527828_v59371754


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


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support