0.11.4 RC4 AD Question

RLane

So, I think I’m going crazy. I was using the release shortly before RC1 came out, had my master image with 0.11.2 and the host rename/join to AD worked flawless on Windows 10.

My SetupComplete has the required service configuration changes in it.

After upgrading to RC4 - using the same master image, same scripts, except 0.11.4 as the client version. Now, after I sysprep it (same method as before) – the service is set to automatic start up, but service status is stopped.

It is renaming the host but it is not joining to the domain because the service has not started.

How can I correct this in the master image? I disabled the service prior to sysprepping and also stopped it.

Tom Elliott

Either the service is first disabled or the service is set for automatic start in the image. Which is it? It cannot be both which is what it seems I’m reading.

That said does restarting the host start making things work again as they should?

RLane

@Tom-Elliott Pre sysprep: Service is disabled and then set to not automatically to run in start up.

Post sysprep: script is used in SetupComplete.cmd to start service.

Yes, in order to get it to work, I have to go back into services on the newly imaged device and manually start the service. It is set to automatically start but is not starting as it should. Once I manually start the service and reboot, it joins the domain and communicates with the servers – no issues.

Joe Schmitt

@RLane this is not an issue with AD joining. Instead of starting the service in setup complete try restarting the machine after enabling the service on startup.

x23piracy

@RLane Hi, are you using OEM? If so you can’t use SetupComplete.cmd but you can use firstlogoncommands in unattend.xml to call SetupComplete.cmd to get done automated i also create a local user and allow 1 autologon via unattend.xml.

Read the whole thread: https://forums.fogproject.org/topic/8097/fog-not-auto-joining-to-the-domain-requires-additional-restart-to-join-windows-10

Regards X23

Wayne Workman

@Joe-Schmitt is correct.

I had the exact same problem here:
https://forums.fogproject.org/topic/8187/fog-client-0-11-2-not-starting-right

The solution is to have setupcomplete.cmd enable the service, and then restart the machine. I’m putting it into the wiki here momentarily.

Also - it renaming the host would indicate that you have Early Hostname Changer enabled. This is going to cause you problems in the long run if you’re sys-prepping and using the new client. you should disable that. It’s in fog settings.

RLane

@Wayne-Workman said in 0.11.4 RC4 AD Question:

@Joe-Schmitt is correct.

I had the exact same problem here:
https://forums.fogproject.org/topic/8187/fog-client-0-11-2-not-starting-right

The solution is to have setupcomplete.cmd enable the service, and then restart the machine. I’m putting it into the wiki here momentarily.

Also - it renaming the host would indicate that you have Early Hostname Changer enabled. This is going to cause you problems in the long run if you’re sys-prepping and using the new client. you should disable that. It’s in fog settings.

Manually restarting it will resolve the issue however that is not exactly possible in most cases. You’re suggesting I had like “shutdown /r /t 60” to the end of my setupcomplete.cmd?

Wayne Workman

@RLane It’s already in the wiki.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

RLane

@Wayne-Workman Hmm… still no dice.

x23piracy

@RLane said in 0.11.4 RC4 AD Question:

@Wayne-Workman Hmm… still no dice.

Would you please answer my question?
https://forums.fogproject.org/post/74899

Regards X23

Bob Henderson

@x23piracy Look at the wiki bud, it’s in there line for line.

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

sc config FOGService start= auto
shutdown -t 0 -r

you basically put that in your setupcomplete.cmd and boom, done.

Wayne Workman

@x23piracy said in 0.11.4 RC4 AD Question:

@RLane Hi, are you using OEM? If so you can’t use SetupComplete.cmd but you can use firstlogoncommands in unattend.xml to call SetupComplete.cmd to get done automated i also create a local user and allow 1 autologon via unattend.xml.

Read the whole thread: https://forums.fogproject.org/topic/8097/fog-not-auto-joining-to-the-domain-requires-additional-restart-to-join-windows-10

Regards X23

Added this as a note in the wiki.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

x23piracy

@Bob-Henderson said in 0.11.4 RC4 AD Question:

@x23piracy Look at the wiki bud, it’s in there line for line.

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
sc config FOGService start= auto
shutdown -t 0 -r
you basically put that in your setupcomplete.cmd and boom, done.

I don’t use that reboot command, my setupcomplete.cmd looks like that:

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

