Troubleshoot Project Honolulu
Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 and Windows 10
This article describes common Honolulu configuration issues and how to fix them.
Clear your browser cache
After upgrading Honolulu from a previous version, you may sometimes need to clear your browser cache if you find that portions of the interface are not responding.
Delete data from previous install
If you have previously installed Honolulu on Windows Server (not Windows 10), you may need to delete the application data if the service fails to start, or if your connection list appears corrupted.
To remove the application data, delete the Server Management Experience folder under C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft
When installing Project Honolulu, you are given the option to let Honolulu manage the gateway’s TrustedHosts setting. This is required in a workgroup environment, or when using local administrator credentials in a domain. If you choose to forego this setting, you must configure TrustedHosts manually.
If you are installing on Windows 10 in a domain and using domain credentials to connect to the managed node, you do not need to modify TrustedHosts.
To modify TrustedHosts using PowerShell commands:
- Open an Administrator PowerShell session.
View your current TrustedHosts setting:
If the current setting of your TrustedHosts is not empty, the commands below will overwrite your setting. We recommend that you save the current setting to a text file with the following command so you can restore it if needed:
Get-Item WSMan:localhost\Client\TrustedHosts | Out-File C:\OldTrustedHosts.txt
Set TrustedHosts to the NetBIOS, IP, or FQDN of the machines you intend to manage:
Set-Item WSMan:localhost\Client\TrustedHosts -Value '192.168.1.1,server01.contoso.com,server02'
For an easy way to set all TrustedHosts at once, you can use a wildcard. Note though that including all hosts is less secure than setting them specifically.
Set-Item WSMan:\localhost\Client\TrustedHosts -Value '*'
When you are done testing, you can issue the following command from an elevated PowerShell session to clear your TrustedHosts setting:
If you had previously exported your settings, open the file, copy the values, and use this command:
Set-Item WSMan:localhost\Client\TrustedHosts -Value '<paste values from text file>'## Credentials ##
Make sure the credentials you are using are a member of the target server’s local administrators group. In some cases, WinRM also requires membership in the Remote Management Users group.
Are you connecting with a local user account?
When entering credentials in the server connection’s Manage As dialog box, you can use a local or domain account that is a member of the local administrators group on the target server. However, if you are using a local user account that is not the built-in administrator account, you will need to enable the policy on the target machine by running the following command in PowerShell or at a Command Prompt as Administrator on the target machine:
REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1
Are you connecting to a workgroup machine on a different subnet?
To connect to a workgroup machine that is not on the same subnet as the gateway, make sure the firewall port for WinRM (TCP 5985) allows inbound traffic on the target machine. You can run the following command in PowerShell or at a Command Prompt as Administrator on the target machine to create this firewall rule:
Set-NetFirewallRule -Name WINRM-HTTP-In-TCP-PUBLIC –RemoteAddress Any
Set-NetFirewallRule -Name WINRM-HTTP-In-TCP –RemoteAddress Any
Hyper-V PowerShell not installed
If you've successfully connected to the server, but receive error message:
The Hyper-V PowerShell feature is not installed on this server
Enable Hyper-V PowerShell features
- Click Roles and Features in the Tools menu.
In Roles and Features find Remote Server Administration Tools and check Role Administration Tools and Hyper-V Module for Windows PowerShell.