Start a Conversation

Unsolved

D

1 Rookie

 • 

66 Posts

1725

November 12th, 2020 10:00

Openmanage integration with Windows Admin Center

I've just set up Windows Admin Center. Most of my machines are VMs, but I have two physical servers running Windows - an R710 running Hyper-V Server 2016, and a T430 running Server 2012 R2 Standard. I have followed the prerequisites instructions for both these OSs on the WIndows Admin Center setup guide:

https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/deploy/prepare-environment

In both cases, I get the following error when I go to the Openmanage Integration section for the machine in Admin Center, and click the inventory button:

Unable to communicate to target node xxxxxxx.xxxx.xxx . 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.

I suspect that the R710 might be too old (it's not listed in the supportability matrix), but I would expect the T430 to work. I've tried putting in a firewall rule on the machine to allow port 445, and even temporarily disabling the firewall, but neither made any difference.

Anyone got any suggestions?

Thanks

4 Operator

 • 

2.9K Posts

November 12th, 2020 14:00

Hello,

 

That process does the following things:

1) Initiates Remote Powershell using the ManagedAs account

2) Creates an Inventory log file

  • C:\Windows\Temp\OMIMSWAC\InventoryXXXX.log

           3) Runs a set of API calls to the iDRAC USB NIC and saves them to the log

4) Exports lgog via SMB port 445

 

Since it seems like the firewall isn’t a factor, then I'd check the following:

    1) ManagedAs Account permissions

    2) permissions to write to c:\windows\temp

    3) iDRAC OS-BMC Passthrough is enabled and set to USB

1 Rookie

 • 

66 Posts

November 13th, 2020 03:00

Thanks. I am using a domain admin account, so points 1 and 2 shouldn't be the problem.

As regards point 3, I've just checked and no, it wasn't enabled. If I enable it, it needs an IP address entering. What should this be? The documentation isn't very clear.

Thanks

4 Operator

 • 

2.9K Posts

November 19th, 2020 08:00

Sorry, I didn't see this message. Is there any chance you might be able to upload an image of what you're seeing? This software product isn't wat I'm best at, so the image may give some helpful context.

1 Rookie

 • 

66 Posts

November 19th, 2020 08:00

Do you mean in the iDRAC? This is what I see there:

idrac.JPG

The IP address field is populated with the default - I've not changed this, and it's not an address we use on our internal network.

Thanks

 

4 Operator

 • 

2.9K Posts

November 19th, 2020 14:00

The IP you're looking at is the default IP it should be loaded with. Looking over the documentation, it's leading me to believe that you may not need to make any changes. I have a colleague that knows this software much better than I do, if you can wait, I'd like to run this passed him when we return after the weekend.

Moderator

 • 

9.4K Posts

November 23rd, 2020 08:00

Generally speaking you need it to be an APIPA address that can talk to the iDRAC. The iDRAC uses a 169 IP Address and the USB NIC has to talk to it and you can’t change the iDRAC internal IP for that.

1 Rookie

 • 

66 Posts

November 23rd, 2020 09:00

Thanks. Looks like the IP it's using is OK then - any idea what the issue might be?

Moderator

 • 

9.4K Posts

November 23rd, 2020 10:00

Have you tried the steps on page 8 here?

 

Let me know.

1 Rookie

 • 

66 Posts

November 25th, 2020 10:00

Yes, I have.


Thanks

No Events found!

Top