Windows 10: How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

John Hallberg1 · Mar 28, 2025

Hi,We have starting to use Autopilot to deploy our windows computer. User-driven is no problem but when we uses Self-deploying the computer sometimes stops in OOBE with the message "Let´s connect you to a network". I noticed that it take a few seconds before Network show up as Connected and it´s causes the deployment to halt. If you click next all works fine but I want "zero touch". We have over 1000 lab computers deployed by using self deployment and we can´t get out to each on of them to click next. It´s have to be automatic. Is there anything I can do to solve this issue? We traditionally u

:)

Brink · Mar 28, 2025

Modernizing Windows deployment with Windows AutoPilot

Windows AutoPilot is a suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. As Rob Lefferts announced this morning, the Windows AutoPilot Deployment service marks the start of these capabilities. With Windows AutoPilot, IT professionals can customize the Out of Box Experience (OOBE) for Windows 10 PCs and enable end users to take a brand-new Windows 10 device and—with just a few clicks—have a fully-configured device ready for business use. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Most importantly, users can go through the process independently, without making any decisions and without needing to involve IT.

I’m Sidd Mantri, Principal PM Manager for Windows AutoPilot and I’ll now explain Windows AutoPilot in a little more detail.

How does Windows AutoPilot Deployment work?

With Windows 10, version 1703 (also referred to as the Creators Update), you can register your organization’s devices with the Windows AutoPilot Deployment service to your Azure Active Directory (Azure AD) tenant and customize the OOBE for your end users using a cloud configuration. This enables users to walk through the self-service deployment of their new Windows 10 devices without needing IT assistance.

Here’s how it works:

Hand out a brand new Windows 10 PC to the user.

The user unboxes and powers on the new Windows 10 device. With a few clicks (select language, choose keyboard layout, connect to a network), the device is recognized as your organization’s device and delivers the customized OOBE you configured. (Additional steps in the standard Windows 10 OOBE such as choosing between a personal device or a work device, selecting privacy settings, OEM registration, Cortana setup, and OneDrive setup can be skipped using Windows AutoPilot Deployment.)*

Once connected to the network, Windows prompts the user to sign with their Azure AD e-mail address and password. (The sign-in experience is branded with your organization’s name and logo before your employee enters their Azure AD sign-in information.)

Upon successful authentication, the device joins Azure AD and is automatically enrolled in Microsoft Intune or other mobile device management (MDM) solution.**

Of course, there is no better way to understand this process than to see it in action. Watch this short Microsoft Mechanics video for an overview:

4K4hC5NchbE

Don’t have time to watch this video now? Bookmark it for easy viewing later.

Some of the benefits of Windows AutoPilot are:

Intune can push policies, settings, and configuration to the device, and install Office 365 and other apps without IT ever having to touch the device or apply a custom image to the device.

Intune can configure Windows Update for Business to apply the latest updates.

The device can automatically upgrade from Windows 10 Pro to Windows 10 Enterprise seamlessly using AAD–no product keys to manage, no reboots, no prompts for the user.***

For Windows AutoPilot Deployment to work, you must register your organization-owned Windows 10 devices to your organization’s Azure AD tenant. This is possible for new Windows 10 PCs acquired from OEMs, distributors, and resellers participating in the Windows AutoPilot Deployment Program. It will soon be possible for OEMs and resellers to take care of this registration automatically on your behalf when fulfilling device orders in the future. Contact your device reseller or OEM partner for their plans to support the Windows AutoPilot Deployment Program.

The Surface team is working with customers and partners to roll out the Windows AutoPilot Deployment program and expects to make it broadly available to customers later this year. Contact your Microsoft Sales team representative for details.

Alternatively, for existing Windows 10 PCs running version 1703 (or higher), you can query the DeviceIDs programmatically and build the deviceID file to register applicable devices into the Windows AutoPilot Deployment service.

When can I start using Windows AutoPilot?

These capabilities are available today for Windows 10, version 1703. To try them out, check out the Windows AutoPilot documentation, which will walk you through the process. The Microsoft Store for Business and Cloud Solution Provider program will provide organizations and partners with the ability to register devices and configure Windows AutoPilot Deployment in the near future. We’re also working with MDM partners to integrate the AutoPilot Deployment configuration experience.

For scenarios where IT will be configuring the device with traditional on-premises or cloud-based modern IT scenarios, Windows Configuration Designer can be used to help automate the process. For simpler school scenarios, the Set Up School PCs app (announced last year) can be used as well. For a comparison of these scenarios, see the Windows AutoPilot overview.

