Microsoft intune manage pc11/13/2023 ![]() Let us know if you have any additional questions by replying to this post or reaching out to on Twitter.Ġ5/25/23: updated post to include clarity on the behavior between the Intune, Azure AD and Defender for Endpoint portals.Ġ8/11/23: updated post to clarify these updates pertain to Microsoft Defender for Endpoint (MDE) attached devices.Parts of this article (those related to documentation) need to be updated. ![]() For example, if you have rules that use the “equals” or “not equals” operator, then you must explicitly update the rule to reference “Windows Server.” If you have rules that use the “contains” or “like” operator, then the rule won’t be impacted. Look to update the dynamic group rules to include Windows Servers specifically. If you’re using Azure AD dynamic device groups with specified rules that reference “Windows,” this will now exclude Windows Servers. If you have any custom scripts that refer specifically to the Windows platform, they will not include the new “Windows Server” value for the deviceType and will need to be updated. In Intune, the OS platform will show up as ‘Windows’ in the All devices list and the hardware details found on the device object page will show up as blank to represent Windows Servers. If you have Windows Server devices configured in your tenant, expect the OS platform to update to “Windows Server” in your reporting views for Azure AD and MDE device lists. What should customers do to prepare for the change? Windows Server 2016 with Microsoft Defender for Down-Level Devices.Windows Server 2012 R2 with Microsoft Defender for Down-Level Devices.Windows 10 Professional/Enterprise (with KB5006738).This will apply to the following device platforms: In addition to the existing “Windows” deviceType, a new value “Windows Server” will be introduced for deviceType. In Intune, the devices will still show as Windows but be treated as a Windows Server endpoint and honor dynamic groups that specify Windows Server endpoints for Windows Server devices managed by Defender for Endpoint.įor example, the All Devices list in Azure AD:Ī screenshot of the All devices pane in Azure Active Directory. ![]() This change applies to Microsoft Defender for Endpoint (MDE) and Azure Active Directory (Azure AD). ![]() Windows Server devices will show up as “Windows Server” rather than “Windows” for the OS platform attribute for Windows Server devices managed by Defender for Endpoint. This allows customers to view and filter against Windows Servers in reporting as well as create groups of devices that contain only Windows Servers or exclusively Windows clients for targeting. Keep reading to see how we’re making improvements and what actions you may need to take.īeginning in June, you can expect Windows Server devices that currently display as “Windows” to update to “Windows Server” as the OS platform for Windows Server devices managed by Defender for Endpoint. This non-specific label makes it difficult to manage these devices when it comes to granular visibility and targeting. Today, Windows Servers are labeled as “Windows” for the attributes that refer to its operating system (OS) platform. With the Microsoft Defender for Endpoint (MDE) Security Management feature, Windows Servers can receive security management policies from Intune as outlined in Use Intune to manage Microsoft Defender for Endpoint Security on devices not enrolled with Microsoft. Currently devices on the Windows Server platform don’t support mobile device management (MDM) and can’t enroll in Intune. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |