@george1421 So I’m not sure what fixed it but I cleaned up the Drivers, combed through my unattend.xml to make sure it was correct and removed a couple of erroneous drivers that were installed, sysprepped and uploaded the image and imaged a 755 this morning without issue!

@Andy-Abplanalp So I think it was the fact that I had enabled the local administrator account in windows but also had the settings in my unattend to enable that account. It was done out of habit. Once I disabled that account in windows, sysprepped again, and uploaded the image, I haven’t had a client fail yet, no matter the model.

@Andy-Abplanalp So I think it was the fact that I had enabled the local administrator account in windows but also had the settings in my unattend to enable that account. It was done out of habit. Once I disabled that account in windows, sysprepped again, and uploaded the image, I haven’t had a client fail yet, no matter the model.

@Andy-Abplanalp I believe that is what was happening. That local admin account did exist that was also in my unattend.xml to create and enable. I am working on that now.

I had an epiphany. I think I enabled the local account already in the image then when the unattend.xml runs it is unable to do what it needs to. Do you think that could be the issue?

@Andy-Abplanalp yes, it is adding the local admin account. Strange thing, i booted the image off of the domain, added to workgroup and then uploaded it again. Didn’t sysprep this time, reimaged a 745 and it worked without issue. I guess because it was no longer looking for that unattend.xml correct?

@george1421 I’ll have to check on the BIOS versions. I think they are up to date but I’ll double check. Should I reset them to factory default and then try?

The crazy part is that it is only affecting models Optiplex 740, 745, and 380 now. I have successfully used this image on Dell Optiplex 990, 360, GX520, 755, 760 and 780 as well as HP 6200, 6300, and 7800.

@george1421 I really don’t think it is the HDD space or anything with the HDD. The image size is only 45GB and I am throwing it onto at least an 80GB HDD. I’ll keep digging.

@Andy-Abplanalp probably too many. 5-10 at this point. I sysprep each time before I upload the image again.

Ok, since I got the 755 working, moved to the next trouble model which is a 380. It failed on startup, I went SHIFT+F10, mmc to view event viewer. Under System I am receiving a TON of Service startup error.

A couple are:

The event logging service encounterd an error (res=112) while initializing logging resources for channel Microsoft-Windows-WPD-MTPClassDriver/Operational

The event logging service encounterd an error (res=112) while initializing logging resources for channel Microsoft-Windows-WPD-CompositeClassDriver/Operational

The event logging service encounterd an error (res=112) while initializing logging resources for channel Microsoft-Windows-WPD-ClassInstaller/Operational

@george1421 So I’m not sure what fixed it but I cleaned up the Drivers, combed through my unattend.xml to make sure it was correct and removed a couple of erroneous drivers that were installed, sysprepped and uploaded the image and imaged a 755 this morning without issue!