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

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.