Blog Post

Windows Admin Center Blog
11 MIN READ

Windows Admin Center (v2) Public Preview build has been updated!

Theo_Tran's avatar
Theo_Tran
Icon for Microsoft rankMicrosoft
Jul 29, 2024

It’s been seven months since we released the last Public Preview for our “Modernized Gateway” (known as v2) -- today, we’re updating the Public Preview build with new functionality and bug fixes. As we get closer to officially releasing this version to general availability (GA), we want to hear from you first so that we proactively address any feedback you may have!

 

Please note that this is still a Public Preview version of Windows Admin Center, so it is not recommended to install this build in your production environment. This preview version will no longer be able to be installed side-by-side with the last GA release (version 2311, or any of the previous releases). Once you install this build and migrate your user data and environment configurations, you will not be able to go back.

 

We’ve been working behind the scenes to ensure that Windows Admin Center is up-to-date, secure, and reliable. We suggest experienced users of Windows Admin Center and Windows Admin Center developers give this new build a try. Read on to learn about the new features and updates!

 

What's new in this v2 build

 

Upgrade to .NET Core 

The Windows Admin Center frontend user-interface (UI) is built on Angular, which is in turn built on our shell. The shell hosts all the core services and most of our UI components, our solutions like server and cluster manager, and, on top of that, every extension that you use for server management.

Our front end interacts with our backend, which is also known as our gateway. The gateway hosts our authorization structure, our PS services, our gateway plug-ins, and plays a critical role in every single experience that you use in Windows Admin Center.

 

 

 

In this release, we have upgraded our backend again, from the .NET Core 6 to .NET Core 8, bringing enhanced security and improved cryptography to our product. This also includes support for HTTP 2, reducing latency and enhancing the responsiveness of Windows Admin Center. Combined with improved performance, providing faster load times, you’ll be able to get your tasks done more quickly and efficiently.

 

Virtual machine tool update

We have heard your feedback and have improved the virtual machine (VM) tool experience! Our primary goal is to provide you with the list of VMs as soon as possible so you are empowered to efficiently carry out your administrative tasks.  

 

Today, we invite you all to enable this feature, use the tool, and share your feedback. 

 

 

Highlights:   

  • The VM Power operations (e.g. start, pause etc.) now only update the VM selected without reloading the entire table, saving customers valuable time 
  • To optimize responsiveness (e.g., clicking, hovering and scrolling), we have removed the runtime pipeline. 
  • To prioritize loading the VM list first, certain operations are deferred until after the initial load (e.g., cluster node check) 
  • To optimize performance, we have reduced the columns in the default view. Note that this can be toggled off using the “Detailed Mode” toggle to switch back to the previous experience  
  • A new streamlined Azure Site Recovery integration experience for users  

 

How to enable the feature 

  1. Navigate to your Windows Admin Center settings by selecting the gear in the top right corner of the header.
  2. Navigate to the “Advanced” tab.
  3. Add the following experiment key:  msft.sme.hyperv.hyperVPreviewMode 

 

 



Updated installer 

While modernizing our gateway, we also made the installer more flexible by providing increased customization options including network access settings, selecting trusted hosts, providing a fully qualified domain name (FQDN) for your gateway machine, and more. For more details about the installer, read on to the Installing the v2 build section.  

 

 

 

Data migration

To ensure that your user and environment data is transferred over, we have implemented a data migration flow so that you will seamlessly transition to the new v2 build. All of your data will be copied over, except for 4 items that will require user intervention. For more details about the installer, read on to the Migrating your data section. 

 

Settings update

As part of our gateway modernization effort, you may notice that your Windows Admin Center settings look a little bit different.

 

 

 

As we discussed in the 2211 Windows Admin Center release, we have deprecated the in-app update experience and have consequently removed the settings blade for Updates. Additionally, the Access and Shared Connections blades are now available on local gateway installations (also known as “desktop mode” in legacy gateway builds).

 

Multi-process, micro-service based

The v2 build also leverages microservice architecture. Prior to this upgrade, Windows Admin Center performed all tasks in a single process. With our new model, we start one process for Windows Admin Center on application startup that serves as a process manager. As you use Windows Admin Center, additional sub-processes are spun up to perform specific tasks.

 

Additionally, gateway plug-ins that are compatible with the v2 build will also run their own collection of sub-processes under the Windows Admin Center service manager to perform their functions.

 

Changing from a monolithic service to a microservice model helps our v2 build be more flexible, scalable, and resilient.

 

Kestrel HTTP web server

Previously, Windows Admin Center utilized Katana components, including a web server, on the backend. With the v2 build, we’ve shifted to an ASP.NET Core Kestrel web server.

 

Kestrel is the recommended web server for ASP.NET Core applications. Kestrel is:

  • High performing: Kestrel is optimized to handle a large number of concurrent connections efficiently.
  • Lightweight: Optimized for running in resource-constrained environments, such as containers and edge devices.
  • Security hardened: Kestrel supports HTTPS and is hardened against web server vulnerabilities.

Additionally, Kestrel supports the HTTP/2 web protocol, where previously we had only supported HTTP1.1 with the Katana components. The upgrade from HTTP1.1 to HTTP/2 brings reduced latency to our application as well as increased responsiveness through enhanced features like multiplexing and server push.

 

Switching to a Kestrel web server will also allow for Windows Admin Center to potentially enable cross-platform support in the future.

 

How does the v2 build impact my extension?

Gateway plug-in extensions will be the most impacted by the changes to our v2 build. Windows Admin Center gateway plug-ins enable API communication from the UI of your tool or solution to a target node. Windows Admin Center hosts a gateway service that relays commands and scripts from gateway plug-ins to be executed on target nodes. The gateway service can be extended to include custom gateway plug-ins that support protocols other than the default ones (PowerShell and WMI).

 

Because gateway plug-ins communicate with Windows Admin Center’s backend to enable API communication, gateway plug-in code may include components written with the .NET framework version 4.6.2, which will not function with .NET Core. This code needs to be updated to use the .NET Core framework.

 

Additionally, we’ve modified the way plug-ins work with our v2 build. Instead of developing a C# class which implements the IPlugIn interface from the Microsoft.ManagementExperience.FeatureInterfaces namespace to extend the gateway plug-in, extensions will now be written in the form of ASP.NET MVC controllers. These controllers have increased flexibility compared to the simple C# class and extensive documentation.

 

Learn more about gateway plug-in development in Windows Admin Center here.

 

What about my tool and/or solution extension?

Solution and tool extensions do not communicate with Windows Admin Center’s backend in-depth and should be minimally impacted by the v2 build. We strongly recommend testing your extension to ensure it continues to run smoothly on the new backend.

 

Installing the v2 build

 

With our v2 build, we’ve made changes to our installer to offer more flexibility to the user.

When running the installer, you will be presented with three different installation modes: express localhost setup, express remote setup, and custom setup.

 

Express setup options

Two of the three installation modes for the v2 build are express modes—express localhost setup and express remote setup.

 

Both express setup options do not allow for the configuration of the following features:

  • Login authentication mode
  • Host access network names
  • Internal and external network ports
  • Certificate type and thumbprint
  • Endpoint FQDN
  • Trusted hosts mode
  • WinRM over HTTPS

 

If you would like to configure any of these features, please use the custom setup option instead.

 

If you select the express localhost setup option, WAC will be accessible through port 6600 and will use internal ports 6601-6610.

 

If you select the express remote setup option, WAC will be accessible through port 443 and will use internal ports 6601-6610.

 

Custom setup

Selecting custom setup allows you to configure all Windows Admin Center setup options:

  • Network access – This page allows you to select how you will be using Windows Admin Center. You may choose to restrict WAC access to other users by selecting localhost access only or allow remote access through machine name of FQDN.
  • Port numbers – This page allows you to select the ports that will be reserved for Windows Admin Center. WAC uses one external port for its primary processes. Other processes use internal ports. There are two internal processes by default, but extensions may define their own services that will require port access. By default, the internal range is 10 ports.
  • Select TLS certificate – This page allows you to select Self-Signed certificates or an official TLS certificate that Windows Admin Center should use. Self-Signed certificates include Self-signed CA root certificates and TLS certificates that work with the latest Edge/Chrome browser.
  • Fully qualified domain name – This page allows you to provide a fully qualified domain name for network access. This name must match the name on the TLS certificate.
  • Trusted hosts – This page allows you to select which type of remote hosts you’d like to manage. You may choose to manage only trusted domain computers or allow access to non-domain joined machines.
  • WinRM over HTTPS - This page allows you to select whether to use HTTPS for WinRM communication. WinRM communicates over HTTP by default.

 

Troubleshooting installation

If your installation failed, or you’re having trouble opening WAC after install, you may need to uninstall and reinstall. This can also happen if you have an older version of a v2 build installed, and you are trying to update to a newer version. To uninstall, follow the instructions in the Uninstalling and cleanup section of this document.

 

