Computers not joining our Domain during Sysprep

[kyle.heath]

Mon Jan 09, 2017 15:11 pm
Running Version 1.3.1-RC-2
SVN Revision: 6052

Fog will not join my computer to our domain after upgrading our FOG Server/Client. I’ll post photos below of my setupcomplete file and our FOG settings but it looks like my setupcomplete is not running and the FOG service may not be starting. Any help?

[Tom Elliott]

First, you should enable the FOGService to auto, but if you’re going to be rebooting the machine DO NOT START the client.

Why?

The client is fast. If the reboot happens when the client is doing work, it’s a good way to get things into a tricky situation.

[kyle.heath]

@Tom-Elliott Am I not enabling the FOG service to auto with the sc config FogService start=auto
net start FogService??
Do I need to change those 2 lines? Also does the caps matter? Should I have FOGService instead of FogService?
I’m not sure I understand what you mean by rebooting the machine do not start the client? Should I take our the last shutdown line?

[kyle.heath]

My image restarts 2 times and then is stuck…it doesn’t restart the 3rd time and join the domain. When I login to the local admin account the FOG log in the drive has tons of information in it. I can post some screenshots if that would help.

[Quazz]

Imo, just remove the shutdown line and it should be fine.

[kyle.heath]

@Quazz Alright I’ll try it and see if it works.

[Quazz]

@kyle.heath To clarify what Tom was getting at: the client should not boot during OOBE phase, which is why you set it to disabled in the image and to auto in the setupcomplete, but this is pointless if you’re going to force a reboot anyway as it will be running in that second round and mess things up.

[kyle.heath]

@Quazz Ahh ok that makes sense…yeah it usually does 3 reboots and on the 3rd it joins the domain. I’ll take out the shutdown line and see if it works. Does the caps in FOGService matter? Can i use FogService and it still work?

[Quazz]

@kyle.heath Yes, the caps matter. But, it seems like I was wrong to suggest removing the reboot line. You should probably remove the

net start FOGService

line. There’s no need to start the service in that instance and is in fact detrimental as you’ve found.

[kyle.heath]

@Quazz Alright and keep the shutdown line?

[Quazz]

@kyle.heath Yes.

[kyle.heath]

@Quazz Alright I’ll test it now and see if it works…Thanks!

[kyle.heath]

@Quazz It still didn’t work. I’m going to take out everything and just have the FOG info in the setupcomplete to see if it works that way.

[Tom Elliott]

If your system is rebooting three times this might be the problem. systemcomplete.cmd only runs on the first run. Once the system has rebooted after getting to the first login, systemcomplete doesn’t get called anymore.

You can validate this by looking in services.msc and I’ll guess the FOGService is still in a disabled state.

[kyle.heath]

@Tom-Elliott Alright I’m capturing the image now using just
sc config FOGService start= auto
net start FOGService

I’ll see if it works this way. If not do you have any other suggestions? Should i post my unattend file?

[Joe Schmitt]

@kyle.heath here’s my 2 cents. Your script should look like:

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

as described in https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep Having any other setup in your script to start the client is not advised as it creates race conditions.

Now, if after that the domain joining still does not happen (will take a couple reboots), post the C:\fog.log file from the host.

[kyle.heath]

@Joe-Schmitt Thanks a lot Joe. I will try this and see if it works. Should i keep both lines
sc config FOGService start= auto
net start FOGService
or just use the top line?

[Joe Schmitt]

@kyle.heath use the snippet i posted (remove the net start FOGService in yours). Manually starting the client is hit or miss right after sysprep and especially if you are invoking a shutdown it will cause many issues. I’m still working on better sysprep integration with the client, but it’s difficult work.

[kyle.heath]

@Joe-Schmitt Thanks! I’ll test it out and see if it works.

[kyle.heath]

@Joe-Schmitt Alright it didn’t work. I’m going to post the FOG.log file and I’ll post my Unattend.xml file. Maybe posting those will help. It’s basically logging itself into the local admin account and not joining the domain. Before when it worked it would finish at the login screen, connected to the domain. Maybe something in my Unattend is also off, but the FOG service did not start. It’s shown as disabled in services.

This is the FOG.log

Below is my Unattend.xml file

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="generalize">
        <component name="Microsoft-Windows-PnpSysprep" 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">
            <DoNotCleanUpNonPresentDevices>false</DoNotCleanUpNonPresentDevices>
            <PersistAllDeviceInstalls>false</PersistAllDeviceInstalls>
        </component>
        <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-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">
            <ExtendOSPartition>
                <Extend>true</Extend>
            </ExtendOSPartition>
        </component>
        <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-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">
            <ComputerName>*</ComputerName>
            <CopyProfile>true</CopyProfile>
            <RegisteredOrganization>Microsoft</RegisteredOrganization>
            <RegisteredOwner>AutoBVT</RegisteredOwner>
            <ShowWindowsLive>false</ShowWindowsLive>
            <TimeZone>Eastern Standard Time</TimeZone>
            <ProductKey>Windows 10 Product Key Here</ProductKey>
        </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">
            <AutoLogon>
                <Password>
                    <Value>Password</Value>
                    <PlainText>false</PlainText>
                </Password>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>CFA</Username>
            </AutoLogon>
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>Password</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>Password</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Description>Local Administrator</Description>
                        <DisplayName>CFA</DisplayName>
                        <Group>Administrator</Group>
                        <Name>CFA</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
        </component>
    </settings>
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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="1">
                    <Path>C:\Windows\Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:c:/users/kyle.heath/desktop/windows%2010/sources/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

It’s basically logging into that CFA local admin account without joining the domain. If you guys see anything that’s wrong in my unattend please let me know. This is really weird because this was working before I upgraded my FOG Client.