4/9/2023 0 Comments Sccm 2012 filelib cleanup![]() ![]() ![]() I’ve selected both options below, specifically the Upload to Microsoft Endpoint Manager admin center option is all that is needed to support the Device Upload feature:Ĭrack on and accept the prompt to register an application in the AAD tenant: Tap in credentials with enough privilege’s in Azure to do this job: Roll on over to Administration, Cloud Services and Co-management, hit that Configure co-management button like a boss: Head on over to the ConfigMgr Console, navigate to Administration and expand the Updates and Servicing node, click on Features.įind the Microsoft Endpoint Manager tenant attach: Device sync and device actions entry, turn it on:Īt this point either restart the server or restart the SMS_EXECUTIVE service as pointed out in the documentation. Light up the Device Upload (Device Sync, Tenant Attach …) feature Make sure AD Connect is correctly synchronising AD users to Azure AD, and make sure Azure Active Directory User Discovery is enabled and working on the ConfigMgr Site server: My lab already has Azure Services configured to enable the Client Management Gateway but you don’t need one, head off and configure Azure Services to onboard your tenant if you haven’t already. We’re not synchronising Azure AD Users into Active Directory quite yet, we just need Azure AD users to show up in ConfigMgr so as to be able to perform client actions: I whittled out a diagram shown below to visualise the requirement for Azure Active Directory User sync, used to sync Azure AD Users into ConfigMgr, and AD Connect to sync AD users to Azure AD. So you’re going to need AD Connect configured. The “ Has been discovered with Active Directory user discovery” bit means AD Connect has replicated the AD User to Azure AD. The “ Has been discovered with Azure Active Directory user discovery” bit means that ConfigMgr has discovered the users from Azure AD, this requires Azure Services to be configured. There are some prerequisites, so make sure you have this lot ticked off: Enrollment to Intune for Co-managed devices can be disabled, and no work-loads need to be transferred. If you throw in the Client Management Gateway, we can communicate with ConfigMgr devices whether they are on or off the corporate network, as long as they are online we’ll be able to reach them from Intune.Īnd although the Device Upload feature sits inside the Co-management feature, we don’t have to enable Co-management for Device Upload to work. Telling ConfigMgr to tell one of its clients to perform an activity, that’s some reach! ![]() What this boils down to is initially in this early technical preview release bringing to bear basic management-capabilities of a ConfigMgr client, performed from Intune via the MEM Admin Center portal. The management planes merge even further with the announcement of the Tenant Attach feature for ConfigMgr, recently released as Preview in the ConfigMgr Technical Preview 2002.2 Build, which allows you to upload your ConfigMgr clients to Intune, and issues to them some initially very basic management capabilities from the MEMAC portal. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |