Windows Admin Center Doesn't ConnectUseful Command-line Commands on WindowsWhy do I get Access Denied when...

My friend is being a hypocrite

Unfrosted light bulb

What if (if any) the reason to buy in small local stores?

Fewest number of steps to reach 200 using special calculator

How could an airship be repaired midflight?

Help rendering a complicated sum/product formula

Turning a hard to access nut?

Do I need to be arrogant to get ahead?

PTIJ What is the inyan of the Konami code in Uncle Moishy's song?

Synchronized implementation of a bank account in Java

Describing a chess game in a novel

How can I wire 7 outdoor posts correctly?

Do US professors/group leaders only get a salary, but no group budget?

How to define limit operations in general topological spaces? Are nets able to do this?

Is there a hypothetical scenario that would make Earth uninhabitable for humans, but not for (the majority of) other animals?

Can other pieces capture a threatening piece and prevent a checkmate?

Can you move over difficult terrain with only 5 feet of movement?

Is there a term for accumulated dirt on the outside of your hands and feet?

Knife as defense against stray dogs

Is honey really a supersaturated solution? Does heating to un-crystalize redissolve it or melt it?

Should I use acronyms in dialogues before telling the readers what it stands for in fiction?

Variable completely messes up echoed string

How does one measure the Fourier components of a signal?

What exactly term 'companion plants' means?



Windows Admin Center Doesn't Connect


Useful Command-line Commands on WindowsWhy do I get Access Denied when using WinRM?Why can a Domain Admin run a powershell cmd locally, but connecting over WinRM with the same account, command returns an UnauthorizedAccessException?Should I add my user account to local admin group to manage remote Windows hosts? (Server 2012)Event log subscription returns error code (0x138C)WinRM cannot connectCan't enable remote management after joining domainNew Vagrant Packaged Windows Server 2016 returning Authentication failure. Retryingwindows-ubuntu-bash + hypervisor winrm + ansible - Server not found in Kerberos databaseCannot connect to Remote Desktop with Windows Hello PIN













0















I've installed version 1804.25 of Windows Admin Center (WAC) onto my Windows 10 Pro v1709 laptop. I accepted the WAC self-signed cert, provided by the installer, on first page load. I then used the WAC interface to add two EC2 servers. That is, I specified the public DNS of the two machines, and then chose "use another account for this connection" and provided the EC2 server's "Administrator" account and password for both machines. WAC indicated that both machines were successfully confirmed and added. I successfully reached this point because I set IP inbound rules on the EC2 security group for WinRM, and opened the WinRM port on the servers' firewall.



However, when I click "Connect" for either of these servers, I get the message:



Couldn't Connect: Verify the connection details and then try again.


I notice there is also the option to connect to my local laptop, where WAC is running. When I choose this option - it still won't connect and gives the same error. In short, WAC acts healthy, but can't connect to anything.



Any ideas? I can successfully connect to both EC2 servers via RDP.



further details:




  • Did you install with the default port setting? Yes

  • Is the machine where Windows Admin Center is installed joined to a domain? Yes

  • Is the machine that you are trying to manage joined to a domain? No

  • Windows version of the machine that you are trying to manage: Windows 2016 and Windows 2016 Core

  • What browser are you using? Edge










share|improve this question
















