Microsoft - MS-101: Microsoft 365 Mobility and Security

Sample Questions

Explanation:

The Technical Requirements section contains the following.

Retention settings must be applied automatically to all the data stored in SharePoint Online sites, OneDrive accounts, and Microsoft Teams channel messages, and the data must be retained for five years.

We need to create one retention policy that applies to SharePoint Online sites and OneDrive accounts and a second retention policy that applies to Teams channel messages. Configuring a single policy that applies to all three locations is not possible.

If you select the Teams or Yammer locations when you create a retention policy, the other locations are automatically excluded.

Reference: Create and configure a retention policy

Explanation:

You'll need to go the onboarding section of the Defender for Endpoint portal to onboard any of the supported devices. Depending on the device, you'll be guided with appropriate steps and provided management and deployment tool options suitable for the device.

To onboard devices to the service:

• Verify that the device fulfills the minimum requirements
• Depending on the device, follow the configuration steps provided in the onboarding section of the Defender for Endpoint portal
• Use the appropriate management tool and deployment method for your devices
• Run a detection test to verify that the devices are properly onboarded and reporting to the service

The following table lists the available tools based on the endpoint that you need to onboard.

Reference: Onboard devices and configure Microsoft Defender for Endpoint capabilities

Explanation:

Intune is used to manage client apps and PowerShell scripts on co-managed Windows 10 or later devices. After you transition this workload, any available apps deployed from Intune are available in the Company Portal. Apps that you deploy from Configuration Manager are available in Software Center.

Compliance policies are applied to the co-management Pilot group. The phrase Pilot group is used throughout the co-management feature and configuration dialogs. A pilot group is a collection containing a subset of your Configuration Manager devices. Use a pilot group for your initial testing, adding devices as needed, until you're ready to move the workloads for all Configuration Manager devices. There isn't a time limit on how long a pilot group can be used for workloads. A pilot group can be used indefinitely if you don't wish to move the workload to all Configuration Manager devices. You can change the Pilot collections on the Staging tab of the co-management properties page.

References:

Client apps

How to enable co-management in Configuration Manager

Switch workloads

Explanation:

MDT is a unified collection of tools, processes, and guidance for automating desktop and server deployment. You can use it to create reference images or as a complete deployment solution. MDT is one of the most important tools available to IT professionals today.

In addition to reducing deployment time and standardizing desktop and server images, MDT enables you to more easily manage security and ongoing configurations. MDT builds on top of the core deployment tools in the Windows Assessment and Deployment Kit (Windows ADK) with more guidance and features designed to reduce the complexity and time required for deployment in an enterprise environment.

MDT supports the deployment of Windows 10, and Windows 7, Windows 8.1, and Windows Server. It also includes support for zero-touch installation (ZTI) with Microsoft Endpoint Configuration Manager.

In order to perform an in-place upgrade to the 64-bit version of Windows 10, it is required that the computer to be upgraded is running the 64-bit version of Windows 7, Windows 8 or Windows 8.1.

To start the MDT Deployment Wizard, start the operating system on the computer to be upgraded and run the script file from the following network path: \\MDTHost\DeploymentShare$\Scripts\LiteTouch.vbs.

It doesn't matter whether the computer to be upgraded was installed from a standard installation image or from a custom image. However, a custom image version cannot be used for upgrade. An in-place upgrade requires using the default installation image install.wim.

Operating systems installed on a native virtual hard disk (Type2) cannot be upgraded.

References:

Get started with MDT

Perform an in-place upgrade to Windows 10 with MDT

Explanation:

To register existing computers for Windows Autopilot, the serial number of the device and a hardware ID (also referred to as hardware hash) are required. To collect the hardware ID from existing devices, the Get-WindowsAutopilotInfo PowerShell script is used.

The script can be downloaded and executed using the following commands:

md c:\\HWID
Set-Location c:\\HWID
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted
Install-Script -Name Get-WindowsAutoPilotInfo
Get-WindowsAutoPilotInfo.ps1 -OutputFile AutoPilotHWID.csv

Reference: Adding devices to Windows Autopilot