Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Merged AD discovered object and Manual machine entry cannot boot

When there is Device object created by Group discovery method in SCCM and we create new Manual machine entry object. It can happen (when device was online during Group discovery process), that objects are merged. In that time Group discovery record's ID wins, so device cannot boot from PXE (Resource IDs are excluded - that make sense). To by pass that we have to delete all objects and recreate manual machine entry object again.

Can Microsoft change the logic, that Manual machine entry Resource ID wins, please?

8 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Ondrej Seda shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • Ondrej Seda commented  ·   ·  Flag as inappropriate

    Technical description: PC not booting due to wrong resource ID
    Computers were discovered by AD Group discovery and recod was created with resource ID starting with "209". After that action Manual machine entry was created starting with resource ID "168".
    After while those two records were merged together but resource ID starting with "209" wins - that's the issue.

    TS was deployed on merged object to start staging.

    PC was not able to boot from PXE, because IDs that are higher than "200" are excluded when WDS is trying to enumerate available TS for OSD. Returned message to PC is, that there is no OSD assigned to Object.

Feedback and Knowledge Base