p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:'Calibri','sans-serif';} a:link, span.MsoHyperlink {color:blue;text-decoration:underline;text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple;text-decoration:underline;text-underline:single;} .MsoChpDefault {font-size:10.0pt;} @page Section1 {size:612.0pt 792.0pt;margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.Section1 {page:Section1;} Hi All, When we try to run a task sequence from an advertisment to rebuild a computer, on some workstations it fails with the following error:- Cannot Run Program This program is currently not available. When we look at the execmgr.log you see the following log entries:- Verifying content availability for package SYD0001E optional program * Could not find the policy in WMI for package SYD00001 program * The package SYD0001E is the task sequence, and the package SYD00001 is the x86 Boot Image. I have checked the distribution points (both normal and PXE), and the package SYD00001 is available, both are the same size, and time stamp. We have tried re-distributing the package, reboot the server, rebooting the client, all to no avail. Although we get this error on a handful of computers, at the same time it works fine on other computers, which suggests that the package SYD00001 is working fine. There is not a smsts.log file generated, so there is no information that I can give form that log file. Has anyone come across this problem? Thanks, Sally

Hi Sally, I have got the same problem since I installed SP1 for SCCM. I found this at MS http://support.microsoft.com/kb/949225/en-us/ Maybe there's a bug in SP1...:-) Regards Mel

Mel, I found the link for KB949225 just today and I also have the problem, only I've not yet installed SP1 for SCCM at this point. So maybe this issue has existed previously? I get the errors when running Task Sequences with "Run Command" selected. Heres my issue when running TSLauncher.exe from a command prompt of a CCM client: C:\>C:\WINDOWS\System32\CCM\TSLauncher.exeEnvironment scope "Global\{___REMOVED___}" successfully createdEnvironment scope "Global\{___REMOVED___}" successfully createdSMS Client GUIDGUID:___REMOVED___Capturing SMS client certificate store.Reading client installation properties.Client SSL is disabled. Setting state to 0x0.Registry entry 'Certificate Store' is either missing or empty.The 'Certificate Store' is empty in the registry, using default store name 'MY'. Registry entry 'Certificate Selection Criteria' is either missing or empty.Registry entry 'Select First Certificate' value is 0.Registry entry 'Internet MP Hostname' is either missing or empty.Error getting package location and access account information. Code 0x80070490Error initializing TS environment. Code 0x80070490Task sequence launcher advertisement failed!. Code 0x80070490Successfully finalized logs to SMS client log directory from C:\WINDOWS\System32\CCM\LogsFailed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\ActiveRequest Handle. Error code 0x80070002Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 Aaron

The problem, as described, must exist with or without the Service Pack applied. I compared the file versions that were listed in the KB article and noticed that most were updated with the SP1 update... My guess is that the hotfix won't do a lot of good if you have SP1 installed. The files listed as a part of theKB are older.

Sally, I'm having this problem as well, with 2007 R3, build 6487. Did you ever get this issue resolved?

Is this the only TS experiencing failures? Have you tried re-creating the advert for it?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Yes, this is the only TS experiencing the issue and yes, I have tried re-creating the advertisement.

How about duplicating the TS and creating a new advert? (just offering alternatives to hopefully get you going).Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I've experienced this issue....often. It happens where there are two or more task sequences advertising the same package ID, but one task sequence has been expired. To resolve, I remove all advertisements, verify that policy has replicated to all primaries (where there's a hierarchy involved), then readvertise the task sequence.

I've seen that said online before in various forums, but that's not the case in my instance. I even search through the reports to find all advertisements for a specific package. Since I deleted the advertisement for the TS I'm having problems with, there are no results. Nothing is advertising this package. On the other hand, task sequences that run the package don't show up in the report. I just created these packages and the TS, within a couple hours of each other. Nothing should be advertising the packages. Just in case, is there a good way to find out what task sequences reference a specific package or program?

Jason, It turned out the root cause of the problem was one of the packages that the TS called. Even though SCCM had been set to use the selected distribution points and said the package was installed on those DPs, it hadn't actually copied the files over. Updating to a new source version and ensuring the files copied correctly resolved the issue. Hopefully SCCM 2012 will do a better job of communicating a dependency problem, but I haven't had a chance to test it yet.