This is our first GA refresh since Windows Admin Center version 1804.25, and it's packed with new features. Check out the official announcement blog post for more information and download or update today!https://cloudblogs.microsoft.com/windowsserver/2018/09/20/windows-admin-center-1809-and-sdk-now-generally-available/

Jeff Woolslayer Yes and Yes both work fine, i use them both quite reguarly. I'm at a loss, i've tried just about everything under the sun. and like i said, it worked fine in 1808. It's on its own vm with nothing else installed other than windows admin center. I'm going to try installing it on a fresh new vm of 2016 and see if that fixes it

And it still pushes US date format everywhere. Can you not pick the date up from the host OS? It's annoying having to work out of 10/1 is the 10th January or 1st October! Better yet just use whole dates.

I upgraded from 1808 to 1809 and now when i try to use remote desktop it just keeps spinning and never loads, same thing happens when i try to console in to a vm from wac, i tried uninstalling and reinstalling, and looked through troubleshooting steps and couldn't find anything. It worked fine on all of my server before 1809 Platform where Windows Admin Center is installed (Windows 10 or Windows Server):If installed on Server, what is the Windows version of the machine running the browser to access Windows Admin Center: Windows Server 2016 StdAre you using the self-signed certificate created by the installer? NoIf you are using your own certificate, does the subject name match the machine? YesIf you are using your own certificate, does it specify an alternate subject name? noDid you install with the default port setting?If not, which port did you specify? 4433Is the machine where Windows Admin Center is installed joined to a domain? yesWindows version where Windows Admin Center is installed: Server 2016 CoreIs the machine that you are trying to manage joined to a domain? yes, except my hyper v host it is not domain joinedWindows version of the machine that you are trying to manage: server 2016What browser are you using? Google Chrome 69.0.3497.100 Kinda bummed because i was really stoked for the hyper-v console feature

Did you ever get Remote Desktop working via admin center?

We've fixed some bugs in the most recent release, check out the 1809.5 announcement here.

Windows Admin Center 1809 Generally Available!

Gary Williams
Copper Contributor
Sep 23, 2018
And it still pushes US date format everywhere. Can you not pick the date up from the host OS? It's annoying having to work out of 10/1 is the 10th January or 1st October! Better yet just use whole dates.
- Jeff Woolslayer
  Microsoft
  Sep 23, 2018
  Gary Williams did you set the regional settings?
  
  If so, please let us know which language and regional setting that you have selected and where you aren't seeing it applied correctly.
  - Gary Williams
    Copper Contributor
    Sep 23, 2018
    Jeff Woolslayer
    Yes I set the regional settings. The Date is fine on the main screen but wrong in other places.
    
    Did you see the screenshot I posted? that's a prime example right there.
Deleted
Oct 01, 2018
I upgraded from 1808 to 1809 and now when i try to use remote desktop it just keeps spinning and never loads, same thing happens when i try to console in to a vm from wac, i tried uninstalling and reinstalling, and looked through troubleshooting steps and couldn't find anything. It worked fine on all of my server before 1809

Platform where Windows Admin Center is installed (Windows 10 or Windows Server):
If installed on Server, what is the Windows version of the machine running the browser to access Windows Admin Center: Windows Server 2016 Std
Are you using the self-signed certificate created by the installer? No
If you are using your own certificate, does the subject name match the machine? Yes
If you are using your own certificate, does it specify an alternate subject name? no
Did you install with the default port setting?
If not, which port did you specify? 4433
Is the machine where Windows Admin Center is installed joined to a domain? yes
Windows version where Windows Admin Center is installed: Server 2016 Core
Is the machine that you are trying to manage joined to a domain? yes, except my hyper v host it is not domain joined
Windows version of the machine that you are trying to manage: server 2016
What browser are you using? Google Chrome 69.0.3497.100
Kinda bummed because i was really stoked for the hyper-v console feature
- Jeff Woolslayer
  Microsoft
  Oct 02, 2018
  Deleted - Will you please try Microsoft Edge and see if the RDP tool works for you there?
  
  In the Virtual machine tool - if you choose to download the RDP file, are you able to successfully connect to the VM's console?
  - Deleted
    Oct 03, 2018
    Jeff Woolslayer Just tried in Edge and it does the same thing. And yes i can connect to my vm's just fine when i download the RDP file.
Elke Endörfer
Copper Contributor
Sep 21, 2018
The upgrade doesn't seem to work.
We use a working installation of v1804 on a Server 2016.
Simply installed the v1809 msi, everything worked fine, but after the update the website isn't reachable anymore. Any idea?
- Jeff Woolslayer
  Microsoft
  Sep 21, 2018
  Check out the troubleshooting guide for common issues and resolution steps. If nothing there solves your issue, please reply back here with the answers to the troubleshooting common questions.
Artur Schneider
Copper Contributor
Sep 25, 2018
Hi Jeff Woolslayer I have the same issue as Elke Endörfer after installation site is either not reachable or if it manages to connect it throws ajax error 0 when trying to display any information (I ran PS script for connecition testing and there was no issues). Any news on that?

Thank You!
I also posted some problems in regards of insider version 1808. Has any of these issue been addressed?
https://techcommunity.microsoft.com/t5/Windows-Admin-Center/WAC-1808-File-Copy-errors-and-powershell-disconnecting/m-p/257019#M119
Regards,
Artur
- Jeff Woolslayer
  Microsoft
  Sep 25, 2018
  Artur Schneider please check out the troubleshooting guide for common issues and resolution steps. If nothing there solves your issue, please reply back here with the answers to the troubleshooting common questions. Ajax error 0 is generally seen if the Windows Admin Center service is not running.
  
  I'll reply on the other thread as well.
  - Artur Schneider
    Copper Contributor
    Sep 26, 2018
    Version:1.0 StartHTML:000000266 EndHTML:000002633 StartFragment:000002016 EndFragment:000002601 StartSelection:000002016 EndSelection:000002597 SourceURL:https://techcommunity.microsoft.com/t5/forums/replypage/board-id/WindowsServerManagement/message-id/134
    Thank you for replying. I tried to apply suggested changes. WAC v.1809 Win Server 2016. Initially after accessing site I was indeed getting error message websocket/powershell could not connect. I checked features on Server 2016 and added WebSocket feature. Now I am not able to connect to server even locally getting connection refused message. As for Ajax error I checked the service and it was running.
BenRadder
Copper Contributor
Sep 26, 2018
I get this error every time I run the upgrade.
- Jeff Woolslayer
  Microsoft
  Sep 26, 2018
  We are tracking that error here: https://windowsserver.uservoice.com/forums/295071/suggestions/35488156

Forum Discussion

Windows Admin Center 1809 Generally Available!

Share

Resources