Citrix DaaS

Create Microsoft Intune enabled catalogs

September 18, 2024

Contributed by:

Note:

Since July 2023, Microsoft has renamed Azure Active Directory (Azure AD) to Microsoft Entra ID. In this document, any reference to Azure Active Directory, Azure AD, or AAD now refers to Microsoft Entra ID.

This article describes how to create Microsoft Intune enabled catalogs using Citrix DaaS. You can enable Microsoft Intune by using Studio or PowerShell.

You can create:

Azure AD joined catalogs enrolled in Microsoft Intune for persistent, single and multi-session VMs. Required VDA version: 2203 and later.
Azure AD joined catalogs enrolled in Microsoft Intune for non-persistent, single-session and multi-session VMs. Required VDA version: 2407 and later.

For information on requirements, limitations, and considerations, see Microsoft Intune.

Use Studio

The following information is a supplement to the guidance in Create machine catalogs. This feature requires the selection of Azure Active Directory joined in Machine Identities during catalog creation. Follow the general guidance in that article, minding the details specific to this feature.

In the catalog creation wizard:

On the Machine Identities page, select Azure Active Directory joined and then Enroll the machines in Microsoft Intune. If enabled, enroll the machines in Microsoft Intune for management. You can create Azure AD joined catalogs enrolled in Microsoft Intune for both persistent and non-persistent single-session and multi-session VMs. However, for non-persistent VMs, you must have the VDA version as 2407 or later.

Use PowerShell

The following are the PowerShell steps that are equivalent to operations in Studio.

To enroll machines in Microsoft Intune using the Remote PowerShell SDK, use the DeviceManagementType parameter in New-AcctIdentityPool. This feature requires that the catalog is Azure AD joined and that Azure AD possesses the correct Microsoft Intune license. For example:

New-AcctIdentityPool -AllowUnicode -DeviceManagementType "Intune" IdentityType="AzureAD" -WorkgroupMachine -IdentityPoolName "AzureADJoinedCatalog" -NamingScheme "AzureAD-VM-##" -NamingSchemeType "Numeric" -Scope @() -ZoneUid "81291221-d2f2-49d2-ab12-bae5bbd0df05"
<!--NeedCopy-->

Troubleshoot

If machines fail to enroll in Microsoft Intune, do the following:

Check if the MCS-provisioned machines are Azure AD joined. The machines fail to enroll in Microsoft Intune if they are not Azure AD joined. See https://docs.citrix.com/en-us/citrix-daas/install-configure/create-machine-identities-joined-catalogs/create-azure-ad-joined-catalogs.html to troubleshoot Azure AD join issues.
Check if your Azure AD tenant is assigned with the appropriate Intune license. See https://learn.microsoft.com/en-us/mem/intune/fundamentals/licenses for license requirements of Microsoft Intune.
For catalogs that use master images with VDA version 2206 or earlier, check the provisioning status of the AADLoginForWindows extension for the machines. If the AADLoginForWindows extension does not exist, possible reasons are:
- IdentityType of the identity pool associated with the provisioning scheme is not set to AzureAD or DeviceManagementType is not set to Intune. You can verify this by running Get-AcctIdentityPool.
- Azure policy has blocked the AADLoginForWindows extension installation.
To troubleshoot AADLoginForWindows extension provisioning failures, you can check logs under C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.ActiveDirectory.AADLoginForWindows on the MCS provisioned machine.

Note:

MCS does not rely on the AADLoginForWindows extension to join a VM to Azure AD and enroll to Microsoft Intune when using a master image with VDA version 2209 or later. In this case, the AADLoginForWindows extension is not installed on the MCS-provisioned machine. Therefore, AADLoginForWindows extension provisioning logs can’t be collected.
Check Windows event logs under Application and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Create Microsoft Intune enabled catalogs

September 18, 2024

Contributed by:

September 18, 2024

Contributed by:

Create Microsoft Intune enabled catalogs

Use Studio

Use PowerShell

Troubleshoot

In this article