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!
Co-management
This article describes the requirements to create co-management enabled catalogs using Citrix DaaS in addition to the requirements outlined in the Citrix DaaS system requirements section.
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.
The devices must meet the minimum system requirements. For more information, see the Microsoft documentation supported operating systems and browsers in Intune.
Co-management works by using the functionality of Hybrid Azure AD.
Prerequisites
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
- 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
- Do not skip image preparation while creating or updating machine catalogs.
- Internet-based client management (IBCM) of Configuration Manager is not supported.
Considerations
-
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:
MdmSccmSiteCode
Value type: String
Value data:
the site code to be assigned
Where to go next
For more information on creating co-management enabled catalogs, see Create co-management enabled catalogs.
Share
Share
In this article
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.