Windows 7 32-bit to Windows 10 64-bit task sequence and MBR2GPT

The Problem: everything in your Windows 7 32-bit to Windows 10 64-bit wipe and load/refresh task sequence works (pretty much) flawlessly, but upon getting to Windows 10 64-bit and attempting to convert to GPT, you notice that Windows is loaded on your D: drive, not your C: drive, or you can’t find any volumes at all.

Documentation: Microsoft has a great article detailing the conversion from MBR to GPT on their docs website. In the table right below the video, they detail some common things you can do with MBR2GPT.

The second item in the list is a bit more meaningful and your success in successfully implementing a Win 7 32-bit to Windows 10 64-bit refresh (wipe and load) task sequence depends on understanding this bullet point:

Convert an MBR disk with BitLocker-encrypted volumes as long as protection has been suspended. To resume BitLocker after conversion, you will need to delete the existing protectors and recreate them.

Because this is a wipe and load/refresh scenario, we know we have to suspend Bitlocker to get the task sequence cooking successfully. Mike Terrill blogged about this and presented on it a couple of years back. Microsoft also has good supporting material over at docs.

So we will go with the assumption that you have found your favorite blog to suspend Bitlocker before you have started the process. (Hint: if you do not use Bitlocker, you should enable it in your Windows 10 task sequence).

Proposed Resolution: Here are the commands to delete your existing tpm protectors and recreating them:

manage-bde -protectors -delete c: -type tpm
manage-bde -protectors -add c: tpm

You should be able to create two task sequence command-line objects to successfully get you to Windows 10 64-bit.

MMS 2019

I attended the Midwest Management Summit a couple of weeks ago. There was a lot to learn in only four short days, but the sessions are very informative and packed with so much information that it is an invaluable resource for career development.

I have attended enough of them now that I am starting to recognize people, both presenters and other attendees.

We have a lot of new attendees this year, so that was also exciting. One of the attractions for me is that it is at the Mall of America, so it is very easy to get to if you live in the midwest.

Because of the success of the Desert edition, they are hosting a Jazz edition in NOLA this fall. Not to mention another edition in San Diego in 2020…so MMS is really going to spread it’s wings as a community-driven conference.

Some highlights for me:

  1. Learning a lot about Intune and Configure. One thing that I think most folks who use Intune never addressed is the “sync button”. Most of the presenters talked about the “Sync Button” like it is an actual button on which to click, but the “Sync Button” is actually more like a hot-link in a webpage under the Accounts section of Control Panel. As I proceed down the path of learning and managing endpoints with Intune, I will keep my ears open to determine if there is ever an actual button, or if we just invoke a sync via the Control Panel.
  2. Announcement of MBAM being fully integrated into ConfigMgr. This lit up #MMSMOA on Twitter when it was announced. (Note: Option #1…Intune! There may be a theme here…)
  3. Discussing the differences between Pulse mode and Rate Limits for Distribution Points with David James, the Director for the ConfigMgr product team at Microsoft. David explicitly stated that the Rate Limits setting uses a percentage of “available bandwidth” and not a percentage of “ALL bandwidth”. The suggestion that setting Rate Limits to 50% would mean that ConfigMgr will use 100% of the bandwidth 50% of the time is not valid.
  4. I was more receptive to learning about some agent-based vendor solutions that may allow us to eliminate Distribution Points and have a more intelligent shared bandwidth usage.
  5. An unplanned Campfire Session with Jörgen Nilsson and Doug Wilson. The great thing about MMS in general is having the chance to meet the people from around the world upon whose blogs you depend for doing your job! When I first started fonding soltuions for my challenges at work, I never imagined that I would ever actually meet the people on the other end of the Interwebs!
  6. And so much more!!! Follow or search the #MMSMOA hashtag for a wealth of information. For that matter, use it to find people to follow on Twitter. The #ConfigMgr hashtag is quite active and the community is responsive.

If you ever have the chance to attend an MMS, you should go. It is well worth the investment to see the community-focused experts show up and present live demos…not to mention the ConfigMgr product team routinely creates a new Technical Preview of Configure based on feedback received from the admins and systems management SMEs that attend the MMS conferences.

And there was fun stuff too…I did an Escape Room (The Heist) and we managed to get out after 45 minutes!

Updating my home lab to 1902, and an ADK install for WinPE

And so it begins.

I decided to take a day of PTO and as I was hanging around at home avoiding the snow, I decided it is high time for me to install the Powershell script to get me into the early ring for 1902.

A quick internet search got me here: ConfigMgr 1902: Enable Early Update Ring and I went ahead an updated my lab.

It had been a a bit since I had updated my ADK, so I went ahead and did that as well. This blog post will list the screenshot for WinPE installation only. Short, simple, next, next, voila!

Pre-requisites: I downloaded and installed the Windows ADK for Windows 10, version 1809. I then downloaded and installed the Windows PE add-on for the ADK. In the olden days, this was a single download. It is nice to have the WinPE download a separate entity now.

01. I like to install my required apps onto a drive other than my system drive. As such, I changed the install path to me E: drive. (Click Next).
02. If you like to send anonymous data to Microsoft, you will want to select YES in this Privacy question. If you prefer to NOT share anonymous usage data, select NO. (Click Next).
03. This is a license agreement. There are many like it, but this one is for the
Windows PE add-on for the ADK. (Click Accept).
04. There is only one option here. If you clear out this checkbox before clicking Install, please find another career. (Click Install).
05. Did you get a UAC prompt? I hope so. It helps to know when privileged operations or system-wide changes are about to happen. (Click Yes).
06. There is nothing to do here…unless you want to click Cancel, which would be sort of pointless. (DO NOT CLICK CANCEL. JUST KEEP WAITING).
07. Congratulations! You now have the latest version of WinPE in your lab environment! Hooray! (P.S. Well, you will as soon as you click CLOSE).

So this is my first blog post. I hope you enjoyed it. It was light, simple, and hopefully it will help someone out there…even if you just borrow screenshots for documentation. Enjoy!!