Launch Windows Admin Center
Applies To: Windows Admin Center, Windows Admin Center Preview
Selecting a client certificate
The first time you open Windows Admin Center on Windows 10, make sure to select the Windows Admin Center Client certificate (otherwise you'll get an HTTP 403 error saying "can't get to this page").
In Microsoft Edge, when you are prompted with this dialog:
Click More choices
Select the certificate labeled Windows Admin Center Client and click OK
Make sure Always Allow Access is selected and click Allow
Connecting to managed nodes and clusters
After you have completed the installation of Windows Admin Center, you can add servers or clusters to manage from the main overview page.
Add a single server or a cluster as a managed node
Click + Add under All Connections.
Choose to add a Server, Failover Cluster or Hyper-Converged Cluster connection:
Type the name of the server or cluster to manage and click Submit. The server or cluster will be added to your connection list on the overview page.
-- OR --
Bulk import multiple servers
On the Add Server Connection page, choose the Import Servers tab.
Click Browse and select a text file that contains a comma, or new line separated, list of FQDNs for the servers you want to add.
Authenticate with the managed node
Windows Admin Center supports several mechanisms for authenticating with a managed node. Single sign-on is the default.
You can use your current Windows credentials to authenticate with the managed node. This is the default, and Windows Admin Center attempts the sign-on when you add a server.
Single sign-on when deployed as a Service on Windows Server
If you have installed Windows Admin Center on Windows Server, additional configuration is required for single sign-on. Configure your environment for delegation
-- OR --
Use Manage As to Specify credentials
Under All Connections, select a server from the list and choose Manage As to specify the credentials that you will use to authenticate to the managed node:
If Windows Admin Center is running in service mode on Windows Server, but you do not have Kerberos delegation configured, you must re-enter your Windows credentials:
You may apply the credentials to all connections, which will cache them for that specific browser session. If you reload your browser, you must re-enter your Manage As credentials.
Local Administrator Password Solution (LAPS)
Using tags to organize your connections
You can use tags to identify and filter related servers in your connection list. This allows you to see a subset of your servers in the connection list. This is especially useful if you have many connections.
- Select a server or multiple servers in the All Connections list
- Under All Connections, click Edit Tags
The Edit Connection Tags pane allows you to modify, add, or remove tags from your selected connection(s):
To add a new tag to your selected connection(s), select Add tag and enter the tag name you would like to use.
To tag the selected connections with an existing tag name, check the box next to the tag name you wish to apply.
To remove a tag from all selected connections, uncheck the box next to the tag you wish to remove.
If a tag is applied to a subset of the selected connections, the check box is shown in an intermediate state. You can click the box to check it and apply the tag to all selected connections, or click again to uncheck it and remove the tag from all selected connections.
Filter connections by tag
Once tags have been added to one or more server connections, you can view the tags on the connection list, and filter the connection list by tags.
- To filter by a tag, enter the tag in the filter text box. Entries appearing in the Server Connection list will be filtered to include that tag.
View PowerShell scripts used in Windows Admin Center
Once you've connected to a server, cluster, or PC, you can look at the PowerShell scripts that power the UI actions available in Windows Admin Center. From within a tool, click the PowerShell icon in the top application bar. Select a command of interest from the dropdown to navigate to the corresponding PowerShell script.