none
Device enrolled in co-management showing alpha numeric characters RRS feed

  • Question

  • Devices we enroll on co-management show alpha-numeric character and not the correct computer name  on Endpoint manager, wipe, reset and other functions are also greyed out. What could be the problem. Device is reporting as it should, and showing the right name on SCCM but not on Endpoint manager. 

    What I have checked

    Client setting is turned on,on SCCM
    User logged on the system has been assigned the intune license too 

    • Edited by Sovrano Friday, June 12, 2020 12:45 PM
    Friday, June 12, 2020 12:44 PM

All replies

  • You will need to provide more details, exactly what is ConfigMgr not showing? Remember that the computer name must adhere to the NetBIOS naming standards. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Friday, June 12, 2020 1:05 PM
  • On ConfigMgr the correct computer name is showing and yes it adheres to the netbios naming standard 

    On Endpoint Manager here is what I see, all alpha numeric characters  

    

    Friday, June 12, 2020 1:29 PM
  • Hi,

    You need to move the compliance policy workload to intune as it's currently set to configmgr. You can do this in administration > cloud services > co-management
    For more details, see:
    https://docs.microsoft.com/en-us/mem/configmgr/comanage/workloads#compliance-policies



    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 15, 2020 8:07 AM
  • The compliance policy is already set to "Pilot Intune". Dont know why it still says see ConfigMgr 
    Monday, June 15, 2020 1:39 PM
  • What version of ConfigMgr CB?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, June 15, 2020 4:07 PM
  • 1906
    Monday, June 15, 2020 7:08 PM
  • I can't tell if this was a specific issue in 1906 or not off-hand, but the recommended action here is to upgrade to 2002.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, June 15, 2020 7:27 PM
  • Hi,

    I agree with Jason, you can try to upgrade the site to 2002 first and see if this problem will disappear.

    After completing the site upgrade, don't forget to upgrade the client agent to the latest version as well.

    Best regards,
    Larry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 16, 2020 9:26 AM
  • is there an article or something I can read regarding this, was prepared for SCCM upgrade now but if we must just want more details 
    Monday, June 22, 2020 3:42 PM
  • Here's the what's new for 2002but if yo uare looking for a specific reference for this issue, none will be available publically: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2002

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, June 22, 2020 7:28 PM