Installing clients with Active Directory Group Policy Object

Article:HOWTO81177  |  Created: 2012-10-24  |  Updated: 2013-10-10  |  Article URL
Article Type
How To


Installing clients with Active Directory Group Policy Object

You can install the client by using a Windows 2000/2003/2008 Active Directory Group Policy Object. The procedures assume that you have installed this software and use Windows Active Directory for installing client software with Active Directory Group Policy Object.

The installation software requires that client computers contain and can run Windows Installer 3.1 or later. Computers already meet this requirement if they run Windows XP with Service Pack 2 and later, Windows Server 2003 with Service Pack 1 and later, and Windows Vista/7/8/Server 2008/Server 2012. If client computers do not meet this requirement, all other installation methods automatically install Windows Installer 3.1 by bootstrapping it from the installation files.

For security reasons, Windows Group Policy Object does not permit bootstrapping to the executable file WindowsInstaller*.exe from the installation files. Therefore, before you install Symantec client software, you must run this file on the computers without Windows Installer 3.1 or later. You can run this file with a computer startup script. If you use a GPO as an installation method, you must decide how to update the client computers with Windows Installer 3.1 or later.

The Symantec client installation uses standard Windows Installer (MSI) files. As a result, you can customize the client installation with MSI properties.

You should confirm that your DNS server is set up correctly before deployment. The correct setup is required because Active Directory relies on your DNS server for computer communication. To test the setup, you can ping the Windows Active Directory computer, and then ping in the opposite direction. Use the fully qualified domain name. The use of the computer name alone does not call for a new DNS lookup. Use the following format:


Table: Steps for installing the client software by using Active Directory Group Policy Object



Step 1

Export the installation package with the option Separate files (required for .MSI).

Step 2

Copy Sylink.xml to the installation files.

Step 3

Stage the folder of installation files.

Step 4

Create a GPO software distribution.

You should also test GPO installation with a small number of computers before the production deployment. If DNS is not configured properly, GPO installations can take an hour or more.

Step 5

Create a startup script to install Windows Installer 3.1 (or later). If your computers already meet this requirement, you may skip this step.

Step 6

Add computers to the organizational unit.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices