DellEMC OpenManage Integration into Windows Admin Center not working

Hi,

Logs not being created seems to be a connection issue, would suggest to look at the below checks

• Authentication : Credentials specified (by selecting Manage As) are appropriate.
• Port : Required firewall ports (inbound and outbound) are enabled.
• PowerShell execution policy in target node is not "Restricted"

Could also you share us the information on scenario?

• OMIMSWAC and WAC versions
• Error message for failure.
• Server connection or cluster connection?

I've checked the firewall, we keep SMB open in the local LAN already.  
Here is the execution policy:

Scope ExecutionPolicy
----- ---------------
MachinePolicy RemoteSigned
UserPolicy RemoteSigned
Process Undefined
CurrentUser Undefined
LocalMachine RemoteSigned

OMIMSWAC is 1.0.1 and WAC is 1910.  Error message is (I subbed out the servername) "Unable to communicate to target node . The possible reasons for failure are: 1. Target node is currently being rebooted, or is powered-off. 2. Firewall is blocking communication through SMB port 445." 

This is just a server connection.  I did notice that it creates a "C:\temp\sme\dell-emc.openmanage-integration.1.0.1\node" folder path on the server I'm trying to manage with some files inside said directory:

installNode.ps1 (PowerShell script that just has Write-Host "Install Node" inside with a commented out SIG block), libcmtbmcapi.dll & WAC-C.exe.

I looked at WAC-C.exe and was able to get a log file using "wac-c.exe --logfile text.log -v -c" from an admin command prompt.  The item that stuck out in the log file was "[[2019-11-10T16:07:57] ][Information][15684]: [104]: ProcHandler-GetString:: Failed to fetch S key with error message [Get size of string value failed.] as errorcode - 2."  

I hope this info helps.

The first command returns nothing.  The second does not work as this is a Server 2012 R2 server.  This is also a physical machine.

Yes, it looks like it:

ServiceName : usbrndis6
MACAddress : 90:B1:1C:00:A4:08
AdapterType : Ethernet 802.3
DeviceID : 3
Name : Remote NDIS Compatible Device
NetworkAddresses :
Speed : 0

and if you use Get-Netadapter it shows up also and is 'up' ?

Yes (Sorry for the bad formatting):

Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
---- -------------------- ------- ------ ---------- ---------
Ethernet Remote NDIS Compatible Device 9 Up 90-B1-1C-00-A4-08 0 bps
NIC2 Broadcom NetXtreme Gigabit Ethernet 3 Not Present 90-B1-1C-00-A4-06 0 bps
NIC1 Broadcom NetXtreme Gigabit Ethernet #2 5 Up 90-B1-1C-00-A4-05 1 Gbps

Then from my perspective it should work, at least that is what I see here on our Windows Server 2019 systems. Maybe (but I do not know for sure) you should at least have Windows Server 2016? So I can not help in this case further and Dell Support should take over again.

Is there a specific number?

FYI My issue ended up being the smartcards as well.

If you login with a smartcard, for some reason, the Dell plugin cannot pass along the credentials properly.  I changed the "Manage as" option to a different domain account that was an administrator on the server and it started working.

Thank you for your response and confirmation.

Dell Open Manage Integration for windows Admin center has some specific things required. The OMIMSWAC is supported with an azure stack HCI cluster and Dell contract for Ax nodes and server 2019, HCI os *22h2 or server 2022 clusters. 

below are the top issues you are likely to see, along with their corrections:

Basic Troubleshooting for Windows Admin Center with OpenManage Integration for Microsoft Windows Admin Center | Dell US

In addition, the USB nic should not be manually touched inside windows. If there had been significant changes, follow this general path to reset those USB NICs - Once done, use the idrac connectivity tab and change the "OS to Idrac Passthrough" Redfish IP - they should be set unique within a cluster. they should also have a distance of 10 or so in the last octet. This change will change the USB nic IP to be one larger then what is entered. IE 169.254.1.10 set as the redfis ip will make 169.254.1.11 as the usb nic- 11 shoudl be able to ping 10. 

Steps. 

1. Get-service -name "idrac service module" - remove if installed (not needed for omimswac)

2. once removed disable usb nic in the idrac (redfish disable) Restart server 

3. re-enable redfish and set the USB nic to a unique vaule in the cluster using idrac os to idrac passthrough tab in idrac. 

4. do this for alll node- folllow the link above and fix any of the 12 isssues. 

When this is all done - omimswac should work up to and including compliance. 

#iwork4dell.

* 22h2 will change as the new version is released. stay current if you have azure stack HCI per guidelines 

Hello Team, 

Things are changing for WAC. Windows Admin center has 2311 out with two minor updates which include use of Angular 15. It's much nicer and makes messages much nicer and less difficult to read. 

Clearing the WAC machine Cache for OMIMSWAC is very likely needed after updates. Clear the %temp% folder and the %appdata% Microsoft Edge User Data Folder. - > Restart the WAC service. 

To check your inventory works directly, you can go to your problem node and do the following: 

Get-PCSVDevice | fl 

Find your server Idrac IP address 

Put this in the browser of your Windows admin center machine.

https://idracIPADDRESS/redfish/v1/Dell/hwinv.xml

Keep the file and open with notepad. This is your inventory contents. IF you get a file, this proves the basics are able to work. 

You should be able to go back to you Open Manage extension (Omimswac) and see the inventory and compliance work well.

#Iwork4Dell Louis