Endpoint Protection

This morning none of our logons are working for our SEP Manager console.

All our active directory logins fail authentication.  The two accounts I have setup using the Symantec Authentication fail as well.  After a while the accounts are locked out.

Any suggestions on where to look?

did u delete your sepm authentication?

How can I check.  First time I heard of that?

Kris

if you run resetpass.bat and able to login with user id: admin
password: admin
the previous account is enabled; can u check that?

Once you login to sepm go to SEPM -Admin - Servers- <server name> -properties- Directory servers..
Make sure its setup properly.

Then go to SEPM -Admin-Administrators and make sure your accounts show up there

So I ran the resetpass script.  It didn't give me an error but I am still getting Authentication Failure. Please try again.   

I am logged on via RDP to my SEPM.  Nothing has changed that I know of on my end.  admin /  admin I am using now to logon.

Kris

If you have synchronized AD with the Admins in SEPM then you will have to use the user name as admin (or an other user name that you have created) and the password would be the password for the active directory user to who you have sync the user.

Also try to login with the domain as 'Default'

RDP in non console sessions will break the manager and the database you dont want to do that. It details this in the installation guide that while installing or using you need to be in a console session. You can use RDP to get console and would recommend you follow those directions. http://support.microsoft.com/kb/278845

What version of SEPM are you using?
There was an issue with this in earlier versions of SEPM, where authentication was broken when using AD authentication.

https://www-secure.symantec.com/connect/forums/cannot-log-symantec-endpoint-protection-manager-after-changing-authentication-method
Not fun, but most articles come up as above...  :-(

OR alternatively...

Wait XX minutes (depending on version) after RESET.bat...
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/22ee901ee66c31e0882573a00057ce92?OpenDocument

Found out today that someone had changed the Domain Controller in the SEPM.  Now all my groups that are setup to sync are not sycning.  They are still pointed to thtat old Domain controller name and information.

How can I change this without having to remove those groups and add them again.

Are you able to login to SEPM ?
Run resetpass put user name /password : admin and domain default.

once you login you can change the domain controller in SEPM

Once you login to sepm go to SEPM -Admin - Servers- <server name> -properties- Directory servers.

Interesting - just this week, this happened to me!
I have my own name setup in SEPM as an administrator. I use my normal network/windows/ad password.
Life was good - I've been logging into the console as me, using my regular password, and now this week, it won't let me in AT ALL!
Authentication failed.
So, I have to login as the default "admin" name of "admin" and the password I assigned when I first installed.
I access the console from my own computers.
I normally use the JAVA console since the web console is so painfully slow and has a bunch of holes and issues it's pretty much unusable (constantly crashing back to a tab's home page, etc.)
Anyway, I've been logging in as myself for weeks, now this week, I can't.
I've added a second domain controller, reset passwords, all sorts of things, it simply won't let me in as me, but will as "admin".
I've done nothing this week that I've not done before other than I deleted a W2003 server that used to be a SEPM server because I've built 2 new servers and they have been up for over a month now.
So for over a month, we had 1 old 2003, and 2 new 2008 servers. This week I decided to go into SEPM, remove the server from the list, delete it in the admin area, then uninstalled SEPM from the server.
That's the only change.
I've been loggin in through the NEW servers for weeks anyway, I specifty the name of the new servers in the console when I log in, so it's not like I was even using the old server, and it was shown as a priority 2 server, no clients on it either.