PENDING Problem when deploying a custom image

[ggehman]

I've recently setup a new Config Manager site and I'm running into an issue I haven't seen before. I'll start by saying I'm using MCM 2303 with the latest hotfixes installed. I'm also using SQL Server 2022 and the latest version of Windows ADK.

Background Info:
We are using a customized Windows 10 Pro 22H2 image. When I create the image, I install Windows and use Shift-CTRL-F3 to enter Sysprep Audit mode. From there I make my customizations and then sysprep it using an answer file that creates a local admin account, copies the profile to the Default user profile, and adds some other settings like locales, time zone, and company information. I then use a capture task sequence to capture the image up to our server. This is the way I've created images for years and have never had an issue...until now.

Issue:
Now, when I deploy the image, I'm able to boot in and select the task sequence. The wim file downloads, is applied, drivers applied, and the client is downloaded as normal. However, once the computer restarts, it goes straight into OOBE. The client does not install, nor does any software. I'm able to login to the computer and find the _SMSTaskSequence folder on the root of the C: drive and the smsts.log shows no errors and looks like it just stops at the reboot and doesn't continue.
I have also noticed that after capturing the image. When the computer reboots, I get a screen that says, "Something went wrong" and below that it says OOBEREGION. I believe something is going wrong when the capture task sequence syspreps before the actual capture, but there are no error that I can see and it captures the image fine.

Lastly, I've tried running the same OSD task sequence using the base Windows 10 wim file from the ISO instead of the custom image and everything works fine. Image downloads, applies, drivers install. After reboot, the client and apps install. No errors.

I was wondering if anyone else has run into this or a similar issue and might have any insight as to how to resolve it?

Thanks

 

[AhmedLS]

I've recently setup a new Config Manager site and I'm running into an issue I haven't seen before. I'll start by saying I'm using MCM 2303 with the latest hotfixes installed. I'm also using SQL Server 2022 and the latest version of Windows ADK.

Background Info:
We are using a customized Windows 10 Pro 22H2 image. When I create the image, I install Windows and use Shift-CTRL-F3 to enter Sysprep Audit mode. From there I make my customizations and then sysprep it using an answer file that creates a local admin account, copies the profile to the Default user profile, and adds some other settings like locales, time zone, and company information. I then use a capture task sequence to capture the image up to our server. This is the way I've created images for years and have never had an issue...until now.

Issue:
Now, when I deploy the image, I'm able to boot in and select the task sequence. The wim file downloads, is applied, drivers applied, and the client is downloaded as normal. However, once the computer restarts, it goes straight into OOBE. The client does not install, nor does any software. I'm able to login to the computer and find the _SMSTaskSequence folder on the root of the C: drive and the smsts.log shows no errors and looks like it just stops at the reboot and doesn't continue.
I have also noticed that after capturing the image. When the computer reboots, I get a screen that says, "Something went wrong" and below that it says OOBEREGION. I believe something is going wrong when the capture task sequence syspreps before the actual capture, but there are no error that I can see and it captures the image fine.

Lastly, I've tried running the same OSD task sequence using the base Windows 10 wim file from the ISO instead of the custom image and everything works fine. Image downloads, applies, drivers install. After reboot, the client and apps install. No errors.

I was wondering if anyone else has run into this or a similar issue and might have any insight as to how to resolve it?

Thanks

it is hard to give you a specifc place to look at as you have a custom image. this type of error is due to an Unattended.xml file wrong configuration or Admin account access errors.

check if you can activate the admin account when the computer stops at the error you mentioned above. after activating the admin acount run the MSOOBE.exe and see if it works.

 

[janajman]

I've recently setup a new Config Manager site and I'm running into an issue I haven't seen before. I'll start by saying I'm using MCM 2303 with the latest hotfixes installed. I'm also using SQL Server 2022 and the latest version of Windows ADK.

Background Info:
We are using a customized Windows 10 Pro 22H2 image. When I create the image, I install Windows and use Shift-CTRL-F3 to enter Sysprep Audit mode. From there I make my customizations and then sysprep it using an answer file that creates a local admin account, copies the profile to the Default user profile, and adds some other settings like locales, time zone, and company information. I then use a capture task sequence to capture the image up to our server. This is the way I've created images for years and have never had an issue...until now.

Issue:
Now, when I deploy the image, I'm able to boot in and select the task sequence. The wim file downloads, is applied, drivers applied, and the client is downloaded as normal. However, once the computer restarts, it goes straight into OOBE. The client does not install, nor does any software. I'm able to login to the computer and find the _SMSTaskSequence folder on the root of the C: drive and the smsts.log shows no errors and looks like it just stops at the reboot and doesn't continue.
I have also noticed that after capturing the image. When the computer reboots, I get a screen that says, "Something went wrong" and below that it says OOBEREGION. I believe something is going wrong when the capture task sequence syspreps before the actual capture, but there are no error that I can see and it captures the image fine.

Lastly, I've tried running the same OSD task sequence using the base Windows 10 wim file from the ISO instead of the custom image and everything works fine. Image downloads, applies, drivers install. After reboot, the client and apps install. No errors.

I was wondering if anyone else has run into this or a similar issue and might have any insight as to how to resolve it?

Thankshi, how do you

I've recently setup a new Config Manager site and I'm running into an issue I haven't seen before. I'll start by saying I'm using MCM 2303 with the latest hotfixes installed. I'm also using SQL Server 2022 and the latest version of Windows ADK.

Background Info:
We are using a customized Windows 10 Pro 22H2 image. When I create the image, I install Windows and use Shift-CTRL-F3 to enter Sysprep Audit mode. From there I make my customizations and then sysprep it using an answer file that creates a local admin account, copies the profile to the Default user profile, and adds some other settings like locales, time zone, and company information. I then use a capture task sequence to capture the image up to our server. This is the way I've created images for years and have never had an issue...until now.

Issue:
Now, when I deploy the image, I'm able to boot in and select the task sequence. The wim file downloads, is applied, drivers applied, and the client is downloaded as normal. However, once the computer restarts, it goes straight into OOBE. The client does not install, nor does any software. I'm able to login to the computer and find the _SMSTaskSequence folder on the root of the C: drive and the smsts.log shows no errors and looks like it just stops at the reboot and doesn't continue.
I have also noticed that after capturing the image. When the computer reboots, I get a screen that says, "Something went wrong" and below that it says OOBEREGION. I believe something is going wrong when the capture task sequence syspreps before the actual capture, but there are no error that I can see and it captures the image fine.

Lastly, I've tried running the same OSD task sequence using the base Windows 10 wim file from the ISO instead of the custom image and everything works fine. Image downloads, applies, drivers install. After reboot, the client and apps install. No errors.

I was wondering if anyone else has run into this or a similar issue and might have any insight as to how to resolve it?

Thanks

Hi! im triing to acomplish the same thing in my organization (way I've created images for years) but run sysprep in audit mode on the reference machine, and cant create in sccm a TS only to capture the image, it has to include the step "prepare windows for capture" thats run sysprep again, deleting all the customizations.
can you please detail how you do it?
thanks!

sorry for mi english