– OMSA (Dell EMC OpenManage Server Administrator) -tuki | Dell Suomi
Thx for your info. BarTender Print Portal. Embarcadero Technologies, Inc.
Dell openmanage server administrator download windows server 2008 r2 free –
I have Dell OpenManage installed on a R2 server. It was originally installed using local admin credentials, and the server has since been joined to a domain. It will not accept domain admin credentials, it just pops back up. If I enter local admin credentials, it is happy. Confusingly, I am also able to get rid of it just by closing it. After that popup has been given local admin credentials, or just closed, the webform-based logon screen appears and that authentication works correctly with either domain or local admin credentials.
Any idea on how to get rid of the irritating popup? It doesn’t seem to be needed but I don’t know why it appears. I’ve tried running a Repair of OpenManage whilst logged on as Domain Administrator, but it didn’t help. You can do this by double clicking the colored warning in IE and adding the cert to the appropriate group.
I can confirm that same thing happens to me. Perhaps for years now. I’ve just learned to instantly close the first pop-up and move on. Scary programming skills over at Dell I don’t have a proper certificate for this server, just the one that Windows creates for itself.
I just checked on one of my servers and it uses the self-generated certificates. My server is also listed in “Trusted Root Certification Authorities”.
Is your server using the Dell self-generated certificate, or a self-generated cert from Windows? Mine is using the former. I’ve checked in the Current User Trusted Root Certification Authorities as both local and domain user, and als in the Local Computer Trusted Root Certification Authorities, and no entry for the server in any of those places. Forgot to mention before but SSO is turned on and as long as I never click “Log Out” in the web interface, it does log me in automatically, once the dialog box is dealt with.
Thanks for the detailed reply, which bizarrely landed at exactly the point I realised that I’d fixed this in a different way All I had to do to get rid of the irritating popup was to explicitly add the domain admin user account to the local computer’s Administrators group. The Domain Admins group was already a member of the local Administrators group, and that Domain Admins group already contains the domain admin user account, so the permissions should have been inherited.
No idea why my extra step was necessary but glad it has worked. As an added bonus, I’ve got rid of the Certificate Error by importing the current certificate to Trusted Root as described in Step 6 above. I’ve tried that before to get rid of OWA errors on connections to servers with self-signed certs, and sometimes it doesn’t seem to work, but on this occasion I’m very pleased to say it did. Yes it’s an odd one. I don’t know why it worked but it did, and as you say, that’s what counts ultimately.
To continue this discussion, please ask a new question. Dell , Followers – Follow Mentions Products. Chris Dell. Get answers from your peers along with millions of IT pros who visit Spiceworks. Thanks Dave. Best Answer. Christopher Aug 23, at UTC. I am using Windows self certificates. View this “Best Answer” in the replies below ».
Popular Topics in Dell Hardware. Spiceworks Help Desk. The help desk software for IT. Track users’ IT needs, easily, and with only the features you need. Learn More ». Christopher Aug 22, at UTC. The issue here is with site authentication and security certificates.
Add your “local server” to trusted sites, supply valid certificate and enable single sign on. Christopher, thanks for the reply. I’d already added the server to trusted sites. I’ve checked the certificate it’s currently using – it’s one that it generated itself. Is that usable, or should I create a new one? Do not forget about the third step – single sign on SSO. Thanks for your help with this, it’s appreciated. Thanks for all your help. Christopher Aug 27, at UTC.
I am not sure if the popup has anything to do with domain vs. I have seen this authentication popup even when logging in with local account at the console. But if it solved your problem – that is what counts ultimately. This topic has been locked by an administrator and is no longer open for commenting. Read these next