Unable to "launch virtual console" from OME console.

Hello thanks for choosing Dell.

We would like your OME and iDRAC version, please.

You can also provide us with your service tag by DM. https://www.dell.com/community/en/direct-messaging

Respectfully,

OME: 4.4.0 (Build 75)

iDRAC: 7.20.30.00

Hello, 
OME 4.4.0 and iDRAC 7.20.30.00 working fine.
We would like to add two things.
1. if popup is not getting blocked by the browser settings 
2. if possible can you remove and rediscover one of the nodes with local credentials instead of LDAP, maybe there are latency issues with authentication.

I logged in as the local admin, removed and re-discovered a device and the same issue remains.

I've been working with Firefox and tried testing with Chrome/Safari and now see this error in both other browsers.

Hello,

On the Knowledge Article Young posted recommends
it is necessary to reset the iDRAC and re-inventory in OpenManage Enterprise

https://www.dell.com/support/kbdoc/en-us/000215592/poweredge-unable-to-launch-the-virtual-console-through-ome-gui

Try adding "Collect Configuration Inventory" option and check results

1. Log in to OpenManage Enterprise: Access the console using your credentials.

2. Navigate to Jobs: Go to the "Jobs" section.

3. Create a New Job:

• Click on "Create Job".

• Select "Inventory" as the job type.

4. Configure the Job:

• Name the job appropriately.

• Set the schedule for when you want the inventory task to run.

5. Enable Configuration Inventory:

• In the job configuration settings, look for the option "Collect Configuration Inventory".

• Check the box to enable this option.

I've deleted two devices, logged into each of their iDRACs directly and initiated a reset by clicking "More Actions->Reboot iDRAC".

Then I went to Monitor->Jobs (the jobs section doesn't actually let you create/run jobs, it's only for viewing. see attached pic).

Hello,

Give this a try:

On the Devices > All Devices screen, select a group on the left pane and from Inventory drop-down menu (center of the screen), click Run Inventory on Group.

One of the options will be Collect configuration inventory.

Inventory wouldn't do much good without adding the devices back first. I went through Monitor->Discovery and added the two nodes back.

Once added back I ran the inventory, but the same issue remains.

Weirder still I've got a custom query group that only added one server back. Sure seems to be a very buggy and not well built app!

Hello,

It won't let you launch Virtual Console from OME.

Have you tried Clear browser cache you are using OME or a different browser and test

Also try Reboot one of the DRAC that won't launch the VC and try launch VC from OME and see how it does.

See what kind of behavior we see.

Yes, I've tried clearing the browser cache. As I'd previously mentioned (and a screenshot of the error was added) the same issue happens in Firefox/Chrome/Safari.

I'm not even sure you're reading any of my posts as this point as I've clearly stated that I've removed the devices from OME, rebooted iDRAC and then re-added them.

Hello, syousef_anl

1 The OME appliance FQDN/IP Address may need to be added to the browser pop-up blocker exclusion list
2 If a proxy server is configured in OME Network Settings, OME appliance FQDN/IP Address may need to be added to the Proxy Exclusion List

So, first part, I believe already been addressed, you can check the second one.
And if nothing helps, we'll need logs and remote session- for that you can open an official ticket through Contact Technical Support | Dell US
Your system is still in warranty. We have a dedicated team in US to support in your region.

Respectfully,

I've added the FQDN with a wildcard in the proxy exclusion list, but the issues persists. I'll go ahead and open a ticket.

@inam0099​ Direct iDRAC access works without issue in the same browser. Not sure where you configure "viewer type" in OME. Don't see any option to choose when logging in, nor any settings of such after logged in.

As for network, ping to the FQDN pass from OME and this is on a flat non-routed network so no firewalls or any other possible blockers. I've probably rediscovered these servers a hundred times trying to fix this issue. I've got a case opened with Dell and they're seeing the same issue in their labs, so it doesn't seem to be related to just our environment but rather a bug (and there're A LOT of them) with OME.