As we move down the path towards modern IT, we will continue to add additional capabilities to Windows AutoPilot to ensure that the process is as simple as possible for both IT and the end user. At the same time, we will strive to provide additional “stepping stone” capabilities for organizations who feel they need to move in more measured increments toward this modern IT future.

New capabilities to Windows AutoPilot that will be added in the Windows 10 Fall Creators Update release later this year include:

Self-service deployment for Active Directory domain-joined devices – Windows AutoPilot Deployment will enable self-service deployment capabilities to get new Windows 10 devices into an Active Directory domain-joined state along with Microsoft Intune enrollment.

Enhanced personalization for self-service deployment – Windows AutoPilot will offer the ability to pre-assign a new Windows 10 device to a specific user in your organization and deliver a highly-personalized OOBE.

Windows AutoPilot Reset – A new reset capability In Windows AutoPilot will enable organizations to easily reset their configured devices while still maintaining MDM enrollment and the Azure AD join state, and automatically get the device back into a business-ready state.

* Starting with Windows 10, version 1703, captive portals are supported in the Windows 10 OOBE, so users can still leverage self-service deployment with Windows AutoPilot when using a Wi-Fi hotspot.
** Automatic enrollment requires an Azure AD Premium subscription.
*** Requires a Windows 10 Enterprise E3 subscription.

How can I learn more about Windows AutoPilot?

For tips on how to best take advantage of Windows AutoPilot in your organization, and a walkthrough of common usage scenarios, stay tuned to this blog and follow us on Twitter @MSWindowsITPro for an announcement about a special Windows AutoPilot webcast in late July.

We’ll also be hosting a one-hour “Ask Microsoft Anything” about Windows 10 management event at 9:00 a.m. Pacific Time on July 25th. Members of the Windows engineering and product teams will be standing by to answer your questions.

Click to expand...

Source: Modernizing Windows deployment with Windows AutoPilot Windows for IT Pros

Brink · Mar 28, 2025

Modernizing Windows deployment with Windows AutoPilot

Windows AutoPilot is a suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. As Rob Lefferts announced this morning, the Windows AutoPilot Deployment service marks the start of these capabilities. With Windows AutoPilot, IT professionals can customize the Out of Box Experience (OOBE) for Windows 10 PCs and enable end users to take a brand-new Windows 10 device and—with just a few clicks—have a fully-configured device ready for business use. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Most importantly, users can go through the process independently, without making any decisions and without needing to involve IT.

I’m Sidd Mantri, Principal PM Manager for Windows AutoPilot and I’ll now explain Windows AutoPilot in a little more detail.

How does Windows AutoPilot Deployment work?

With Windows 10, version 1703 (also referred to as the Creators Update), you can register your organization’s devices with the Windows AutoPilot Deployment service to your Azure Active Directory (Azure AD) tenant and customize the OOBE for your end users using a cloud configuration. This enables users to walk through the self-service deployment of their new Windows 10 devices without needing IT assistance.

Here’s how it works:

Hand out a brand new Windows 10 PC to the user.

The user unboxes and powers on the new Windows 10 device. With a few clicks (select language, choose keyboard layout, connect to a network), the device is recognized as your organization’s device and delivers the customized OOBE you configured. (Additional steps in the standard Windows 10 OOBE such as choosing between a personal device or a work device, selecting privacy settings, OEM registration, Cortana setup, and OneDrive setup can be skipped using Windows AutoPilot Deployment.)*

Once connected to the network, Windows prompts the user to sign with their Azure AD e-mail address and password. (The sign-in experience is branded with your organization’s name and logo before your employee enters their Azure AD sign-in information.)

Upon successful authentication, the device joins Azure AD and is automatically enrolled in Microsoft Intune or other mobile device management (MDM) solution.**

Of course, there is no better way to understand this process than to see it in action. Watch this short Microsoft Mechanics video for an overview:

Don’t have time to watch this video now? Bookmark it for easy viewing later.

Some of the benefits of Windows AutoPilot are:

Intune can push policies, settings, and configuration to the device, and install Office 365 and other apps without IT ever having to touch the device or apply a custom image to the device.

Intune can configure Windows Update for Business to apply the latest updates.

The device can automatically upgrade from Windows 10 Pro to Windows 10 Enterprise seamlessly using AAD–no product keys to manage, no reboots, no prompts for the user.***

