Explanation:

Box 1: can modify the desktop settings only for themselves

We see: User account type: Standard (not Administrator)

Incorrect:

* can create additional local users on the device

* can modify the desktop settings for all device users

Box 2: Cortana settings

Incorrect:

* computer name

We see: Hide change account options: Hide

* keyboard layout

We see: Automatically configure keyboard: Yes

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

Explanation:

Box 1: Install the Windows Assessment and Deployment Kit (Windows ADK)

Server1

MDT installation requires the following:

The Windows ADK for Windows 10

Windows PowerShell (version 5.1 is recommended; enter $host to check)

Microsoft .NET Framework

Box 2: Windows 11 image and task sequence only

Deployment share

Create a deployment share and reference image

A reference image serves as the foundation for Windows 11 devices in your organization.

*Details omitted*

The next step is to create a task sequence to reference the operating system that was imported. To create a task sequence, right-click the Task Sequences node and then select New Task Sequence.

Create a Windows 11 reference image

Reference:

https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/prepare-for-windows-deployment-with-mdt

https://learn.microsoft.com/en-us/windows/deployment/windows-10-poc-mdt#create-a-deployment-share-and-reference-image

Explanation:

Step 1: Modify the CustomSettings.ini file

CustomSettings.ini (CS) may be edited to include information that you wish to take into account prior to beginning the deployment processCsuch as data that will exist as variables that can be called upon as needed. This is extremely useful when working with multiple sites or when you want certain settings to apply to desktops, while mobile devices receive a different set of settings.

Example of line included:

SkipBDDWelcome=NO

Step 2: Modify the task sequence

Create the deployment task sequence, example:

Explanation:

Step 1: Modify the CustomSettings.ini file

CustomSettings.ini (CS) may be edited to include information that you wish to take into account prior to beginning the deployment processCsuch as data that will exist as variables that can be called upon as needed. This is extremely useful when working with multiple sites or when you want certain settings to apply to desktops, while mobile devices receive a different set of settings.

Example of line included:

SkipBDDWelcome=NO

Step 2: Modify the task sequence

Create the deployment task sequence, example:

Explanation:

Step 1: Modify the CustomSettings.ini file

CustomSettings.ini (CS) may be edited to include information that you wish to take into account prior to beginning the deployment processCsuch as data that will exist as variables that can be called upon as needed. This is extremely useful when working with multiple sites or when you want certain settings to apply to desktops, while mobile devices receive a different set of settings.

Example of line included:

SkipBDDWelcome=NO

Step 2: Modify the task sequence

Create the deployment task sequence, example:

Explanation:

Step 1: Modify the CustomSettings.ini file

CustomSettings.ini (CS) may be edited to include information that you wish to take into account prior to beginning the deployment processCsuch as data that will exist as variables that can be called upon as needed. This is extremely useful when working with multiple sites or when you want certain settings to apply to desktops, while mobile devices receive a different set of settings.

Example of line included:

SkipBDDWelcome=NO

Step 2: Modify the task sequence

Create the deployment task sequence, example:

Explanation:

Box 1: No

Device1 has no Mobile device Management (MDM) configured.

Note: Device1 is running Windows 8.1, and is registered, but not joined.

Device1 is in Group1.

Profile1 is assigned to Group1.

Box 2: No

Device2 has no Mobile device Management (MDM) configured.

Note: Device2 is running Windows 10, and is joined.

Device2 is in Group2.

Group2 is in Group1.

Profile1 is assigned to Group1.

Box 3: Yes

Device3 has Mobile device Management (MDM) configured.

Device3 is running Windows 10, and is joined

Device1 is in Group1.

Profile1 is assigned to Group1.

Mobile device management (MDM) enrollment: Once your Windows 10 device joins Azure AD, Autopilot ensures your device is automatically enrolled with MDMs such as Microsoft Intune. This program can automatically push configurations, policies and settings to the device, and install Office 365 and other business apps without you having to get IT admins to manually sort the device. Intune can also apply the latest updates from Windows Update for Business.

Reference: https://xo.xello.com.au/blog/windows-autopilot