win2k server crashed.....need to recover..but no system state backups

  • Thread starter Thread starter sphilip
  • Start date Start date
S

sphilip

hi there...i need some urgent help.

we have this win2k server with SP4 which is used as our
domain server & also our file server. we have about 100
workstations each having win xp pro OS, which are
coonected to this domain.

now our server HDD crashed n we replaced the same &
resetup the entire server from scratch by installing win2k
server & all updates & patches.

now when each user tries to logon to this domain (whose
details are just as they were) we face the following
problems:

1. it takes a minimum of 20 mins for loging on. if it
doesnt logon then the computer freezes

2. in case we logon then we cannot explore or do anything
else

3. at the same time if we try going to 'My Computer' on
the server the window opens and the torch just keeps
searching for ever.

the negatives tht i want to tell is that:

1. we donot have a system/registry backup of the server
before it crashed. but we do have a system-registry backup
which is 75 days old.

2. we havent rebuild the active directory

can someone tell me if rebuilding the active directory is
the solution for this or r there any other solution for
the same.

thanks
 
sphilip said:
now our server HDD crashed n we replaced the same &
resetup the entire server from scratch by installing win2k
server & all updates & patches.
Click to expand...

You can't do that. Creating a new Domain of the same name is not the same
thing. The new one is a *new* one and the old one is gone forever unless you
have backups or have a second DC that is still running.
1. we donot have a system/registry backup of the server
before it crashed. but we do have a system-registry backup
which is 75 days old.
Click to expand...

If you haven't done anything with the clients yet (like join them to the new
domain) then this is your only hope. 75 days old is better than having
nothin at all. If you have joined the new domain from the clients, then
they will have to be done again to the restored Domain.
 
sphilip said:
now our server HDD crashed n we replaced the same &
resetup the entire server from scratch by installing win2k
server & all updates & patches.
Click to expand...

You can't do that. Creating a new Domain of the same name is not the same
thing. The new one is a *new* one and the old one is gone forever unless you
have backups or have a second DC that is still running.
1. we donot have a system/registry backup of the server
before it crashed. but we do have a system-registry backup
which is 75 days old.
Click to expand...

If you haven't done anything with the clients yet (like join them to the new
domain) then this is your only hope. 75 days old is better than having
nothin at all. If you have joined the new domain from the clients, then
they will have to be done again to the restored Domain.
 
The problem is that the only way to restore a domain when you have only one domain
controller is using Directory Services Restore Mode from a backup of the System State
that is no more than sixty days old. The problems you are having is because the
computer accounts do not exist on the "new domain" unless you physically join all the
computers to the domain again and all the user accounts will have to be recreated. I
don't know if this will work as I have never tried it but your only other option
would be to try to reset the date of your domain controller back sixteen days and
then try to reinstall your AD and IF it reinstalls OK then try to set the computer
date to the current date. I have no idea if it will work but may be worth a try. The
link below may be of help. --- Steve

http://www.microsoft.com/technet/pr...de/part1/adogd03.mspx#XSLTsection128121120120
http://tinyurl.com/28476 -- same link as above, shorter.
 
The problem is that the only way to restore a domain when you have only one domain
controller is using Directory Services Restore Mode from a backup of the System State
that is no more than sixty days old. The problems you are having is because the
computer accounts do not exist on the "new domain" unless you physically join all the
computers to the domain again and all the user accounts will have to be recreated. I
don't know if this will work as I have never tried it but your only other option
would be to try to reset the date of your domain controller back sixteen days and
then try to reinstall your AD and IF it reinstalls OK then try to set the computer
date to the current date. I have no idea if it will work but may be worth a try. The
link below may be of help. --- Steve

http://www.microsoft.com/technet/pr...de/part1/adogd03.mspx#XSLTsection128121120120
http://tinyurl.com/28476 -- same link as above, shorter.
 
Back
Top