It sounds like there was a big change. You deleted an account and created a new one. Please forgive me if this seems obvious, but does the new account have the same group memberships as the old one? Don't BE service accounts typically call for Domain Admin privileges? ( http://seer.entsupport.symantec.com/docs/253759.htm)
Are you trying to figure out what happened because you're curious, or _must_ you figure out what happened because you have no other account with which to log on to the server? I sure hope it's the former. Good luck, RS On Sat, May 1, 2010 at 2:40 PM, Cliff Partlow <cliff...@cox.net> wrote: > SBS Server 2003 service pack 2 - w/internal Exchange Server 2003. > On a reboot I was presented with: > “The local policy of this system does not permit you to logon > interactively.” > When logging on as administrator which I have been doing all along. > > What I did just prior to the reboot was update Backup Exec 11d to service > pack 5. > I had a: > “Access is denied to Remote Agent. Check the login account for the > specified device.” > That I have been trouble shooting. > I followed Symantec guidance to delete and recreate the Backup Exec service > account. And then applied the update to service pack 5. In the instructions > it states that this account is not associated with the server system > account. I thought that I was very careful to understand the relationship of > the Backup Exec service account and the server system account. There may be > a relationship here that caused the issue that I am not aware of? > > This server has been up for over 2 years. I am totally baffled. I have done > 3 to 4 hours of research and looks like I have my work cut out for me. > > Is there any one on the list who has had this issue? > > Here is the MS KB that specifically deals with this error message dialog: > Article ID: 841188. > I am going to do all of this first before I try some of the more evasive > solutions. > > I am just at a loss to understand how this might have occurred without any > user, group, or policy changes. The reason I can make that statement is I > was logging into the server all morning long and this occurred after a > successful login and then reboot with out me making any of those changes. > > I will not have access to the server until Monday morning. I have an SBS > 2003 VM that I am going to try and create the same error message and then > see if I can correct it. > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
