Deployment of Symantec Endpoint Protection install file to clients using Symantec Endpoint Protection Integration Component fails to work

Article:TECH182430  |  Created: 2012-02-27  |  Updated: 2013-02-12  |  Article URL http://www.symantec.com/docs/TECH182430
Article Type
Technical Solution


Issue



When using Symantec Endpoint Protection Integration Component (SEPIC) in the Altiris Symantec Management Platform (SMP) Console to deploy Symantec Endpoint Protection (SEP) install files (setup.exe) to clients, this fails to work. The SEP install file may arrive on the Altiris client but then fails to install.


Cause



Software Delivery is being used not SEPIC, or, configuration issues exist with the SEPIC package/migration job/SEP install file.


Solution



Ensure that SEPIC is being used to deploy SEP install files to the Altiris clients. If not, most likely what is occurring is that Software Delivery (SWD) is being used for this purpose. While SWD can be used for this, doing so removes SEPIC from being able to assist in any way as it has no control over SWD.

Check the following areas in the SMP Console to help determine which Altiris Solution is being used to deploy SEP install files:

Check SEPIC

  1. In the SMP Console, click on the Home button > Symantec Endpoint Protection Management.
  2. Click on Configure Endpoint Protection Packages.
  3. If the Home > Symantec Endpoint Protection Management menu option does not exist or there are no client packages listed under the Client Package Configuration window, SEPIC is either not installed or not configured to send SEP install files to clients. SWD is most likely then doing this. If SWD is believed to be used, skip to the next section for verification. If, however, packages exist, next determine if these are configured correctly. As it then appears that SEPIC is being used, perform the following next steps to test SEPIC. 
  4. Create a new package in Configure Endpoint Protection Packages.
  5. Point the new package to the SEP install file to be used. This must be configured in Silent Mode and 32-bit for 32-bit operating systems or 64-bit for 64-bit operating systems, in the SEPM Console. Refer to the following article for more information:

    Creating custom client installation packages in the Symantec Endpoint Protection Manager console
    http://www.symantec.com/business/support/index?page=content&id=TECH102817

    Note: It may not be known where the correct install file is located at or there may be doubt which one is which. In these cases, create a new one (as outlined above) in the SEPM Console to use and then copy this to the SMP Server for use.
     
  6. Create a new migration job by clicking on Create Migration Job from the SEPIC window. Have this run against a filter known to have at least one Altiris client and have it run Now. Note: The filter may be the issue. Create a new filter or use an existing one after verifying (in Manage > Filters) that the computer in question is listed by the filter.
  7. Does the new package/migration job succeed? If so, then the old ones may be the issue. If not, the SEP install file may be the issue. To troubleshoot this, check the following:

    a. Are there any older versions of SEP or other anti-virus type products already on the client? SEPIC can uninstall certain competitor's anti-virus versions and certain older versions of SEP, as listed here:

    Does Symantec Endpoint Protection Integration Component uninstall other anti-virus agents?
    http://www.symantec.com/business/support/index?page=content&id=HOWTO10184

    However, if non-supported other anti-virus products or versions are installed, the new install of the SEP install file may fail if SEPIC cannot uninstall the prior product/version. Try the migration job therefore to a client that has no prior anti-virus or to one that has the supported products and versions as listed in KB HOWTO10184.

    b. Copy the SEP install file to the client and manually run it. Does this work? If not, it will not work either via the SEPIC/Altiris deployment. Resolve what ever SEP install file issues occur by most likely recreating the file appropriately using the SEPM Console.
     

Check Software Delivery

  1. SWD can be used instead of SEPIC to deploy SEP install files or even uninstall prior anti-virus products and then install SEP. If SEPIC is not deploying the SEP install file, then most likely SWD is. Check the following areas in the SMP Console to help determine where this is occurring at. Note: The SEPIC Technical Support Team is unable to assist with creating or troubleshooting SWD jobs and policies. Please contact that team for appropriate technical support.
  2. Click on Manage > Policies.
  3. Under the Software folder, such as in Managed Software Delivery, there may be a policy that has been created by the user to deploy SEP install files. Browse through the folders here to determine if a policy exists or not for this purpose.
  4. If no policies exist, next check Manage > Jobs and Tasks.
  5. Click on Software. Under the Software folder, check for jobs such as Quick Job, that may be used to deploy SEP install files. Browse through the folders here to determine if a job exists or not for this purpose.
  6. If a policy or job is found, it would then need to be determined if this is what is being used in the failing deployment process and if so, what is going wrong. Perform SWD troubleshooting to further resolve the issue.


Related Article


How to create and deploy a Symantec Endpoint Protection install package using the Altiris Symantec Endpoint Protection Integration Component Solution
http://www.symantec.com/business/support/index?page=content&id=HOWTO60858




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


Terms of use for this information are found in Legal Notices