Microsoft MD-102 (page: 8)

Explanation:

Self-deploying mode uses a device's TPM 2.0 hardware to authenticate the device into an organization's Azure AD tenant. Therefore, devices without TPM 2.0 can't be used with this mode.

Reference:

https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/self-deploying

Explanation:

How to enable WinRM with domain controller Group Policy for WMI monitoring First, we need to create a Group Policy object for your domain.
Next, edit the new Group Policy object you just created. When you're done, there will be three WinRM service settings enabled:
B: Allow remote server management through WinRM
1. Right-click on the new Enable WinRM Group Policy Object and select Edit.
2. From the menu tree, click Computer Configuration > Policies > Administrative Templates: Policy definitions > Windows Components > Windows Remote Management (WinRM) > WinRM Service.
3. Right-click on Allow remote server management through WinRM and click Edit.
4. Select Enabled to allow remote server management through WinRM.
5. Enter an asterisk (*) into each field.
6. Click OK.
C: Now that Windows Remote Management has been enabled on the Group Policy, you need to enable the service that goes with it.
1. From the Group Policy Management Editor window, click Preferences > Control Panel Settings > Services.
2. Right-click on Services and select New > Service.
3. Select Automatic as the startup.
4. Enter WinRM as the service name.
5. Select Start service as the service action.
6. All remaining details can stay on the defaults. Click OK.
F: Now you must allow for inbound remote administration by updating the firewall rules. When you're done, there will be two rules enabled:
Windows Firewall: Allow inbound remote administration exception Windows Firewall: Allow ICMP exception

Reference:

https://support.auvik.com/hc/en-us/articles/204424994-How-to-enable-WinRM-with-domain-controller-Group- Policy-for-WMI-monitoring

Explanation:

Windows
Subscription Activation
Windows 10 Pro supports the Subscription Activation feature, enabling users to "step-up" from Windows 10 Pro or Windows 11 Pro to Windows 10 Enterprise or Windows 11 Enterprise, respectively, if they are
subscribed to Windows
Enterprise E3 or E5.

Reference:

https://docs.microsoft.com/en-us/windows/deployment/windows-10-subscription-activation

Explanation:

Box 1: Co-management
Existing Windows 11 devices managed by using Configuration Manager

Co-management enrollment
If you use Configuration Manager, and want to continue to use Configuration Manager, then co-management enrollment is for you. Co-management manages Windows
devices using Configuration Manager and Microsoft Intune together. You cloud-attach your existing Configuration Manager environment to Intune. This enrollment option runs some workloads in Configuration Manager, and other workloads in Intune.

Box 2: User enrollment
Personal iOS devices

BYOD: User and Device enrollment
These iOS/iPadOS devices are personal or BYOD (bring your own device) devices that can access organization email, apps, and other data. Starting with iOS 13 and newer, this enrollment option targets users or targets devices. It doesn't require resetting the devices.

Note: Enroll iOS and iPadOS devices in Microsoft Intune
Personal and organization-owned devices can be enrolled in Intune. Once they're enrolled, they receive the policies and profiles you create. You have the following options when enrolling iOS/iPadOS devices:

Automated device enrollment (ADE)
Apple Configurator
BYOD: User and Device enrollment

Incorrect:
* Automated Device Enrollment
Automated Device Enrollment (ADE) (supervised)
Previously called Apple Device Enrollment Program (DEP). Use on devices owned by your organization. This option configures settings using Apple Business Manager (ABM) or Apple School Manager (ASM). It enrolls a large number of devices, without you ever touching the devices. These devices are purchased from Apple, have your preconfigured settings, and can be shipped directly to users or schools. You create an enrollment profile in the Intune admin center, and push this profile to the devices.

* Apple Configurator
Apple Configurator enrollment
Use on devices owned by your organization, and includes Direct Enrollment. This option requires you to physically connect iOS/iPadOS devices to a Mac computer using the USB port.

Reference:

https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment-windows https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-enrollment-ios-ipados

Explanation:

Reference:

https://docs.microsoft.com/en-us/mem/intune/enrollment/android-enroll https://powerautomate.microsoft.com/fr-fr/blog/mam-flow-mobile/

Explanation:

Box 1: Retained and the passphrase will be retained
The Windows Autopilot Reset process automatically keeps information from the existing device:

* Wi-Fi connection details.

Box 2: Removed
Windows Autopilot Reset:
* Removes personal files, apps, and settings.

Box 3: Removed
Windows Autopilot Reset:

Removes personal files, apps, and settings.
Reapplies a device's original settings.
Sets the region, language, and keyboard to the original values.
Maintains the device's identity connection to Azure AD.
Maintains the device's management connection to Intune.

The Windows Autopilot Reset process automatically keeps information from the existing device:
Wi-Fi connection details.
Provisioning packages previously applied to the device.
A provisioning package present on a USB drive when the reset process is started. Azure Active Directory device membership and MDM enrollment information.

Reference:

https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/windows-autopilot-reset

Explanation:

Box 1: Standard Client Upgrade Task Sequence
Use Template: Standard Client Upgrade Task Sequence

In-place upgrade is the preferred method to use when migrating from Windows
to a later release of Windows
, and is also a preferred method for upgrading from Windows 7 or 8.1 if you do not plan to significantly change the device's configuration or applications. MDT includes an in-place upgrade task sequence template that makes the process really simple.

Box 2: Install.wim
In-place upgrade differs from computer refresh in that you cannot use a custom image to perform the in-place upgrade.

Reference:

https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/upgrade-to-windows-10-with-the- microsoft-deployment-toolkit