@jpaul 0.32 is VERY old, but I’m glad you got it working.

@Wayne-Workman I don’t know when the global max size stopped being used, but I’m fairly certain it was removed when 1.0.0 released. (more or less).

I’ll look through the code to verify if anything is using it anymore.

Thanks Sebastian, for your answer.
Friday I’ll be in the office is I will try as you suggested

@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.

Bug confirmed, the culprit? There was a + typed in the code instead of a ,
https://github.com/FOGProject/fog-client/blob/master/Modules/GreenFOG/Windows/WindowsGreen.cs#L50

This will be patched in the next version.

@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.

Solved
https://forums.fogproject.org/topic/7441/fog-7645-and-client-10-6-printers-and-snapins-not-working/7

@Jbob Thanks a million! Now I sat down and made the described changes from the wiki and it works flawlessly.

@Arrowhead-IT Usually I like to use DNS but I don’t have access to it. I need to submit an email to my network dept. for that.

@Wayne-Workman Good to know that the new client works smoother.
I just upgraded to trunk a few days ago and didn’t have the time to test yet.

Hi there Goempie!

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).

Implementing the FOG Cloning Solution with
Universal Windows 7 Images

Good luck!

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.

Thank you so much for all your assistance!!!
FOG is fully functional again.

You guys are the best!!!

Did you ever try [SHIFT] + [SHUTDOWN] ?

@Tom-Elliott Just tested it and its working fine again now. Thanks!

@cojohnson You have a very unique troubleshooting style.

@Tom-Elliott @ChrisRaff That usually depends on the contents of the unattend file (assuming one is being used). Using the Fog client for domain joins would probably resolve this issue, assuming there is a group policy in place to disable the firewall or modify settings so that your remote management software would be able to connect.