Forum Discussion

Prasidh_Arora's avatar
Prasidh_Arora
Icon for Microsoft rankMicrosoft
Mar 31, 2020

Now Available: Windows Admin Center 1910.2 Insider Preview

Windows Admin Center version 1910.2 is a cumulative update to our 1910 GA release in November. This release contains updates to the platform’s accessibility and numerous bug fixes. In addition, we’ve...
Prasidh_Arora's avatar
Prasidh_Arora
Icon for Microsoft rankMicrosoft
Apr 01, 2020

Jared Lambe Thanks for helping me troubleshoot. A few more questions:

1. What OS are you running?

2. If you are able, can you share a screenshot of what you are seeing (with sensitive values ommited)

3. Was this a problem in our previous Windows Admin Center release?

mkhof's avatar
mkhof
Copper Contributor
Apr 17, 2020

Prasidh_Arora 

Hi, I'm running into the same issue and did some testing. As far as i can tell, it seems to come down to the admin center expecting some values (maybe provided by the bios, like manufacturer and model, etc?) to be present, that might not always be there.

In my tests I created two identical Server2016-VMs and ran one using VirtualBox, and the other one using my Proxmox-Server (which uses KVM and QEMU for virtualization). When trying to manage these VMs using the admin center, the one running in VirtualBox worked flawlessly while the other one showed me the exact same erros, that have already been reported by the other people.

I don't know if this is helpful, but if you think it is, i'll be happy to provide you with more information, if you tell me what you need.

  • EdKutsko's avatar
    EdKutsko
    Copper Contributor
    Apr 22, 2020

    I am seeing the same issue mkhof noted.  In my case Nutanix AHV VM's running UEFI and 2019 core are giving the error.  A VMWare  server running core works fine.  I do not know if that server is UEFI or BIOS at this time.

  • Nicklas Thomsen's avatar
    Nicklas Thomsen
    Copper Contributor
    Apr 21, 2020

    mkhof 

    It's not - It's somekind of bug in latest 1910.2 - I could not connect to my Hyper-V 2019 server - Winadm event log tells that it can't read servername property.

     

    Would also give me 401 access denied even though psremoting works fine from within the VM.

    Uninstalled 1910.2 and installed 1910 with same settings. Can now connect to the Hyper-V server.

     

    Will make an bug report on UserVoice. 

     

    Spoiler
    sessionId : adf7e686-5c9a-458e-903e-bad8b864ed70
    eventId : Trace
    level : Error
    sourceName : msft.sme.shell
    source : MultiToolComponent
    timestamp : 1587485984939
    message : Cannot read property 'serverName' of null
    stack :
    moreEventData :
  • vhajek's avatar
    vhajek
    Copper Contributor
    Apr 19, 2020

    I can confirm the same issue like mkhof. I'm running ProxmoxVE and I've just installed fresh new Win2019 Server Core (1809.2) VM (also with virtio) and latest WAC.

     

    Something is working (i.e. registry), something not (dashboard, services). And I have no clue how to add server roles (my first core and Win2019 too), imho menu entry is probably missing due to this problem.