@george1421 I can’t imagine the drivers would install correctly with the persist & do not clean set to true. This is probably your issue @kyle-heath.

@Rusty I’m using our existing Win 7 unattend file without any issues on Win 10 Enterprise (1511). I made zero changes to the file and everything within the file is being completed.

Server

• FOG Version: RC23 (6018? Tom custom build we’ll call it)
• OS: Ubuntu 14.04 LTS

Client

• Service Version: 0.11.5
• OS: Win 10 Enterprise

Description

If a new host reports through the client and shows up as a pending host, deleting the host adds it to the DB. Selecting approve or delete does the same action - registering the host in the DB.

@Psycholiquid Ah, so the pieces you’re doing in “FirstLogonCommands” I’m doing in the SetupComplete.cmd script.

del /Q /F C:\Windows\system32\sysprep\unattend.xml
del /Q /F C:\Windows\panther\unattend.xml
net start FOGService

@Tom-Elliott I agree that it should appear in pending if it’s not in the host DB but the client is installed on it and reporting to the server.

The issue is that when I delete the host from pending hosts (I’m not approving it), it should not still be added to the DB as a valid host.

@Arrowhead-IT You will likely run into issues with WSUS and KMS without running sysprep. I’m not trying to convince you to switch your method which seems to work well for you guys, but just want to be sure people know what the risks are when they do not use the Microsoft method of creating images.

@mr626 FYI - Their step 6 is wrong. See here: https://forums.fogproject.org/topic/6720/image-windows-10-upgrade/5

Also see here for existing sysprep info on Win 10 - https://forums.fogproject.org/topic/5873/windows-10-unattend-xml-sysprep-answer-file-challenge/2

@Arrowhead-IT You can remove the “Modern” apps in audit mode so you don’t run into any issues. See here: https://forums.fogproject.org/topic/6720/image-windows-10-upgrade/5

@Arrowhead-IT You have to be on the network selection screen in OOBE to get into audit mode. (I know this is completely non-obvious - it’s a very MS thing to do.)

@cojohnson You have a very unique troubleshooting style.

@Boyan-Biandov Hmm, that’s really odd. The unattend file I posted is what I still use today on brand new installs of 10586 (the Nov update) and I place the file (named unattend.xml) in C:\Windows\system32\sysprep - that’s it, nowhere else. Below is the sysprep command I execute (I run this from C:\Windows\system32\sysprep):

sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml