Simo

My case hasn't really gone anywhere yet - we've been back and forward with logs... It's not going to be easy for many people to work around (though as noted above, there are some ways to get past it). It will be interesting to see whether they'll hang fire on more widespread availability of SCCM SP1 - because unless the problem occurs only with some pre-condition, it has the potential to make SCCM SP1 a fairly messy release. Guess we'll have to wait and see...

Unsurprisingly, cheating on the date also works, though is somewhat less practical

Hi, What's the precise error the task sequence gives? What stage does it occur at? Are any logs generated on the client? - Particularly the smsts.log (http://technet.microsoft.com/en-us/library/bb932135.aspx) (it's easier to get at if the command prompt is accessible from your boot image) Cheers, Simo

Howdy, By any chance are you running SCCM 2012 SP1? Either way - have a look at the expiry date of the code-signing certificate on the MSI, I'd guess it expires today... I suspect any clients you try to create now will fail. I've got a case logged with Microsoft about this issue as well. Cheers, Simo