Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell OpenManage Integration with Microsoft Windows Admin Center Version 3.0 User’s Guide

PDF

Prerequisites check details

Use prerequisite checks to verify if the extension meets the requirements for monitoring and management operations.

Prerequisite checks for inventory

When the extension loads or before retrieving the inventory, the following prerequisites are checked.
NOTE: As part of "integrated deploy and update" and "full-stack update" of Azure stack HCI clusters using OpenManage Integration snap-in, the same inventory prerequisites are checked.
Prerequisites check name Category (Manual or Auto fix) Applies to (Gateway OS/Node OS/iDRAC) Recommendation
Proxy is configured Auto fix Target node OS If node has network proxy configured, click Resolve to add the Remote NDIS network adapter IP (169.254.* series IPs) of that node to the proxy exclusion list. These IPs are used to communicate with iDRAC.
NOTE: If this issue is not resolved, check if the Proxy in the Network and Internet settings page on the iDRAC OS or server OS of that node is open. If it is open, close the page and try to resolve the issue again.
Redfish is enabled Auto fix iDRAC If Redfish is disabled, click Resolve to enable the Redfish service in the iDRAC of the target node. Redfish is used to retrieve target node inventory.
Remote NDIS adapter is enabled Auto fix Target node OS If remote NDIS adapter is disabled, click Resolve to enable the adapter as it is used to communicate with iDRAC.
Lockdown is disabled Auto fix iDRAC (Applicable to iDRACs with firmware version lower than 4.40) If infrastructure lock is enabled, click Resolve to unlock the infrastructure.
OS-iDRAC passthrough IPs are unique across cluster nodes Manual fix Target node OS Each cluster node host OS should have a unique remote NDIS network adapter IPV4 IP. Otherwise, this may cause IP-conflict for the cluster.
NOTE: Change OS to iDRAC passthrough IP address only from iDRAC. After the IP is changed on iDRAC, Remote NDIS network adapter IP on host OS is automatically set.
OS-iDRAC passthrough IPs are unique across OS and iDRAC Manual fix iDRAC The remote NDIS network adapter IP in host OS and OS to iDRAC passthrough IP in iDRAC should be different in a node. Otherwise, it can cause failure in inventory retrieval.
NOTE: Change OS to iDRAC passthrough IP address only from iDRAC. After the IP is changed on iDRAC, Remote NDIS network adapter IP on host OS is automatically set.
SMB 445 Port is enabled Manual fix Target node OS On the target node, enable File and Printer Sharing (SMB-In) from the Windows Admin Center Firewall tool. OpenManage Integration extension uses SMB port 445 to copy files to the target node.
iDRAC has one empty slot Manual fix iDRAC (Applicable to iDRACs with firmware version lower than 4.40) Ensure one empty slot is available on iDRAC. If all slots are full in iDRAC8, run the RACADM command to create one empty slot. Refer Integrated Dell Remote Access Controller 9 RACADM CLI Guide.
Execution Policy is configured Manual fix Gateway OS, Node OS Ensure that the PowerShell execution policy on the target node and gateway is not set as "Restricted". When the policy is restricted, it can prevent the execution of necessary PowerShell scripts to manage the node.
Node is up and reachable Manual fix Target node OS Ensure the node is powered on and reachable from the Windows Admin Center gateway.
Remote NDIS adapter IPV4 is enabled Manual fix Target node OS Enable IPv4 on host OS in "Remote NDIS Compatible Device" from network settings.
OS-iDRAC passthrough IP should be 169.254.0.1 Manual fix iDRAC8 and below, Recommended to change that to '169.254.0.1'
IPMI driver is running Manual fix Target node OS Install or enable the IPMI driver. For more information, see https://www.dell.com/support/kbdoc/en-in/000150763/dell-emc-openmanage-integration-with-microsoft-windows-admin-center-omimswac-fails-to-query-host-information
Powershell remoting is enabled Manual fix Target node OS Enable PowerShell remoting and then set the firewall rules as per Microsoft recommendations. For more information, see https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_requirements?view=powershell-5.1#windows-network-locations
Smb Share is enabled Manual fix Target node OS Enable or add administrative share. For more information, see https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/problems-administrative-shares-missing
User Access Control (UAC) is disabled Manual fix Target node OS If UAC is enabled, ensure to disable the UAC. For more information, see https://docs.microsoft.com/en-us/troubleshoot/windows-server/windows-security/user-account-control-and-remote-restriction

