WINDOWS 2003 EMERGENCY BECAUSE OF MY STUPIDITY

As long as both server were DC in the same domain you can take over the FMSO role with a prolem but you will have to clean out AD first or bring the rebuilt server in to the domain under a diffrent name

Okay.  Both servers were on same domain.  We're small company with one domain.
Transfer FMSO roles to backup server?
Data is not an issue:  I have data both on disk and backup.

Backup server ran DNS but not DHCP.

Can I bring new Server up with same NAME, DTC-SERVER2?

Just FYI These are Windows 2003 Server STD

Okay,  Transferred FMSO roles over and cleaned up AD.   DNS is running fine.  

A few concerns and questions I need help with (to help calm my nerves)

Original Server is back up as a member server.  Data drives are located on this server.
Backup Exec needs to be installed again on the original server since the tape drives are located there.

Concerns/Questions
Original DHCP scope:  I know I have to create it but what about my reservations I had for all of my printers?  Is this retrievable?  Can I get this information back?  My boss has IP assignment somewhere but not sure where it is
How should I go about getting EVERYONE and every piece of equipment pointing to the new server?
Specifics please :)

Is there anything else I'm missing?  Mapped drive assignments are important.

Thanks
Terry

Terry,

KCTS has given you some excellent information and your network should be pretty much accessible now. But, your DHCP scope and address pool for that server, printers, and mapped drives are domain specific, much like your network shares would be specific to your network.  Without additional information from you, we may not be able to help you get this the way you want. Some of this may need to be fixed by scratch/manual rebuild.

Can you tell us these things:
-Did  you have logon scripts that mapped your network drives for you?
-Was the backup DC used for printers as well?
-What about personal shares, like DFS shares?..Did you have any personal data at all on the bad server?
-What do  your backups look like? ... are they true images and can you pull certain data from the image like you can with acronis?

Your boss' old IP should still be found in DNS host records. So, you can figure it out by looking in DNS.
-

Good morning you all. First off, thank you to you all for your help. This is unreal situation. Never had any problems or crashes until last night; thanks to MS updates / bad stick of memory. Can't remember last time I had to restart server.

What KCTS provided helped me. Network is accessible. The Backup DC is running DNS (always has) and DHCP with original scope. My worries were accessibility to users data and shared data.

Can you tell us these things:
-Did you have logon scripts that mapped your network drives for you?
YES login scripts are used and I Had a backup and they do show up under sysvol and domain (system32)
-Was the backup DC used for printers as well? No. WE had some printers on the main DC. Raises a good point I need to look at this morning.
-What about personal shares, like DFS shares?..Did you have any personal data at all on the bad server? Each user has a folder that they get mapped too. We also have a shared folder with child folders sorted by department. After checking the data drives, they seem to be accessible. Engineering department just advised they could access their application and data, so far.
-What do your backups look like? ... are they true images and can you pull certain data from the image like you can with acronis? We use Symantec Backup Exec. Having to do some restores in the past, I can restore right down to the file. We run an incremental M-T and Full BU on Fridays. Our Exchange on the other hand is handled on a smaller tape drive. Exchange seems to be operational without problems.


I have some WINS errors this morning on Original / newly rebuilt DC.

Source: WINSCTRS
EventID: 4314

WINS Performance Monitor Counters could not get WINS Stats.

Your well on your way to resolving these issues and I think KCTS can probably help you zip up these issues with the above information.

Tracking down the WINS issue should be fairly simple once you get higher priority things working well. I will stick around if you have issues remaining with WINS and the Domain browser services.

Logon scripts saved your mappings, and DFS shares that were replicated from one DC to the other saved your client's personal data. Good work.

Manually setting up DHCP to hold the scope of the entire network was also helpful. Many Administrators advocate the primary DC as the primary DHCP server and another DC as a secondary DHCP server that is NOT authorized as a DHCP server until failure of the primary.

Good planning on your part saved your back side!

Thanks Chief and KCTS.
So far so good.  My boss agreed that DHCP will be installed on the 2nd DC server but not authorized.
So far so good.
The pain in the arse thing I dread is having to reinstall Backup Exec and re create my jobs.
Any advice on that?
If not, thanks gentlemen and I'll close this thread out.

If you're ladies, thank you :)

Any symantec Backup Exe experienced techs out there? I use Acronis.

NOt looking forward to that installation.  Besides some small bugs popping up here and there, all is well.

Thanks to Chief as well.