Transcription
Dell EMC OpenManage Enterprise Version 3.0User's Guide
Notes, cautions, and warningsNOTE: A NOTE indicates important information that helps you make better use of your product.CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid theproblem.WARNING: A WARNING indicates a potential for property damage, personal injury, or death. 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.Other trademarks may be trademarks of their respective owners.2018 - 09Rev. A01
1About Dell EMC OpenManage EnterpriseOpenManage Enterprise is a systems management and monitoring application that provides a comprehensive view of the Dell EMCservers, chassis, storage, and network switches on the enterprise network. With OpenManage Enterprise, a web-based and one‑to‑manysystems management application, you can: Discover and manage devices in a data center environment.Create and manage OpenManage Enterprise users.Group and manage devices.Monitor the health of your devices.Manage device firmware versions and perform system updates and remote tasks.Create and deploy device configuration templates.Create and assign identity pools, and perform stateless deployment on target devices.Create configuration compliance baselines and remediate devicesView and manage system alerts and alert policies.View hardware inventory and compliance reports.Monitor and report about warranty and licenses.NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on thesupport site.Some of the security features of OpenManage Enterprise are: Role-based access that limits access to console settings and device actions.Hardened appliance with Security-Enhanced Linux (SELinux) and an internal firewall.Encryption of sensitive data in an internal database.Use of encrypted communication outside the appliance (HTTPs).Create and enforce firmware and configuration-related policies.Provision for configuring and updating the bare-metal servers.OpenManage Enterprise has a domain-task-based GUI, where the navigation is designed by considering the sequence of tasks that arepredominately used by an administrator and device manager. When you add a device to an environment, OpenManage Enterpriseautomatically detects the device properties, places it under relevant device group, and enables you to manage the device. The typicalsequence of tasks performed by OpenManage Enterprise users: Deploying and managing OpenManage EnterpriseConfigure OpenManage Enterprise by using Text User InterfaceDiscovering devices for monitoring or managementManaging All DevicesMonitoring devices by using the OpenManage Enterprise dashboardOrganize devices into groupsManage the device firmwareViewing and configuring devicesMonitoring device alertsView archived alertsView device warranty informationManage device configuration templatesManage the device configuration compliance baselineMonitor device compliance with compliance templatesManage audit logsManaging OpenManage Enterprise appliance settingsRun an inventory job nowManage the device warrantyReportsManaging MIB filesRole-based OpenManage Enterprise user privilegesAbout Dell EMC OpenManage Enterprise3
Directory services integration in OpenManage EnterpriseTopics: New in this releaseOpenManage Enterprise—Server Configuration Management LicenseNew in this release You can now edit the deployment template attributes by using: Guided view Advanced viewSupport for discovery and inventory of MX7000 chassis—as a standalone chassis and as a lead chassis in a Multi-ChassisManagement (MCM) group.Support for configuration compliance and remediation of MX7000 chassis.Ability to assign virtual identities to servers and perform stateless deployment, and support for VLAN management.Ability to monitor devices and remediate tasks in Dell EMC OpenManage Mobile by integrating with OpenManage Enterprise.Dell EMC Repository Manager can generate firmware catalogs from the OpenManage Enterprise inventory.Support for the following devices: Latest 14th generation PowerEdge servers including the new blade servers of MX7000 chassis PowerEdge FD332 storage module Dell Compellent FS8600 storage deviceSupport of alert policies for devices not discovered in OpenManage Enterprise.Support of additional remote tokens for remote script execution.REST API services for network configuration, identity pool creation, device template configuration, and profile management. OpenManage Enterprise—Server ConfigurationManagement LicenseNOTE: Installing and using OpenManage Enterprise does not require the OpenManage Enterprise — ServerConfiguration Management license. Only the server configuration management feature requires that the OpenManageEnterprise — Server Configuration Management license is installed on target servers. This license is not required forcreating device configuration template from a server. The OpenManage Enterprise — Server ConfigurationManagement and OpenManage Essentials licenses are required only for deploying device configurations and verifyingconfiguration compliance on servers.The OpenManage Enterprise — Server Configuration Management license enables you to deploy a device configuration and verify deviceconfiguration compliance on licensed servers. The license is a perpetual license that is valid for the life of a server, and can be bound to theService Tag of only one server at a time. OpenManage Enterprise provides a built-in report to view the list of devices and their licenses.Click OpenManage Enterprise Monitor Reports License Report. Click Run. See Run reports.NOTE: Enabling the server configuration management feature in OpenManage Enterprise does not require any separatelicense. If the OpenManage Enterprise — Server Configuration Management license is installed on a target server, youcan use the server configuration management feature on that server.Licensable ServersYou can deploy the OpenManage Enterprise — Server Configuration Management license on the following PowerEdge servers: 413th generation (13G) servers having the iDRAC8 2.50.50.50 or later firmware versions. 13G iDRAC versions are backward compatibleto support the iDRAC7 versions (12G) also.14th generation (14G) servers having the iDRAC9 3.10.10.10 or later firmware versions.About Dell EMC OpenManage Enterprise
Purchasing LicenseYou can purchase the OpenManage Enterprise — Server Configuration Management license when you purchase a server or bycontacting your sales representative. You can download the purchased license from the Software License Management Portal atDell.com/support/retail/lkm.Verifying License InformationOpenManage Enterprise provides a built-in report to view the list of devices that are monitored by OpenManage Enterprise, and theirlicenses. Click OpenManage Enterprise Monitor Reports License Report. Click Run. See Run reports.You can verify if the OpenManage Enterprise — Server Configuration Management license is installed on a server by: On all pages of OpenManage Enterprise, in the upper-right corner, click the i symbol, and then click Licenses.In the Licenses dialog box, read through the message and click appropriate links to view and download OpenManage Enterpriserelated open-source files, or other open-source licenses.License-based features in OpenManage EnterpriseTo view the latest version of the installed OpenManage Enterprise appliance: Click the i symbol in the upper-right corner commonly displayed on all the OpenManage Enterprise pages.Click Application Settings Console Update.NOTE: To view if any newer version of OpenManage Enterprise is available, see Check and update the OpenManageEnterprise version. Also, see the OpenManage Enterprise Release Notes available on the support site.About Dell EMC OpenManage Enterprise5
2Security features in OpenManage EnterpriseSome of the security features of OpenManage Enterprise are: Role-based access that limits access to console settings and device actions.Hardened appliance with Security-Enhanced Linux (SELinux) and an internal firewall.Encryption of sensitive data in an internal database.Use of encrypted communication outside the appliance (HTTPs).WARNING: Unauthorized users can obtain OS-level access to the OpenManage Enterprise appliance bypassing DellEMC's security restrictions. One possibility is to attach the VMDK in another Linux VM as a secondary drive, and thusgetting OS partition access, whereby OS-level login credentials can possibly be altered. Dell EMC recommends thatcustomers encrypt the drive (image file) to make unauthorized access difficult. Customers must also ensure that forany encryption mechanism used, they can decrypt files later. Else, the device would not be bootable.NOTE: AD and LDAP directory users can be imported and assigned one of the OpenManage Enterprise roles (Admin,DeviceManager, or Viewer). The Single-Sign-On (SSO) feature can be used only till logging in to the console. Actionsrun on the devices require a privileged account on the device.Related informationDeploying and managing OpenManage EnterpriseTopics: Role-based OpenManage Enterprise user privilegesOpenManage Enterprise user role typesRole-based OpenManage Enterprise userprivilegesUsers are assigned roles which determine their level of access to the console settings and device management features. This is termed asRole-Based Access Control (RBAC). This is a common list of RBAC for users based on their roles and OpenManage Enterprise features.However, where required, an individual task-level user RBAC list is provided in respective sections for quick reference. Therefore, theconsole enforces one role per account. For more information about managing users on OpenManage Enterprise, see ManageOpenManage Enterprise users.Table 1. Role-based user privileges in OpenManage EnterpriseOpenManage EnterprisefeaturesUser levels for accessing OpenManage EnterpriseAdminDevice ManagerViewerRun reportsYYYViewYYYManage BaselineYYNConfigure deviceYYNUpdate deviceYYNManage jobsYYNCreate monitoring policiesYYNDeploy OSYYNPower controlYYN6Security features in OpenManage Enterprise
OpenManage EnterprisefeaturesUser levels for accessing OpenManage EnterpriseAdminDevice ManagerViewerManage reportsYYNManage templatesYYNSet up the OpenManageEnterprise applianceYNNManage discoveryYNNManage groupsYNNRefresh inventoryYNNSet up securityYNNManage trapsYNNRelated tasksDeploying and managing OpenManage EnterpriseRelated referenceOpenManage Enterprise user role typesOpenManage Enterprise user role typesNOTE: AD and LDAP directory users can be imported and assigned one of the OpenManage Enterprise roles (Admin,DeviceManager, or Viewer). The Single-Sign-On (SSO) feature can be used only till logging in to the console. Actionsrun on the devices require a privileged account on the device.Table 2. OpenManage Enterprise User role typesUser with this role.Has the following user privilegesAdministratorHas full access to all the tasks that can be performed on theconsole. Full access (by using GUI and REST) to read, view, create, edit,delete, export, and remove information related to devices andgroups monitored by OpenManage Enterprise.Can create local, Microsoft Active Directory (AD), and LDAPusers and assign suitable rolesEnable and disable usersModify the roles of existing usersDelete the usersChange the user passwordDevice Manager (DM) NOTE: DMs can share permissions to the tasks andpolicies created by each other. This sharing occurs by having complete overlap with the device groupscontained in the task or policy, and those assigned to the DM. If the DM loses complete overlap with the groupscontained in the task or policy, the DM will no longer beable to run or edit it unless this overlap is restored.Get only device permissions from the admin. All otherpermissions are fixed.Run tasks, policies, and other actions on the devices assignedby the administrator.Cannot delete or modify any groups.ViewerCan only view information displayed on OpenManage Enterpriseand run reports.By default, has read-only access to the console and all groups.Cannot run tasks or create and manage policies. NOTE: Users with Device Manager (DM) privilegescannot be assigned groups.Security features in OpenManage Enterprise7
User with this role.Has the following user privilegesNOTE: If a viewer or DM is changed to an administrator,they get the full administrator privileges. If a viewer ischanged to a DM, the DM has the same privileges as aviewer.NOTE: A change in the user role will not affect a loggedin user. The changes become effective only after thenext user login.NOTE: An audit log is recorded when: A group is assigned or access permission is changed. User role is modified.Related tasksDeploying and managing OpenManage EnterpriseRelated informationRole-based OpenManage Enterprise user privileges8Security features in OpenManage Enterprise
3Deploying and managing OpenManageEnterpriseDell EMC OpenManage Enterprise is provided as an appliance that you can deploy on a hypervisor and manage resources to minimizedowntime. The virtual appliance can be configured from the application web console after initial network provisioning in the Text UserInterface (TUI). For steps to view and update the console version, see Check and update the OpenManage Enterprise version. Thischapter describes the installation prerequisites and minimum requirements.NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on thesupport site.Related referenceOpenManage Enterprise user role typesProcess map for checking and updating the OpenManage Enterprise versionOpenManage Enterprise Graphical User Interface overviewSecurity features in OpenManage EnterpriseRelated informationRole-based OpenManage Enterprise user privilegesTopics: Installation prerequisites and minimum requirementsDeploy OpenManage Enterprise on VMware vSphereDeploy OpenManage Enterprise on Hyper-V 2012 R2 and earlier hostDeploy OpenManage Enterprise on Hyper-V 2016 hostDeploy OpenManage Enterprise by using Kernel-based Virtual MachineInstallation prerequisites and minimumrequirementsFor a list of supported platforms, operating systems, and browsers, see the Dell EMC OpenManage Enterprise Support Matrix on thesupport site and Dell TechCenter.To install OpenManage Enterprise, you require local system administrator rights and the system you are using must meet the criteriamentioned in the Minimum recommended hardware and Minimum system requirements for installing OpenManange Enterprise.Minimum recommended hardwareTable 3. Minimum recommended hardwareMinimum recommended hardwareLarge deploymentsSmall deploymentsNumber of devices that can bemanaged by the applianceUp to 80001000RAM16 GB16 GBProcessors8 cores total4 cores totalHard drive200 GB20 GBDeploying and managing OpenManage Enterprise9
Minimum system requirements for deployingOpenManange EnterpriseTable 4. Minimum requirementsParticularsMinimum requirementsSupported hypervisors VMware vSphere versions: vSphere ESXi 6.5 vSphere ESXi 6.0 vSphere ESXi 5.5Microsoft Hyper-V supported on: Windows Server 2016 Windows Server 2012 R2KVM supported on: Red Hat Enterprise Linux 7.2Red Hat Enterprise Linux 7.0Red Hat Enterprise Linux 6.5NetworkAvailable virtual NIC which has access to the managementnetworks of all the devices which is managed from OpenManageEnterprise.Supported browsers User interfaceHTML 5, JS basedInternet Explorer (64-bit) 11 and laterMozilla Firefox 52 and laterGoogle Chrome 58 and laterNOTE: For the latest update about the minimum requirements for OpenManage Enterprise, see the Dell EMCOpenManage Enterprise Support Matrix on the support site.Deploy OpenManage Enterprise on VMwarevSphereNOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-basedOpenManage Enterprise user privileges.1. Extract the .zip file to a location accessible by VMware vSphere Client. It is recommended to use a local drive or CD/DVD, becauseinstalling from a network location can take up to 30 minutes.2. In vSphere Client, select File Deploy OVF Template.The Deploy OVF Template wizard is displayed.3. On the Source page, click Browse, and then select the OVF package. Click Next.4. On the OVF Template Details page, review the information that is displayed. Click Next.5. On the End User License Agreement page, read the license agreement and click Accept. To continue, click Next.6. On the Name and Location page, enter a name with up to 80 characters, and then select an inventory location where the templatewill be stored. Click Next.7. Depending on the vCenter configuration, one of the following options is displayed: If resource pools are configured — On the Resource Pool page, select the pool of virtual servers to deploy the appliance VM.If resource pools are NOT configured — On the Hosts/Clusters page, select the host or cluster on which you want to deploythe appliance VM.8. If there are more than one datastores available on the host, the Datastore page displays such datastores. Select the location to storevirtual machine (VM) files, and then click Next.9. On the Disk Format page, select one of the following options:10Deploying and managing OpenManage Enterprise
To allocate storage space to VMs, as required, click Thin Provision.To pre-allocate physical storage space to VMs at the time a drive is created, click Thick provision.10. On the Ready to Complete page, review the options you selected on previous pages and click Finish to run the deployment job.A completion status window displays where you can track job progress.Deploy OpenManage Enterprise on Hyper-V 2012R2 and earlier host1. Extract the openmanage enterprise vhd format.zip file, and then move or copy the enclosed VHD file into the appropriatelocation on your system where you want to store the OpenManage Enterprise (OME) virtual drive.2. Start Hyper-V Manager in the Windows Server 2012 R2 and earlier versions. The Windows Hyper-V should be displayed under HyperV Manager. If not, right-click Hyper-V Manager, and then select Connect to Server.3. Click Action New Virtual Machine.4. On the Specify Name and Location page, select the VM name and a storage location appropriately for your environment.5. Navigate to the Specify Generation page and select Generation 1. OpenManage Enterprise does not support Generation 2.NOTE: Ensure that 8192 MB is assigned as the memory. Dynamic memory can be turned on, but for bestperformance, it is recommended to leave the option 'disabled'.6. On the Networking Configuration page, ensure that the network adapter is connected to the network. If set to 'Not Connected',OME will not function properly during the first reboot, and requires redeployment if this situation recurs.7. On the Connect Virtual Hard Disk page, select Use an existing virtual disk drive, and then go to the VHD file you copied in step1.8. Complete the on-screen instructions.9. Open the settings of the newly created VM.Deploy OpenManage Enterprise on Hyper-V 2016host1. Extract the openmanage enterprise vhd format.zip file, and then move or copy the enclosed VHD file into the appropriatelocation on your system where you want to store the OpenManage Enterprise (OME) virtual drive.2. Start Hyper-V Manager.3. Select the host and select Action Import Virtual Machine.4. Select the folder that contains the OpenManage Enterprise virtual appliance including snapshots, virtual drives, VMs, and import files.Click Next.5. On the Select Virtual Machine page, select the virtual machine to import (there is only one option available), and then click Next.6. On the Choose Import Type page, select Copy the virtual machine, and then click Next.7. On the Choose Destination page, retain the default values, or select the location of the VM, snapshot, and smart paging.8. Click Next.9. On the Choose Storage Folders page, retain the default values or click Browse and select the location of virtual drives, and thenclick Next.10. On the Summary page, review the options you selected on earlier pages, and then click Finish to deploy OpenManage Enterprisevirtual appliance on the Hyper-V host.11. After OpenManage Enterprise virtual appliance is deployed, select the OpenManage Enterprise virtual appliance, and then click Startunder Actions.NOTE: The OpenManage Enterprise appliance file can also be deployed by using a compatible KVM environment.Deploy OpenManage Enterprise by using Kernelbased Virtual Machine1. Download the openmanage enterprise.qcow2 file into the appropriate location on your system where you want to store theOpenManage Enterprise (OME) virtual drive.Deploying and managing OpenManage Enterprise11
2. Install Kernel-based Virtual Machine (KVM) by running the following command on any Linux system:yum install qemu-kvm python-virtinst virt-manager \3. Start the virtual manager and select File Properties.4. On the Network Interfaces page, click Add.5. Select Bridge as the interface type and click Forward.6. Set the start mode to onboot and select the Activate now check box.7. Select the interface to bridge from the list and ensure the properties match with the host device, and then click Finish.A virtual interface is now created, and you can configure the firewall settings by using the terminal.8. On the Virtual Machine Manager, click File New.9. Enter a name for the VM and select the Import existing disk image option, and then click Forward.10. Navigate the file system and select the QCOW2 file that is downloaded in step 1, and then click Forward.11. Assign 8192 MB as the memory and select two processor cores, and then click Forward.12. Assign the required disk space for the VM and click Forward.13. Under Advanced options, ensure that the bridged host device network is selected and KVM is selected as the Virt Type.14. Click Finish.OpenManage Enterprise appliance is now deployed by using the KVM. To get started with OpenManage Enterprise, see Log in toOpenManage Enterprise.12Deploying and managing OpenManage Enterprise
4Getting started with OpenManage EnterpriseTopics: Log in to OpenManage EnterpriseConfigure OpenManage Enterprise by using Text User InterfaceConfigure OpenManage EnterpriseRecommended scalability and performance settings for optimal usage of OpenManage EnterpriseSupported protocols and ports in OpenManage EnterpriseLog in to OpenManage EnterpriseWhen you boot the system for the first time from the Text User Interface (TUI), you are prompted to accept the EULA, and then changethe administrator password. If you are logging in to OpenManage Enterprise for the first time, you must set the user credentials throughthe TUI. See Configure OpenManage Enterprise by using Text User Interface.CAUTION: If you forget the administrator password, it cannot be recovered from the OpenManage Enterprise appliance.1. Start the supported browser.2. In the Address box, enter the OpenManage Enterprise appliance IP address.3. On the login page, type the login credentials, and then click Log in.NOTE: The default user name is admin.If you are logging in to OpenManage Enterprise for the first time, the Welcome to OpenManage Enterprise page is displayed. Click InitialSettings, and complete the basic configuration setup. See Configure OpenManage Enterprise. To discover the devices, click DiscoverDevices.NOTE: If incorrect OpenManage Enterprise login credentials are entered, your OpenManage Enterprise account islocked and you will not be able to log in until completing the lockdown period. By default, the lockdown duration is 900seconds. To change this duration, see Set the login security properties.Configure OpenManage Enterprise by using TextUser InterfaceThe Text User Interface (TUI) tool provides you a text interface to change the admin password, view appliance status and networkconfiguration, configure networking parameters, and enable field service debug request.NOTE: To navigate on the TUI interface, use the arrow keys or press Tab to step forward, and press Shift Tab to stepback through the options. Press Enter to select an option. The Space bar toggles the status of a check box.1. Before logging in to the TUI, accept EULA when prompted.a) On the Change admin password screen, enter the new password and confirm the password.NOTE: For the first time, you must change the password by using the TUI screen.b) Use the arrow keys or press Tab to select Apply.c) On the confirmation screen, select Yes, and then press Enter.Now you can configure OpenManage Enterprise through the TUI. On the TUI screen, you can view the following options: Change the Admin PasswordDisplay Current Appliance StatusDisplay Current Network ConfigurationSet Networking ParametersEnable Field Service Debug (FSD) ModeReboot the ApplianceGetting started with OpenManage Enterprise13
NOTE: Possibly after running a command to restart the services, it may be observed that the TUI displays thefollowing message: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 36s! [java:14439]. This soft lockup issue likely occurs as a result of the hypervisor being overloaded. In such environments, it isrecommended to have at least 16 GB of RAM and CPU of 8000 MHz reserved to the OpenManage Enterpriseappliance. It is also recommended that the OpenManage Enterprise appliance be restarted when this message isdisplayed.Setup Debug Logging Enable Debug Logs Disable Debug Logs Enable SCP Retention Disable SCP RetentionRestart Services2. To confirm the current appliance administrator password, select Change the Admin Password, and then enter the password. PressTab and select Continue.3. On the TUI screen:a) To view appliance status and the IPv4 and IPv6 statuses and addresses, select Current Appliance Status.b) To configure network interface, select Set Networking Parameters.On the Configure Network Interface screen, to enable IPv4, or IPv6, or both, press Enter. Select Apply.NOTE: If the OpenManage Enterprise appliance fails to acquire a V6 address, check if the environment isconfigured for router advertisements to have the managed bit (M) turned on. Network Manager from currentLinux distributions causes a link failure when this bit is on, but DHCPv6 is not available. Ensure that DHCPv6 isenabled on the network or disable the managed flag for router advertisements.NOTE: To perform any write operations on TUI, ensure that you type the admin password, and then configureIPv4 or IPv6.NOTE: To configure IPv6, ensure that it is already configured by vCenter server.NOTE: In an IPv6 environment, when a Router Advertisement is configured for stateless configuration of multipleIPv6 IPs on a port, iDRAC supports a maximum of 16 IPs addresses. In such a case, OpenManage Enterprisedisplays only the last discovered IP and uses that IP as the out-of-band interface to iDRAC.NOTE: By default, the last discovered IP of a device is used by OpenManage Enterprise for performing alloperations. To make any IP change effective, you must rediscover the device.c) To enable console debug, select Enable Field Service Debug (FSD) Mode. See Field service debug workflow.d) To collect the debug logs of the application, monitoring tasks, events, and task execution history, select Setup Debug Logging .In addition, to collect the template .XML files, select the Enable SCP retention option under Setup Debug Logging . You candownload the debug logs by clicking Monitor Audit Logs Export Export Console Logs in OpenManage Enterprise.e) To restart OpenManage Enterprise, select Reboot the Appliance.Configure OpenManage EnterpriseIf you are logging in to OpenManage Enterprise for the first time, the Welcome to OpenManage Enterprise page is displayed. Toconfigure the basic settings, click Initial Settings, and type or select the following data in the dialog box:1. From the Time Zone drop-down menu, select a time zone. Click Apply to save the selected time zone. To set the time zone to adefault value, click Discard. After updating the time zone, all active users are logged out of OpenManage Enterprise.2. If you want to use the NTP Server for time synchronization, select the Use NTP Server check box.NOTE: When the NTP Server settings are updated, the currently logged in users are automatically logged out fromtheir OpenManage Enterprise sessions.3. Type the IP address or hostname in Primary NTP Server Address and Secondary NTP Server Address (optional) for timesynchronization.4. If you want to set proxy server for external communication, select the Use HTTP Proxy Settings check box.5. In the Server IP Address box, enter the IP address or host name for the proxy server.6. In the Port box, enter the port number for the proxy server.7. If the proxy server requires credentials to log in, select the Use Proxy Credentials check box, enter the username and password.14Getting started with OpenManage Enterprise
8. Click FINISH.NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on thesupport site.Recommended scalability and performancesettings for optimal usage of OpenManageEnterpriseThe following table lists the performance parameters of the supported features in OpenManage Enterprise. To ensure an optimalperformance of OpenManage Enterprise, Dell EMC recommends to run the tasks at the specified frequency on the maximum number ofdevices that are recommended per task.Table 5. Scalability and performance considerations of OpenManage EnterpriseTasksRecommended frequency ofrunning the tasksTasks whether pre-canned?Maximum devices that arerecommended per taskDiscoveryOnce a day for environment with Nofrequent network changes.InventoryOpenManage Enterpriseprovides a pre-canned task thatautomatically refreshesinventory once a day.Warrant
User with this role. Has the following user privileges NOTE: If a viewer or DM is changed to an administrator, they get the full administrator privileges. If a viewer is changed to a DM, the DM has the same privileges as a viewer. NOTE: A change in the user role will not affect a logged-in user. The changes become effective only after the .
