Solved

recovering windows 2000 server

Posted on 2004-03-28
2
220 Views
Last Modified: 2010-03-18
Hi,

Just completed upgrade from windows nt4.0 to windows 2003 one pdc which upgraded domain to windows 2003.  All servers and workstations able to log in to new environment but one windows 2000 server which is sql server had corrupted file in c:\winnt\system32\config and so wouldn't load operating system.  I installed another instance of windows 2000 on d drive and was able to get in no problem and then installed veritas backup exec 9.0 so i can restore from tape.  What i did was to start by restoring entire config folder and was able to get in to original windows 2000 but got lots of messages of installing new hardware such as nic card and scsi which obviously had already been installed but must have lost more settings.  My question is should i just restore the entire c drive from tape from day before or are there specific system folders that i should do first such as system volume folder and winnt.  Also, i was attempting to restore system state but gave message about domain controller but this server is not domain controller.  I didn't know where to target the system state restore coz i don't know if it resides in a specific folder or is just part of c drive.  This is production server so really need help on this.  Thanks.
0
Comment
Question by:eservando
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 5

Accepted Solution

by:
visioneer earned 500 total points
ID: 10699443
You want to restore the System State, and don't worry about the target location because the System State *is* the target location.  System State is the registry and associated system files for it.

What message did you see regarding a domain controller?  If the system is/was not a DC, it should let you restore the system state just fine.  If you see something about how you can't restore the system state to a DC without being in Directory Services Restore Mode, just click OK past that message because it doesn't apply to you in this case.

My suggestion would be to restore the entire C: drive *and* the System State.
0
 

Author Comment

by:eservando
ID: 10703313
Thanks for the info it is very concise and  to the point.  I'm actually going to try it not but of course what happened is that this darn veritas backup exec keeps rolling back the install at the end so can't restore obviously without it.  I was able to get in to the original windows 2000 by restoring the config folder in c:\winnt\system32\config from the parallel install but i should have just done the system state while veritas was working coz it probably would have let me in the domain already.  Instead it gave me message about system account not being in primary domain so had to log in locally but at least i was in but lot of stuff wasn't working so really need to restore that system state once i get veritas working so i can join domain.  Of course when i went to uninstall veritas from original windows 2000 coz it's required in order to reinstall, it uninstalled the working one on parallel install on d drive!  So when i went back in to do what you were instructing, veritas was gone!  Thanks for help.  I should be able to get it back since i have tapes from couple of days back and weeks if i have to since system state doesn't really change i guess.  
0

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question