How to bypass "Let's connect you to a network"

Question

_{Tuesday, July 9, 2019 2:39 PM}

We recently determined that we need to reimage a large number of our workstations.  The reimaging task sequence appears to work fine until this appears on the screen at the end of the TS:

If someone is around to click Skip for now within the time limit set for TS execution, the TS completes successfully.  If no one is around, the TS times-out and fails.  The machine cannot connect to the Internet because our proxy is configured by user-based group policy.  The machine can connect to our internal network.  I am looking for a clue as to why this screen appears and how I can bypass it.  I was thinking it is due to activation, but we have a KMS server on the internal network.

TIA

All replies (5)

_{Wednesday, July 10, 2019 3:11 AM}

Hi Thomas Walters,

1.Firstly, it's recommended that we add an answer file to skip the network connection prompt or all OOBE steps. For more details, please refer to:
"Let's connect you to a network" - Let's NOT!
Windows 10 Editions - deployment issues
Windows 10 1703 OSD Issues

2.We can also try to disable the first sign-in animation by group policy. The path is located in: 
Computer Configuration > Administrative Templates > System > Logon > Disable "Show first sign-in animation".

Hope it helps. 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 [email protected].

_{Monday, July 15, 2019 3:03 AM}

Dear Sir,

Just checking in to see if there is any update. Has this issue been solved? Or is there any other assistance we can provide?

Please feel free to feedback and if the reply is helpful, please kindly click "Mark as answer". It would make the reply to the top and easier to be found for other people who has the similar question.

Thanks and regards,
Simon

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, July 15, 2019 11:05 AM}

Hi Simon,

Thank you for your response.  Unfortunately, my task sequence stops in the same place when using an unattend xml file with the settings described in the Reddit article you linked above.  I believe the answer to this question lies in determining exactly what the task sequence is trying to accomplish when it halts because it can't see the Internet.  Clicking "Skip this step" immediate takes to  machine to a state where a user can logon successfully.  No further warnings.  I can't find anything in the smsts.log file.  I keep coming up with two questions. 1) For what, other than activation, would a new Windows 10 machine need to get to the Internet?  2)  If it is activation, why isn't the machine activating using our internal KMS server?

Thanks,

Tom

_{Wednesday, July 17, 2019 7:23 AM}

Hi Tom,

1. For what, other than activation, would a new Windows 10 machine need to get to the Internet?
   For example, join the domain, install application. Connecting the network is necessary if there is any TS step that need use the ConfigMgr client. 

2)  If it is activation, why isn't the machine activating using our internal KMS server?
If the machine is able to join your domain and find the KMS server. You don't have to put any product key in the task sequence, just leave it blank . Once the workstation will be live and join to the domain it will try to activate itself. The way it work when you install the KMS service you can have the service (or a human) create a service record in the DNS. The computer will look for this service and will get the information where to activate.

Please refer to:Entering KMS Key During OSD

If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you. And if the reply is helpful, please kindly click "Mark as answer". It would make the reply to the top and easier to be found for other people who has the similar question.

Thanks and regards,
Simon 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, July 17, 2019 2:47 PM}

What version of ConfigMgr exactly are you using and what version of Windows exactly are you trying to deploy?

This is a ConfigMgr 2012 forum so assuming you are using 2012 (and not current branch), 2012 does *not* support any version of Windows 10 (except 2015 LTSB).

Jason | https://home.configmgrftw.com | @jasonsandys