@Quazz Thank you good sir, this will help me in my future endeavors. I have already re-mastered my image using these steps, but it will help with my next rebuild.
@jaffascake FGO 1.1.2 is quite old. Does not have the kernel debug options mentioned. You might look into bringing up a new FOG trunk server to see if this one is imaging your Dell E5570 fine.
@ChrisRaff Can you please try this again and check the Test Management in the web gui after some minutes. Lately we had some machines that did actually image but just didn’t show anything on the client screen. By the way, which FOG version are you running?
@Wayne-Workman I remoted in and we found this was due to any webpage requiring ad auth to access. As that access was not granted it couldn’t download the file.
@falko If you have questions IM me on them. I couldn’t post everything because of contractual reasons. But I can help provide direction if you need it. The key with that process is to set the registry to tell it where to look for drivers. For now you can just create an empty c:\drivers folder change the registry key and stop. Everything in your image will work the same as it did before. Then you can get to the part about driver injection later.
i’m on my last day in my internship.
And i must say… i get a superduper good tutorial what i followed.
Its only for W7 (can work for w10 – i don’t know).
Ow ya
I tried a couple of things for injecting the drivers.
One is putting them in the windows/inf – that works great after sysprep.
Or you can use Stand Alone Driver Utility (SAD3) !
@Jbob Luckily (not best practice) 95% of our PC’s use the legacy client as part of our old images (recently moved to trunk). We have a handful of test machines that the new client is on for building new images. We also tested that if you don’t uncheck the option to put fog.log at the root of the 😄 drive, everything is ok. Thanks for your help!
I use snappy driver installer and I drop chipset + ethernet drivers in a driverpack folder inside of windows/inf and it works fine. After setup it launches SDI over network and installs the rest of the drivers.
There’s other reasons why sysprep could fail, such as Windows Media Player service (or whatever it’s called) running or your windows grace period expiring.
Got it thanks. Trying to trouble shoot AD not working. We never had a AD before, we were eDir. The machines manually join or will join with power shell. Thanks. so now I know when it renames it should join. Will help with my trouble shooting.
