Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Dave

My feedback

  1. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
    Dave shared this idea  · 
  2. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  3. 33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Remote Control  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  4. 64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback and suggestions, updating status to started.

    We added these CmdLets in our 1910 release:
    New-CMDuplicateHardwareIdGuid
    New-CMDuplicateHardwareIdMacAddress
    Remove-CMDuplicateHardwareIdGuid
    Remove-CMDuplicateHardwareIdMacAddress

    More details here:
    https://docs.microsoft.com/en-us/powershell/sccm/1910-release-notes?view=sccm-ps

    Please try them out and share any feedback you may have, then I’ll likely close this item with our 2002 release.

    Dave supported this idea  · 
    An error occurred while saving the comment
    Dave commented  · 

    Adding on to this, a description or comment field would be nice so I can know what the MAC address went to and what site it was at.

  5. 72 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
  6. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Troubleshooting & Support  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  7. 152 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  8. 863 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  28 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. 284 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Ideas » Asset Management  ·  Flag idea as inappropriate…  ·  Admin →

    This can be done today w/ #SCCM 1802 (and previous versions too). I will mark started… and watch comments for why this doesn’t just work… before I mark this straight up completed…

    Steps:
    1) On the CAS (or standalone primary), go to Administration → Hierarchy Configuration → Discovery methods
    2) right click on Active Directory System Discovery and bring up the Properties form. Active Directory Attributes tab, and then click on Custom. In the form that appears, type the name of the attribute. Click OK, and make sure you have added it as an attribute to discover. Run discovery after exiting properties form.
    3) Now when you go to the Devices view and right click on a device and go to its Properties form, you will see the new attribute showing up there.

    Dave supported this idea  · 

Feedback and Knowledge Base