For Windows AutoPilot Deployment to work, you must register your organization-owned Windows 10 devices to your organization’s Azure AD tenant. This is possible for new Windows 10 PCs acquired from OEMs, distributors, and resellers participating in the Windows AutoPilot Deployment Program. It will soon be possible for OEMs and resellers to take care of this registration automatically on your behalf when fulfilling device orders in the future. Contact your device reseller or OEM partner for their plans to support the Windows AutoPilot Deployment Program.

The Surface team is working with customers and partners to roll out the Windows AutoPilot Deployment program and expects to make it broadly available to customers later this year. Contact your Microsoft Sales team representative for details.

Alternatively, for existing Windows 10 PCs running version 1703 (or higher), you can query the DeviceIDs programmatically and build the deviceID file to register applicable devices into the Windows AutoPilot Deployment service.

When can I start using Windows AutoPilot?

These capabilities are available today for Windows 10, version 1703. To try them out, check out the Windows AutoPilot documentation, which will walk you through the process. The Microsoft Store for Business and Cloud Solution Provider program will provide organizations and partners with the ability to register devices and configure Windows AutoPilot Deployment in the near future. We’re also working with MDM partners to integrate the AutoPilot Deployment configuration experience.

For scenarios where IT will be configuring the device with traditional on-premises or cloud-based modern IT scenarios, Windows Configuration Designer can be used to help automate the process. For simpler school scenarios, the Set Up School PCs app (announced last year) can be used as well. For a comparison of these scenarios, see the Windows AutoPilot overview.

As we move down the path towards modern IT, we will continue to add additional capabilities to Windows AutoPilot to ensure that the process is as simple as possible for both IT and the end user. At the same time, we will strive to provide additional “stepping stone” capabilities for organizations who feel they need to move in more measured increments toward this modern IT future.

New capabilities to Windows AutoPilot that will be added in the Windows 10 Fall Creators Update release later this year include:

Self-service deployment for Active Directory domain-joined devices – Windows AutoPilot Deployment will enable self-service deployment capabilities to get new Windows 10 devices into an Active Directory domain-joined state along with Microsoft Intune enrollment.

Enhanced personalization for self-service deployment – Windows AutoPilot will offer the ability to pre-assign a new Windows 10 device to a specific user in your organization and deliver a highly-personalized OOBE.

Windows AutoPilot Reset – A new reset capability In Windows AutoPilot will enable organizations to easily reset their configured devices while still maintaining MDM enrollment and the Azure AD join state, and automatically get the device back into a business-ready state.

* Starting with Windows 10, version 1703, captive portals are supported in the Windows 10 OOBE, so users can still leverage self-service deployment with Windows AutoPilot when using a Wi-Fi hotspot.
** Automatic enrollment requires an Azure AD Premium subscription.
*** Requires a Windows 10 Enterprise E3 subscription.

How can I learn more about Windows AutoPilot?

For tips on how to best take advantage of Windows AutoPilot in your organization, and a walkthrough of common usage scenarios, stay tuned to this blog and follow us on Twitter @MSWindowsITPro for an announcement about a special Windows AutoPilot webcast in late July.

We’ll also be hosting a one-hour “Ask Microsoft Anything” about Windows 10 management event at 9:00 a.m. Pacific Time on July 25th. Members of the Windows engineering and product teams will be standing by to answer your questions.

Click to expand...

Source: Modernizing Windows deployment with Windows AutoPilot Windows for IT Pros

Brink · Mar 28, 2025

Introducing Windows Autopilot for HoloLens 2

In addition to supporting the deployment and management of Windows 10 devices like laptops, tablets, and desktops, we are taking Windows Autopilot to uncharted territory by introducing the private preview of Windows Autopilot deployment for HoloLens 2!

Since Windows Autopilot was first introduced with Windows 10, version 1703, it has come a long way to enable organizations to deploy and manage their Windows 10 devices in significant less time and at noticeable cost savings. At its core, Windows Autopilot is a set of cloud technologies that offers greater efficiency and automation over traditional deployment and setup experiences.

As a critical component of Microsoft Endpoint Manager and our commitment to empowering IT, Windows Autopilot is designed to meet you where you are in your journey to simplified endpoint management and help you get where you want to be. We started with deployment scenarios for Azure AD then, in response to your feedback, Hybrid AD Join. In the spirit of innovation, we are working to support a broader range of devices with Windows Autopilot, starting with HoloLens 2.

