Scribd Logo
Upload

Welcome to Scribd!

  • 80 views

    Manage Conflicting Records

    Uploaded by

    siddu_shinde
    Configuration Manager uses hardware identifiers to identify duplicate client records and alerts administrators to conflicts. It can automatically resolve conflicts using Windows authentication or PKI certificates. Administrators can manually resolve conflicts by merging, creating a new record, or blocking the record. They can also ignore duplicate hardware identifiers by adding them to the hierarchy settings.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Manage Conflicting Records

    Uploaded by

    siddu_shinde
    80 views2 pages
    Configuration Manager uses hardware identifiers to identify duplicate client records and alerts administrators to conflicts. It can automatically resolve conflicts using Windows authentication or PKI certificates. Administrators can manually resolve conflicts by merging, creating a new record, or blocking the record. They can also ignore duplicate hardware identifiers by adding them to the hierarchy settings.

    Original Description:

    Manage conflicting records

    Original Title

    Manage conflicting records

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Configuration Manager uses hardware identifiers to identify duplicate client records and alerts administrators to conflicts. It can automatically resolve conflicts using Windows authentication or PKI certificates. Administrators can manually resolve conflicts by merging, creating a new record, or blocking the record. They can also ignore duplicate hardware identifiers by adding them to the hierarchy settings.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    80 views2 pages

    Manage Conflicting Records

    Uploaded by

    siddu_shinde
    Configuration Manager uses hardware identifiers to identify duplicate client records and alerts administrators to conflicts. It can automatically resolve conflicts using Windows authentication or PKI certificates. Administrators can manually resolve conflicts by merging, creating a new record, or blocking the record. They can also ignore duplicate hardware identifiers by adding them to the hierarchy settings.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    Manage conflicting records

    Configuration Manager uses the hardware identifier to attempt to identify clients that might be
    duplicates and alert you to the conflicting records. For example, if you reinstall a computer, the
    hardware identifier would be the same but the GUID used by Configuration Manager might be
    changed.

    Configuration Manager automatically resolves conflicts by using Windows authentication of the


    computer account or a PKI certificate from a trusted source. When Configuration Manager can't
    resolve the conflict of duplicate hardware identifiers, a hierarchy setting determines the behavior.

    Change the hierarchy setting for managing conflicting records

    1. In the Configuration Manager console, go to the Administration workspace, expand Site


    Configuration, and select the Sites node.
    2. In the ribbon, select Hierarchy Settings.
    3. Switch to the Client Approval and Conflicting Records tab, and select one of the
    following options:
    o Automatically resolve conflicting records
    o Manually resolve conflicting records
    Manually resolve conflicting records

    1. In the Configuration Manager console, go to the Monitoring workspace, expand System


    Status, and select the Conflicting Records node.
    2. Select one or more conflicting records, and then choose Conflicting Record.
    3. Select one of the following options:
    o Merge: Combine the newly detected record with the existing client record.
    o New: Create a new record for the conflicting client record.
    o Block: Create a new record for the conflicting client record, but mark it as
    blocked.

    Manage duplicate hardware identifiers


    You can provide a list of hardware identifiers that Configuration Manager ignores for PXE boot
    and client registration. This list helps to address two common issues:

    1. Many new devices don't include an onboard Ethernet port. Technicians use a USB-to-
    Ethernet adapter to establish a wired connection for purposes of OS deployment. These
    adapters are often shared because of cost and general usability. The site uses the MAC
    address of this adapter to identify the device. So reusing the adapter becomes problematic
    without additional administrator actions between each deployment. To reuse the adapter in
    this scenario, exclude its MAC address.
    2. While the SMBIOS attribute should be unique, some specialty hardware devices have
    duplicate identifiers. Exclude this duplicate identifier and rely on the unique MAC address
    of each device.
    Use the following process to add hardware identifiers for Configuration Manager to ignore:

    1. In the Configuration Manager console, go to the Administration workspace, expand Site


    Configuration, and select the Sites node.
    2. On the Home tab of the ribbon, in the Sites group, choose Hierarchy Settings.
    3. Switch to the Client Approval and Conflicting Records tab. To add new hardware
    identifiers, choose Add in the Duplicate hardware identifiers section.

     Tip

    Starting in version 1910, use the following PowerShell cmdlets to automate the management of
    duplicate hardware identifiers:

     New-CMDuplicateHardwareIdGuid
     Remove-CMDuplicateHardwareIdGuid
     New-CMDuplicateHardwareIdMacAddress
     Remove-CMDuplicateHardwareIdMacAddress
    Start policy retrieval
    A Configuration Manager client downloads its client policy on a schedule that you configure as a
    client setting. You can also start on-demand policy retrieval from the client. For example, for
    troubleshooting or testing situations.

     Client notification
     The client control panel
     Support Center
     A script
    Start client policy retrieval with client notification

    1. In the Configuration Manager console, go to the Assets and Compliance workspace, and


    select Devices.
    2. Select the device that you want to download policy. On the Home tab of the ribbon, in
    the Device group, select Client Notification, and then choose Download Computer
    Policy.

    You might also like