Hello,
In last article we have understand overview of autopilot to continew. let focus on senarios. what are scenarios we have to go though and possible options available in autopilot. let focus on subject topics. let focus on subject topics.
Windows AutoPilot Scenarios:
While we deploy new devices to end users, Windows Autopilot uses the OEM-optimized image of Windows Operating system (OS). This OS version is preinstalled on the device, so you don't have to maintain custom images and drivers for every device model. Instead of re-imaging the device, your existing Windows installation can be transformed into a "business-ready" state that can have the following settings,
-
Apply settings and policies from Intune
-
Install apps deployed through Intune
-
Change the edition of Windows being used to support advanced features. For example, from Windows Pro to Windows Enterprise.
Windows Autopilot helps organizations easily provision new devices by using the preinstalled OEM image and drivers. This functionality lets end users get their devices business-ready by using a simple process.
They are different versions of AutoPilot modes that can deployed to the end users depending on the suitable scenarios. Those different scenarios are prescribed below,
-
Windows Autopilot user-driven mode:
Windows Autopilot user-driven mode lets you configure new Windows devices to automatically transform them from their factory state to a ready-to-use state. This process doesn't require that IT personnel touch the device.
The process is simple. Devices can be shipped or distributed to the end user directly with the following instructions:
-
Unbox the device, plug it in, and turn it on.
-
If it uses multiple languages, choose a language, locale, and keyboard.
-
Connect it to a wireless or wired network with internet access. If using wireless, first connect to the wi-fi network.
-
Specify your e-mail address and password for your organization account.
-
The rest of the process is automated. The device does the following steps:
-
Join the organization.
-
Enroll in Microsoft Intune or another MDM service.
-
Get configured as defined by the organization.
You can suppress any other prompts during the out-of-box experience (OOBE).
2. Windows Autopilot self-deploying mode:
Windows Autopilot self-deploying mode lets you deploy a device with little to no user interaction. For devices with an Ethernet connection, no user interaction is required. For devices connected via Wi-Fi, the user must only:
-
Choose the language, locale, and keyboard.
-
Make a network connection.
Self-deploying mode provides all the following:
-
Joins the device to Azure Active Directory.
-
Enrolls the device in Intune (or another MDM service) using Azure AD for automatic MDM enrollment.
-
Makes sure that all policies, applications, certificates, and networking profiles are provisioned on the device.
-
Uses the Enrollment Status Page to prevent access until the device is fully provisioned.
Autopilot self-deploying mode is only supported for Azure AD join devices. Autopilot self-deploying mode isn't supported for hybrid Azure AD join devices.
Self-deploying mode lets you deploy a Windows device as a kiosk, digital signage device, or a shared device. Autopilot now has a kiosk mode that supports Kiosk Browser, any UWP app and specific versions of Edge.
Self-deploying mode does not presently associate a user with the device (since no user ID or password is specified as part of the process).
-
Windows Autopilot for existing devices:
Windows Autopilot for existing devices lets you reimage and provision a Windows device for Autopilot user-driven mode using a single, native Configuration Manager task sequence. The existing device can be on-premises domain-joined. The end result is a Windows 10 or Windows 11 device joined to either Azure Active Directory (Azure AD) or Active Directory (hybrid Azure AD join).
In Next : We will cover details AutoPilot Capabilities
0 Comments
No Comments