none
Deploying Symantec Endpoint Protection 12 using CM2012

    Question

  • Hello Everyone,

    I am currently having a problem in deploying SEP12 in my Windows 7 machines using CM2012

    I have deploying it as Application (i have a msi package created). My settings is just the basic.

    msiexec.exe /i "Sep64.msi" /q

    However I cant install this. As I inspect the AppEnforce.log, I can see the following errors.

        App enforcement environment: 
    	Context: Machine
    	Command line: msiexec.exe /i "Sep64.msi" /q
    	Allow user interaction: No
    	UI mode: 1
    	User token: null
    	Session Id: 2
    	Content path: C:\Windows\ccmcache\e
    	Working directory: 	AppEnforce	8/2/2013 9:11:34 PM	3300 (0x0CE4)
        Prepared working directory: C:\Windows\ccmcache\e	AppEnforce	8/2/2013 9:11:34 PM	3300 (0x0CE4)
    Found executable file msiexec.exe with complete path C:\Windows\system32\msiexec.exe	AppEnforce	8/2/2013 9:11:34 PM	3300 (0x0CE4)
        Prepared command line: "C:\Windows\system32\msiexec.exe" /i "Sep64.msi" /q /qn	AppEnforce	8/2/2013 9:11:34 PM	3300 (0x0CE4)
    Valid MSI Package path = C:\Windows\ccmcache\e\Sep64.msi	AppEnforce	8/2/2013 9:11:34 PM	3300 (0x0CE4)
        Advertising MSI package [C:\Windows\ccmcache\e\Sep64.msi] to the system.	AppEnforce	8/2/2013 9:11:34 PM	3300 (0x0CE4)
        Executing Command line: "C:\Windows\system32\msiexec.exe" /i "Sep64.msi" /q /qn with user context	AppEnforce	8/2/2013 9:11:35 PM	3300 (0x0CE4)
        Working directory C:\Windows\ccmcache\e	AppEnforce	8/2/2013 9:11:35 PM	3300 (0x0CE4)
        Post install behavior is NoAction	AppEnforce	8/2/2013 9:11:35 PM	3300 (0x0CE4)
        Waiting for process 376 to finish.  Timeout = 120 minutes.	AppEnforce	8/2/2013 9:11:35 PM	3300 (0x0CE4)
        Process 376 terminated with exitcode: 1612	AppEnforce	8/2/2013 9:11:36 PM	3300 (0x0CE4)
        Looking for exit code 1612 in exit codes table...	AppEnforce	8/2/2013 9:11:36 PM	3300 (0x0CE4)
        Unmatched exit code (1612) is considered an execution failure.	AppEnforce	8/2/2013 9:11:36 PM	3300 (0x0CE4)
    

    When I try to create a scheduled task that will install the SEP 12 on a windows 7 machine, it was installed perfectly.

    When I install manually using the command line, it was installed properly also.

    I cant think of any more solution. Please help me. Thank you

    Saturday, August 03, 2013 4:34 AM

