SCCM 2007 OSD defaults to D drive

Hi,

For some reason my OSD Win 7 deployments are defaulting to D drive. This has just start to happen...? It was always default to the C drive.

I have tried adding OSDPreserveDriveLetter vaule FALSE and it still installed on the D drive. I also tried select the location where you wan to apply this operating system destination Specific logical drive letter C drive and it installed on the D drive.

Any ideas how to fix this?

Thanks!



Try these


Method 1: Configure The Format And Partition Disk Task To Properly Assign Drive Letters

In this method, the Format and Partition Disk task is used to control what drive letters the partitions are assigned. Using this method will ensure that the OS partition receives a drive letter of C: while in WinPE. OSDPreserveDriveLetter will then be set to False so that after the Task Sequence reboots out of WinPE, the Windows partition ends up with the drive letter of C:


Method 2: Use WinPEshl.ini To Reassign Drive Letters Before The Task Sequence Begins

As explained in the Cause section, the problem can happen when a partition before the OS partition is assigned a drive letter before the OS partition is assigned a drive letter. This is a common scenario with Windows 7 and newer because the default configuration in Windows 7 and newer is to have a "System Reserved" partition (which is basically the boot partition) followed by the OS partition. Assigning of drive letters to these partitions is handled by WinPE when it first boots up. It normally assigns the System Reserved partition a drive letter of C: and the OS partition a drive letter of D:. After WinPE has assigned the drive letters, it processes a file called WinPEshl.ini. Any commands in the WinPEshl.ini file are then automatically ran.



Method 3: Force The New Windows OS To Reevaluate Drive Letters

Normally ConfigMgr determines what drive letters are assigned to each partition during the WinPE phase of the Task Sequence. However when deploying Windows outside of a ConfigMgr task sequence, Windows Setup determines the drive letters assigned to each partition. When allowing Windows to determine the drive letters, it will always assign the OS partition a drive letter of C:.

Instead of allowing ConfigMgr to determine the drive letters, the default behavior of allowing Windows to determine the drive letters can be used instead. This can be accomplished by deleting the registry entries that determine the drive letters as created by ConfigMgr.



Try these


Method 1: Configure The Format And Partition Disk Task To Properly Assign Drive Letters

In this method, the Format and Partition Disk task is used to control what drive letters the partitions are assigned. Using this method will ensure that the OS partition receives a drive letter of C: while in WinPE. OSDPreserveDriveLetter will then be set to False so that after the Task Sequence reboots out of WinPE, the Windows partition ends up with the drive letter of C:


Method 2: Use WinPEshl.ini To Reassign Drive Letters Before The Task Sequence Begins

As explained in the Cause section, the problem can happen when a partition before the OS partition is assigned a drive letter before the OS partition is assigned a drive letter. This is a common scenario with Windows 7 and newer because the default configuration in Windows 7 and newer is to have a "System Reserved" partition (which is basically the boot partition) followed by the OS partition. Assigning of drive letters to these partitions is handled by WinPE when it first boots up. It normally assigns the System Reserved partition a drive letter of C: and the OS partition a drive letter of D:. After WinPE has assigned the drive letters, it processes a file called WinPEshl.ini. Any commands in the WinPEshl.ini file are then automatically ran.



Method 3: Force The New Windows OS To Reevaluate Drive Letters

Normally ConfigMgr determines what drive letters are assigned to each partition during the WinPE phase of the Task Sequence. However when deploying Windows outside of a ConfigMgr task sequence, Windows Setup determines the drive letters assigned to each partition. When allowing Windows to determine the drive letters, it will always assign the OS partition a drive letter of C:.

Instead of allowing ConfigMgr to determine the drive letters, the default behavior of allowing Windows to determine the drive letters can be used instead. This can be accomplished by deleting the registry entries that determine the drive letters as created by ConfigMgr.



I would assume that you have just started to use some new hardware that you are imaging with your Windows 7 OSD? My guess, from experience in this and similar errors, is that the new hardware comes pre-configured with a small system partition. Your format & partition step is not removing this, and so is then deploying to the next drive it can, the D drive.

Check your format step to ensure it is correctly configured, as I believe that is where the cause of your error sits.



The below method worked.

http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence.aspx


Method 3: Force The New Windows OS To Reevaluate Drive Letters

Normally ConfigMgr determines what drive letters are assigned to each partition during the WinPE phase of the Task Sequence. However when deploying Windows outside of a ConfigMgr task sequence, Windows Setup determines the drive letters assigned to each partition. When allowing Windows to determine the drive letters, it will always assign the OS partition a drive letter of C:.

Instead of allowing ConfigMgr to determine the drive letters, the default behavior of allowing Windows to determine the drive letters can be used instead. This can be accomplished by deleting the registry entries that determine the drive letters as created by ConfigMgr.





Share this

Related Posts

There was an error in this gadget