Endpoint Encryption

Hi all, 

I encounter a login problem for (administrator and limited administrator). My SEPM is integrated with AD, So, I thought it might be AD causing the problem but I created 3 admins(local) account with the different right. Only, the system administrator can successfully log in.  The rest got a problem with an error message 

The error message is as follow 

Administrator's user name or password is incorrect. Type a valid user name or password. 

does anyone encounter this problem before?? 

I have both Local and AD accounts as a System administrators. All are working fine. 

My AD account as a system admin is working fine. 

What is the test function ?? 

If AD-Linked SEP System Administrators are working fine, and the issue is restricted to Administrator and Limited Administrator accounts only, then the issue is usually with SEP admins getting Windows Domains and SEP Domains mixed up.

Assuming that all these accounts were created within SEP's default domain, then please make sure they do not enter a domain in the SEPM's Domain field of the login screen.  Doing so causes the SEPM to look for a SEP Domain of that name, which usually fails because most companies do not create additional SEP domains (managed under Admin -> Domains in the SEPM Console).

Also note, this thread appears to have been created in the Endpoint Encryption forums, instead of the Endpoint Protection ones.

Hi, 

Is there any solution for that?? 

My team created for 5 servers with different domains. only 1 have that kind of problem. 

only that server with both default and domain.

I'm not sure what you mean.  My description is of an admin user issue, not a bug, and therefore must be rectified by amending user behaviour.  That is to say, make sure you enter the SEP Domain (not Windows Domain) into the domain field at SEPM Console log in, or don't enter one at all.

This does all assume that you are entering the username for a SEP Admin account that doesn't exist in the SEP Domain you're naming though, and while this is the most common reason I've seen for the issue you've described, you've not yet provided enough information to confirm or refute that assumption.

Feel free to ping us more details, if you need further assistance.

Your analysis is correct. Now I removed one of the domains and so far. working fine.