DellEMC OpenManage Integration into Windows Admin Center not working

Mgamerz,

I would start with verifying the steps you have taken are the same as seen on the install guide found here, or manual found here.

Also, verify the following, as they are necessary for it to function properly.

Firewall in your enterprise environment enables communication through SMB port 445.
Redfish service is enabled on the target node.
An iDRAC user slot is available on the target node.
The target node is not booted to Lifecycle Controller.
The target node is not in the reboot state, or is powered off.
The USB NIC adapter is not disabled on the target node OS.
The lockdown mode is disabled on target node.

I would also recommend that you update the server to current as well.

Let me know 

I went through what was listed here, but the same issue persists.

WAC:

test from WAC server to virtual host:

PS C:\Users\redacted> test-netconnection redacted -port 445

ComputerName : redacted
RemoteAddress : redacted
RemotePort : 445
InterfaceAlias : Ethernet
SourceAddress : redacted
TcpTestSucceeded : True

iDRAC users list:

iDRAC USB NIC:

redfish:

USB NIC on virtual host:

Can't figure out why it won't show the idrac USB setting image. Here it is.

Hi,

This is Shiv from Dell EMC OpenManage Integration engineering team.

Additional to the above mentioned check, what is the PowerShell remoting policy in your node? is it set to "Remote-Signed"?

If setting the above policy does not help proceed with inventory retrieval, could you help us with the logs located in your target (managed) node at   \Temp\OMIMSWAC.

See this link to retrieve the logs

Sorry about the late response. Yes our powershell policy on all systems is set to remote signed. I do not have the permissions to change this setting, as we are a multi-tiered organization.

When you say managed system, I assume you mean the target server? I am on looking for C:\windows\temp\omimswac, but that directory does not exist on the target server. Given how fast the collection fails (it's almost as soon as the UI loads), I assume it did not actually install anything.

If you meant on the managing server, it does not look like that folder exists there either.

Thank you for the details.

Issue seems to be in

• Connecting to the target node operating system through the required ports and credentials or 
• IPMI driver (OMIMSWAC internally performs IPMI operations on target node) has issues.

I would recommend few more checks (mentioned below) to be done:

1. While connecting to the target node from Windows Admin Center, select "Manage As" and enter Operating System administrator credentials.
2. Check the 445 port configuration against the table mentioned here
3. Ensure the IPMI driver and service up and running. Refer details on issue identification and solution here.

If the above checks does not resolve the issue, could you share the below details to categorize the issue:

1. iDRAC firmware version.
2. Windows Admin Center version.
3. OpenManage Integration build number (specified in About screen of the Integration).
4. How many target nodes is the issue seen in?

This seems to be an issue with some sort of credentials and how Windows Admin Center passes credentials.

Our organization uses separated standard and administrative accounts. Standard accounts must log on using smart cards except in very special circumstances. Administrative accounts don't actually have passwords (that we know) and smart cards must be used for logon. Due to this, I have installed WAC on a VM that I remote into as an administrator, as doing a run-as doesn't really seem to work with WAC. WAC supports smart cards but it doesn't seem to work properly with how my organization set up their delegations (I am not a domain controller administrator so I don't know too much about that).

This does not seem to work with Dell OpenManage plugin. I can administer all of the servers just fine, make config changes, etc, but Dell OpenManage integration plugin fails immediately.

I have some service accounts I use that do password, but they have very specific documented usage. I tried one out for testing and it worked fine.

I am wondering if Windows is not passing an elevated credential through. I remember seeing something like [Elevated] a while ago when I had to update a plugin, but I don't see this anymore.

So it works... but I have to manually specify credentials I am not supposed to be using for this purpose. 

Thank you for details on issue identification and scenario.

Could you answer this query i have on the scenario ?

Has the "Smart Card Authentication" been enabled on both systems (system where Windows Admin Center is installed and target node)?

To work with OMIMSWAC we do recommend connecting to the target node with administrator credentials (with password) by using "Manage As" from Windows Admin Center.

