Dell OMSA Install Issues

I'm trying to install Dell OMSA on Server 2016 but it keeps giving me errors.  I'm following the guide here, http://www.dell.com/support/article/us/en/04/how10613/how-to-install-openmanage-server-administrator-omsa-on-vmware-to-collect-logs?lang=en, and installed the 6.0 vib files.
Next I go to install the x64bit OMSA version on server 2016 and it keeps complaining about the https listener.  I've tried doing so many different things but nothing will work to clear this error.  If I continue with the install and do custom, once its complete, it doesn't launch the web version.
LVL 1
cmb991Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wayne88Commented:
I have encountered this before and can't remember what I did.  However, have a look at this:

https://www.urtech.ca/2018/02/solved-dell-openmanage-server-administrator-install-alert-https-listener-not-configured-windows-remote-management/

Also, can you try running the install by right clicking the install file and run as administrator (even if you are already logged in as admin)?
0
cmb991Author Commented:
Tried this already, it didn't change anything.
0
Wayne88Commented:
Any chance of posting the screenshot to capture exact moment of installation failure and message?
0
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

cmb991Author Commented:
This is all it shows.  The install goes through but the web doesn't load.
Screen-Shot-2018-05-04-at-9.50.38-PM.png
0
Wayne88Commented:
Can you confirm that you tried running the installer by right clicking and run as administrator?  Can you also post the error you get when you run the OMSA?

Btw, if you didn't use any SSL certificate you will normally get a message on the browser stating that the connection is untrusted preventing you to proceed.  Depending on the browser you will have to manually proceed.  Sometimes this step is not that obvious (as in Chrome) and looked like you failed to connect.
0
cmb991Author Commented:
It just doesn’t load anything.  It’s not an ssl error.
0
Wayne88Commented:
Did you speficy the port number to use for the connection?  Try opening a browser on the server where OMSA is installed then type https://localhost:1311 as the URL

Anything comes up?
0
cmb991Author Commented:
Tried that.  Nothing comes up.  Page not found.
0
Wayne88Commented:
Ok, let's try another thing.  Then let's test it without using HTTPS since that's what giving you the problem.  Try using just HTTP and type http://localhost:1311 

Any luck?

Failing that then have you tried installing the WRM and configuring the inbound firewall rule?

https://www.petri.com/configure-windows-remote-management-https-listener
0
arnoldCommented:
Try different browsers.
Check whether i.e. enhanced security is what causes this issue.

Is this a core install or ...
Which Dell system and which version?
0
arnoldCommented:
Just re-read your question, you are asking about installing on sa on Windows server 2016, but the reference you include point to a VMware environment.

The VM does not have access to HW of the host...
0
cmb991Author Commented:
SA connects to the servers hosting esxi.
That isn't the issue.  The issue is something to do with the certificate/ssl/winrm which i'm trying to figure out.  The dependency in the screenshot needs to be cleared first and then it'll work.  The problem is getting it cleared.
0
Wayne88Commented:
Have you tried using just HTTP and type http://localhost:1311 to see if it's reachable?
0
cmb991Author Commented:
Wayne88 - Yes already tried that.
0
arnoldCommented:
Look at the reference, potentially the issue is that the default certificate is not-trusted, potentially adding either the self signed cert as trusted, or on the host, use an internally trusted ca to sign the certificate Omsa uses.

Double check the VMware Omsa components.....are set for remore.  The other possibility is that the item needing configuration dealing with idrac.....
0
cmb991Author Commented:
arnold - No cert was created with this.  Any guides on it?  All I have is a single cert in certs > personal > certs.  We have a CA and its domain joined.
0
Wayne88Commented:
Hmmm, I am running out of ideas and I know I came across the same thing years ago but can't remember the fix.  I will let you know if anything comes to mind.
0
arnoldCommented:
Within the idrac /remote access, there is an option to allow remote management.

Check whether you can access the idrac remotely ........
0
cmb991Author Commented:
I'm trying the latest version now.  I just installed the VIBs to esxi, and will be install OMSA after.  I will report back.  http://www.dell.com/support/contents/us/en/04/article/product-support/self-support-knowledgebase/enterprise-resource-center/systemsmanagement/omsa
0
arnoldCommented:
The issue is with the idrac config, during bootup, see what the idrac settings/configurations are and make sure remore management via idrac is enabled.

The default ip is usually 192.168.0.120, might need to be set during bootup.....
0
cmb991Author Commented:
iDrac is configured already.
0
cmb991Author Commented:
This is now the error I'm getting "The installer has detected correct version of Windows Remote Management. Use the "Custom" installation later during the installation to select this feature. 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. "
Screen-Shot-2018-05-11-at-11.51.49-P.png
0
arnoldCommented:
If memory erves this is informational warning dealing with whether you want https://servername:1311 to be accessible.
THe warning if followed wlll deal with the setup of a certificate, the default will be self-signed which which generate warnings on the client attempting access..
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.