Installing Windows clients with Microsoft SCCM/SMS

You can use Microsoft System Center Configuration Manager (SCCM) to install Symantec client software. We assume that system administrators who use SCCM have previously installed software with SCCM. As a result, we assume that you do not need detailed information about installing Symantec client software with SCCM.
This topic also applies to Microsoft Systems Management Server (SMS).
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 SCCM/SMS packages launch Setup.exe rather than the MSI directly. This method enables installer logging. Use the custom package creation feature in SCCM/SMS to create custom packages instead of the package wizard feature.
You should use a managed client installation package that you exported from
Symantec Endpoint Protection Manager
. If you use the client installation packages from the product download or the installation file, you deploy unmanaged clients. Unmanaged clients install with default settings and do not communicate with a management server.
Process for installing the client using Microsoft System Center Configuration Manager / Systems Management Server
Step
Description
Step 1
Export a managed client installation package from
Symantec Endpoint Protection Manager
that contains the software and policies to install on your client computers. By default, a managed client installation package contains a file named Sylink.xml, which identifies the server that manages the clients.
Step 2
Create a source directory and copy the Symantec client installation package into that source directory. For example, you would create a source directory and copy the Setup.exe file that you exported from
Symantec Endpoint Protection Manager
.
Step 3
In SCCM/SMS, create a custom 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 SCCM/SMS, see the Microsoft documentation that is appropriate for your version.