Thanks @george1421 , the reason I wasn’t using sysprep oobe generalize was because it was causing my system to lock up at “Please Wait”. I found that un-joining and re-joining it to the domain “generalizes” the system enough so that everything works for us. Anyway - I re-built the image and integrated the FOG Client (agent) into it. Now it appears the domain joining is working. Bad news is I’ll need to do another round of manual deployment, but that is the last time - after that I will have a full hands off deployment system. Thanks for your help so far!

I agree with George. Your unattend.xml is not complete/correct. Use Windows System Image Manager to create and verify the XML file. You can get the WSIM from Windows ADK: https://docs.microsoft.com/en-gb/windows-hardware/get-started/adk-install Here is one of my sysprep files: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <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"> <TimeZone>GTB Standard Time</TimeZone> <ProductKey>NW6C2-QMPVW-D7KKK-3GKT6-VCFB2</ProductKey> <!-- This is the Enterprise Edition key --> <!-- <ProductKey>VK7JG-NPHTM-C97JM-9MPGT-3V66T</ProductKey> --> <!-- This is the Professional Edition key --> <ComputerName>*</ComputerName> <RegisteredOrganization>CUNBM</RegisteredOrganization> <RegisteredOwner>LABSWKS</RegisteredOwner> <!-- LabS WorKStation --> <CopyProfile>true</CopyProfile> </component> <component name="Microsoft-Windows-UnattendedJoin" 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"> <Identification> <JoinWorkgroup>LABSWKS</JoinWorkgroup> </Identification> </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> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>ro-RO</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> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> </OOBE> <AutoLogon> <Enabled>true</Enabled> <Username>Student</Username> <Password> <Value>student</Value> <PlainText>true</PlainText> </Password> </AutoLogon> </component> </settings> <!-- <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"> <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> </component> </settings> --> </unattend>

@george1421 You are the man! That was it! I made the changes and the menu came up. It was the - before the Windows 10 1809 - Office 2013 image

Wait… Maybe I’ve been going at this wrong. Am I supposed to manually register each computer I image? I assumed the client would register the computer in the FOG server. My bad if so, I’ve looked at the quick register settings, enabled it but that isnt bringing new clients on to the server

@george1421 Thank you very much for the help, and surprised by the quick response that great work do you congratulations.

@browolf Are you running into the CPU stall issue too?

@fhrivers It would be saved in the directory where you ran the tcpdump command.

@Sebastian-Roth Brilliant. Thank you so much!

@Sebastian-Roth I have 70 same model PCs and same SSDs. The PCs were purchased at the same time and were configured on the same day.

Hey Tom my savior Here is the information in the graphical interface Here is the information with the command line I tried with the single disk - resizable option and it doesn’t work either

@Sebastian-Roth First, thanks for the effort. Sure, I’ll try what you suggest and see what I can come up with.

@Sebastian-Roth said in Adding needed repository... Failed!: @Wayne-Workman The installer test seems absolutely fine but possibly that’s because you have the package software-properties-common pre-installed? Can you check on that? I have had a look at the logs from your installer tests but the package is not mentioned and that’s why I guess you have it pre-installed… Yes, it’s pre-installed. This is on Ubuntu 18.04 server, minimal installation. root@ip-10-0-0-165:~# dpkg -l | grep software-properties-common ii software-properties-common 0.96.24.32.7 all manage the repositories that you install software from (common)

Will do.

@EricLA2K Thanks heaps for keeping us posted. I am fairly sure this will help other users as well!!

@dpusser_CMS Yes, ich can understand that it seems a little over the top to build your very own kernel just having started to use Linux. Bu hey, I think it’s never to early to get your fingers dirty and this is not very hard to do with all the things provided. There is not much you can mess up so I’d encourage you to just give it a go and simply ask if you think something is not going the right way. Just take a picture of the screen with an error or whatever and we’ll guide you the rest of the way!

@jsch As far as I know this is the latest tutorial on building a USB boot media: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image But still I think that you might run into an issue with that. Multicast might not work with that. We were discussing this in another thread with @george1421 and I am not sure if he was able to confirm multicast to work or not using the USB boot method.

@jcabuco Yeah, in gernal that’s right. But switching forth and back is not very convenient. You might want to look into setting up dnsmasq as ProxyDHCP as George suggested at some point.

@Sebastian-Roth I managed to cause a different issue troubleshooting, and had to rollback then update my server. I’ll probably make a separate thread later. Thank you though!

@ConJon Ok, I’ll take a closer look at this stuff in the next days! Information from the capture machine is fine. Exactly what I need.