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

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

[Tom Elliott]

Of course I’m not doing sysprep for Windows 10 yet.

[x23piracy]

@Tom-Elliott how could it run if you are not using sysprep?

[x23piracy]

Hi,

here is the evidence that SetupComplete.cmd does not run with OEM:

https://community.landesk.com/docs/DOC-33051

Regards X23

[Tom Elliott]

@x23piracy What I meant is my windows 10 image is not sysprepped, so the setupcomplete.cmd isn’t even a thought. My windows 7 worked, which I’m guessing is the same for you.

I suppose, one approach, to get the “setupcomplete.cmd” effects with OEM and Windows 10 would be to have the machine auto login one time. In the Audit mode layout, add a startup script that calls your setup complete script. Once the setupcomplete is done, have the startup script delete itself as well. Then when the system finishes setup, it should login to the administrator prompt, and perform the actions you have defined in the startup script.

This is theory, I don’t know how feasible such a setup would actually be though. The nicety that was setupcomplete.cmd is the explorer wasn’t started until after the setupcomplete completed its tasks, which shortly after would be rebooted due to the re-enabling of the FOG Client. Using the “startup script” method would mean the administrator login is fully accessible.

[x23piracy]

@Tom-Elliott i tried the method with firstlogon command and this seems to work but i need to enforce hostname change, can someone tell me how to force this?

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 22.07.2016 11:52 Client-Info Client Version: 0.11.4
 22.07.2016 11:52 Client-Info Client OS:      Windows
 22.07.2016 11:52 Client-Info Server Version: 1.3.0-RC-1
 22.07.2016 11:52 Middleware::Response Success
 22.07.2016 11:52 HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
------------------------------------------------------------------------------

I need to force this, else i need to logoff manually.
My idea is also to use unattend.xml for 1 auto logon, but i need hostname change forced else i need to logoff manual.

Regards X23

[Tom Elliott]

@x23piracy In the GUI under Active Directory, there’s a checkbox under the password legacy field.