Computers not joining our Domain during Sysprep

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

[kyle.heath]

I’m also using this command to run sysprep.

cd c:\windows\system32\sysprep
sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml

[Tom Elliott]

Is your Windows 10 image an OEM type or Volume License type?

[kyle.heath]

@Tom-Elliott It’s a Volume License . Windows 10 EDU we use a KMS key.

[kyle.heath]

Been messing with the setupcomplete and nothing I change fixes the issue?

[Tom Elliott]

@kyle.heath Where is your setupcomplete.cmd file located on the post-sysprepped system?

[kyle.heath]

@Tom-Elliott I stick it in the C:\Windows\Setup\Scripts folder

[Wayne Workman]

@kyle.heath as Joe said, please post the entire C:\fog.log We can’t help much without knowing what’s in it.

[kyle.heath]

@Wayne-Workman I did. There was very little in the FOG log.

That’s all that was in it.

[kyle.heath]

Also…not sure if this matters but I am trying to “capture” my image from my VM. I created a windows 10 VM and set it up the way I wanted it. I fully registered it…and I chose join domain as 1 of the options it gives you when your full register a client. I put the unattend.xml in the sysprep folder and the setupcomplete in the scripts folder.

[Wayne Workman]

@kyle.heath And you’re looking at c:\fog.log ? If that’s literally it, reinstall the fog client. You should have more in the log just from when you installed it and rebooted before capture.

[kyle.heath]

@Wayne-Workman I reinstalled FOG and now there is no file at all. I’ll post a pic. Since I reinstalled FOG should I try to recapture now?