We have Office 365 ProPlus in our Windows 10 Fog Image. We are a school district and use the device based activation. After imaging, a Fog snapin runs a batch file that calls the opptransition.exe with the noinstall parameter so it does the activation only (since it needs to run after the computer is renamed, which Fog does).
The strange thing is this snapin used to work fine. Recently it stopped working properly. We can see in the logs the process creates that the snapin is calling the process successfully, but the activation process is not working right for some reason. But if I manually run the same batch file it activates fine.

Any thoughts?

Thank you!

I had created the image originally in a Hyper-V virtual machine. Our newer machines are UEFI but we used it with some older machines ok that had legacy chosen in their bios and not uefi I think.

It may be UEFI based image then from the Hyper-V?

We have a Windows 10 image we are deploying via Fog. It is working on our new desktops and laptops and on many of our older computers. However, we have some older Dell 960 desktops. On these the image comes down fine. After the imaging is done we turn off the pxe boot as it wants to keep going there first. But the computer does not boot into windows or even try to load windows. As you can see in the screenshot, it just shows “no boot device available”. We have tried changing some of the bios settings. Manual installs of Windows work ok on it.

Thank you

That was exactly what I needed! After doing this we reimaged a number of computers and they had all the drivers each time.

The only trick was finding the dpinst.exe. Since MS removed it from the newer Windows 10 driver kits you have to get it from the Windows 8.1 driver kit.

Thank you for sharing

I created a Windows 10 image. I put drivers for our current HP desktop and HP laptop model in C:\drivers. In the answer file it has the drivers path set for c:\drivers.

Here is the weird thing. We have tested the image on a number of machines of the exact same hardware and on some the process will install all the drivers properly and on some it has unknown drivers or basic video drivers. We have tried letting the machine sit for awhile or doing a few more reboots to see if it would pick them up and it usually does not. We can right click on the unknown or wrong driver and have it search and it installs it but that is extra manual work and is weird since it sometimes adds them all.

Any ideas? I have no idea why some are doing it and some are not.

Thank you