SOLVED
Home

Can't connect/Find servers in Windows Admin Center 1909

%3CLINGO-SUB%20id%3D%22lingo-sub-869120%22%20slang%3D%22en-US%22%3ECan't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-869120%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20installed%20Windows%20Admin%20Center%201909%20on%20Windows%2010%20build%2018985%2C%3C%2FP%3E%3CP%3Eset%20it%20to%20only%20use%20HTTPS%20connections%20and%20set%20the%20custom%20port%206666%20for%20it.%3C%2FP%3E%3CP%3Ethen%20I%26nbsp%3Bfollowed%20this%20guide%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.tenforums.com%2Ftutorials%2F113966-windows-admin-center-centrally-manage-all-your-windows-10-pcs.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.tenforums.com%2Ftutorials%2F113966-windows-admin-center-centrally-manage-all-your-windows-10-pcs.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Enow%20I%20am%20having%20problem%20even%20managing%20my%20own%20computer%20(Not%20domain%20joined)%2C%20let%20alone%20the%20Windows%20Server%202019%20(domain%20joined)%20which%20is%20running%20on%20Hyper-V%20VM%20on%20my%20computer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20enabled%26nbsp%3B%3CSTRONG%3EEnable-PSRemoting%26nbsp%3B%3C%2FSTRONG%3Eon%20Windows%20server%202019%20and%20on%20my%20computer%20as%20well.%20still%20when%20I%20type%20in%20the%20IP%20address%20of%20the%20server%20in%20WAC%2C%20it%20doesn't%20find%20anything.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-869120%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E1909%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECan't%20find%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EConnection%20Problem%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWAC%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870763%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870763%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20this%20time%2C%20Windows%20Admin%20Center%20only%20supports%20the%20default%20WinRM%20ports%3A%205985(http)%20%26amp%3B%205986(https)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20tracking%20interest%20with%20%3CA%20href%3D%22https%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295071-management-tools%2Fsuggestions%2F33981802--configuration-winrm-connect-using-non-default%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20feedback%20item%3C%2FA%3E%2C%20add%20your%20vote!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870797%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870797%22%20slang%3D%22en-US%22%3EThanks.%20but%20why%20does%20it%20let%20us%20choose%20other%20ports%20then%20during%20WAC%20installation%20if%20custom%20ports%20are%20not%20supported%3F%20doesn't%20make%20sense.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871042%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871042%22%20slang%3D%22en-US%22%3EBy%20the%20way%2C%3CBR%20%2F%3EI'm%20just%20installing%20the%20WAC%201909%20and%20the%20default%20port%20on%20the%20installation%20screen%20is%20%226516%22.%20how%20is%20that%20possible%3F%3CBR%20%2F%3E%3CBR%20%2F%3Ealso%20when%20I%20check%20the%20box%20for%20HTTPS%20only%20connection%2C%20the%20port%20stays%20the%20same.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871055%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871055%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20port%20selection%20in%20the%20installer%20is%20for%20the%20HTTPS%20endpoint%20of%20the%20WAC%20interface.%3C%2FP%3E%0A%3CP%3E6516%20is%20the%20default%20on%20desktop%20installations.%20You'll%20see%20when%20you%20launch%20WAC%20from%20your%20start%20menu%2C%20it%20will%20open%20a%20browser%20to%20https%3A%2F%2Flocalhost%3A6516%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871069%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871069%22%20slang%3D%22en-US%22%3ESo%20If%20i%20set%20the%20port%20for%20%22HTTPS%20endpoint%20of%20the%20WAC%20interface%22%20to%206666%20instead%20of%206516%2C%20during%20installation%2C%20it%20should%20work%2C%20right%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871077%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%2FFind%20servers%20in%20Windows%20Admin%20Center%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871077%22%20slang%3D%22en-US%22%3E%3CP%3ENo%2C%20sorry%20-%20if%20you%20take%20a%20look%20at%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fmanage%2Fwindows-admin-center%2Fmedia%2Farchitecture.png%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ediagram%3C%2FA%3E%20on%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fmanage%2Fwindows-admin-center%2Funderstand%2Fwhat-is%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20page%3C%2FA%3E%2C%20it%20should%20be%20easier%20to%20visualize.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20port%20selection%20in%20the%20installer%20corresponds%20to%20the%20HTTPS%20port%20for%20the%20WAC%20UI%20where%20the%20client%20browser%20will%20connect%2C%20like%20a%20webpage.%20In%20the%20diagram%2C%20this%20is%20the%20HTTPS%20between%20the%20%3CSTRONG%3Eclient%20browser%3C%2FSTRONG%3E%20and%20WAC.%20This%20is%20the%20only%20%22side%22%20that%20is%20configurable%20currently.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhere%20you%20have%20WinRM%20set%20up%20to%20use%20HTTPS%20transport%20on%20port%206666%20is%20on%20the%20%3CSTRONG%3Emanaged%20nodes%3C%2FSTRONG%3E%20on%20the%20other%20%22side%22%20of%20WAC%2C%20at%20the%20bottom%20of%20the%20diagram.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
HotCakeX
Esteemed Contributor

I've installed Windows Admin Center 1909 on Windows 10 build 18985,

set it to only use HTTPS connections and set the custom port 6666 for it.

then I followed this guide:

https://www.tenforums.com/tutorials/113966-windows-admin-center-centrally-manage-all-your-windows-10...

 

now I am having problem even managing my own computer (Not domain joined), let alone the Windows Server 2019 (domain joined) which is running on Hyper-V VM on my computer.

 

I enabled Enable-PSRemoting on Windows server 2019 and on my computer as well. still when I type in the IP address of the server in WAC, it doesn't find anything.

6 Replies

At this time, Windows Admin Center only supports the default WinRM ports: 5985(http) & 5986(https)

 

We are tracking interest with this feedback item, add your vote!

Thanks. but why does it let us choose other ports then during WAC installation if custom ports are not supported? doesn't make sense.
By the way,
I'm just installing the WAC 1909 and the default port on the installation screen is "6516". how is that possible?

also when I check the box for HTTPS only connection, the port stays the same.

The port selection in the installer is for the HTTPS endpoint of the WAC interface.

6516 is the default on desktop installations. You'll see when you launch WAC from your start menu, it will open a browser to https://localhost:6516

So If i set the port for "HTTPS endpoint of the WAC interface" to 6666 instead of 6516, during installation, it should work, right?
Solution

No, sorry - if you take a look at the diagram on this page, it should be easier to visualize.

 

The port selection in the installer corresponds to the HTTPS port for the WAC UI where the client browser will connect, like a webpage. In the diagram, this is the HTTPS between the client browser and WAC. This is the only "side" that is configurable currently.

 

Where you have WinRM set up to use HTTPS transport on port 6666 is on the managed nodes on the other "side" of WAC, at the bottom of the diagram. 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies