ConcernedCCMER
New Member
- Messages
- 3
- Solutions
- 1
- Reaction score
- 0
- Points
- 1
Hello All,
I'm trying to figure out why some computers are not getting pushed to Intune for Management. They show ‘see ConfigMgr’ instead of showing the compliance, and the ‘Managed By’ column shows ‘ConfigMgr’. in an effort to fix this, i caused a new problem, where it doesn't show up at all, or did only breifly.
Taking the example of one, COMP1, Steps Taken so far:
-it is confirmed as hybrid joined and registered. To ensure a clean start, I deleted the computer object from AD and rejoined it and delta syncced it through AD connect because it was stuck in 'pending' in azure registration.
-it is a virtual machine on vmware
-I have checked and the IP falls into a boundary group.
-I repaired the client, then reinstalled it. I also had to delete the SMS SMS store with certutil because it was showing up in SCCM disappearing on me. The certutil trick fixed that.
...Now it shows up in SCCM consistently, but this morning I saw it only briefly in intune and then disappeared. After repeating some of the above steps, it was in Intune
-The client reports co-management enabled with 12543.
-The comanagehandler log states it is enrolled and it updated the coManagement registry key to 0x30ff.
-All our workloads are pushed to Intune.
-Ive check with get-cmduplicatehardwareID and its not a duplicate.
-COMP1 syncs fine from “Access Work or School”
Any tips as to how i can dig into the comanagement so as to determine why it is stuck at 'See ConfigMgr' would be appreciated. In addition, any hints as to why it showed up then disappeared shortly after from intune.
Thanks
I'm trying to figure out why some computers are not getting pushed to Intune for Management. They show ‘see ConfigMgr’ instead of showing the compliance, and the ‘Managed By’ column shows ‘ConfigMgr’. in an effort to fix this, i caused a new problem, where it doesn't show up at all, or did only breifly.
Taking the example of one, COMP1, Steps Taken so far:
-it is confirmed as hybrid joined and registered. To ensure a clean start, I deleted the computer object from AD and rejoined it and delta syncced it through AD connect because it was stuck in 'pending' in azure registration.
-it is a virtual machine on vmware
-I have checked and the IP falls into a boundary group.
-I repaired the client, then reinstalled it. I also had to delete the SMS SMS store with certutil because it was showing up in SCCM disappearing on me. The certutil trick fixed that.
...Now it shows up in SCCM consistently, but this morning I saw it only briefly in intune and then disappeared. After repeating some of the above steps, it was in Intune
-The client reports co-management enabled with 12543.
-The comanagehandler log states it is enrolled and it updated the coManagement registry key to 0x30ff.
-All our workloads are pushed to Intune.
-Ive check with get-cmduplicatehardwareID and its not a duplicate.
-COMP1 syncs fine from “Access Work or School”
Any tips as to how i can dig into the comanagement so as to determine why it is stuck at 'See ConfigMgr' would be appreciated. In addition, any hints as to why it showed up then disappeared shortly after from intune.
Thanks
