Forum Discussion
CRDP
Aug 27, 2025Copper Contributor
Enrolments referencing old Intune Connector Server for something
Hope all is well. A couple of weeks ago, we moved our Intune Connector to a new server. The new server name has already been showing in the Microsoft Intune Admin Centre as "active" and it's healthy...
Dionysis_K
Aug 28, 2025Copper Contributor
Hello,
Thank you for sharing the details. From what you describe, it sounds like some enrolments are still being redirected to the old Intune Connector server despite it being removed from the Intune Admin Center. This can happen in a few scenarios:
- DNS / Service Connection Point (SCP) References
- The old server’s name or service records may still exist in AD or DNS (e.g., SCP under CN=Configuration, DC=... in Active Directory). New enrolments may attempt to resolve it first before falling back.
- Certificates or Tokens
- Devices that started enrolment before the switch might still be holding enrolment information pointing to the old connector until the process completes.
- Group Policy / MDM Auto-enrolment
- Check if there are any Group Policy Objects or local settings that still reference the old server’s name or connector path.
- Connector Cleanup
- While the Intune Admin Centre shows the new server as active and the old one removed, there may still be cached entries at the device level or within the Connector installation itself that need manual cleanup.
Recommended Actions
- Check AD Service Connection Points (SCP) for any lingering references to the old server.
- Verify DNS records / CNAMEs that may still point to the old machine.
- Review event logs on both servers during enrolment to confirm which connector is being called.
- Reinstall or repair the Intune Connector on the new server to force refresh of all references.
- After confirming cleanup, decommission the old server again and test with a new device enrolment.
This should help identify and eliminate dependency.