Its been a little while since I’ve had chance to sit down and think up a post. The end of September was the deadline for a big project I’ve been working on, so I was pretty busy trying to make sure things were done. Things have slightly settled down now, so I’ve had more time to play with personal projects and improve my ConfigMgr app.
A separate idea I had for PowerShell and ConfigMgr, was to create some kind of portal for 1st line technicians to add machines for Operating System builds. The idea being they wouldnt have to go into the console to import computer information. My initial thoughts were to use a html frontend, which I would host on a tiny web server and then have PowerShell do my script work. After digging into this I figured it would require a proper web app to do something like that, using server code.
Continue reading “ConfigMgr Preflight with XAML and PowerShell Part 2”
I came across this issue during a deployment for a customer:
Windows PE initialization failed with error code 0x80220014.
The fix is well documented here.
Essentially, the PE wims included in ADK 10 1511 require a fixed schema.dat file. So you have to mount the wims in DISM and replace the existing schema.dat files with the ones provided in the hotfix download.
Or you could update to ADK 10 1607.
I’ve had a bit of time recently to work on my ConfigMgr lab environment and one of the tasks I had on my list was to look into offline image servicing. This functionality allows you to inject updates into your reference image on a scheduled basis, straight from the console.
However, when I tried to schedule servicing for my Windows 10 1511 images, it only showed me Windows 8 updates. After a lot of digging I discovered that in my image properties it was displaying my image version number as
6.2.10240.16384. You can see this by selecting your image and in the bottom pane, viewing your OS Version:
Continue reading “Offline Image Servicing – Windows 10 Image shows Windows 8 updates”