ConfigMgr 2012 SP1 issues with OSDPreseveDriveLetter

Ran into this issue when trying deploy an existing image – the image was created without the propertly OSDPreseveDriveLetter in the Build and Capture task sequence.

My deployment task sequence kept failing Setup Windows and Configmgr.
The CCM client installed on the system ended up broken

The error messages from ccmsetup.log

C:WINDOWSccmsetup{1AF71F68-6089-4211-ADDC-06DF40606141}client.msi installation failed. Error text: ExitCode: 1603
– Client installation has failed too many times. Ccmsetup will now abort.

Solution:

– Add OSDPreseveDriveLetter=False to Build and Capture Task sequecen

I really wanted to use the image that i already had created, so here is what i did:

1. Added the OSDPreseveDriveLetter=False in my deployment task sequecen
2. Added /forceinstall /SMSMP=FQDN /SMSSLP=FQDN to step Setup Windows and ConfigMgr

Feel free to comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.