Migrating your data

Once you have installed the v2 build, much of your transferable data is automatically copied over to the new build, reducing the time it takes for you to get started. However, there are four items that will require your input on:

  1. Proxy credentials
  2. WebSocket Origin configuration
  3. Azure registration
  4. Extensions

 

You will only have to do this once. Once your data is fully migrated, future releases of Windows Admin Center will have the seamless update experience you know and love.

 

 

 

Proxy credentials

Windows Admin Center will not be able to able access Azure services and the public extension feed without proper proxy credentials. If you have a proxy set up, then you will need to enter the proxy address, as well as the username and password to give Windows Admin Center access.

 

 

 

WebSocket Origin configuration

If you had previously configured WebSocket Origins, you can review and edit them here. To get you started, we have imported the WebSocket Origins list from your previous Windows Admin Center setup.   

 

 

 

Azure registration

Windows Admin Center now requires additional redirect URLs to be configured with the Azure App Registration instance. This can only be done through the Azure Portal. Selecting the “Configure” button will programmatically update the Azure App Registration on your behalf. After it is registered, you may need to re-enable Azure login to Windows Admin Center.

 

You will need the elevated permissions on this Azure subscription to perform this re-registration.

 

 

 

Extensions

The extension feed for v2 builds is not currently fully configured. You may notice missing extensions from this Windows Admin Center instance, including extensions not installed by default on install and ones you may have installed from your own feed or from external partners. As of right now, this page is read-only. We’re working with our internal and external partners to ensure that all extensions are compatible with v2—these extensions will be available soon.

 

 

 

Review + complete

You will not be allowed to use Windows Admin Center unless you complete these steps.

 

 

Uninstalling the v2 build

To uninstall the Windows Admin Center (v2), perform one of the following actions:

  • In the Apps & Features page of your gateway machine settings, select Windows Admin Center (v2) Preview from the program list and then select uninstall.
  • Navigate to the folder where the Windows Admin Center (v2)is installed (default directory is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Admin Center (v2)) and select “Uninstall Windows Admin Center (v2)”
  • Run C:\Program Files\WindowsAdminCenter\unins000.exe

 

Running the installer again will not result in an uninstall option at this time. To ensure your installation was removed successfully, check if a WindowsAdminCenter folder exists in C:\ProgramData or C:\Program Files. If it does not exist in either location, your application has been successfully uninstalled.

 

During the uninstallation process, everything put on the machine during installation will be removed, except for the Windows Admin Center (v2) .exe installer file. If you have another build of Windows Admin Center also installed at the time of your v2 build uninstallation, no files or properties of the other build will be touched during the uninstallation process. There are no interdependencies between the two installations.

 

FAQs

Q: Can you install a build of Windows Admin Center (v2) when you already have an existing build of Windows Admin Center installed?

A: No, you cannot. Once you install this build and migrate your data over, you will not be able to run the legacy build of Windows Admin Center since they use the same ports. 

 

Q: Can I change the ports my Windows Admin Center installation is using after install?

A: Yes, In the Program Files for Windows Admin Center, we’ve included a PowerShell module called Microsoft.WindowsAdminCenter.Configuration.psm1. This module allows you to modify your WAC configuration after installation and can be found in the PowerShellModules folder of your installation (C:\Program Files\WindowsAdminCenter\PowerShellModules\ by default).

To change the ports WAC is using, run the following command:

Set-WACHttpsPort -Wacport <port> -ServicePortRangeStart <port> -ServicePortRangeEnd <port>

 

Q: Changing the ports is great, but can I change other configuration settings after install?

A: Yes! You may use the PowerShell module Microsoft.WindowsAdminCenter.Configuration.psm1 to change your configuration settings. It can be found in the PowerShellModules folder of your installation.

 

Q: Why aren’t all these changes just in the 2311 release?

A: To ensure the best quality experience, we require customer and developer feedback before these changes are generally available.

 

Q: Are all the features in the 2311 release available in this build?

A: Yes! Read more about the Windows Admin Center 2311 release.

 

Known issues

The account for the PowerShell session in the PowerShell tool always defaults to the user signed into the Windows Admin Center gateway, even if different management credentials were specified when remoting to a connection.

 

