Custom Task Sequence in Native Mode
We have a new SCCM 2007 Sp2 R2 native mode site. Clients are installing properly and working. We are trying to use a Task Sequence to remove McAfee a/v and install Forefront but the task sequence just errors when it starts. We have advertised the packages seperately and the client runs them sucessfully but when we use a TS nothing get executed. It doesn't matter what's in the TS .... it never gets to the point of runing the commands. We get errors in the SMSTS.LOG about unable to get the certificate from the registry and then unable to setup TS environment. The network access account is configured and verified. What am I missing? Thanks
June 16th, 2010 10:44pm

What's the error? Can you post the relevant portion f the SMSTS.log?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2010 12:37am

Here it is <![LOG[Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created]LOG]!><time="16:31:29.824+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="1112" file="environmentscope.cpp:250"> <![LOG[Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created]LOG]!><time="16:31:29.840+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="1112" file="environmentscope.cpp:250"> <![LOG[SMS Client GUIDGUID:E6A2754C-5F20-4797-B76F-B4D9184E4DAC]LOG]!><time="16:31:29.965+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="1112" file="tslaunchinfo.cpp:818"> <![LOG[Capturing SMS client certificate store.]LOG]!><time="16:31:29.965+240" date="06-15-2010" component="TSLauncher" context="" type="0" thread="1112" file="tslaunchinfo.cpp:82"> <![LOG[Could not get size of certificate in store (0x80090016)]LOG]!><time="16:31:30.058+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="1112" file="tslaunchinfo.cpp:98"> <![LOG[Error getting package location and access account information. Code 0x80090016]LOG]!><time="16:31:30.058+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="1112" file="tslaunchinfo.cpp:306"> <![LOG[Error initializing TS environment. Code 0x80090016]LOG]!><time="16:31:30.058+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="1112" file="tslauncher.cpp:798"> <![LOG[Task sequence launcher advertisement failed!. Code 0x80090016]LOG]!><time="16:31:30.058+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="1112" file="tslauncher.cpp:1007"> <![LOG[Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs]LOG]!><time="16:31:30.183+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="1112" file="tslogging.cpp:1536"> <![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="16:31:30.183+240" date="06-15-2010" component="TSLauncher" context="" type="2" thread="1112" file="utils.cpp:2924"> <![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="16:31:30.183+240" date="06-15-2010" component="TSLauncher" context="" type="2" thread="1112" file="utils.cpp:3093"> <![LOG[Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created]LOG]!><time="16:31:32.025+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="2852" file="environmentscope.cpp:250"> <![LOG[Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created]LOG]!><time="16:31:32.025+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="2852" file="environmentscope.cpp:250"> <![LOG[SMS Client GUIDGUID:E6A2754C-5F20-4797-B76F-B4D9184E4DAC]LOG]!><time="16:31:32.181+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="2852" file="tslaunchinfo.cpp:818"> <![LOG[Capturing SMS client certificate store.]LOG]!><time="16:31:32.181+240" date="06-15-2010" component="TSLauncher" context="" type="0" thread="2852" file="tslaunchinfo.cpp:82"> <![LOG[Could not get size of certificate in store (0x80090016)]LOG]!><time="16:31:32.274+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="2852" file="tslaunchinfo.cpp:98"> <![LOG[Error getting package location and access account information. Code 0x80090016]LOG]!><time="16:31:32.274+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="2852" file="tslaunchinfo.cpp:306"> <![LOG[Error initializing TS environment. Code 0x80090016]LOG]!><time="16:31:32.274+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="2852" file="tslauncher.cpp:798"> <![LOG[Task sequence launcher advertisement failed!. Code 0x80090016]LOG]!><time="16:31:32.274+240" date="06-15-2010" component="TSLauncher" context="" type="3" thread="2852" file="tslauncher.cpp:1007"> <![LOG[Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs]LOG]!><time="16:31:32.415+240" date="06-15-2010" component="TSLauncher" context="" type="1" thread="2852" file="tslogging.cpp:1536"> <![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="16:31:32.415+240" date="06-15-2010" component="TSLauncher" context="" type="2" thread="2852" file="utils.cpp:2924"> <![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="16:31:32.415+240" date="06-15-2010" component="TSLauncher" context="" type="2" thread="2852" file="utils.cpp:3093">
June 17th, 2010 2:47pm

"Could not get size of certificate in store" 0x16 = 22 = "The device does not recognize the command." That looks to be a key, recurring error message. Not sure what could be causing it though. Have you locked down the systems in some non-standard way? Have you changed service accounts? Have you tried disabling any host based security software? Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2010 2:59am

Ok OK. We removed NAK and McAfee but still no task sequence will execute. We looked at thread http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/53e310aa-3dfc-44ea-8e41-3ae1374d9437 which pointed to KB977203 as the MS09-56 patch had already been deployed. We installed the hotfix on the server and the client system but still the same issue. SMSTS.LOG ^^^^^^^^^^^^^^^^^^^^^^^^ Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) SMS Client GUIDGUID:C774A226-A25B-4169-BECF-7D4CC00FA122 TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Capturing SMS client certificate store. TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Could not get size of certificate in store (0x80090016) TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Error getting package location and access account information. Code 0x80090016 TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Error initializing TS environment. Code 0x80090016 TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Task sequence launcher advertisement failed!. Code 0x80090016 TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/22/2010 2:24:15 PM 2736 (0x0AB0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Execmgr.log ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Verifying content availability for package A0100005 optional program * execmgr 6/22/2010 2:24:14 PM 3196 (0x0C7C) The created request is a Task Sequence request execmgr 6/22/2010 2:24:14 PM 3196 (0x0C7C) Requesting content from CAS for package A0100003 version 3 execmgr 6/22/2010 2:24:14 PM 3196 (0x0C7C) Successfully created a content request handle {F8B1B277-F7FE-4D03-9957-4E2F12671257} for the package A0100003 version 3 execmgr 6/22/2010 2:24:14 PM 3196 (0x0C7C) Content availability verification for package A0100005 program * is in progress execmgr 6/22/2010 2:24:14 PM 3196 (0x0C7C) Content for optional program is now available. The location request ID is {F8B1B277-F7FE-4D03-9957-4E2F12671257} execmgr 6/22/2010 2:24:14 PM 3736 (0x0E98) Validating chain of dependent programs for package A0100005 optional program * execmgr 6/22/2010 2:24:14 PM 2492 (0x09BC) Validating package A0100005 program * in the chain. The content request ID is {45E0C64F-EEEB-4621-AFE9-A94BC51F90E2} execmgr 6/22/2010 2:24:14 PM 2492 (0x09BC) Creating an optional execution request for package A0100005 program * execmgr 6/22/2010 2:24:14 PM 2492 (0x09BC) Execution Request for package A0100005 program * state change from NotExist to WaitingDependency execmgr 6/22/2010 2:24:14 PM 2492 (0x09BC) Execution Manager timer has been fired. execmgr 6/22/2010 2:24:14 PM 3736 (0x0E98) Notify user package A0100005 optional program * is ready to run execmgr 6/22/2010 2:24:15 PM 2492 (0x09BC) Execution Request for package A0100005 program * state change from WaitingDependency to NotifyExecution execmgr 6/22/2010 2:24:15 PM 2492 (0x09BC) Executing program in Admin context execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Execution Manager timer has been fired. execmgr 6/22/2010 2:24:15 PM 3736 (0x0E98) Execution Request for package A0100005 program * state change from Running to NotifyExecution execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Executing program as a task sequence. execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Successfully prepared command line "C:\WINDOWS\system32\CCM\TSLauncher.exe" execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Command line = "C:\WINDOWS\system32\CCM\TSLauncher.exe", Working Directory = C:\WINDOWS\system32\ execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Created Process for the passed command line execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramStartedEvent { AdvertisementId = "A0120009"; ClientID = "GUID:C774A226-A25B-4169-BECF-7D4CC00FA122"; CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\TSLauncher.exe\""; DateTime = "20100622182415.437000+000"; MachineName = "LOAN-HZ18L71L"; PackageName = "A0100005"; ProcessID = 1748; ProgramName = "*"; SiteCode = "A01"; ThreadID = 200; UserContext = "NT AUTHORITY\\SYSTEM"; WorkingDirectory = "C:\\WINDOWS\\system32\\"; }; execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Raised Program Started Event for Ad:A0120009, Package:A0100005, Program: * execmgr 6/22/2010 2:24:15 PM 200 (0x00C8) Program exit code 22 execmgr 6/22/2010 2:24:16 PM 2560 (0x0A00) Looking for MIF file to get program status execmgr 6/22/2010 2:24:16 PM 2560 (0x0A00) Script for Package:A0100005, Program: * failed with exit code 22 execmgr 6/22/2010 2:24:16 PM 2560 (0x0A00) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramErrorEvent { AdvertisementId = "A0120009"; ClientID = "GUID:C774A226-A25B-4169-BECF-7D4CC00FA122"; DateTime = "20100622182416.045000+000"; ExitCode = "22"; MachineName = "LOAN-HZ18L71L"; PackageName = "A0100005"; ProcessID = 1748; ProgramName = "*"; SiteCode = "A01"; ThreadID = 2560; UserContext = "NT AUTHORITY\\SYSTEM"; }; execmgr 6/22/2010 2:24:16 PM 2560 (0x0A00) Raised Program Error Event for Ad:A0120009, Package:A0100005, Program: * execmgr 6/22/2010 2:24:16 PM 2560 (0x0A00) Execution is complete for program *. The exit code is 22, the execution status is FailureNonRetry execmgr 6/22/2010 2:24:16 PM 2560 (0x0A00) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If I run TSLauncher.exe from a command prompt, I get ^^^^^^^^^^^^ C:\WINDOWS\system32\CCM>tslauncher Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully c reated Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully c reated SMS Client GUIDGUID:C774A226-A25B-4169-BECF-7D4CC00FA122 Capturing SMS client certificate store. Could not get size of certificate in store (0x80090016) Error getting package location and access account information. Code 0x80090016 Error initializing TS environment. Code 0x80090016 Task sequence launcher advertisement failed!. Code 0x80090016 Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32 \CCM\Logs Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Any help would be appreciated.
June 22nd, 2010 10:04pm

Are you using chained programs?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2010 3:07am

We did a chain deployment to see if that would function as the task sequenece but it didn't handle reboots nicely. I've changed the chaining that is shown in the logs. Still no change.
June 23rd, 2010 2:00pm

Did anyone ever figure out what this error code 22 was? I'm having the same issue all of the sudden on a group of computers.
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2011 9:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics