Last Update: Sep 04, 2024 | Published: Jun 29, 2021
Back at Microsoft Ignite 2017 in Orlando, FL, I attended the session where ‘Project Honolulu’ was announced and demonstrated. This was a fresh, built-from-scratch new server management tool for Windows Servers, Windows 10, and Azure resources. I do recall there being a large number of applause sessions from all the IT Pros in the audience!
When the product officially went live on April 12, 2018, they christened it ‘Windows Admin Center.’ In this article, I will show you how to download and install Windows Admin Center (WAC).
You can install the Windows Admin Center MSI on any supported version of Windows Server, Windows 10, or Windows 11. It only needs network access, of some kind, to the servers and computers you wish to manage. For this guide, I’ll be using my Windows Server 2022 Hyper-V AD lab environment. I’ll be installing the tool on a small file server running the latest version of Windows Server 2025 (in the Windows Server Insider Program), due to be released during the 2nd half of 2024. Let’s see how things go.
Windows Admin Center is available for download as a Microsoft Install (MSI) file. You can download Windows Admin Center from Microsoft’s website. The link provides you with the latest version of WAC. Once WAC has been installed, it is updated automatically using its internal updating mechanism and/or Microsoft (Windows) Update.
Now let’s install Windows Admin Center.
In December 2023, the Windows Admin Center modernized gateway was released in public preview with the Windows Server Insider program. This new modernized gateway has gone through a significant backend upgrade of infrastructure components including moving from .NET 4.6.2 to .NET Core, an updated installer, multi-process and micro-service based architecture, a new web server, and more.
Let me give you a brief demo of installing this new modernized gateway. Because it can be installed side-by-side with the existing ‘production’ version of WAC (version 2311 as of this writing), I’ll install it on the same Windows Server 2025 server as above. Let’s get started.
Click to accept the licensing agreement, and click Next.
I tested it by logging in with my Domain Admin account on one of my Windows 11 client PCs and it worked.
First, you’ll need to download the latest version of WAC. You can download Windows Admin Center from Microsoft’s website. Once downloaded, transfer the .msi file to your Windows Server virtual machine. The easiest way to do that is using the Copy-VMFile PowerShell cmdlet. But before you can run Copy-VMFile, make sure that guest services are enabled for the VM. You can check the status of guest services for your Windows Server 2019 VM using the Get-VMIntegrationService cmdlet.
Open a PowerShell prompt in the Hyper-V host OS and run the command shown below, replacing Server2019 with the name of your VM as it is displayed in Hyper-V manager.
Get-VMIntegrationService -name Guest* -VMName Server2019
If guest services aren’t enabled for the VM, enable them using Enable-VMIntegrationService as shown below, again replacing Server2019 with the name of your virtual machine:
Enable-VMIntegrationService -name Guest* -VMName Server2019 -Passthru
Now we’re ready to copy the WAC installer file to Windows Server 2019. Using the command line below, replace Server2019 with the name of your virtual machine as you see it in the Hyper-V management console. The -SourcePath parameter should be the full path to the .msi file on the host OS and -DestinationPath where you want to transfer it to in the guest OS.
Copy-VMFile “Server2019” -SourcePath “C:UsersUserDownloadsWindowsAdminCenter1804.msi” -DestinationPath “C:tempWindowsAdminCenter1804.msi” -CreateFullPath -FileSource Host
The final step is to run the WAC installer file silently on Server Core. If you haven’t already logged in to Windows Server 2019, log in using a local administrator account. In a command prompt window, run the following command.
msiexec /i c:tempWindowsAdminCenter1804.msi /qn /L*v log.txt SME_PORT=443 SSL_CERTIFICATE_OPTION=generate
SME_PORT sets the port on which users will connect to the WAC gateway. In this test environment, we don’t have our own certificate to use with WAC, so the SSL_CERTIFICATE_OPTION is used to generate a certificate for Secure Sockets Layer (SSL). Before closing the command prompt, type ipconfig and press ENTER. Make a note of the VM’s IP address.
Once WAC is installed, which takes just a few seconds, connect to WAC from the Hyper-V host OS or other device that has network connectivity to the Windows Server 2019 VM. WAC supports Microsoft Edge and Google Chrome, although it might work in other browsers. Open a browser, type https://192.168.1.67 in the address bar, and press ENTER, replacing 192.168.1.67 with the IP address of your Windows Server 2019 VM. You’ll get a warning that the site is not secure because the browser doesn’t trust the certificate that was generated when WAC was installed. In our test environment, that’s OK. I’m using Edge, so to continue I need to click Details on the warning page and then Go on to the web page (Not recommended).
You will be prompted to log in to the gateway. Enter a username and password, in this case the administrator account in Windows Server 2019, and click OK. Click Skip Tour on the welcome screen. Under All Connections, you should see your Windows Server 2019 VM. Click on the server, enter the local administrator account for your Windows Server again in the Specify your credentials panel and click Continue. Now you have access to the WAC tools page for your Windows Server!