Hi there
Having a miserable time trying to resolve OSD issues showing since SCCM 2012 SP2 upgrade.
OSD is basically shot.
DETAILS
OSD prior to the SP2 upgrade was fine, task sequences completed successfully. Post-SP2 upgrade the task sequence stops after restarting after the CCM Client is installed and goes straight to the logon screen.
To even get this far I have to use a MDT boot image created before the SP2 upgrade since newly created MDT boot images crash the task sequence almost immediately.
I can't post full logs due to nature of our business, but here is some information.
ccmsetup.log
Only error I can see in this log is 'Unexpected row count (0) retrieved from AD' then 'Failed to get site version from AD with error 0x80004005'.
I can't determine how serious this error is; had it been 'failed to get site code' that would have been different, but not sure what impact there is from not getting the site message. Further on in the log there is this entry 'Couldn't determine site version
for site 'sitecode'. Let deployment continue.' That suggests this isn't one of root causes of the CCM client failure.
Another thing I noticed in this log is, it first downloads the content from the default CCM Client package (the one created by the SCCM server) then shortly afterwards decides to instead download the content from a CCM Client package I created after the SP2
upgrade (created via a MDT task sequence). Not sure why the files in the default CCM Client package are replaced by the newer package.
At the very end of the ccmsetup.log file it says 'CcmSetup is exiting with return code 0'. This would obviously suggest a successful install of the CCM Client.
client.msi.log
No obvious errors in this log. Near the end there is this entry 'MSI (s) (D0:DC) [16:27:57:399]: Product: Configuration Manager Client -- Installation operation completed successfully' which suggests there were no problems installing the CCM Client.
smsts.log
Near the end of this log (since it stops when the task sequence stops) is this entry 'Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0'.
From all that it would seem the CCM Client is installing successfully - so why does it stop the task sequence afterwards?
ADK 8.1 was installed prior to the SP2 upgrade then MDT 2013 was installed afterwards.
The SP2 setup log states the process completed successfully.
Struggling badly with this one, have run out of blogs and posts to read, and frankly the information published exclusively about SP2 by Microsoft is very disappointing. R2, yes, screeds of information, but SP2 not so much.
No other changes were made other than ADK 8.1, SP2 and MDT 2013 being installed.
There are other issues too. For example, using a newly created MDT boot image (post-SP2 upgrade) crashes the task sequence immediately. One problem at a time though.
If anyone has encountered this and found the root problem and a resolution I'd be glad to hear.
Best regards
John
Glasgow, Scotland.