This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Microsoft Intune
This article describes the requirements to create Microsoft Intune enabled catalogs using Citrix DaaS in addition to the requirements outlined in the Citrix DaaS system requirements section.
Microsoft Intune is a cloud-based service that focuses on mobile device management (MDM) and mobile application management (MAM). You control how your organization’s devices are used, including mobile phones, tablets, and laptops. For more information, see Microsoft Intune. The devices must meet the minimum system requirements. For more information, see the Microsoft documentation Supported operating systems and browsers in Intune.
Important:
Before enabling this feature, verify that your Azure environment meets the licensing requirements to use Microsoft Intune. For more information, see the Microsoft documentation: https://docs.microsoft.com/en-us/mem/intune/fundamentals/licenses. Do not enable the feature if you do not have the appropriate Intune license.
You can create:
- Azure AD joined catalogs enrolled in Microsoft Intune for persistent and non-persistent, single-session and multi-session VMs. For requirements, limitations, and considerations, see Requirements for Azure AD joined catalogs enrolled in Microsoft Intune.
- Hybrid Azure AD joined catalogs enrolled in Microsoft Intune for persistent single and multi-session VMs using device credential with co-management capability. For requirements, limitations, and considerations, see Requirements for Hybrid Azure AD joined catalogs enrolled in Microsoft Intune.
Requirements for Azure AD joined catalogs enrolled in Microsoft Intune
- Control plane: Citrix DaaS
- VDA type: Single-session and multi-session OS VDA
-
VDA version
Type of catalog VDA version Azure AD joined catalogs enrolled in Microsoft Intune for persistent, single and multi-session VMs 2203 and later Azure AD joined catalogs enrolled in Microsoft Intune for non-persistent, single-session and multi-session VMs 2407 and later - Provisioning type: Machine Creation Services (MCS) persistent and non-persistent machine catalogs using the Machine Profile workflow only
Limitations
- Do not skip image preparation while creating or updating machine catalogs.
Considerations
- Create a device profile that disables Windows Hello for Business.
- Use VDA version 2212 or later if Microsoft Intune must manage a master VM.
- Configure Microsoft Intune to delete the stale devices. This ensures that your device records stay current. For information on deleting the stale devices, see Automatically delete devices with cleanup rules.
Requirements for Hybrid Azure AD joined catalogs enrolled in Microsoft Intune
Hybrid Azure AD joined catalogs, persistent single and multi-session VMs, enrolled in Microsoft Intune use the device credentials with co-management capability.
Co-management enables you to concurrently manage Windows 10 or later devices by using both Configuration Manager and Microsoft Intune. For more information, see Co-management.
Prerequisites for co-management
Before enabling this feature, verify that:
- Your Azure environment meets the licensing requirements to use Microsoft Intune. For more information, see the Microsoft documentation.
- You have a valid Configuration Manager deployment with co-management enabled. For more information, see the Microsoft documentation.
Requirements for co-management
- Control plane: Citrix DaaS
- VDA type: Single-session or multi-session
- VDA version: 2407 or later
- Provisioning type: Machine Creation Service (MCS), Persistent
- Assignment type: Dedicated and pooled
- Hosting platform: Any hypervisor or cloud service
Limitations for co-management
- Do not skip image preparation while creating or updating machine catalogs.
- Internet-based client management (IBCM) of Configuration Manager is not supported.
Considerations for co-management
-
Intune enrollment might be delayed if too many machines in the catalog are powered on simultaneously.
Microsoft imposes a per-tenant Intune enrollment restriction that limits the number of devices that can be enrolled within a specific time frame. The allowable number of devices varies depending on the number of Microsoft Intune licenses associated with the tenant. Consult your Microsoft account team to find out the allowable limit for your tenant. This approach helps Microsoft Intune enrollment scale better for large environments.
For persistent machines, there might be an initial wait time required for all devices to complete Intune enrollment.
- Configure Cloud Attach of Configuration Manager. For more information, see the Microsoft documentation.
- Manually install Configuration Manager client on the master VM without assigning the site code. For more information, see the Microsoft documentation.
-
MCS created machines use the automatic site assignment mechanism to find site boundary groups that are published to Active Directory Domain Services. Ensure that the boundaries and boundary groups of Configuration Manager are configured in your environment. If automatic site assignment is not available, a static Configuration Manager site code can be configured in the master VM through the following registry setting:
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\MachineIdentityServiceAgent\DeviceManagement <!--NeedCopy-->Value name:
MdmSccmSiteCodeValue type: String
Value data:
the site code to be assigned
Where to go next
- For information on creating Microsoft Intune enabled catalogs, see Create Microsoft Intune enabled catalogs.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.