Fog not auto joining to the domain requires additional restart to join-Windows 10

[Tom Elliott]

I going to guess you need to enable “Enforce changes even while users are logged in” as the client is unable to reboot the system first after the hostname is changed.

[Tom Elliott]

Moved to problems for now as we’re not sure if it is really a bug (but I’m sure many would have reported if it was at this point).

[LJedi]

@Tom-Elliott I did verify that those settings are correct and I still need to do a second restart for the PC to join to the domain.

[Tom Elliott]

@LJedi can you try unchecking and clearing and update then re apply these settings using the checkbox and saving the host again? May this can help?

[LJedi]

@Tom-Elliott Just an update. I did try that and that did not work. But I did look at the fog log and did notice that the last entry was over 30 minutes old so just for fun I looked at the Fog service and it was stopped. I restarted the service and the computer restarted to change the host name but was not joining to the domain so I looked again and the service was stopped again. The Startup time is set for Automatic but for some reason it is not starting on its own I had to go in and manually start the FogService. I think that is the smoking gun to my issue.

[Wayne Workman]

@LJedi Does the image have antivirus installed? Can you try to uninstall it and see how that goes?

[LJedi]

@Wayne-Workman No antivirus is installed in the image. I guess just the Windows 10 built in defender is on but other than that no. I will do more testing today. I post back what I find.

[Joe Schmitt]

Sounds to me like the service isnt set to start after imaging. If you sysprep and disable the service are you re enabling and starting it on completion?

[Wayne Workman]

Please post the contents of C:\Windows\Setup\scripts\SetupComplete.cmd

[x23piracy]

Hi,

i don’t have any problems from 10.6 up to 11.4 with domain joining for win10.
Before i sysprep i stop the fog service and set it to delayed-start, afaik delayed is not needed anymore but i still stay with this.

FYI, i don’t use setupcomplete.cmd for nothing

Regards X23

[Joe Schmitt]

@x23piracy while you can do that, it is risky and unadvised. You’re basically creating a race condition and just hoping it works out. I recommend following the written wiki article for how to configure the client and sysprep. We recommend setupcomplete.cmd as that is the proper and safest way to do so.

[LJedi]

@Joe-Schmitt For my image, I just install the Fog client. I do not do anything special with it before sysprep.

[Wayne Workman]

@LJedi said in Fog not auto joining to the domain requires additional restart to join-Windows 10:

@Joe-Schmitt For my image, I just install the Fog client. I do not do anything special with it before sysprep.

And that’s why it’s not working. You need to follow the wiki instructions, they are here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

[LJedi]

@Wayne-Workman Ah. Did not know I had to do that first. Thank you for your help.

[x23piracy]

@Joe-Schmitt said in Fog not auto joining to the domain requires additional restart to join-Windows 10:

@x23piracy while you can do that, it is risky and unadvised. You’re basically creating a race condition and just hoping it works out. I recommend following the written wiki article for how to configure the client and sysprep. We recommend setupcomplete.cmd as that is the proper and safest way to do so.

Hi,

well i know this but my SetupComplete.cmd never worked, i placed it in C:\Windows\Setup\scripts\ and i have the following in it:

del C:\Windows\System32\Sysprep\unattend.xml
sc config FOGService start= auto
net start FOGService

I am using Windows 10 Pro, Source iso is from “Media Creation Tool”.
If someone could tell why this is not working i could walk away from the knife edge i am using.

For my luck the normal workstations work with my method but when i try to redeploy to the vm i am using to prepare the image again and again i get the error message joe was talking about.

Is SetupComplete.cmd only working for Enterprise Win 10? I cannot imagine why else it’s not working for me. hmm…

Regards X23

[Greg Plamondon]

@x23piracy said in Fog not auto joining to the domain requires additional restart to join-Windows 10:

@Joe-Schmitt said in Fog not auto joining to the domain requires additional restart to join-Windows 10:

@x23piracy while you can do that, it is risky and unadvised. You’re basically creating a race condition and just hoping it works out. I recommend following the written wiki article for how to configure the client and sysprep. We recommend setupcomplete.cmd as that is the proper and safest way to do so.

Hi,

well i know this but my SetupComplete.cmd never worked, i placed it in C:\Windows\Setup\scripts\ and i have the following in it:

del C:\Windows\System32\Sysprep\unattend.xml
sc config FOGService start= auto
net start FOGService

I am using Windows 10 Pro, Source iso is from “Media Creation Tool”.
If someone could tell why this is not working i could walk away from the knife edge i am using.

For my luck the normal workstations work with my method but when i try to redeploy to the vm i am using to prepare the image again and again i get the error message joe was talking about.

Is SetupComplete.cmd only working for Enterprise Win 10? I cannot imagine why else it’s not working for me. hmm…

Regards X23

Does your setup complete contain a reboot command?

shutdown /r /f /t 0 

[x23piracy]

@Greg-Plamondon not it does not i pasted my complete SetupComplete.cmd in my post above, that is needed? What should this change? Lets say i place that reboot as last line, the unattend.xml should be deleted anyway, also the service auto should work but does not.

I don’t unterstand why a reboot line should let the 3 lines above work? confusing.
The Script is not triggered, if so u should not find the unattend.xml in sysprep folder anymore and the service should be set to auto but it’s still disabled, so the only reason could be that setupcomplete.cmd is not executed, the question is why?

Is anyone using SetupComplete.cmd with a Windows 10 Pro, while source is from Windows Media Creation Tool?

Regards X23

[x23piracy]

@x23piracy said in Fog not auto joining to the domain requires additional restart to join-Windows 10:

Is anyone using SetupComplete.cmd with a Windows 10 Pro, while source is from Windows Media Creation Tool?

Regards X23

Hi,

i am busted: http://www.overneteducation.it/v2beta/UserFiles/file/ebook/Microsoft_Press_ebook_Deploying_Windows_10_PDF.pdf

This damn company does not use Enterprise… grrr i have to stick with OEM. So i need to use my race condition method, damn it.

What should i do now?

Regards X23

[x23piracy]

@Joe-Schmitt said in Fog not auto joining to the domain requires additional restart to join-Windows 10:

@x23piracy while you can do that, it is risky and unadvised. You’re basically creating a race condition and just hoping it works out. I recommend following the written wiki article for how to configure the client and sysprep. We recommend setupcomplete.cmd as that is the proper and safest way to do so.

You should add this information to the wiki so others user does not try making this work with oem for days:
https://forums.fogproject.org/post/74398

Regards X23

[Tom Elliott]

@x23piracy I use oem at work and my setupcomplete.cmd does run.