#IntuneNugget14

[@abdelalielghazrani5956]

thks for your explanation sir.

[@kushalgoswami9146]

Informative videos, thanks for sharing

[@rafidali178]

Very detailed and helpful.. thanks

[@Be_only_alone]

Again, Another great video. Thank you for Co-Mgmt Deep Dive. Please add more videos. We are waiting...

[@TheRao86]

Great stuff Saurabh !! Could you please share the slides as well , really appreciate all your hard work putting together great content

[@veer_psjvlogs]

Please share the link to nugget 13

[@lennyfrombrooklyn]

Good stuff thanks!

[@Locaaa0]

Hi, I would like to thank you for this great video, I have a question related to the co-management during the current crisis for WFH users, the most of the users start to work remotely and they are not co-managed yet so is the manual enrollment will solve the issue or we can have another workaround?!!

[@everythingaboutintune1713]

ayman shazly yes. Manual enrollment would also work. We have to make sure that the user has the license to do the same and the workload is set correctly in the sccm console

[@meamittripathi]

What is foo user? not able to get it propperly.

[@everythingaboutintune1713]

Think of it like a service account.

[@sunilpal7933]

@1:48:31 device gets enrolled with AADdevice credentials why it not tried using foo users.

[@everythingaboutintune1713]

Sunil PAl The enrollment happened using device credential at that point because the logged in user didnot have a Intune license assigned to him! No matter whether the enrollment is done by device creds/user cred, in the registry it will always show foouser in case of enrollment via sccm/gpo