Do you need a powerful browser-based management tool (not monitor only)? Microsoft Project Honolulu is your right choice.
It can full control server infrastructure, allow you to manage them from anywhere with Microsoft Edge or Google Chrome. Let’s follow step by step to deploy it.
The Project Honolulu is still on technical preview (but coming soon!), here are its current capabilities:
- Displaying resources and resource utilization
- Certificate Management
- Event Viewer
- File Explorer
- Firewall Management
- Configuring Local Users and Groups
- Network Settings
- Viewing/Ending Processes and Creating Process Dumps
- Registry Editing
- Managing Windows Services
- Enabling/Disabling Roles & Features
- Managing Hyper-V VMs & Virtual Switches
- Managing Storage
- Managing Windows Update
There are 3 options to deployment Microsoft Project Honolulu as follow:
I am going to use option 2 to deployment Microsoft Project Honolulu. Project Honolulu requires PowerShell features that are not included in windows 2012 and 2012 R2 server, you need to follow steps to install it if you are using windows 2012 and windows 2012 R2 as a Project Honolulu Gateway or managed node
- Download and install WMF 5.1 for Project Honolulu Gateway or managed node (reboot server needed).
2. Register and download Project Honolulu software from follow link:
3. Logon to Gateway Server.
4. Open PowerShell and run follow cmdlet to make sure the Windows Management Framework 5 or higher loaded.
5. Double click HonoluluTechnicalPreview1709-20016.msi.
6. Select I accept the terms in the License Agreement and then click Next.
7. Select Allow Project “Honolulu” to modify this machines’s trusted hosts settings and Create a desktop shortcut to launch Project “Honolulu” then click Next.
8. On the Configure Gateway Endpoint page, type port number and then click Install.
9. Click Yes on the User Account Control prompt.
10. Click Finish after install completed and you will see a Project ‘Honolulu’ icon on the desktop.
11. Double click Project ‘Honolulu’ icon and enter the user name and password.
12. Because Project ‘Honolulu’ doesn’t support IE so It will show Unfortunately, Project ‘Honolulu’ doesn’t support this browser error message.
13. You need to open the url https://GATEWAY SERVER’s FQDN:management port number to open Project ‘Honolulu’ management web interface.
14. The Welcome to Project Honolulu page will pop up, click Next.
15. On the Help us build the future of Management page, click Finish.
16. You will see the gateway server be added already.
17. Click +ADD from web management Interface to add new connection.
18. Select Add Server Connection on Add Connection page.
19. Enter the server name and it will found the FQDN name automatically and then click Submit (you also can select import servers to import all of servers from txt file).
20. You can repeat the steps to Add Failover Cluster Connection and Add Hyper-Converged Cluster Connection.
21. Click server name which you would like to manage and you will see the detail monitor items and management tools that you can use to change the settings for the server.
Hope you enjoy this post!!
Cary Sun @SifuSun
I done by installation of Honolulu, when I am trying to add server it show me this error:
on my server and my client WMF 5.1 installed all ready
Connecting to remote server (ServerName) failed with the following error message : WinRM cannot process the request. The following error with error code 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated.
This can occur if the provided credentials are not valid on the target server, or if the server identity could not be verified. If you trust the server identity, add the server name to the TrustedHosts list, and then retry the request. Use winrm.cmd to view or edit the TrustedHosts list. Note that computers in the TrustedHosts list might not be authenticated. For more information about how to edit the TrustedHosts list, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.