Introducing Windows Autopilot for HoloLens 2

Microsoft HoloLens 2 is an untethered holographic computer with apps and solutions that help people across organizations learn, work, communicate, and collaborate more effectively using mixed reality. HoloLens 2 devices are commercial-ready with support for Azure AD, mobile device management (MDM), kiosk mode, always-on BitLocker, Windows Update for Business, and Microsoft Store for Business.

As adoption of HoloLens 2 is increasing, medical and educational institutions have found that deploying these devices at scale is challenging, time-consuming, and costly. Imagine an IT admin putting a HoloLens 2 device, calibrating the device, then moving through all the decision-making steps, such as user id and password, to join the device to their tenant. Now repeat this process for every device they need to deploy in their organization.

Windows Autopilot for HoloLens 2 with Microsoft Endpoint Manager solves this problem and delivers on the same promise of efficiency, simplified deployment, and streamlined device security and endpoint management as other Windows Autopilot deployment scenarios, driving significant cost and time savings for your organization.

How Windows Autopilot for HoloLens 2 works

With the current private preview, Windows Autopilot for HoloLens 2 support self-deploying mode with Azure AD only. That means the deployment process looks like this:

Join the device to Azure AD.

Enroll in Microsoft Endpoint Manager/Microsoft Intune (or another MDM service), leveraging Azure AD for automatic MDM enrollment to begin downloading all device targeted policies, user targeted applications, certificates, and networking profiles.

Land a shared device login state for the user with zero interaction.

Here is an illustration of Windows Autopilot self-deployment for HoloLens 2 devices:

The deployment scenarios currently supported with the private preview of Windows Autopilot for HoloLens 2 are as follows:

Azure AD join

Self-deployment mode

MDM enrollment with polices, certificates, kiosk mode, etc. applied during deployment

Device name setup before Azure AD join

Preset keyboard language from list of HoloLens 2 supported languages

Windows Autopilot can be used with HoloLens 2 devices with Windows 10 build 19041.1002.200107-0909 or later, and an internet connection.

Registering a HoloLens 2 device with Windows Autopilot

In the coming months, HoloLens 2 devices will be shipped as "Windows Autopilot ready" and have a Windows product key ID (PKID) barcode printed on the outside of the box. This PKID will simplify Windows Autopilot device registration by allowing distributors and resellers to register HoloLens 2 devices with their customers' tenants without powering on the actual devices. To learn more about how this process works, see adding devices to Windows Autopilot.

HoloLens 2 hardware ID collection for Windows Autopilot

We have also simplified the process of collecting the hardware ID (also referred to as hardware hash) and diagnostic logs for HoloLens 2 devices. There is no need to run a PowerShell script to collect the hardware ID or diagnostic logs during setup. With HoloLens 2 devices, you can simply collect logs and hardware IDs by following these simple steps:

While the HoloLens 2 device is powered on, press and release the Power and Volume down buttons together to trigger the hardware ID and diagnostic log collection process.

Connect the HoloLens 2 device to a PC using a USB cable so that it shows up in File Explorer.

Browse to Internal Storage > Documents and extract AutopilotDiagnostics.zip. This file/folder will contain a CSV file with a a file name that begins “DeviceHash…”.

Getting started with the private preview of Windows Autopilot for HoloLens 2

If you are interested in joining the private preview, here is the process:

Make sure your organization meets all requirements for Windows Autopilot and self-deploying mode, which include networking, licensing, and configuration requirements.

Enroll in the Windows Autopilot for HoloLens 2 private preview program by visiting Microsoft Forms, or scanning this QR code:

We will send you confirmation when your tenant is accepted into the program.

Follow the instructions documented in this Windows Autopilot for HoloLens 2 evaluation guide. If your organization is using Microsoft Endpoint Manager and Windows Autopilot, most steps will not be new to you, but this guide will take you the process step by step.

We look forward to hearing your feedback on the Windows Autopilot for HoloLens 2 private preview and thank you in advance for your interest and participation!
Click to expand...

Source: https://techcommunity.microsoft.com/...2/ba-p/1371494

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment? - Similar Threads - avoid Let´s connect

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

how to shut window that is stuck on "lets connect you to a network"

how to shut window that is stuck on "lets connect you to a network"

Stuck on the "Let's connect you to a network" screen

Stuck on lets connect you to a network

Stuck on lets connect you to a network

bypass "lets connect you to a network"

bypass "lets connect you to a network"

bypass "lets connect you to a network"