Posts made by zpoling

@Wayne-Workman The fog service is disabled on startup until the setupcomplete.cmd is called for. That was actually my thread where you created the Wiki post about it

I just checked through our unattend file and I cannot find <ComputerName>*</ComputerName>.

@Quazz Enabling that feature did not fix this issue.

@george1421 Fog is doing all of the work as far as Active Directory.

Alrighty, I’ll enable that and see if it resolves the issue.

As the title says, our computers are joining our domain before the hostname is changed. I assume that’s what’s happening because the default Windows 10 names of “DESKTOP-XXXXXX” are appearing in mass under our default computers OU. After the Fogservice is done doing its stuff and correctly renames the machine, the previous names (DESKTOP-XXXXXX) are shown as disabled in the OU, while the proper hostname appears.

Is there a way to set the order of how the Fogservice performs its tasks?

EDIT: This issue only happens sometimes. I just imaged four machines, all of which joined the domain, but only two showed with the DESKTOP- hostnames.

@Wayne-Workman I had to look up where to put the script in the first place, and was instructed to use SetupComplete.cmd; that is what worked for me.

@Wayne-Workman This fixed my original issue as well. Thanks for the help!

@Quazz I’m sorry, do you mean remove the unattend file and upload the image without syspreping?

@Quazz

Hmm, we’ve always used the same unattend.xml file for all of our images without issue. I actually created another image today that used this unattend file. Uploaded the image and pulled it back down without any issue. It’s a very basic unattend to my understanding.

I’ll keep trying to image other G1’s and see if one finally works. If it does, I’ll see if there are some hardware differences.

@Quazz

Yes, we use /oobe /generalize /reboot in that order.

So this is a known issue?

We do not use the same image, but I have tried the image on other models and it doesn’t have this issue.

We sysprep the image right before capturing the image. Once the capture is done, I then attempt to pull the image back down onto the same laptop. Windows starts the initial setup process that occurs after sysprep; this is when the error occurs.

Specifically on our HP Probook G1 laptops, after deployment I am getting an error on the boot screen that says, “Windows Setup could not configure Windows to run on this computer’s hardware.” The message displays for a only a second, then the machine reboots. I then get the following error, “Windows could not complete the installation. To install Windows on this computer, restart the installation.” This error will stay on screen until I click okay.

We’ve had this issue happen since we were using Fog .32 and a Windows 7 image. We’ve since upgraded to the newest Trunk version multiple times, and this issue has occurred every time on these laptops. It has yet to happen on any other model of computer.