Windows 10: Autopilot V2

Sunny Handa · Jun 22, 2024

I am unable to perform the autopilot-v2 because "Device shouldn't be registered or added as a Windows Autopilot device - if the device is registered or added as Windows Autopilot device, the Windows Autopilot profile takes precedence over the Windows Autopilot device preparation policy" I have removed the device and deleted it from all the places but some reason Autopilot takes precedence over prepration. could not find any info to bypass autopilot and opt for prepration policy. https://learn.microsoft.com/en-us/autopilot/device-preparation/overview#enrollment-time-grouping

:)

RonBarker · Jun 22, 2024

Autopilot/LTSC

Hi Mat, I have no idea what LTSC means? Anyhow, have a look at this article: Overview of Windows Autopilot | Microsoft Docs

PS: Windows Autopilot documentation | Microsoft Docs

PPS: I now know what LTSC means. 'Long-Term Servicing Channel (LTSC)'

Enrolling Windows Modern Devices using Autopilot and Azure Join (soti.net) "The following Microsoft Windows 10 editions are supported for Windows Autopilot:

Windows 10 Pro

Windows 10 Pro Education

Windows 10 Pro for Workstations

Windows 10 Enterprise

Windows 10 Education

Windows 10 Enterprise 2019 LTSC"

R Cord · Jun 22, 2024

Autopilot error

Hi,

R. Cord here, Independent Expert. Hope you are doing well.

My suggestion:

I am not sure, but disabling this service could cause other dependencies in your system to malfunction, which could explain the lagging and error messages that you're seeing.

To fix the issue, I would suggest re-enabling the "Microsoft Account Sign-in Assistant Service" and then trying to troubleshoot the error messages that you're receiving. Here are the steps you can follow:

Press the Windows key + R to open the Run dialog box.

Type "services.msc" and press Enter to open the Services window.

In the Services window, locate the "Microsoft Account Sign-in Assistant Service" and double-click on it.

In the properties window that opens, set the startup type to "Automatic" and click on the "Start" button to start the service if it's not already running.

Click "OK" to save your changes and close the properties window.

After re-enabling the service, restart your computer and see if the lagging and error messages have been resolved. If the problem persists, you may need to look into other troubleshooting steps such as running a virus scan or performing a system restore to a previous point in time before the issue occurred.

I hope this helps!

Also check topic:

Windows Autopilot - known issues applied to Win10 / Win11:

https://learn.microsoft.com/en-us/mem/autopilot...

Please let me know if you need any further assistance.

Best Regards,

R. Cord

Brink · Jun 22, 2024

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: Autopilot V2

Autopilot V2

Autopilot V2

Autopilot V2

Autopilot V2 - Similar Threads - Autopilot

Unable to install NET.3.5 on Win 11 24H2 Autopilot Pcs

Unable to install NET.3.5 on Win 11 24H2 Autopilot Pcs

Autopilot device with Entra and Intune mismatch

Autopilot device with Entra and Intune mismatch

Generic Product ID After Motherboard Replacement Preventing Autopilot Registration

Generic Product ID After Motherboard Replacement Preventing Autopilot Registration

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?

Autopilot device deregistration