OMSA on Hyper-V Server 2016 - Prerequisite Checker

Hi,

Would you be able to give a try on OMSA 9.3, and also, could you check if all firmware on the server has been updated? 

By the way, when you run the prerequisite check, does it have a return code?

I tried 9.3, same result.  PreReqChecker finishes instantly, no visible return.  This time, it didn't even make any registry entries (before all it did was a SYSTEMID and VENDOR in the OpenManage key).  Can't find anything in the Temp folder, so no return code I can find.  When I went to run the SysMgmtx64, it still says that the PreReq checker hadn't been run.

Hey Nathaniel, just as a matter of quick clarification, are we talking about the standalone Hyper-V Server 2016? If not that's fine, but I want to make sure that we're not making incorrect assumptions on the OS.

Correct:  Hyper-V Server 2016 (basically Windows Server Core, the one with two command line shells for the entire interface)

Well, weird. Very helpful statement, I know.

I'm downloading the .ISO now, I'm going to deploy an instance myself and see what happens. Based on my understanding of what you're doing - I think you're doing exactly what you're supposed to. I'll see if I can make any progress and share it with you and Joey, if I do.

Hi,

Dylan had a feedback to me on his finding before left for work. Are you doing the installation in an upgrade version or a new installation of OMSA? If an older OMSA is installed, could you uninstall it and install an either 9.3 or 9.4. Let us know the outcome. 

These are clean installs. I've never had OMSA installed on these systems before.

Give this syntax a shot and see if it works for you:

It appears to have installed; the folder and services are there.  However, when I try to connect to the webpage, it times out.

Digging into the Program Files\Dell\Sysmgt folder, and comparing it to a near-identical blade running full Windows Server 2016, it appears the install may not have done everything.  For example, in that SysMgt folder, the OM.ico and OMAStart.exe are both missing (but the OMIver.db file is there).

msiexec /i SysMgmtx64.msi /qn /L*v omsainstall.log

You might need to run an uninstall first. At any rate, this will hopefully generate a log we can use to figure out the problem.

I have the log, but it's 15MB, 35,000 lines.  How do I get it to you?

Our company rules forbid posting documents to public filedrop sites, so I can't just drop it on a sharing site or any such.

I'm going to be out of the office next week, so I'll ask you to email it to Joey and I both. Let me PM you.

Upon reviewing the log, would you confirm if port 1311 is blocked with the default firewall enabled in Hyper-V Core (since installing OMSA will not open that).

Let me know what you see.

That seems to have done the trick.  The firewall was supposed to have been disabled by group policy, but that got missed somehow.

Thank you!