Domain join and hostname change by fog will do any reboots needed
Maybe it’s the combination i use:

early hostname change off
1 time autologon with local user
setupcomplete execution via unattend.xml firstlogoncommand
fog used for changing hostname and domain join

Everything works fully automated.

Regards X23

x23piracy

@Wayne-Workman said in 0.11.4 RC4 AD Question:

Added this as a note in the wiki.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

alt text

Well done

Wayne Workman

@x23piracy said in 0.11.4 RC4 AD Question:

Domain join and hostname change by fog will do any reboots needed
Maybe it’s the combination i use:

early hostname change off
1 time autologon with local user
setupcomplete execution via unattend.xml firstlogoncommand
fog used for changing hostname and domain join

Everything works fully automated.
Regards X23

This is fine.
Of course, everyone is free to customize as much as they like.
The change to the recommended setup was requested by Senior Developer @Joe-Schmitt , who develops the new FOG Client - and other things. This change will guarantee the service is ran at the right moment, and timing will no longer be an issue on slow machines.

RLane

SetupComplete.cmd

@ECHO OFF

TITLE Post Sysprep Configuration Script

REM *** Activating Windows
TITLE Activating Windows 10...

cscript slmgr.vbs /skm sx.org
cscript slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript slmgr.vbs /ato

REM *** Activate Office 
TITLE Activating Office...

cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /sethst:x.org
cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /act

REM *** Starting FOG Service after boot
TITLE Start FOG Service...

sc config FOGService start= auto
net start FOGService

REM *** Finalize Script Actions and Cleanup the Scripting Environment
TITLE Finalizing Script Actions...

DEL /Q /F c:\Windows\System32\Sysprep\unattend.xml
DEL /Q /F c:\Windows\panther\unattend.xml
RD /S /Q c:\windows\setup\scripts

Unattend.xml

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing></servicing>
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:action="add" wcm:keyValue="b895faa4">
                    <Path>C:\Windows\Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <settings pass="generalize">
        <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SkipRearm>1</SkipRearm>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SkipAutoActivation>true</SkipAutoActivation>
        </component>
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Activates Built-in Administrator account</Description>
                    <Order>1</Order>
                    <Path>net user administrator /active:yes</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DesktopOptimization>
                <ShowWindowsStoreAppsOnTaskbar>false</ShowWindowsStoreAppsOnTaskbar>
                <GoToDesktopOnSignIn>false</GoToDesktopOnSignIn>
            </DesktopOptimization>
            <OEMInformation>
                <Logo>C:\Windows\System32\oobe\info\info.bmp</Logo>
                <Manufacturer>Hewlett Packard</Manufacturer>
                <SupportHours></SupportHours>
                <SupportURL></SupportURL>
            </OEMInformation>
            <TimeZone>Eastern Standard Time</TimeZone>
            <RegisteredOrganization>Name Here</RegisteredOrganization>
            <RegisteredOwner>Name Here</RegisteredOwner>
            <CopyProfile>true</CopyProfile>
            <ComputerName>*</ComputerName>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>en-us</InputLocale>
            <SystemLocale>en-us</SystemLocale>
            <UILanguage>en-us</UILanguage>
            <UserLocale>en-us</UserLocale>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <ProtectYourPC>1</ProtectYourPC>
                <HideEULAPage>true</HideEULAPage>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                <HideLocalAccountScreen>false</HideLocalAccountScreen>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>pw_here</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>pw_here</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Name>Administrator</Name>
                        <Group>Administrators</Group>
                        <DisplayName>Administrator</DisplayName>
                        <Description>Local Administrator</Description>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <VisualEffects>
                <FontSmoothing>ClearType</FontSmoothing>
            </VisualEffects>
            <RegisteredOrganization>Name</RegisteredOrganization>
            <RegisteredOwner>Name</RegisteredOwner>
            <TimeZone>Eastern Standard Time</TimeZone>
            <AutoLogon>
                <Password>
                    <Value>pw_here</Value>
                    <PlainText>false</PlainText>
                </Password>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>administrator</Username>
            </AutoLogon>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:c:/users/laner/desktop/windows%2010%20deployment/sw_dvd5_win_edu_10_1511.1_64bit_english_mlf_x20-93836/sources/install.wim#Windows 10 Education VL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Windows 10 for Education x64.

0.11.4 RC4 AD Question

193

11.6k

17.1k

154.6k