MDT Fails only on HP desktop

PowerCycleIT wrote:

Big Green Man wrote:

PowerCycleIT wrote:

Big Green Man wrote:

PowerCycleIT wrote:

Gorfmaster1 wrote:

Once you update the drivers, you need to update the deployment share to update the Boot images. If you are PXE booting, you will also need to replace the Boot image with the updated boot images

I did update the deployment share and even completely rebuilt the boot images. This setup is a bit different than I'm used to, this one uses WDS as well. Do I need to replace the .wim file in WDS as well?

Yes. That's exactly what he's referring to.

Ok keep in mind WDS is new to me...so I went into WDS and replaced the .wim file with the newly updated one. The bad news is now when I boot to the deployment share my whole screen now looks different, it's just a big white screen with our logo on it and nothing else?  How does updating the wim file change the way the deployment looks?  The good news is on this screen I can hit F8 and ping the MDT server and can Net Use over to the deployment share but because the screen is just blank I have no options to deploy anything

How long did you let it sit at this stage? It should either prompt you for credentials to connect to deployment share or go right into the OSD wizard (task sequence selection, etc.) if you have credentials supplied in customsettings.ini.

Sometimes boot images don't generate correctly (still not sure why). When that happens, I find it best to delete them from the deployment share and then update the deployment share, which forces MDT to create them from scratch. After that, upload the new .wim files to WDS exactly as you did.

Sounds like we're making progress, though.

Good call on the waiting, I gave it a bit longer and the window finally popped up and I was able to move to the next step.  Strange how the background image changed, where does that come from?

Also can you bring me up to speed on ADK? I'm new to MDT and that is not familiar to me

Wonderful! We should still make sure you have the latest build of MDT and ADK (plus WinPE add-on). It all used to be a single download/install, but a lot of people don't need the WinPE stuff, so they have it separate now.

The ADK and WinPE add-on is basically the set of tools that MDT uses to create and service images. That means it's used for creating boot images (this is where the WinPE add-on is needed), injecting drivers, installing Windows, and servicing Windows during some post-install tasks.

The latest ADK and WinPE add-on can be downloaded here:

https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install Opens a new window

You can expect a new version to be released with every (or sometimes every other) Windows feature upgrade. Your ADK version should be equal to or greater than the version of Windows you're deploying.

The latest build of MDT can be downloaded here:

https://www.microsoft.com/en-us/download/details.aspx?id=54259 Opens a new window

After updating MDT, you'll need to right-click your deployment share and choose Upgrade Deployment Share. This will update any files in your deployment share that have been changed with the new version of MDT.

After updating the ADK and WinPE add-on, you'll need to update your deployment share. I typically do the MDT and ADK/WinPE updates back-to-back, then do the upgrade and update back-to-back. Then don't forget to replace your boot images in WDS.

For the background:When your deployment share is updated, the background that's used in the boot images will be copied from C:\Program Files\Microsoft Deployment Toolkit\Samples\background.bmp. It's likely that this file was changed after the boot images that existed when you took over were created. The default background is a grey image that says Microsoft Deployment Toolkit with a blue bar under it.

EDIT: Spelling