Windows 11 SetupComplete.cmd skipped
-
I am having troubles with my SetupComplete.cmd from the guide running. On Windows 10 devices it works fine, but on 11 it doesn’t seem to run. I thought it might be because of the Windows Key i have in my unattend.xml, but after changing it it still doesn’t run. I had my Windows 10 key in the unattended file at first and thought that was it, and now have the extracted Windows 11 Key from an activated and working Windows 11 machine. Wondering if I need to get the right volume key, or if I’m missing something else.
Thanks in advance!
-
@george1421 So removing my key from the unattend file fixed the SetupComplete.cmd running issue. I forgot to tell it to join the domain after deploy and made a snap in for that which worked to test it out (I could tell the service was running because it rebooted to change its name as well but wanted to verify with the snap in). Windows must have activated based on something in the hardware because the machine is activated as well, so the key didn’t really need to be there I guess(?)
Also thanks for all your help, several years ago under another username you helped me a lot with random issues on another fog set up. The whole FOG project team is amazing!
-
@cookc I can’t speak specifically to Win11 deployment since I’ve left that space, but I’ve seen reports that the setupcomplete.cmd file doesn’t run in Win11 if you are using OEM media. VLK media appears to still run this file, but not OEM. I think that is regardless of the actual key you are using. Its the media (DVD Image) that seems to be causing this issue. But again I need to clarify that I don’t deploy windows products now so I have no first hand experience.
You maybe able to get around this by using the autoadmin login and the first run commands in the unattend.xml file.
I had to explain the process for another reason here: https://forums.fogproject.org/post/157075
-
@george1421 That first run commands is my next try. In case my Keys are somehow being read as OEM I just took them out for now to see if that helped or not. I am booting up a freshly imaged device to see if it will start up the fog service from the setupcomplete script or not. I’ll report back once I know.
-
@george1421 So removing my key from the unattend file fixed the SetupComplete.cmd running issue. I forgot to tell it to join the domain after deploy and made a snap in for that which worked to test it out (I could tell the service was running because it rebooted to change its name as well but wanted to verify with the snap in). Windows must have activated based on something in the hardware because the machine is activated as well, so the key didn’t really need to be there I guess(?)
Also thanks for all your help, several years ago under another username you helped me a lot with random issues on another fog set up. The whole FOG project team is amazing!
-
[[undefined-ago, C cookc, ]]
