6 Posts
0
1076
OME 2.5 on Server 2016 AccessCheck(): Client logon credentials not authorized
I am migrating our Dell OME from a Windows Server 2008 R2 VM to a Windows Server 2016 VM. The original OME server was set up by a former Systems Administrator that is no longer here. I have no idea what he did to get the original install working. I am just tasked with migrating it to the new operating system.
I backed up the OME database with SQL Server Management Studio 18 on the old server, following the documentation I could find online. I installed OME on the new server and tested logging into the blank database - which worked.
I restored the database backup on top of the clean OME database according to the white paper from Dell. When I try to login it gives me the error "AccessCheck(): Client logon credentials not authorized."
This is a fresh server 2016 Datacenter install and it is not a domain controller.
In my DCs I have a security group named "OME" but no groups named like the other forum threads suggest. The user I am attempting to log on as is in that OME security group in my DC. I still cannot log on.
Any ideas of what I need to do to get this working? Is there something I must do to point to this restored database as a new install? Is the restored database still "pointed" to the old server install?
DELL-Charles R
Moderator
Moderator
•
3.6K Posts
0
November 4th, 2021 13:00
Hello sdelvisco,
You may try a fresh install again. "while installing OME, target this pre-created database" (your backup) that will allow it to write the permissions.
https://dell.to/3GU2SrI
Try re-start the OME services and check results. They are called "DSM Essentials ..."
This was fixed in a previous version but worth a try. Perform an IISRESET at the cmd or Run line which will allow the re-added user to login normally.
DELL-Young E
Moderator
Moderator
•
4K Posts
0
November 1st, 2021 21:00
Hi, thanks for choosing Dell.
I'm afraid the message alone doesn't give much as to what we can do about it,
I am migrating our Dell OME from a Windows Server 2008 R2 VM to a Windows Server 2016 VM. -> it seems like you made a change. This may change the account and the login policy may be different for windows2016. I'm sorry I can't be of much help this time but OS level issues aren't something we can look into. My apologies once again.
sdelvisco
6 Posts
0
November 2nd, 2021 05:00
You're supposed to be an expert? This is your software and we did not make a change other than migrating to Windows Server 2016! It's on a large domain and my login is the same across the domain. It's something in your software settings, Mr. Expert.
Why would you even answer the post? This is ridiculous. You are worthless. How do you keep your job?
Dell-Martin S
Moderator
Moderator
•
3.3K Posts
0
November 2nd, 2021 08:00
Hi,
Sorry that you had an unexpected experience.
But we need more information to assist you.
Please be nice when you communicate in our Dell Community Forum.
Regards Martin.
sdelvisco
6 Posts
0
November 4th, 2021 11:00
Nice? I am being nice. What other information do you require? There was no request for more information! I only got told that you could do nothing for me for a false reason. That isn't support. That's blowing me off because the problem seems too difficult.
Request information and you will receive it. Tell me you can't help on YOUR product and you get spoken to as such.
sdelvisco
6 Posts
0
November 4th, 2021 11:00
My local groups are in there for OMEAdministrators, OMEPowerUsers, and OMEUsers. My login account is in the OMEAdministrators and OMEPowerUsers groups. My login is also in the Domain Controller group "OME".
What other information do you require? You never asked for any.
sdelvisco
6 Posts
0
November 5th, 2021 05:00
Thank you for your solution, Charles. I appreciate you taking the time to address my issue instead of blowing me off and telling me there's nothing that can be done because I, as a systems administrator, did my job and "changed something."
The uninstall and reinstall keeping the restored database did the trick, then I restarted the server for good measure. Essentials opened right up after the restart. I'm a little mad I didn't figure it out myself but I appreciate the advice.