I think we can chalk this one up as solved. I went back to my original audit image and I undid pretty much everything I had tried with the exception of using the newer FOG client. With my original SetupComplete file and everything else back to the way it was, it seems to be working now.
I truly believe the fix was just a matter of updating the FOG client to 11.16 I apologize for all of the hassle but I appreciate all of the help you tried to give me.
@David-Osinski Okay, I can try to start from scratch. It has been working fine for years with dozens of images that I created, so I am pretty sure that process is fine. I might have missed something on the past two I created, but I kind of doubt it. The only thing that is really different this time is the addition of the 1903 update.
@Sebastian-Roth No, nothing in the event viewer like the last time. Like I said, if I manually start the service the first time it then automatically starts after about ten minutes or so on subsequent reboots.
@Sebastian-Roth Yes, all of the Windows updates have been applied. I do all of that before I capture my audit image. I even double checked this time before I created it. Other services appear to be starting just fine.
@Sebastian-Roth I think we are close. FOG is still not starting automatically though. I checked the event viewer and there are no errors there so I think it just isn’t getting the command to start as opposed to last time when it was trying but was erroring out. I tried starting it manually and then restarting and it does eventually start running in that case. Without doing that, I have been waiting about 45 minutes and the status hasn’t changed to running yet.
@Sebastian-Roth Let me check that. I have had to change my audit and sysprep images so many times through this troubleshooting that it is possible I moved the file you sent into the folder and didn’t rename it to modules.dll.
@Sebastian-Roth I replaced the code I had in my “setupcomplete” file with what you sent me in the previous message. I am still seeing the same behavior. After deploy, the Fog service is stopped even though it is set to Delayed-Automatic. When I try to start the Fog Service manually, it immediately stops. I don’t see anything in the FOG log that indicates why it is immediately stopping.
I went into Event viewer and here are the two errors it is showing when I try to start the service.
@Sebastian-Roth Okay, I am apparently a bit of a dolt, but it has led to another issue along the same lines… Let me explain.
Somewhere between upgrading to the new FOG client 0.11.16 and capturing my audit image, I failed to create the scripts folder and add my setup complete file to it. FOG Service was remaining disabled, that is why the log file was recording no information.
I took care of that and recaptured the image. Now when I deploy the image, it is not starting the FOG service it is setting the service to “automatic” but the service is never actually starting. Each time I go into the system after restarting, the FOG service is stopped. Is there something I needed to change in the setupcomplete file for the new FOG client?
This is the contents of my setupcomplete file that I have been using flawlessly for the past several years:
sc config FOGService start= auto
shutdown -t 0 -r
Thank you,
@george1421 Thanks for the reply. That makes sense to me. I figured it has to be something small and new with 1903 because it never happened before and nothing on my server has changed. Luckily right now I only have a handful of machines to image and I can wait it out until a new version comes out or something. Worst case as you said, I can add it to my unattend file. Thanks again.
@Sebastian-Roth So that’s it? I am just SOL? I can’t really change what it is doing automatically. I did exactly what you asked me to.
@Sebastian-Roth I apologize for the log delay in this. Here is the file after I used the other Modules.dll file.fog.log
@Sebastian-Roth No, this was just something I noticed before you posted that request. Sorry, like I said, things have been nuts and I am a couple of days behind to work on this.
I apologize, I had to put this on the back burner for a couple of days. It is the beginning of the school year and things are nuts. I am starting to wonder if it does have something to do with my Sysprep process and changes between 17xx and 19xx that the file doesn’t like. When I pushed my audit image to remove the older FOG client and install the newer one, I forgot to uncheck the box in FOG that says “Name Change/AD Join Forced Reboot”. As soon as I installed the new FOG client on the audit image, it joined itself to the domain. I wiped it back to my original audit image and followed the same process but I first unchecked that box. I uploaded my audit image and then rechecked that box before uploading my sysprepped image. Upon deploy the sysprep image will still not automatically join to my domain.
@Sebastian-Roth Oh crap, I already captured my image already. I am running out of time today, so I might not be able try and create a whole new image again until tomorrow.
@Sebastian-Roth Okay, thank you. I will adjust my audit image and add the new client. Maybe it not having to update that will fix things.
@Sebastian-Roth Thanks for the reply. Here is the screenshot:
As I said, nothing has been physically changed on the server from this work vs. not working. The only key thing that has been changed is I am using Windows 10 1903 instead of 17xx in my audit image.
@Sebastian-Roth I just imaged another machine this morning. Here is the log.fog.log
Great Questions! 
Sorry about that.
Server is 1.5.5
Client is 0.11.16
Thanks,
