Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, July 18, 2019 1:28 AM
Trying to get a 1902 task sequence built out but it keeps getting hung at the "Getting Ready" and the "Just a Moment" Screen. I have been pretty stuck on this and not sure where to look. Most articles recommend adding a skip oobe line in your unattend.xml. I have done this and even tested it on multiple WIMS to no avail. Below is what I have in my unattend.xml for skipping oobe. I have added in clean XML's also to see if I had typoed anything but nothing still
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
After the task sequence runs Setup Windows and Configuration Manager, the machine reboots and gets stuck on either "Getting Ready" or the "Just a Moment" Screen. This is starting to hold me back. I have the 1902 hotfix installed in. Versions below.
- Version 1902
- Console Version:5.1902.1085.2600
- Site Version: 5.0.8790.1000
- MDT: 6.3.8456.1000
- ADK: 10.1.18362.1
This is a basic, non-MDT task sequence with the install.wim extracted from clean ISO. I have tried using a captured WIM from DISM, but it still runs into the same issue.
I saw where one user who posted this below:
>"I removed the wlidsvc start type configuration from the optimization script, regenerated my Windows 10 images and to my immense satisfaction, the issue was gone."
I am not sure how to go about this and any help would be appreciated.
The main logs that concern me are unattendGC\sutupact.log
[DJOIN.EXE] Unattended Join: NetJoinDomain attempt failed: 0x2, will retry in 10 seconds...
(This repeats about 50 times)
-[msoobe.exe] Processing cache change notification for setting NETWORKSTATUS.
-[msoobe.exe] Posted cache change notification for setting NETWORKSTATUS.
-[msoobe.exe] Connectivity changed: No connection detected
(These repeat about 50 times)
-[CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\WINDOWS\system32\oobe\info\oobe.xml with hr=0x80070003
-[CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\WINDOWS\system32\oobe\info\default\oobe.xml with hr=0x80070003
-[CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\WINDOWS\system32\oobe\info\244\oobe.xml with hr=0x80070003
-[CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\WINDOWS\system32\oobe\info\default\1033\oobe.xml with hr=0x80070003
-[CloudExperienceHostBroker.exe] Failed to load oobe.xml file at C:\WINDOWS\system32\oobe\info\244\1033\oobe.xml with hr=0x80070003
(This repeats twice)
-[msoobe.exe] CheckRegKey Reg get value (PushButtonReset) failed. with error 0x2
-[msoobe.exe] Failed to get recovery entries: 0xc0000225
-[msoobe.exe] Failed to find winre.wim because WinRE is not installed.
-[msoobe.exe] WinReValidateRecoveryWimInternal failed: 0x490
-[msoobe.exe] winreConfigureValidationTask failed: 0x490, a non critical error
-[msoobe.exe] RegOpenKeyEx(GP) failed: 0x2
-[msoobe.exe] WinReGetGroupPolicies failed with error code 0x2
-[msoobe.exe] Failed to get recovery entries: 0xc0000225
(This repeats twice)
Please tell me someone has seen this before or know of a solution. I am spinning my tires and getting nowhere at this point. If any more info is needed, let me know.
Thank you,
All replies (3)
Thursday, July 18, 2019 4:08 AM
Hi YoungLarryDavid69,
From the log, [DJOIN.EXE] Unattended Join: NetJoinDomain attempt failed: 0x2, will retry in 10 seconds...
- May we know if the SCCM client agent installation succeed on the workstation? Please review the ccmsetup.log, if the SCCM client agent installation failed on the workstation, thus the subsequent application installation task failed.
2.Please help take a look at the C:\Windows\debug\netsetup.log on the client computer where it's failing.
Are you specifying a specific OU in the task secuence, or are you joining to default "computers"?
3.Maybe adapter doesn't initialize quickly enough after the machine has rebooted and needs some time to get up. Please try the following actions:
•Change the Apply Network Settings -step to join your machine to workgroup.
•Then put a little pause after the Setup Windows & ConfigMgr step, for example add "Run a commandline" -step with command "ping localhost -n 10"
•After that, add "Join domain" -step to actually join the machine to your domain.
- May we know if you have cloned the OSD Task Sequence or copied the Task Sequence item? If yes, this may be related to the account not being able to join machines to the domain because it does not have the proper access, because cloning task sequences oftentimes do not preserve the passwords. The Network Settings item is one of these. So whenever you copy it, make sure you re-enter the password on the new copy or the computers may fail to join the OU.
Hope my answer could help you. Thanks for your time.
Best regards,
Simon Ren
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, July 19, 2019 2:57 AM
Hi,
May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Thanks and regards,
Simon
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, October 22, 2019 6:21 AM
Were you able to fix this?
AMIM MUHAMMAD KHAN | CTTCNET USER GROUP LEAD | EVENT SPEAKER, MCT, MCTS, MCITP-ENTERPRISE, MCSA http://amimkhan.wordpress.com