Last week I wrote a blogpost about "Deployment issues with OSDPreserveDriveLetter parameter". In this blogpost I mentioned that OS deployment stops after installing the SCCM client. At the first application mentioned in the task sequence everything stops.
Error message in SMSTS.LOG:
- (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)- 401 - Authentication failure on request with anonymous access, retrying with context credentials.
I solved above issue by creating and deploying a new task sequence, with all same applications and steps in it.
Now it comes: The issue has nothing to do with the OSDPreserveDriveLetter parameter, but with change credentials in the task sequence. After changing credentials (for example: Domain Join account and password) in the task sequence, the issue is back again. Errors are same as mentioned above.
Is this issue specific for SCCM 2012 with SP1 and has anyone the same behaviour seen in SP1? I cannot found this on the "List of System Center 2012 SP1 issues" (which is still growing).
I think the SCCM configuration should be okay, because with a copied task sequence it installs all fine again. Strange issue it is..
Update 4-6-2013: For it seems there's still no solution for this. Have seen this issue once at customer location, curious when it happens again..