If you are trying to install Dell OpenManage Server Administrator (OMSA) and you might see this alert / error:
The installer has detected that the HTTPS listener is not configured for Windows Remote Management. You can either configure the HTTPS listener before installing Remote Enablement, or install Remote Enablement now by selecting the “Custom” installation screen and configure the HTTPS listener later. See the “Remote Enablement Requirements” section in the Server Administrator Installation Guide for information on configuring the HTTPS listener. Note: Remote Enablement is required to manage this system from a remote Server Administrator Web Server and is applicable only for those systems that support Server Instrumentation. Click here to configure HTTPS Listener for Windows Remote Management.
All it means is that you will not be able to manage this server from a different server, but OMSA will function just fine locally.
If you want to manage that server from a different server, or you just don’t like the alert / error, it is pretty easy to correct:
- The server in question MUST be joined to a Domain to avoid this alert
- The server must be connected to the Domain during the install. If you have a Domain joined server connected only to the internet or not connected at all, you will see that error
- If the problem still exists, you likely need to force the install of WINRM using HTTPS
- Open a CMD prompt and type of copy/paste: (see THIS for more details)
winrm quickconfig -transport:https
- Open a CMD prompt and type of copy/paste: (see THIS for more details)
If you see an error relating to the certificate (quite likely) you simply need to request one, which is easy to do:
- Click START and type MMC.EXE
- Click FILE > ADD/REMOVE SNAP INS
- Double click CERTIFICATES and select COMPUTER ACCOUNT
- Click FINISH button (i.e. leave it on LOCAL COMPUTER)
- Click OK
- Expand CERTIFICATES
- Right click on PERSONAL > ALL TASKS > REQUEST NEW CERTIFICATE
- NEXT NEXT NEXT then Reboot
- Perform the OMSA install again and you will not see the WINDOWS REMOTE MANAGEMENT alert.
Be sure to select CUSTOM INSTALL and enable SERVER INSTRUMENTATION > MANAGEMENT INTERFACES > REMOTE ENABLEMENT
- Have a good day!
5 Comments
Justin Lockman · March 31, 2022 at 8:09 am
Hello, I’m stuck on step 8. I am running Server 2016 Essentials as a non-domain-joined Hyper-V host only (the actual 2016 Server Essentials that does AD, DC etc is running as a VM – don’t ask me why, I inherited this). After I Request New Certificate… all I get is the option “Configured by you” with a blue Add New link. I can’t just click next next next as your instructions say. How do I get past this? Thanks!
Ian Matthews · April 4, 2022 at 5:54 pm
Hi Justin;
I am sorry to say I no longer have access to a machine with Dell OpenManager. I hate to let you down, but I am hoping someone else reads this an knows the answer.
Franck · January 4, 2021 at 5:53 am
it doesn’t work
Ian Matthews · January 19, 2021 at 3:53 pm
Hi Franck;
It has worked for us at several sites in the past.
Alvin · October 13, 2021 at 9:57 pm
Confirmed that this works on an R830 system.
As clarification, the certificate generated must have a CN equal to that of the OMSA node’s hostname.