*note this is hackish*
In my case also the browser was never opening but the Java process was spawning in the background. I wrote a powershell script to workaround the issue and happen to trying chrome and it worked.
$OnCommandPath = 'C:\Program Files\NetApp\OnCommand System Manager\';
Start-Process "$($OnCommandPath)SystemManager.exe"
while (!(Test-Path "$($OnCommandPath)SystemManagerLaunchURL.txt")){
Start-Sleep -s 1
}
Start-Process 'chrome.exe' (Get-Content "$($OnCommandPath)SystemManagerLaunchURL.txt")
I wrote this to file called Start-OnCommand.ps1 and then created a shortcut to call the file as follows:
powershell .\Start-OnCommand.ps1
/begin edit/
Make sure the shortcut start location is the same directory as your script file location. I actually edited the default OnCommand Shortcut and placed the file in C:\Program Files\NetApp\OnCommand System Manager\ which was my install path.
If you heavily customize your powershell environment you might add -noprofile to the execution command to speed it up as well.
I also run with elevated rights, though I think you can just change the directory security on C:\Program Files\NetApp\OnCommand System Manager\ to negate this requirement.
/end edit/
Somewhat hackish as I said but it works. You could of course use IE or FireFox (or anything else if it works) if that is your preference. Make sure you update the $OnCommandPath to match your install location.
Message was edited by: Michael Thomas
