OMSA will not load after login

Question

I have a PowerEdge R510 on 2008R2 still. OpenManage Server Administrator (Managed Node) does not get past the log screen (it worked previously so I suspect WinUpdate or browser issue - I cleared cache/cookies, tried low security and compatibility view in IE). I'm talking about the OpenManage (black) login screen, not the Windows security popup that you get sometimes.

When logging in with the correct credentials, the screen says "verifying credentials", clears, begins to paint the title bar of the OMSA system status page left nav, and then the login screen comes back again.

When logging in with the wrong credentials, a dialog comes up with "login failed" before the login screen comes back. This is what makes me believe it is not a credential issue (I know the administrator password).

The system originally had OMSA 8.2 loaded. I uninstalled it, rebooted, and loaded OMSA 8.5 but it does the same thing.

OMSA 8.5 is showing as supported for this system, and it worked with 8.2 previously.

Is there an uninstall or cleanup tool? Anybody seen this behavior before?

DELL-Sirisha U · Answer

Hi,

OM8.5 supports windows2008 R2 OS on PER510.

I think proper uninstall of OM8.2 should be done.

clear cookies/cache very much. compatible IE browser.

Now install OM8.5, this should happen without any login screen issues.

uninstall ->controlpanel->Programs->Programs and Features->

Dell EMC OpenManage XXXX - click on this and uninstall thats it.

This is the way to uninstall.

Just for reference, further you can delete C:\Program Files\Dell -> SysMgt folder.

This should work without any login screen issue.

let me know if you need any input.

Thanks

DELL-Sirisha U

#Iwork4Dell

mkalqimi · Answer

We are seeing the same thing across several Dell R510 W2K8 SP2 systems. This appears to have occurred recently ~ with last 4 weeks. Systems with OMSA 8.50. that were working are no longer working. We suspect a Windows update may be the culprit. De-/Reinstall, FQDN in the URL, cache clears, compatibility mode etc. did not fix the issue.

mkalqimi · Answer

Thinking the issue might be related to a recent IE patch, we removed these two (KB4519974,
KB4516046) incrementally with no improvement. We then removed this security patch (KB4520003) and we regained functionality. The release notes do list some prerequisites for this patch that we still need to study, but it does appear to be the offending party.

mkalqimi · Answer

One additional note, we verified that the account activity for the OMSA login shows a success status for the login in the security log.

mkalqimi · Answer

Sirisha, As noted in my previous post. We have isolated the issue to KB4520003. Following the installation notes, we have verified all of the prerequisite packages were satisfied. One outstanding question we have deals with this not from Microsoft. Version:Security-only update IMPORTANT Verify that you have installed the required updates listed in the How to get this update section before installing this update. IMPORTANT Customers who have purchased the Extended Security Update (ESU) for on-premises versions of some operating systems must follow specific procedures to continue receiving security updates after extended support ends on January 14, 2020. For more information, see KB4522133. Improvements and fixes This security update includes quality improvements. Key changes include: Addresses an issue in security bulletin CVE-2019-1318 that may cause client or server computers that don’t support Extended Master Secret (EMS) RFC 7627 to have increased connection latency and CPU utilization. This issue occurs while performing full Transport Layer Security (TLS) handshakes from devices that don’t support EMS, especially on servers. EMS support has been available for all the supported versions of Windows since calendar year 2015 and is being incrementally enforced by the installation of the October 8, 2019 and later monthly updates. Security updates to Windows Authentication, Microsoft JET Database Engine, Windows Kernel, Internet Information Services, and Windows Server. For more information about the resolved security vulnerabilities, please refer to the Security Update Guide. Known issues in this update Symptom Workaround Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events: 'The request was aborted: Could not create SSL/TLS secure Channel' SCHANNEL event 36887 is logged in the System event log with the description, 'A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.​' For information, see KB4528489. This KB guides us to check with the OEM of the hardware/software involved to see if it meets the requirements. Please confirm that OMSA 8.5.0 is compliant or are you able to advise if this is an issue that is being worked in Dell?

Frederic Dedieu · Answer

Hi,

I have the same issue.

Uninstalling Windows update KB4519972 and KB4507004 TEMPORARILY solved the problem. But it's not a solution.

I hope Dell will release a patch to OMSA 8.5 to fix this bug.

Sirisha, can you please escalate the issue ? Many thanks.

Best regards

Fred

Frederic Dedieu

wilspin · Answer

Same issue here using version 8.3 on multiple servers running 2012 r2. uninstall kb4519974 no help must be kb4519990 and IE that is the culprit. And guess what? Chrome works!!!! Don't install it on your server. Use workstation, add port rule 1311 on your server and paste url into chrome and log in. if your dns is issue sub name of server with ip address.

wilspin · Answer

So my google chrome work around is effective on all my Dell servers. So openmanage is not the issue, More likely IE is no longer compatible due to patch from MS.

DELL-Vivek S · Answer

Could you please attempt with google chrome with the KBs installed and see if the issue is popping up. Please give it a try. Regards Vivek #iwork4dell

Mark Kerr · Answer

So was there ever a fix or work around published for this problem?

MK1024 · Answer

This problem does not occur in IE if the OS is Windows Server 2016 or Windows Server 2019.  This is another case of Microsoft introducing problems in older operating systems that they don't bother to fix.

MK1024 · Answer

OMSA 9.4.0 fixed this for me with IE on Windows Server 2012 R2.  But OMSA 9.4.0 does not support older servers, and it erroneously reports that the system board CMOS battery is missing.  When I reinstall 8.5.0, the CMOS battery is correctly detected, but the IE login problem returns.

Frederic Dedieu · Answer

None of recent browsers work with OMSA 8.5 for me (IE, Chrome, Firefox). The only solution I found is using an 'old' portable version of Firefox 3.6... Regards Frederic Dedieu

shellOS · Answer

I have the same problem with OMSA 8.5 (win 2008r2) using IE and Edge on Windows 10 Pro. OMSA 9.4 works ok (win2012r2).   I'm using Chrome meanwhile to access OMSA 8.5

schillernet · Answer

Same issue. Was for some time able to connect remotely from another server. Now I have the issue on all servers I try and even using different browsers.

Systems Management General

OMSA will not load after login

Was this post helpful?