Issue description: On Microsoft Windows operating system, SNMP walk stops working in a 32-bit to 64-bit upgrade installation.
Issue description: SNMP MIB walk does not display any information in an upgrade from 32-bit to 64-bit version of OpenManage 9.1.
Resolution: To resolve the issue, add this registry entry to the windows registry and restart OS SNMP service
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents] "SysMgmtDataEngine"="SOFTWARE<\\Dell Computer Corporation\\OpenManage\\DataEngine\\SNMP Agent\\CurrentVersion>".
Issue description: If the uninstall operation is aborted, some of the Server Administrator component tree objects may not appear.
Resolution: To resolve this issue, Server Administrator installation must be repaired. Go to . Select Repair on the Server Administrator installation.
Issue description: Server Administrator launch using the desktop
icon fails in a remote desktop session. (BITS053605)
When Server Administrator
is deployed to a system with an active remote desktop session, launching Server Administrator in that session fails with
the error message: The program cannot start because
libxml2.dll is missing from your computer. To fix this issue, reinstall
the program.
Resolution:
To resolve this issue:
- Log off from the remote session and login again.
(or)
- Perform the following steps in the same remote session:
- Right-click My Computer.
- Go to the Advanced tab.
- Click Environment Variables.
The Environment Variables pop-up screen
is displayed.
- Click OK and exit from the screen.
Issue description: Configure HTTPS
Listener link page does not time out. (498330). If you click the Configure
HTTPS listener link in the Prerequisite page, the page does not time
out.
Resolution: To resolve this issue,
close and reopen the page.
Issue description: Insufficient Privilege error message while uninstallation
(241136) (241498)
Error message appears when an Active Directory user, member of Domain Admins , and Domain Users group uninstall Server Administrator.
Resolution: To fix this issue,
the user can open the command prompt as Administrator and run the
command: msiexec /x <msiname>.msi