Hello, We have a SCCM hierarchy including 1 central site and 2 primary sites. Central is only used for manage software packages, adv, TS, reporting, software updates and so on. Each primary site have its own DP, MP, PXE, SUP, SMP. The task sequence is the same for both, it's inherited from the Central site, same with the software packages. The TS works only on ONE of those primary sites. SMSTS.log on the client that fails says it's failing because of error code 0x80008004 which Microsoft says it's because the software package is disabled (it's not). This can be ensured cause it's working against the other site and they using the same packages. From SMSTS.LOG Failed to invoke Execution Manager to Install Software for PackageID="-" ProgramID="-" AdvertID="-" hr=080008004 InstallSoftware failed, hr=0x80008004 I have excluded the ID's. One thing that differs between the primary sites is the clock and time in the logs. On the one that works it's the correct time and on the one that isn't working it's 1/1/1601. Can this affect the failure of our TS? According to following forum post it can. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/9b72f604-04ae-4eec-9e42-405742f10a90/ But I'm using a virtual machine which have the correct BIOS time. It's the same machine which is succeeding and failing (depending which site it will be assigned). My thoughts was that maybe the sites time could affect the failure too. If so, how do I change it? It's correct inside Windows on the server. Any ideas what to do? Keep in mind it's working on one of the two sites and I'm using the same virtual client for both. Thanks! Best Regards

any other errors in your smsts.log ? are you pxe booting to do this ? on the site that is giving problems (in relation to the client getting deployed) do the component status logs reveal anything ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Error code 0x80008004 = "The program cannot run because it is currently disabled."Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

If you are advertising the TS for a refresh scenario, it sounds like that software package had been disabled at one point and the machine attempting to run it never processed the policy update enabling it. Try restarting the SMS Agent Host, refreshing the machine and user policies and running the TS again. /mike

Hi, thanks for the answers. I also get 'Task sequence execution failed with error code 80004005.'I have tried both PXE booting and boot media.Which logs do you have in mind? Mike: I'm advertising the TS for a bare metal scenario. Thanks, appreciated! :)

As your stated that the clock and time in the logs are different between the primary sites, you may check if this will cause the advertisement is expired on the problematic primary sites. Also please refer to the following threads to see if the information helps: SCCM error 0x80008004 software installation Task Sequence and Software Install FailsSabrina TechNet Community Support

As your stated that the clock and time in the logs are different between the primary sites, you may check if this will cause the advertisement is expired on the problematic primary sites. Also please refer to the following threads to see if the information helps: SCCM error 0x80008004 software installation Task Sequence and Software Install FailsSabrina TechNet Community Support