bumped to the homepage by Community 3 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I've installed version 1804.25 of Windows Admin Center (WAC) onto my Windows 10 Pro v1709 laptop. I accepted the WAC self-signed cert, provided by the installer, on first page load. I then used the WAC interface to add two EC2 servers. That is, I specified the public DNS of the two machines, and then chose "use another account for this connection" and provided the EC2 server's "Administrator" account and password for both machines. WAC indicated that both machines were successfully confirmed and added. I successfully reached this point because I set IP inbound rules on the EC2 security group for WinRM, and opened the WinRM port on the servers' firewall.



    However, when I click "Connect" for either of these servers, I get the message:



    Couldn't Connect: Verify the connection details and then try again.


    I notice there is also the option to connect to my local laptop, where WAC is running. When I choose this option - it still won't connect and gives the same error. In short, WAC acts healthy, but can't connect to anything.



    Any ideas? I can successfully connect to both EC2 servers via RDP.



    further details:




    • Did you install with the default port setting? Yes

    • Is the machine where Windows Admin Center is installed joined to a domain? Yes

    • Is the machine that you are trying to manage joined to a domain? No

    • Windows version of the machine that you are trying to manage: Windows 2016 and Windows 2016 Core

    • What browser are you using? Edge










    share|improve this question
















    bumped to the homepage by Community 3 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I've installed version 1804.25 of Windows Admin Center (WAC) onto my Windows 10 Pro v1709 laptop. I accepted the WAC self-signed cert, provided by the installer, on first page load. I then used the WAC interface to add two EC2 servers. That is, I specified the public DNS of the two machines, and then chose "use another account for this connection" and provided the EC2 server's "Administrator" account and password for both machines. WAC indicated that both machines were successfully confirmed and added. I successfully reached this point because I set IP inbound rules on the EC2 security group for WinRM, and opened the WinRM port on the servers' firewall.



      However, when I click "Connect" for either of these servers, I get the message:



      Couldn't Connect: Verify the connection details and then try again.


      I notice there is also the option to connect to my local laptop, where WAC is running. When I choose this option - it still won't connect and gives the same error. In short, WAC acts healthy, but can't connect to anything.



      Any ideas? I can successfully connect to both EC2 servers via RDP.



      further details:




      • Did you install with the default port setting? Yes

      • Is the machine where Windows Admin Center is installed joined to a domain? Yes

      • Is the machine that you are trying to manage joined to a domain? No

      • Windows version of the machine that you are trying to manage: Windows 2016 and Windows 2016 Core

      • What browser are you using? Edge










      share|improve this question
















      I've installed version 1804.25 of Windows Admin Center (WAC) onto my Windows 10 Pro v1709 laptop. I accepted the WAC self-signed cert, provided by the installer, on first page load. I then used the WAC interface to add two EC2 servers. That is, I specified the public DNS of the two machines, and then chose "use another account for this connection" and provided the EC2 server's "Administrator" account and password for both machines. WAC indicated that both machines were successfully confirmed and added. I successfully reached this point because I set IP inbound rules on the EC2 security group for WinRM, and opened the WinRM port on the servers' firewall.



      However, when I click "Connect" for either of these servers, I get the message:



      Couldn't Connect: Verify the connection details and then try again.


      I notice there is also the option to connect to my local laptop, where WAC is running. When I choose this option - it still won't connect and gives the same error. In short, WAC acts healthy, but can't connect to anything.



      Any ideas? I can successfully connect to both EC2 servers via RDP.



      further details:




      • Did you install with the default port setting? Yes

      • Is the machine where Windows Admin Center is installed joined to a domain? Yes

      • Is the machine that you are trying to manage joined to a domain? No

      • Windows version of the machine that you are trying to manage: Windows 2016 and Windows 2016 Core

      • What browser are you using? Edge







      windows powershell windows-server-2016 winrm sysadmin






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 7 '18 at 4:56







      Brent Arias

















      asked Aug 7 '18 at 4:50









      Brent AriasBrent Arias

      16210




      16210





      bumped to the homepage by Community 3 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 3 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I discovered the problem. It is a design flaw in Windows Admin Center. Here is a User Voice ticket that describes the problem and work-around.



          Simply put, I'm giving FQDN server identifiers to WAC on my domain-joined laptop. It confirms that the server exists and that I've provided the correct credentials. Then it stores the server connection using the hostname of the server instead of the FQDN. Unfortunately, the cloud-based servers I'm targeting are not on my own domain - or any domain at all. So the hostname does not resolve.



          The solution is for me to put the hostname into my HOSTS file with explicit IP addresses. Very obnoxious, since the cloud-servers have dynamic IP's!






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "2"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f925218%2fwindows-admin-center-doesnt-connect%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I discovered the problem. It is a design flaw in Windows Admin Center. Here is a User Voice ticket that describes the problem and work-around.



            Simply put, I'm giving FQDN server identifiers to WAC on my domain-joined laptop. It confirms that the server exists and that I've provided the correct credentials. Then it stores the server connection using the hostname of the server instead of the FQDN. Unfortunately, the cloud-based servers I'm targeting are not on my own domain - or any domain at all. So the hostname does not resolve.



            The solution is for me to put the hostname into my HOSTS file with explicit IP addresses. Very obnoxious, since the cloud-servers have dynamic IP's!






            share|improve this answer




























              0














              I discovered the problem. It is a design flaw in Windows Admin Center. Here is a User Voice ticket that describes the problem and work-around.



              Simply put, I'm giving FQDN server identifiers to WAC on my domain-joined laptop. It confirms that the server exists and that I've provided the correct credentials. Then it stores the server connection using the hostname of the server instead of the FQDN. Unfortunately, the cloud-based servers I'm targeting are not on my own domain - or any domain at all. So the hostname does not resolve.



              The solution is for me to put the hostname into my HOSTS file with explicit IP addresses. Very obnoxious, since the cloud-servers have dynamic IP's!






              share|improve this answer


























                0












                0








                0







                I discovered the problem. It is a design flaw in Windows Admin Center. Here is a User Voice ticket that describes the problem and work-around.



                Simply put, I'm giving FQDN server identifiers to WAC on my domain-joined laptop. It confirms that the server exists and that I've provided the correct credentials. Then it stores the server connection using the hostname of the server instead of the FQDN. Unfortunately, the cloud-based servers I'm targeting are not on my own domain - or any domain at all. So the hostname does not resolve.



                The solution is for me to put the hostname into my HOSTS file with explicit IP addresses. Very obnoxious, since the cloud-servers have dynamic IP's!






                share|improve this answer













                I discovered the problem. It is a design flaw in Windows Admin Center. Here is a User Voice ticket that describes the problem and work-around.



                Simply put, I'm giving FQDN server identifiers to WAC on my domain-joined laptop. It confirms that the server exists and that I've provided the correct credentials. Then it stores the server connection using the hostname of the server instead of the FQDN. Unfortunately, the cloud-based servers I'm targeting are not on my own domain - or any domain at all. So the hostname does not resolve.



                The solution is for me to put the hostname into my HOSTS file with explicit IP addresses. Very obnoxious, since the cloud-servers have dynamic IP's!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 10 '18 at 18:52









                Brent AriasBrent Arias

                16210




                16210






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Server Fault!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f925218%2fwindows-admin-center-doesnt-connect%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    117736 Шеррод Примітки | Див. також | Посилання | Навігаційне...

                    As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                    Маріан Котлеба Зміст Життєпис | Політичні погляди |...