BDEDrive assigned drive letter in ConfigMgr 1610 and MDT 8443


Strange one today.

MDT integrated Task Sequence, version 8443, running in ConfigMgr (1610) kept creating a BDEDrive with an assigned drive letter when building a device using legacy BIOS.

I’d ticked the usual checkbox in the BDEDrive Partition properties, ‘Do not assign a drive letter to this partition’ but a drive letter was assigned with every build.

2017-04-24 22_07_16-Partition Properties.jpg

The fix was to untick the box!

Not seen this behaviour before.  I would love to know if others have experienced this. Let me know if you have.

2017-04-24 22_07_24-Partition Properties.jpg

7 comments

  1. We were getting this issue using SCCM 2012 R2 SP1. We have recently migrated to 1606 and soon will be upgrading to 1702. Will try this option with both versions.

  2. We had the same problem. A new deployment of Windows 10 left the system with the BDEDRIVE assigned to D:.
    After unchecking te Box in the TS it all worked well. No driver letter assignment.
    Thanks for the tip.

    System:
    SCCM 2012 R2 SP1 version 1702
    MDT 2013 Update 1

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s