How long should the polling schedules be for AD system group, security group, and system discovery. My goal is to deploy software through AD Groups linked to collections. However I am getting duplicate records in SCCM during OSD.
It appears that the polling schedules are messing things up. If I set the polls too long, clients wont get their advertisements after OSD for an extended amount of time. To short seems to put in duplicate records and they never receive advertisements.
One record says
MP_ClientRegistration
Heartbeat Discovery
The other says
SMS_AD_SYSTEM_DISCOVERY
SMS_AD_SYSTEM_Group_DISCOVERY
For our migration we are prestaging computers in the appropriate OU prior to OSD. I assume AD discovery is finding the machine name prior to finishing OSD and adding it to the SCCM database. Then duing the task sequence the client installation is registering again.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
How long should the polling schedules be for AD system group, security group, and system discovery. My goal is to deploy software through AD Groups linked to collections. However I am getting duplicate records in SCCM during OSD.
It appears that the polling schedules are messing things up. If I set the polls too long, clients wont get their advertisements after OSD for an extended amount of time. To short seems to put in duplicate records and they never receive advertisements.
One record says
MP_ClientRegistration
Heartbeat Discovery
The other says
SMS_AD_SYSTEM_DISCOVERY
SMS_AD_SYSTEM_Group_DISCOVERY
For our migration we are prestaging computers in the appropriate OU prior to OSD. I assume AD discovery is finding the machine name prior to finishing OSD and adding it to the SCCM database. Then duing the task sequence the client installation is registering again.
Share this post
Link to post
Share on other sites