Posts made by Jeffrey Boulais

@sudburr I believe that solved it! On my first attempt I inserted a 5 second delay after every command in my SetupComplete.cmd; that did not help. Then I added an additional 60 second delay at the start of the SetupComplete.cmd and my first test after was successful.

The image I am pushing is actually captured from a VM, not from an HDD.

Deploying a Windows 10 1803 image to Dell OptiPlex 9020, 5050, and 5060 SFF PCs. The deployment works as expected as long as the computers have a regular (spinning platters) hard drive. We have begun moving to SSDs recently, and now we are seeing some issues.

If I take any of the above models and put an SSD in, after deployment the PC reboots a few times and gets stuck on a “Why did my PC reboot?” screen. If the computer is manually rebooted it will eventually finish the processes (joining the domain, snapins, etc). All of the above models are set to legacy BIOS boot.

We have tried 3 different SSDs: Western Digital SATA, Wester Digital M.2, and LiteOn M.2. In all cases, the deployment works fine with a HDD, but fails with an SSD.

I’m having the same issue as is show in atessin’s screenshot of the “FOG Configuration” screen, but SELinux doesn’t appear to be my issue. I’ve run the 'sestatus|grep -e “SELinux status”| awk ‘{print $3}’ and it returned “disabled”.

@x23piracy That image is on 1607.

@x23piracy I believe this may have solved our issue; we are still testing. This was for a Windows 10 LTSB image.

@josken71 I think I am having a similar issue, on specific Dell computers (Optiplex 380s for example). Newer Dell computers do not have the issue. After imaging is complete, post sysprep re-enables the FOG Client and reboots the computer; on the troublesome computers the FOG Client never full re-enables. If you log in as local admin and check under services the FOG Client is set to automatic, but not started. If we manually start the service, the computer reboots after a few minutes, joins the domain, and renames the computer as expected.

This is not a problem on newer Dell computers or VMs.