Do help us with details on Smart Card, # of administrators (separate for WAC and for target node?) and any other that could help us build this case for offering in our integration.

It was working fine when my server started of as a stand alone server. Fresh Windows install. 

Once I setup my server as an Active Directory server, the EMC extensions in Windows Admin Center stopped working. 

All other checks mentioned in this article are good. 

Hi,

Could you help us with below details to understand this issue better.

• What is the failure message.
• Windows Admin Center and Dell EMC OpenManage extension versions
• Any error in logs @ C:\windows\temp\omimswac of target node
• iDRAC firmware version of the target node
• What is the authentication mode to connect to target node from Windows Admin Center (Note : Specifying credentials while connecting by choosing "Manage As" is Dell EMC recommended authentication method)

Also, here are a few checks that may help the extension get working,

1. Required ports (443) are enabled for Domain in firewall configuration - against the table mentioned here

2. While connecting to the target node from Windows Admin Center, select "Manage As" and specify target node Administrator credentials

3. PowerShell execution policy (on target node) of the user used to connect to target node is not Restricted

4. Ensure the IPMI driver and service up and running. Refer details on issue identification and solution here.

The link in #4 isn't working.

But I have the same problem.  Firewall is off on all interfaces, Execution policy is RemoteSigned, connecting as the local administrator account.  This is the second server in the last few weeks that we have had this problem, both brand new installs.

We would love to use the OMSA extension in WAC rather than go into iDRAC all the time but.....this does not seem to work properly out of the box.

Hi,

Curious about your mention of "OMSA". OpenManage integration with Windows Admin Center is independent of OMSA or works in-band.

To narrow down on the failure point, could you help us with below details,

• What is the failure message.
• Windows Admin Center and Dell EMC OpenManage integration versions (v1.0.1 just got released this week)
• Any error in logs @ C:\windows\temp\omimswac of target node
• iDRAC firmware version of the target node

Help if here if my understanding is wrong, issue occurred post addition of the target node to domain (was working when the target node was just part of WORKGROUP). With this specific information, could check if firewall outbound \ inbound rules are enabled for domain? refer image below :

On our system I found the error. It is that it is recommended for Hyper-Converged Cluster to deactivate the remote NDIS adapter in OS, but for Dell extension this interface is necessary, because it is the link to USB NIC. After activating this interface the Dell extension is able to display data in Windows Admin Center.

If you are on Server Core, then this may help:
$wmi = Get-WmiObject -Class Win32_NetworkAdapter -filter "Name LIKE '%Remote%'"
$wmi.enable()

Cheers
Werner 

I can't get this to work for us either.  There are no logs in C:\Windows\Temp\omimswac (the folder is not even being created).  I have checked all the steps like the others.  If its not getting to the point of creating the folder, where or what should I check?

If you did this command: $wmi = Get-WmiObject -Class Win32_NetworkAdapter -filter "Name LIKE '%Remote%'"

and the execute: $wmi

Is it empty? If no just execute $wmi.enable(), and test if you now can see the Remote NDIS Adapter with the command Get-NetAdapter

If it is empty, then you can try the following:

# Get InstanceID of NDIS Adapter
$hostname = 'YourServerName'
Get-PnpDevice -FriendlyName 'Remote NDIS Compatible Device' | fl *

# use the value found above for InstanceID and enable NDIS Adapter
$InstanceID = 'USB\VID_413C&PID_A102\7&6540616&0&3'

Enable-PnpDevice -InstanceId $InstanceID -CimSession $hostname -Verbose -Confirm:$False

# execute Get-NetAdapter to check if Remote NDIS Adapter is available now, without this adapter integration in Windows Admin Center does not work. If you want you can rename this adapter:
Get-NetAdapter | ? InterfaceDescription -Like 'Remote*' | Rename-NetAdapter -NewName NDIS

If you use the Integration with Hyper-V converged system do not forget to disable this network for Cluster usage and clear the checkbox for 'Live Migration' on properties of Network in Failover Cluster Manager.