Thank you for the video, it really helps a lot. After we enable co-management and set the workload to pilot for pilot collection which has only devices, we observed that autopilot registered devices are not able to enroll and stucks at esp for a long time with no errors
Hi Dean, thank you for your video. Regarding your question with the two "Access work or school" entries, I have them too in my work environment. Like you I was wondering why did they lay out like that so I took advantage of one of the already raised tickets with Microsoft and I've asked one of the consultants about this and he told me it's a good indication that your device is indeed a "Hybrid Azure AD Joined" one, with both visual confirmation for a regular "Domain Joined" and one telling you the device is "AzureAD Joined". Optionally, another thing that I did because I had some issues with devices not being registered properly, was to add an additional entry into Task Scheduler on the local Azure AD server for the "Azure AD Connect" tu run/sync daily, repeating the task every 10 minutes with the following PS command: "Start-ADSyncSyncCycle -PolicyType Delta".
Thanks! The two entries have disappeared now, not sure what I did to make that happen either. Interesting point about the AADConnect sync. I thought the delta ran pretty regularly anyway ?
Hi mate, Great video, I have an issue where non of the devices synced from CM have any MDM authority shown in my Intune tenant, do you know how to fix this ?
Good video, but request - would you mind date stamping in the description? Videos on such dynamic content quickly age. It'll help the rest of us judge how current the guide is going to be.
Why would the lab admin account need an Intune license? One of the major points of using comanagement is that you can manage the devices in Intune without purchasing Intune licensing for the users. The Config Manager client license is supposed to also cover Intune device licensing.
Great question! The next episode focussed on Windows Update for Business, as mentioned at 15:30 Here's that episode: th-cam.com/video/Cjv8Opn2OQE/w-d-xo.html !
Thank you for the video, it really helps a lot. After we enable co-management and set the workload to pilot for pilot collection which has only devices, we observed that autopilot registered devices are not able to enroll and stucks at esp for a long time with no errors
Hi Dean, thank you for your video. Regarding your question with the two "Access work or school" entries, I have them too in my work environment. Like you I was wondering why did they lay out like that so I took advantage of one of the already raised tickets with Microsoft and I've asked one of the consultants about this and he told me it's a good indication that your device is indeed a "Hybrid Azure AD Joined" one, with both visual confirmation for a regular "Domain Joined" and one telling you the device is "AzureAD Joined".
Optionally, another thing that I did because I had some issues with devices not being registered properly, was to add an additional entry into Task Scheduler on the local Azure AD server for the "Azure AD Connect" tu run/sync daily, repeating the task every 10 minutes with the following PS command: "Start-ADSyncSyncCycle -PolicyType Delta".
Thanks!
The two entries have disappeared now, not sure what I did to make that happen either.
Interesting point about the AADConnect sync. I thought the delta ran pretty regularly anyway ?
Hi mate, Great video, I have an issue where non of the devices synced from CM have any MDM authority shown in my Intune tenant, do you know how to fix this ?
Good video, but request - would you mind date stamping in the description?
Videos on such dynamic content quickly age. It'll help the rest of us judge how current the guide is going to be.
Interesting - the video was uploaded 22 Jun 2021, which I assumed provided that type of age-related info?
Why would the lab admin account need an Intune license? One of the major points of using comanagement is that you can manage the devices in Intune without purchasing Intune licensing for the users. The Config Manager client license is supposed to also cover Intune device licensing.
We have enabled co-management but existing devices how can fetch the primary username automatically. Kindly need a solution
where is part 3? thank you
Great question! The next episode focussed on Windows Update for Business, as mentioned at 15:30
Here's that episode: th-cam.com/video/Cjv8Opn2OQE/w-d-xo.html !