Herc08
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
I’m looking to deploy a task sequence to automatically re-install Windows, and configured it based off collection variables. However, every time I run this task sequence (whether available or required), it “completes” (read as fails) after the Setup ConfigMgr step.
Now, the way we have our environment set up is by using nested task sequences. We have a Main Deployment (which is hidden), and from there call other TS’es based on the where the device is going. This works fine using boot media and UI++ 100% of the time. So what I did was create a TS called “Reimage” with the following steps:
The issue is, once it is starting to install the client, it seems the install calls for a reboot. However, once it reboots, it boots into a vanilla image. Usually, this goes into OSD-mode with the TS UI progress bar. I looked for logs, but nothing is there. There is no _SMSTaskSequence folder, no CCM nor CCMSETUP. Then I check the “panther” folder and look at setupacct.log and see that it completes successfully. After reading, it seems that setupcomplete.cmd needs to run, and it tries to run osdsetuphook.exe. However, that .exe is not there. I searched the entire C: drive in case it was moved. So my next step was to figure out if the .exe is getting copied in WinPE, and it is when I check the C: drive (along with the _SMSTaskSequence folder). It is sitting in System32. However, once it reboots, it is gone.
I also check smsts.log in WinPE and everything completes successfully, according to the log. While the task sequence is in progress, I have a Status Message window opened, and monitor it, and it says that the ConfigMgr Setup step has completed successfully…even though it is not.
So then I went through every TS that is nested and called, and copied each step into the Reimage TS, just to rule out nesting, but I got the same results. I verified the boot image is the same as our Main Deployment boot image and the boot media ISO.
After digging more into this, I found these links, but none of them fit my bills. In the Windows Noob post, the logs and status messages are pretty much dead on. I can say that we don’t use product keys in our Windows Image object.
https://forums.prajwaldesai.com/threads/osd-task-sequence-doesnt-continue-after-reboot.2533/
We have over 400+ devices across three floors and two buildings, and this will come in handy. Has anyone else ran across this?
Now, the way we have our environment set up is by using nested task sequences. We have a Main Deployment (which is hidden), and from there call other TS’es based on the where the device is going. This works fine using boot media and UI++ 100% of the time. So what I did was create a TS called “Reimage” with the following steps:
- Restart in WinPE
- Set TS Variables
- Format Disk
- Run Nested TS that contains majority of the steps
The issue is, once it is starting to install the client, it seems the install calls for a reboot. However, once it reboots, it boots into a vanilla image. Usually, this goes into OSD-mode with the TS UI progress bar. I looked for logs, but nothing is there. There is no _SMSTaskSequence folder, no CCM nor CCMSETUP. Then I check the “panther” folder and look at setupacct.log and see that it completes successfully. After reading, it seems that setupcomplete.cmd needs to run, and it tries to run osdsetuphook.exe. However, that .exe is not there. I searched the entire C: drive in case it was moved. So my next step was to figure out if the .exe is getting copied in WinPE, and it is when I check the C: drive (along with the _SMSTaskSequence folder). It is sitting in System32. However, once it reboots, it is gone.
I also check smsts.log in WinPE and everything completes successfully, according to the log. While the task sequence is in progress, I have a Status Message window opened, and monitor it, and it says that the ConfigMgr Setup step has completed successfully…even though it is not.
So then I went through every TS that is nested and called, and copied each step into the Reimage TS, just to rule out nesting, but I got the same results. I verified the boot image is the same as our Main Deployment boot image and the boot media ISO.
After digging more into this, I found these links, but none of them fit my bills. In the Windows Noob post, the logs and status messages are pretty much dead on. I can say that we don’t use product keys in our Windows Image object.
https://forums.prajwaldesai.com/threads/osd-task-sequence-doesnt-continue-after-reboot.2533/
We have over 400+ devices across three floors and two buildings, and this will come in handy. Has anyone else ran across this?
