question

Heimdallr avatar image
0 Votes"
Heimdallr asked Heimdallr commented

Getting ready screens during and post OSD TS - How to remove?

Hi All,

I found out that some people have problem after building their device, that they are stuck forever(or at least a very long time) on "getting ready" or "this might take several minutes" screen.

I do have a different issue though(I think so). During OSD, when device restarts after apply operating system step, It is getting stuck on "Getting Ready" for few moments. Then, after build, the first user logon is stuck on that "This might take several minutes" screen, for few minutes also, it's nothing that terrorizes me to be honest, but since it is my first built TS, I wanted to ask:

Is there a way to optimize this? Anyway to make whole TS run smoothly, without these screens, and getting rid of this screen during first log in? It would be a neat process of build>log in if I would be able to cut all the unnecessary screens

Thank you

mem-cm-osd
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered Heimdallr commented

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

We can try to use unattend.xml file or task sequence to skip/customize OOBE process. For more information, please refer to:
USE UNATTEND.XML TO SKIP WINDOWS 10 OOBE DURING AN SCCM TASK SEQUENCE
USE UNATTEND.XML TO FIX WINDOWS 10 SCCM IMAGE STUCK ON “JUST A MOMENT…” SCREEN
SCCM Customize Windows Out of Box Experience OOBE Using ConfigMgr

Hope it helps. Thanks for your time.

Best regards,
Simon


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for ideas.

I've used:

 <?xml version="1.0" encoding="utf-8"?>
 <unattend xmlns="urn:schemas-microsoft-com:unattend">
      <settings pass="oobeSystem">
           <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
                <OOBE>
                     <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                     <NetworkLocation>Work</NetworkLocation>
                     <SkipMachineOOBE>true</SkipMachineOOBE>
                     <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
           </component>
      </settings>
 </unattend>

It helped a bit, it's pretty good, just wondering if that's all that can be done. I am not sure as I never did it if we can cut off completely the getting ready screens. This above xml, lowered the time to minimum though so I am happy. Just wondering if we can go even further with that.


0 Votes 0 ·