The extension feed for the v2 build has not been configured. Extensions not included in the Windows Admin Center installer (including external partner extensions) will not be available unless you add an extension feed. Even with an added feed, the following extensions do not currently function with the v2 build:

  • Dell OpenManage
  • Lenovo XClarity Integrator
  • HPE OneView
  • HPE Server extension and HPE Azure Stack HCI extension
  • HPE Storage manager
  • Fujitsu ServerView RAID
  • Fujitsu Software Infrastructure Manager (ISM)
  • Fujitsu ServerView Health
  • Pure Storage FlashArray

 

Looking forward

Please be on the lookout later this year for our next GA release. It will include even more features for Hyper-V, several Windows Server 2025 exclusive features, and will be the most performant build of Windows Admin Center to date!

  

Download now!

We hope you enjoy this new, modern version of Windows Admin Center and the various new functionality in preview.

 

Direct Download Link! 

 

As always, thanks for your ongoing support, adoption, and feedback. Your contributions through user feedback continue to be vital and valuable to us, helping us prioritize and sequence our investments.

 

Windows Admin Center is continuously evolving and growing as a tool and a platform, and we are beyond thrilled to have you part of our journey.

 

Thank you,

Windows Admin Center Team (@servermgmt)

 

 

 

 

 

 

Updated Jul 30, 2024
Version 2.0
  • Michiel_van_Heerde's avatar
    Michiel_van_Heerde
    Brass Contributor
    Aug 25, 2024

    Hi,

     

    Can we install this v2 version on Windows Server Core?

    The download delivers an .exe which is not a valid application for this OS platform, so it tells me.

  • patrickhees's avatar
    patrickhees
    Copper Contributor
    Aug 28, 2024

    Thanks Theo_Tran for this update.

     

    During my tests I came across a few errors in the preview:

    • If the new version is installed on a system where Windows Admin Center 2311 v1 is installed, the migration works without any problems. However, there are now entries for both versions of Windows Admin Center under "Installed apps".



      If the old version is now uninstalled, the binding for the certificate under "netsh http show sslcert" is lost. This means that the installation of the new version no longer works and the binding for the certificate must be set manually or the installation must be carried out again.

      The result of "netsh http show sslcert" before the uninstallation of the version v1:

       

      After the uninstallation:

       

    • Furthermore, the PowerShell module "Microsoft.WindowsAdminCenter.ConnectionTools" contains a few errors. Importing new shared connections fails if Windows Authentication is set up as the login, because the API key is always expected in the function "ApplyConnection".
      Variables are also named differently in the script, for example in the function "GetConnection":

     

    Function GetConnection {
    param(
        [Uri]
        $Endpoint,
        [System.Management.Automation.PSCredential]
        $Credentials,
        [string]
        $AccessKey
    )

    $params = @{
        Method          = "Get"
        useBasicParsing = $true
        userAgent       = "Scripts"
        uri             = [Uri]($Endpoint.ToString() + "api/connections")
    }

    # if there is no access token, it assumes it uses NTLM connection with Credentials or current user's context.
    $accessToken = CreateApplicationAccessToken -credentials $Credentials -accessKey $AccessKey
    if (-not [System.String]::IsNullOrEmpty($accessToken)) {
        $params.headers = @{ "application-acccess-token" = $accessToken; }
    }
    else {
        if ($Credential) {
            $params.credential = $Credential
        }
        else {
            $params.useDefaultCredentials = $true
        }
    }

    $response = Invoke-WebRequest @params
    if ($response.StatusCode -ne 200 ) {
        throw "Failed to get the connections"
    }

    $connections = ConvertFrom-Json $response.Content
    return $connections
}
​

     

    • I also wonder how the API key can be retrieved from outside if the form login is configured. The only option currently is to gather it manually via the "Access" setting in the Windows Admin Center, which prevents any automation.

     

  • MasterMorgan's avatar
    MasterMorgan
    Copper Contributor
    Nov 03, 2024

    Hi. Glad to finally see a new version of WAC v2!

    I use a custom certificate with WAC and that causes this error in the Application log and the WAC service terminates:

    Application: WindowsAdminCenter.exe
    CoreCLR Version: 8.0.1024.46610
    .NET Version: 8.0.10
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.InvalidOperationException: The requested certificate CN=servername.local could not be found in LocalMachine/My with AllowInvalid setting: False.

    If I use the self-signed certificate the error is not present.

     

    I figured out that what is causing the 'not found' error is that is it looking for the certificate without the X.500 prefix. Do the correct subject in the appsettings.json file should be just 'servername.local' and not 'CN=servername.local'. Once I made this change to my appsettings.json WAC started successfully with my custom certificate.