All replies

  • Can sep63.msi be found in C:\Windows\ccmcache\e?

    Torsten Meringer | http://www.mssccmfaq.de

    Sunday, August 04, 2013 9:28 AM
    Moderator
  • Can sep63.msi be found in C:\Windows\ccmcache\e?

    Torsten Meringer | http://www.mssccmfaq.de

    Yes, it was there..
    Tuesday, August 06, 2013 12:00 AM
  • Try logging msi activity. 

    The command line will just look like this msiexec.exe /i "Sep64.msi" /q /l*v "c:\logs\Sep.log"

    Reviewing sep.log file will give you more information. 


    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

    Tuesday, August 06, 2013 12:50 PM
  • Try logging msi activity. 

    The command line will just look like this msiexec.exe /i "Sep64.msi" /q /l*v "c:\logs\Sep.log"

    Reviewing sep.log file will give you more information. 


    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

    okay, I will try that again. I tried that before however it didnt log. Thanks
    Tuesday, August 06, 2013 11:14 PM
  • Endpoint 12 no longer uses MSI installer, it is using the setup with passing parameters to the installer

    "Setup.exe" /s /v

    • Edited by Amnon Feiner Wednesday, August 07, 2013 12:36 AM
    Wednesday, August 07, 2013 12:36 AM
  • Endpoint 12 no longer uses MSI installer, it is using the setup with passing parameters to the installer

    "Setup.exe" /s /v

    Even if I can still create .MSI package using the SEPM? Should I create a single .EXE file and install with those params?
    Wednesday, August 07, 2013 1:01 AM
  • No need. Just put the source folder and update your DP, the SETUP.EXE is a part of your SEP 12 package (you use SEP 12 server to create the package?)
    Wednesday, August 07, 2013 1:11 AM
  • No need. Just put the source folder and update your DP, the SETUP.EXE is a part of your SEP 12 package (you use SEP 12 server to create the package?)
    Yes. I can see that. Hold on I'll try
    Wednesday, August 07, 2013 1:36 AM
  • Endpoint 12 no longer uses MSI installer, it is using the setup with passing parameters to the installer

    "Setup.exe" /s /v

    Even if I can still create .MSI package using the SEPM? Should I create a single .EXE file and install with those params?

    Update.

    the above params worked. But as I can see there will be user intervention during the install.

    when I try to do it silently using,

        "Setup.exe" /s

    It installs at first then I get an error..

    The software change returned error code 0x643(1603).

    So my install still fails.

    Can  you enlighten me? thank you

    -----------

    AppEnforce.log

    +++ Application not discovered. [AppDT Id: ScopeId_62E5052A-3B3E-47CE-B5FD-A415C561CCE3/DeploymentType_0b5dc587-f20c-4d05-b492-aded82b53c26, Revision: 10]	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        App enforcement environment: 
    	Context: Machine
    	Command line: Setup.exe /s
    	Allow user interaction: No
    	UI mode: 0
    	User token: null
    	Session Id: 2
    	Content path: C:\Windows\ccmcache\p
    	Working directory: 	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Prepared working directory: C:\Windows\ccmcache\p	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Prepared command line: "C:\Windows\ccmcache\p\Setup.exe" /s	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Executing Command line: "C:\Windows\ccmcache\p\Setup.exe" /s with user context	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Working directory C:\Windows\ccmcache\p	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Post install behavior is BasedOnExitCode	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Waiting for process 3220 to finish.  Timeout = 120 minutes.	AppEnforce	8/6/2013 11:52:16 PM	1428 (0x0594)
        Process 3220 terminated with exitcode: 1603	AppEnforce	8/6/2013 11:58:15 PM	1428 (0x0594)
        Looking for exit code 1603 in exit codes table...	AppEnforce	8/6/2013 11:58:15 PM	1428 (0x0594)
        Unmatched exit code (1603) is considered an execution failure.	AppEnforce	8/6/2013 11:58:15 PM	1428 (0x0594)
    ++++++ App enforcement completed (358 seconds) for App DT "Symantec Endpoint Protection 64" [ScopeId_62E5052A-3B3E-47CE-B5FD-A415C561CCE3/DeploymentType_0b5dc587-f20c-4d05-b492-aded82b53c26], Revision: 10, User SID: ] ++++++	AppEnforce	8/6/2013 11:58:15 PM	1428 (0x0594)
    

    Wednesday, August 07, 2013 7:01 AM
  • 1603 is a generic msi error. You would have to examine the setup logs of the exe (if there are any).

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, August 07, 2013 7:39 AM
    Moderator
  • 1603 is a generic msi error. You would have to examine the setup logs of the exe (if there are any).

    Torsten Meringer | http://www.mssccmfaq.de

    I tried to use the following command and run it manually on the machine..

    Setup.exe /s"/l*v \"c:\logtest.log\" /qn"

    however it doesn't create the C:\logtest.log that I wish to have. also this pops out a Symantec install window, though it just shows the progress bar. This installs fine but I dont want to see this windows. I want it to be silent.

    Wednesday, August 07, 2013 7:44 AM
  • hays, even if I use the same command that I've used to run manually, it still fails when SCCM is pushing the install.. why oh why..
    Wednesday, August 07, 2013 8:33 AM
  • Hello,

    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.

    Check these Articles:

    Installing clients with Microsoft SMS 2003

    http://www.symantec.com/business/support/index?page=content&id=HOWTO55425

    The above article also applies to Microsoft System Center Configuration Manager (SCCM).

    Install SEP client on Microsoft System Center Configuration Manager 2007

    http://www.symantec.com/docs/TECH182773

    Check this Thread with similar issue:

    https://www-secure.symantec.com/connect/forums/sccmsystem-center-configurution-manager

    Hope that helps!!

    Wednesday, August 07, 2013 1:52 PM
  • Have you seen this?
    http://www.symantec.com/business/support/index?page=content&id=TECH177946

    Are you using the setaid.ini and read setup.ini? what does appenforce.log say now?

    Wednesday, August 07, 2013 5:03 PM
  • Yes, I am using that, and it says the same error as above AppEnforce.log
    Thursday, August 08, 2013 12:42 AM
  • Do not add the log to the command line,it should be created under %temp%. just run setup /s /v
    Thursday, August 08, 2013 4:05 AM
  • Hello,

    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.

    Check these Articles:

    Installing clients with Microsoft SMS 2003

    http://www.symantec.com/business/support/index?page=content&id=HOWTO55425

    The above article also applies to Microsoft System Center Configuration Manager (SCCM).

    Install SEP client on Microsoft System Center Configuration Manager 2007

    http://www.symantec.com/docs/TECH182773

    Check this Thread with similar issue:

    https://www-secure.symantec.com/connect/forums/sccmsystem-center-configurution-manager

    Hope that helps!!

    Hi Ive read those before, however I still fails to install.. I am having a 259 error now. hayst!

    An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task.	execmgr	8/7/2013 6:04:03 PM	604 (0x025C)
    Request a MTC task for execution request of package HIC00020, program SEP12 32BIT Install with request id: {23D523A9-8173-4292-9334-FF175D525A94}	execmgr	8/7/2013 6:04:03 PM	604 (0x025C)
    Execution Request for advert HIC2001F package HIC00020 program SEP12 32BIT Install state change from WaitingContent to Ready	execmgr	8/7/2013 6:04:03 PM	604 (0x025C)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="HIC00020",ProgramID="SEP12 32BIT Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	8/7/2013 6:04:03 PM	604 (0x025C)
    MTC task with id {23D523A9-8173-4292-9334-FF175D525A94}, changed state from 0 to 4	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    MTC signaled SWD execution request with program id: SEP12 32BIT Install, package id: HIC00020 for execution.	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Sending ack to MTC for task with id: {23D523A9-8173-4292-9334-FF175D525A94}	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Executing program Setup.exe /s /v in Admin context	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Execution Request for advert HIC2001F package HIC00020 program SEP12 32BIT Install state change from Ready to NotifyExecution	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="HIC00020",ProgramID="SEP12 32BIT Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Execution Manager timer has been fired.	execmgr	8/7/2013 6:04:03 PM	280 (0x0118)
    Checking content location C:\WINDOWS\ccmcache\c for use	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Successfully selected content location C:\WINDOWS\ccmcache\c	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Executing program as a script	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Successfully prepared command line "C:\WINDOWS\ccmcache\c\Setup.exe" /s /v	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Command line = "C:\WINDOWS\ccmcache\c\Setup.exe" /s /v, Working Directory = C:\WINDOWS\ccmcache\c\	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Created Process for the passed command line	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    {
    	AdvertisementId = "HIC2001F";
    	ClientID = "GUID:FD2B6BFE-86DB-47A4-8582-59063651D4EC";
    	CommandLine = "\"C:\\WINDOWS\\ccmcache\\c\\Setup.exe\" /s /v";
    	DateTime = "20130808010403.910000+000";
    	MachineName = "DEPLOYTEST2";
    	PackageName = "HIC00020";
    	ProcessID = 1848;
    	ProgramName = "SEP12 32BIT Install";
    	SiteCode = "HIC";
    	ThreadID = 872;
    	UserContext = "NT AUTHORITY\\SYSTEM";
    	WorkingDirectory = "C:\\WINDOWS\\ccmcache\\c\\";
    };
    	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Raised Program Started Event for Ad:HIC2001F, Package:HIC00020, Program: SEP12 32BIT Install	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="HIC00020",ProgramID="SEP12 32BIT Install", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="HIC00020",ProgramID="SEP12 32BIT Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	8/7/2013 6:04:03 PM	872 (0x0368)
    MTC task with id {23D523A9-8173-4292-9334-FF175D525A94}, changed state from 4 to 5	execmgr	8/7/2013 6:04:03 PM	1940 (0x0794)
    A user has logged on.	execmgr	8/7/2013 6:08:49 PM	1520 (0x05F0)
    The logged on user is HIC\_Craymundo	execmgr	8/7/2013 6:08:49 PM	1520 (0x05F0)
    Program exit code 259	execmgr	8/7/2013 8:04:04 PM	3932 (0x0F5C)
    Looking for MIF file to get program status	execmgr	8/7/2013 8:04:04 PM	3932 (0x0F5C)
    Program ran past its maximum runtime. It will be orphaned	execmgr	8/7/2013 8:04:04 PM	3932 (0x0F5C)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramExceededTime
    {
    	AdvertisementId = "HIC2001F";
    	ClientID = "GUID:FD2B6BFE-86DB-47A4-8582-59063651D4EC";
    	DateTime = "20130808030404.052000+000";
    	MachineName = "DEPLOYTEST2";
    	MaximumTime = "120";
    	PackageName = "HIC00020";
    	ProcessID = 1848;
    	ProgramName = "SEP12 32BIT Install";
    	SiteCode = "HIC";
    	ThreadID = 3932;
    };
    	execmgr	8/7/2013 8:04:04 PM	3932 (0x0F5C)
    Raised Program Exceeded Time Event for Ad:HIC2001F, Package:HIC00020, Program: SEP12 32BIT Install	execmgr	8/7/2013 8:04:04 PM	3932 (0x0F5C)
    Execution is complete for program SEP12 32BIT Install. The exit code is 259, the execution status is Unknown Status	execmgr	8/7/2013 8:04:04 PM	2620 (0x0A3C)
    

    Thursday, August 08, 2013 4:27 AM
  • Do not add the log to the command line,it should be created under %temp%. just run setup /s /v

    Yes, I've already did that also.. I saw that the Setup.ini from my installation folder, creates the log. however... its been running for 2 hours and I know eventually it will fail. It will not have the log in %temp%\sep_inst.log

    this is so frustrating. I dont know where I did wrong.

    Thursday, August 08, 2013 5:01 AM
  • Have you considered saving yourself the hassle and just using System Center Endpoint Protection instead of that wonderful Symantec stuff?

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    Thursday, August 08, 2013 5:37 AM
  • Hello,

    Make sure you use the .msi package rather that the setup.exe package.

    Check these Articles:

    Creating a managed .MSI package in Symantec Endpoint Protection 12.1

    http://www.symantec.com/docs/TECH165483

    How do I create and configure a custom Symantec Endpoint Protection installation package in version 12.1?

    https://www-secure.symantec.com/connect/articles/how-do-i-create-and-configure-custom-symantec-endpoint-protection-installation-package-vers

    and check this Thread with similar issue:

    https://www-secure.symantec.com/connect/forums/sep-12-sccm-deploy-sepmsi-or-setupexe

    Hope that helps!!

    Thursday, August 08, 2013 1:22 PM
  • Have you considered saving yourself the hassle and just using System Center Endpoint Protection instead of that wonderful Symantec stuff?

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    I have consider this before, however, we have Symantec license and it was the standard in all our sites.
    Thursday, August 08, 2013 11:30 PM
  • Hello,

    Make sure you use the .msi package rather that the setup.exe package.

    Check these Articles:

    Creating a managed .MSI package in Symantec Endpoint Protection 12.1

    http://www.symantec.com/docs/TECH165483

    How do I create and configure a custom Symantec Endpoint Protection installation package in version 12.1?

    https://www-secure.symantec.com/connect/articles/how-do-i-create-and-configure-custom-symantec-endpoint-protection-installation-package-vers

    and check this Thread with similar issue:

    https://www-secure.symantec.com/connect/forums/sep-12-sccm-deploy-sepmsi-or-setupexe

    Hope that helps!!

    Hi Thank you for these.

    I did the last part, however I am still having some errors. I did exactly how he resolved it. It doesnt work for me I guess. I am confused on which source directory it cannot access..

    Failed to clear product advertisement, error code 1612
    
    
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramErrorMIFEvent
    {
    	AdvertisementId = "HIC2002B";
    	ClientID = "GUID:CA1D8A35-57B1-4020-9B5A-D8F1768388B9";
    	DateTime = "20130809015349.633000+000";
    	MachineName = "DEPLOYTEST1";
    	MIFDescription = "The installation source for this product is not available.  Verify that the source exists and that you can access it.";
    	MIFDescription7 = "";
    	MIFDescription8 = "";
    	MIFDescription9 = "";
    	PackageName = "HIC0002B";
    	ProcessID = 2788;
    	ProgramName = "Per-system unattended";
    	SiteCode = "HIC";
    	ThreadID = 1144;
    	UserContext = "NT AUTHORITY\\SYSTEM";
    };
    

    Friday, August 09, 2013 2:00 AM
  • I saw a thread in Symantec regarding this however I am still having problem.

    https://www-secure.symantec.com/connect/forums/sep-12-sccm-deploy-sepmsi-or-setupexe#comment-9106131

    ---------------------------------------------

    Hello, I did the following steps but still I am getting Error 1612.. maybe I am missing something?

    CM2012
    Create Package from Definition Wizard

    Package Definition
    ​             - browse to my SEP 12 .msi file, next

    Source Files
                 - create a compressed version of the source file, next

    Source Folder 
                 - choose source folder. used the Network path

    Summary
    Progress 
    Completion
     
    Distribute Content to DP
     
    Edit properties of Per-system unattended program.
    - After running = Configuration Manager restarts computer
    Command line: "msiexec.exe /q ALLUSERS=2 /m MSIUUJRP /i "Sep64.msi"
     
    Deploy
     
    After that I can see that the source files are downloaded on the client. but it fails to run. with Error Code 1612 
     
    Failed to clear product advertisement, error code 1612
    
    
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramErrorMIFEvent
    {
    	AdvertisementId = "JCF2002B";
    	ClientID = "GUID:CA1D8A35-57B1-4020-9B5A-D8F1768388B9";
    	DateTime = "20130809015349.633000+000";
    	MachineName = "TEST1";
    	MIFDescription = "The installation source for this product is not available.  Verify that the source exists and that you can access it.";
    	MIFDescription7 = "";
    	MIFDescription8 = "";
    	MIFDescription9 = "";
    	PackageName = "JCF2002B";
    	ProcessID = 2788;
    	ProgramName = "Per-system unattended";
    	SiteCode = "JCF";
    	ThreadID = 1144;
    	UserContext = "NT AUTHORITY\\SYSTEM";
    };


     
    Wednesday, August 14, 2013 7:24 AM