Prerequisites check for generating server/cluster hardware compliance, HCP compliance, and Cluster Recommendation report

In the Check Hardware Compliance page, after you select the appropriate catalog and click Check Compliance, OpenManage Integration checks the below prerequisite along with inventory prerequisites before generating the hardware compliance report.

Prerequisites check name Category (Manual or Auto fix) Applies to (Gateway OS/Node OS/iDRAC) Recommendation
Max envelope size is configured Auto fix Target node OS Click Resolve to configure the 'MaxEnvelopeSizeKb' registry value to 8192 KB. This is required to copy required files from Windows Admin Center gateway to the target node.

If the value is set below 8192 KB, compliance generation may fail.

Prerequisites check for server update

During server update using OpenManage Integration extension, following prerequisites are checked along with inventory prerequisites.

Prerequisites check name Category (Manual or Auto fix) Applies to (Gateway OS/Node OS/iDRAC) Recommendation
No pending job in iDRAC Manual fix iDRAC Reboot the node or clear the pending job from the node iDRAC. This is required by the extension for configuring BIOS or using Server Configuration Profile of iDRAC.
Access Windows Admin Center locally Manual fix Gateway OS (Not applicable to Windows 10 OS) Use a browser to access the Windows Admin Center remotely.

Prerequisites check for cluster update (CAU), HCP compliance (Fix compliance), Cluster recommendation (Apply recommendation), Secured Core, and CPU Core operations

Before triggering any update operations, OpenManage Integration checks the below prerequisites along with inventory prerequisites.

Prerequisites check name Category (Manual or Auto fix) Applicable for CAU or Configure operation Applies to (Gateway OS/Cluster/iDRAC) Recommendation
No pending job in iDRAC Manual fix CAU, Configure iDRAC Reboot the node or clear the pending job from the node iDRAC. This is required by the extension for configuring BIOS or using Server Configuration Profile of iDRAC.
Disks are healthy Manual fix CAU, Configure (Applicable only for HCI clusters) Cluster Before CAU or configure operation, verify that the disks are in a healthy state. If disks are in maintenance mode, wait for the disks to become healthy. To take disks out of maintenance mode manually, see https://docs.microsoft.com/en-us/azure-stack/hci/manage/maintain-servers
Cluster node is healthy Auto fix CAU, Configure Cluster If cluster nodes are not healthy, click Resolve to bring the cluster nodes to healthy state.
No pending storage jobs Manual fix CAU, Configure (Applicable only for HCI clusters) Cluster Before CAU or configure operation, verify that no storage job is pending in the target node OS. If any job is pending, wait until the job is complete. For more information, see https://docs.microsoft.com/en-us/azure-stack/hci/manage/maintain-servers#wait-for-storage-to-resync-1
CredSSP is configured Auto fix CAU, Configure Gateway OS, Node OS If CredSSP is disabled, click Resolve to enable the CredSSP on gateway and target node. This is required to run cluster aware update from the extension. See Microsoft documentation to enable CredSSP.
Remote shutdown is enabled Manual fix CAU, Configure Target node OS Enable the remote shutdown firewall rule. This is required to manage node restart during cluster update operations. For more information, see https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-aware-updating-requirements#BKMK_FW
CAU role permissions are set Manual fix CAU, Configure Cluster Verify that the cluster has sufficient permission to create or add CAU clustered role. However, because of the security policies in certain organizations, it may be necessary to prestage the object in Active Directory. For a procedure to do this, see https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731002(v=ws.10)#steps-for-prestaging-the-cluster-name-account

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\