Back to Blog
Hololens keyword manager6/16/2023 Complete the Rules section as follows, then click Next.From the Platform dropdown field, select “Windows 10” and click Next.Navigate to Tenant admin > Filters (preview) > Create, choose a Filter name.Any setting that is not applicable on the HoloLens 2 can mark the device non-complaint.įirst, create a Filter to include or exclude HoloLens 2 devices when using user-based targeting: It therefore makes sense to deploy your compliance policy to a user group. In this case, the same Intune compliance policy will be applicable to both devices. You have a group of users that use both Windows 10 Desktop devices and HoloLens 2 devices. You can populate a dynamic group with HoloLens devices by using a device attribute where “Model” is “HoloLens 2” or by a Group Tag set on the Autopilot object. This can be done with an Azure AD static or dynamic group. In this case, we recommend deploying your compliance policy to a device group. When onboarded with Autopilot the device is enrolled. Let’s take a HoloLens device that is enrolled into Intune by the Windows Autopilot self-deploying mode process and automatically put in KIOSK mode. When a compliance policy is deployed to a user, all the user’s devices are checked for compliance. Scenarios drive whether you deploy your compliance policy to users in user groups or devices in device groups. How to deploy a compliance policy to HoloLens * = Settings are not included in the supported list of CSP for Windows Holographic for Business Not applicable = Will show as Not applicable in the compliance status Require the device to be at or under the machine risk score Microsoft Defender Antimalware security intelligence up-to-date Microsoft Defender Antimalware minimum version Require encryption of data storage on device. Require password when device returns from idle state (Mobile and Holographic) Number of previous passwords to prevent reuse Maximum minutes of inactivity before password is required Require a password to unlock mobile devices Require device compliance from Configuration Manager Require Secure Boot to be enabled on the device HoloLens 2 has BitLocker Device Encryption enabled automatically on the operating system and fixed data volumes and cannot be turned off – even by IT administrators – so that the device is always protected. This is similar to how BitLocker and HoloLens work. The same compliance policy is used for Windows 10 desktop and HoloLens in Microsoft Intune, however some settings supported for Windows 10 are not available for HoloLens. HoloLens 2 runs the Windows Holographic Operating System, which is not the same as Windows 10 Desktop, and therefore some capabilities (like win32 apps) do not exist in this platform. The ConfigMgr agent is a Win32 app, and Win32 apps cannot run on a HoloLens device. You can find out more about supported CSPs in the Policies in Policy CSP supported by HoloLens 2 document.Ĭonfiguration Manager Compliance is not supported with Hololens devices. Microsoft Intune as a capability of Endpoint Manager, uses Configuration Service Providers (CSPs) to control and verify many of the settings in the compliance policy, so those CSP’s need to be supported on the HoloLens. How to manage compliance policies on HoloLens devices is one of the most common questions we get from customers as they start to manage their HoloLens fleet with Microsoft Endpoint Manager.Ĭompliance policies are used to mark the device compliant or non-compliant, which can be used in conjunction with Azure Active Directory (Azure AD) Conditional Access to allow or block access to corporate data. Program Manager | Microsoft Endpoint Manager – Intune See the original author and article here.īy Per Larsen – Sr.
0 Comments
Read More
Leave a Reply. |