Jump to content

Win2003 server backing up all AD, DNS and DCHP config data


Recommended Posts

Posted

Hello fellow geeks,

 

In win 2003 server is there a straight forward way that will enable me to backup all AD, DNS and DCHP configuration data to neatly take home for my dummy server?

Posted

Start from scratch its much more fun that way :wink: DHCP you can export to a file which is just a netsh script. There are plenty of scripts that will make you 100 dummy users etc.

You will also end up with an eventlog full of errors about cant replicate with x server etc etc if you have your work setup at home.

Posted
I was just thinking of backing up the dummy server at work to take home so it enables me to work on and off site :wink:

 

Sounds like trouble to me :) . You could sync the data and take it home but I wouldnt dream of reconnecting it again later.

Posted
yep that's what I mean. I have a VPN connection from home to school. I run ssh/VNC/RDP over it depending on what I'm trying to talk to.
Posted
Ah, I see. I don't usually go for the full vpn connection, just use a forwarded port from the firewall to connected to the allocated server, its a bit safer that way but more restrictive
Posted
Our LEA set it up so we don't have to admin much beyond running a RADIUS server and allowing dialin access in AD for the relevant users.
Posted
I just pick the server up and put it in the car, far simpler :D

 

LOL ;)

 

.....I'm looking at doing something similar regarding backing up the domain data.

 

I was thinking of rebuilding the server as its been dog-slow since the change of IP ranges here [yes, we've discussed that one lol].

 

What I'm thinking is if I can backup the AD, DHCP and Group Policy setup [all the home dirs is already backed up ;)] and then rebuild the DC again, I could import the AD, import the DHCP & then the group policy, and enjoy a nice clean setup :)

 

The DNS can be damned btw lol wont be needing that backed up i dont think.

 

I'm thinking of doing this as I warey of promoting the email server to a DC, and also, because i fear that the "problem" with the system might carry across - making it all pointless that way.

 

My only other thought is the Exchange server - what would I need to do with that? lol [Everyone is using OWA btw]

 

The other thing i wanted to do is alter the domain name slightly i.e.

 

curriculum.broddyfi-hs...

becomes just:

broddyfi-hs...

 

so dropping the curriculum part - but having the Pre2000 domain still called CURRICULUM - just to avoid hassles hehe ;)

 

Any thoughts?

Nath

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...