Posts made by MRCUR

If you’re using WSUS, you should be running a sysprep generalize (at a minimum) before capturing the image. Otherwise you’ll have conflicting computer ID’s in WSUS.

Second this request.

@cojohnson You have a very unique troubleshooting style.

@Tom-Elliott @ChrisRaff That usually depends on the contents of the unattend file (assuming one is being used). Using the Fog client for domain joins would probably resolve this issue, assuming there is a group policy in place to disable the firewall or modify settings so that your remote management software would be able to connect.

@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.)

@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

@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 It speeds up a fast connection because there’s additional bandwidth to use that wouldn’t otherwise be used. On a 1Mb connection, that is not the issue - there simply isn’t any more bandwidth available to use.

@ITCC Try adding this to SetupComplete.cmd:

net start FOGService

@ITCC Is this happening immediately after imaging/sysprep?

@Wayne-Workman I would ask for verification that “spanning-tree bpdufilter enable” is set for the port OR that “spanning-tree portfast (int num) enable” is set.

@Wayne-Workman Have you verified that the problem port on the switch isn’t being put into blocking mode by STP? Running a sh span should give you the port status (at least on an HP switch, Cisco is likely the same). This would “linger” depending on your switch STP config.

@John-Sartoris I think Meraki may have added something for Win 10 in their latest Systems Manager release, but you’d need to be on the Enterprise version (free for 100 or less devices, paid otherwise).

@John-Sartoris I would try those commands again while in audit mode. They 100% work for me on Enterprise 1511 (latest update, build 11586.104 I think?) while in audit mode using the built in admin account. You’ll see a bunch of failures for apps that cannot be removed (like Edge), but it still works. The Start menu should be pretty much empty once they’re run.

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

@Arrowhead-IT Edge is also removed. We’re deploying Enterprise with all of the “Modern” apps removed at first. We’ll add some back later, but for now we’re starting with a minimal install.

@John-Sartoris I’m not sure what the issue is with connecting to the network. Below are the commands to remove the “Modern” apps and make it so they never reinstall.

Get-AppXPackage -AllUsers | Remove-AppXPackage
Get-AppXProvisionedPackage -Online | Remove-AppXProvisionedPackage -Online

Can you post the unattend file and whatever your cleanup script is? I just finished our initial batch of Win 10 Enterprise images and haven’t run into any issues with sysprep (I’m using our existing Win 7 sysprep file without any modifications).

This thread might be a good resource to compare your sysprep file to mine and others: https://forums.fogproject.org/topic/5873/windows-10-unattend-xml-sysprep-answer-file-challenge/15

I’m a big proponent of sysprep so I won’t try talking you out of using it.

@d4rk3 Are you running FOG on them?

@Tom-Elliott Thank you Tom!