[6-Jul-2018: Updated Script to v 1.2 – New .NET 3.5.1 install command (per Mike Horton @mikeh36)]
After attending MMS one of the items that I put on my “Post-MMS To Do” list was to patch my OS Upgrade package source the proper way. I don’t want to do it manually, nobody does, so I set out to learn exactly how to do it right and script it.
That where Mike Terrill and Johan Arwidmark come in.
“It’s been a long time…”
– Jimmy Page [Led Zeppelin]
It’s been too long since my last post.
Well, my wife’s laptop started getting the popup to reserve her copy of Windows 10 so I thought I’d spend a Sunday doing the upgrade. The problem was that the hard drive in her laptop was just about full. The laptop was a few years old and the drive (120GB) which might have been enough when it was new just wasn’t making the cut lately.
To be honest with her birthday coming up next month it’s about time to get her a new laptop.
Anyway, I needed to replace the original hard drive with a larger one so I could 1) complete the Windows 10 upgrade and 2) giver her some breathing room for a while.
The upgrade from Windows 7 to Windows 10 is pretty straight forward and well documented so I’m not going to focus on that. Instead I’m focused on the process of cloning her hard drive to the bigger drive.
Last week ConfigMgr blogger and Twitter friend Paul Winstanley ran a live blog detailing the process of using SCCM 2012 to upgrade an existing Windows 10 machine from one build (build 9926) to the next (build 10041).
Paul is a number of time zones ahead of me so he had a good head start when I tuned in Tuesday morning. We both ran into a bit of a stumbling block when our upgrades failed.
While Paul ran into this error upgrading 9926 to 10041, I received the same error attempting to upgrade Windows 8.1 to Windows 10 (9926).
In both of our cases the error was triggered by a mismatch of our original OS with the intended OS we were trying to upgrade to. Specifically in my case I was starting with the evaluation version of Windows 8.1 from the TechNet Evaluation Center, so the SKU of my Windows 8.1 machine was “EnterpriseEval” while the Windows 10 SKU was “Enterprise“. This mismatch triggered the error.
While I was troubleshooting the failure I started to document the process of setting this all up in my lab and I decided to share it for others who might be interested in giving this a try.
Just finished upgrading my machine from build 9879 to build 9926 and wanted to document some issues. 1) before I forget since the Windows Feedback app won’t work and 2) so others might learn from my pain.
First, the updated Start Menu is awful! I cannot re-size it. I can only make it full screen or the size that Microsoft has decided to make it. In 9879 I had made it taller, but now with 9926 I cannot. I also lost all my pinned items in both my Start Menu and my Taskbar. (Search isn’t working so I have to hunt my apps all down and re-pin them.) The alphabetized Start Menu is terrible. Some might like it, but not me. How can I change it? The Customize button is disabled.
My paused Hyper-V VMs will not restart. I get an error about the saved state is not compatible. I probably shot myself in the foot and should have powered my VMs down before starting the upgrade. But I imagine that if I had left them up and running over the weekend the 9926 build would have installed anyway, so….
I was really hoping to try this but there looks to be some GPO setting in our domain that is blocking it.