[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 631
  • Last Modified:

Cannot login to 2008 Server after restore

I'm trying to do a test restoration of our single domain controller using Symantec Backup Exec System Recovery into VMWare.  I can get the server to boot, but when I try to login I receive the error "The security database on the server does not have a computer account for this workstation trust relationship".  I've seen other fixes for this out there, but they all refer to logging into one of the other domain controllers.
0
gk906
Asked:
gk906
  • 3
  • 3
  • 2
  • +2
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
Does this machine that you recovered hold the FSMO roles? What you might need to do is log on to the machine "locally" and then remove then re-add to the domain (without rebooting). Once you have added the machine back into the domain you can reboot and then try and logging back into the domain.

Once you have got back into the domain controller you will need to seize the FSMO roles to the domain controller you are currently logged into.

Seizing/Transfering FSMO Roles - http://support.microsoft.com/kb/255504

Will.
0
 
Thomas GrassiSystems AdministratorCommented:
you "I'm trying to do a test restoration of our single domain controller "
Is this the only domain controller on the network?

When doing a domain controller restore you perform a nonauthoritative restore of Active Directory Domain Services (AD DS)

Did you do that?

Here are the procedures

http://technet.microsoft.com/en-us/library/cc772519(v=WS.10).aspx

Best to have two domain controllers having just one makes it harder to recover.
0
 
amclaughlin01Commented:
Are you trying to log into the server itself or are you trying to login on a workstation to the server?

If it's a workstation, log in locally as an administrator, then run the network ID wizard under the properties of MyComputer > Change Settings.  This will reset the computer account password in AD, which will then allow you to login to the network.

AD will periodically change an AD computer account password.  When you restored the server, it is most likely that the password had been changed and now they are not in sync causing the error you are seeing.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
mebaby333Commented:
Have you tried disconnecting it from the network and logging on? Or logging in locally so you can repair the issue?

Ha ha guess I was late... :)
0
 
gk906Author Commented:
To answer your questions:

This is a single DC environment, so it has all of the FSMO roles on it.  Since it's a DC there's no way for me to log on locally

The link provided regarding non-authoritative DS restore refers to Windows Backup, which is not in play here.

This test server is not currently connected to any network.  It's just a test-restore in VMWare.
0
 
Thomas GrassiSystems AdministratorCommented:
•The link provided regarding non-authoritative DS restore refers to Windows Backup, which is not in play here.

I would then contact Symantec here is a link to what I found

http://www.symantec.com/business/support/index?page=content&id=TECH87405&actp=search&viewlocale=en_US&searchid=1387474293479
0
 
mebaby333Commented:
Here is a symantec convo that may benefit you....

http://www.symantec.com/connect/forums/security-database-server-does-not-have-computer

Another user with same issue... keep reading :)

There is a hidden switch in the recovery program...
0
 
mebaby333Commented:
Have you tried to restore again and change the switch within the restore program yet? I am interested to see if this repairs your issue
0
 
gk906Author Commented:
I haven't dug back into this yet, but hope to do so today.  I'll post back the results.
0
 
gk906Author Commented:
I'm just doing the test-restore again right now, but it makes sense that the Windows mini-setup generated a new SID and that's why I can't login.  I have used the hidden settings before but it's been a LONG time.  Thanks for the refresher!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now