@Tom-Elliott I stick it in the C:\Windows\Setup\Scripts folder
Posts made by kyle.heath
-
RE: Computers not joining our Domain during Sysprep
-
RE: Computers not joining our Domain during Sysprep
Been messing with the setupcomplete and nothing I change fixes the issue?
-
RE: Computers not joining our Domain during Sysprep
@Tom-Elliott It’s a Volume License . Windows 10 EDU we use a KMS key.
-
RE: Computers not joining our Domain during Sysprep
I’m also using this command to run sysprep.
cd c:\windows\system32\sysprep
sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml -
RE: Computers not joining our Domain during Sysprep
@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.
-
RE: Computers not joining our Domain during Sysprep
@Joe-Schmitt Thanks! I’ll test it out and see if it works.
-
RE: Computers not joining our Domain during Sysprep
@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? -
RE: Computers not joining our Domain during Sysprep
@Tom-Elliott Alright I’m capturing the image now using just
sc config FOGService start= auto
net start FOGServiceI’ll see if it works this way. If not do you have any other suggestions? Should i post my unattend file?
-
RE: Computers not joining our Domain during Sysprep
@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.
-
RE: Computers not joining our Domain during Sysprep
@Quazz Alright I’ll test it now and see if it works…Thanks!
-
RE: Computers not joining our Domain during Sysprep
@Quazz Alright and keep the shutdown line?
-
RE: Computers not joining our Domain during Sysprep
@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?
-
RE: Computers not joining our Domain during Sysprep
@Quazz Alright I’ll try it and see if it works.
-
RE: Computers not joining our Domain during Sysprep
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.
-
RE: Computers not joining our Domain during Sysprep
@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? -
Computers not joining our Domain during Sysprep
Mon Jan 09, 2017 15:11 pm
Running Version 1.3.1-RC-2
SVN Revision: 6052Fog 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?
-
Images not deploying after 1.3.1 upgrade. Error messages below
Server
- FOG Version:
- OS:
Client
- Service Version:
- OS:
Description
Getting error messages when trying to image, I’ll post them below. It won’t let me deploy any of my images for some reason. It gets stuck on attempting to send inventory then the blue screen comes up like it’s going to image but it errors out. I’ll post screenshots below. Any help would be great as I really need to deploy some images.
-
RE: Help with Win10 Driver injection
@george1421 It’s not installing the same number because when i point the missing drivers to the C:\Windows\Drivers folder it installs them. I got them from the Dell website and they were on the Dell Deployment CAB. It installs certain ones like the networks ones, but SMBUS and USB ones it does not.
-
RE: Help with Win10 Driver injection
@Quazz So right now I have a folder on my FOG server that pushes out a folder called Drivers onto my machines. If I push out a folder called INF into windows instead of Drivers that should push them into the correct area for Microsoft installation. It’s installing some of my drivers but not all. SMBus and some USB drivers don’t install.
-
RE: Help with Win10 Driver injection
@MRCUR I tested this by changing the values of those to false and it still didn’t install all the drivers. It installed a couple, but I’m missing
I’m going to try dpinst.exe to see if that works.