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

[Tom Elliott]

@x23piracy update the host first. That checkbox is imperfect as it attempts to set itself based on the host. If he host isn’t set it looks at what the default value is. My guess the default value is on, but the host value is 0.

[x23piracy]

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

@x23piracy update the host first. That checkbox is imperfect as it attempts to set itself based on the host. If he host isn’t set it looks at what the default value is. My guess the default value is on, but the host value is 0.

When i uncheck the option and update, it will be checked again. I think we had this in the past with some other option as a little bug.
Means, i uncheck, click update, popup tells option saved and then the checkbox is checked again while i unchecked it. hmmm funny…

I also tried to change this option for other hosts, it works no where, can you check for bug please?

How to find out if this option is set or not for a particular host when the webif always rechecks the checkbox?

Regards X23

[Tom Elliott]

@x23piracy It’s just how it is for now. Simple enough to fix, but not deeply impacting currently. Just understand, if you uncheck it and save it means you’ve unset that field, and the host will not perform those actions.

[x23piracy]

Hi,

i could finally fix my non working SetupComplete.cmd for Windows 10 OEM.
To get the SetupComplete.cmd being executed i use the unattend.xml section FirstLogonCommmands:

<SynchronousCommand wcm:action="add">
<Description>SetupComplete</Description>
<Order>1</Order>
<CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>

To get sure this is done automatically i allow autologon of a local admin once:

<AutoLogon>
<Password>
<Value>password</Value>
<PlainText>true</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>1</LogonCount>
<Username>username</Username>
</AutoLogon>

This will then execute the SetupComplete.xml while first login:

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

Regards X23

[Tom Elliott]

@x23piracy I’ve edited the source for the “enforce” option so it will display what the current selection is. If there is no selection, it will be unchecked. If there is a selection it will be checked. This will be available for RC 2.

[x23piracy]

@Tom-Elliott Thank You

[Wayne Workman]

wiki worthy

setupcomplete.cmd doesn’t run on OEM licensed hosts.

[Tom Elliott]

@Wayne-Workman for Windows 10.

[x23piracy]

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

#wiki worthy

setupcomplete.cmd doesn’t run on OEM licensed hosts.

not even only this also that:
https://forums.fogproject.org/post/74436

Regards X23

[x23piracy]

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

@Wayne-Workman for Windows 10.

no that should be the case since windows 8!
Look here: https://community.landesk.com/docs/DOC-33051

With Windows 8 and Windows 8.1 Microsoft made a change to the sysprep environment to improve the end user experience by skipping the SetupComplete.cmd section if an OEM license is detected. This allows the end user to get to the Welcome Screen faster. This is what causes provisioning to fail to start after the reboot.

My opinion? What a Bullshit, why not an option to enable it? Well they like to force business to enterprise section also by license reimaging oem is forbidden just FYI.

Regards X23

[Wayne Workman]

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

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

This has been added to the wiki previously, here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

[x23piracy]