help me wrap my brain around this one

[kato2274]

OK here is the deal. I support 15 offices each with their own (smallish) active directory domain. there is only 1 server at each location.

so now I need to completely replace a server at one location. and I'm trying to figure the best way to do it. Ideally I'd like the new server to be a complete replacement for the old one, i.e. same computer name, ip address etc. If there were more than one domain controller in place it would be easy as pie. I could demote the old server then promote the new server with the same computer name, but alas the company won't spend the money for more than one server at a location.

what would be the best way to accomplish this. I have a couple thoughts but need more input.

the first thought is since there aren't a whole lot of OUs, users, and the like, just to backup the data files from the old server. demote it thus killing the domain, then build it from scratch on the new server. not sure if I want to go this way though cause it could take some time.

the other thought is to take my laptop with virtual pc and boot up a virtual windows 2000 server and promote it as a domain controller. then after replication demote the old server. put the new server in and promote it. after replication demote the virtual server on my laptop.

I've seen some articles about backing up active directory using system state backups and parrellel installations but these methods seem pretty complicated.

anyone have any thoughts?

[emr]

Haven't got much to add from the ideas that you put forward kato. If you are happy with the existing AD stucture at the site and can easily chuck in the temporary virtual W2k Server then go with that.

I suppose you have to weigh up how long it is going to take you to load the virtual 2k server against how long it will take you to re-create the domain, users, permissions, join each pc to domain, transferring profiles on each pc, and the list goes on.

emr

[confus-ed]

How about you build the replacement & put it in as backup & then promote it & demote the other, & leave that on 'test' so to speak, then go back later & pull the old stuff, infact just persuade the boss to leave it like that ?

[kato2274]

How about you build the replacement & put it in as backup & then promote it & demote the other, & leave that on 'test' so to speak, then go back later & pull the old stuff, infact just persuade the boss to leave it like that ?

won't work. the old server (a generation 1 compaq ml370) is already spoken for. it is going to be moved to another location where they have a workstation pc running nt4

[confus-ed]

Oh my master plan blown by the boss again .. !

Well then you are left with plan A & b then per your opener as all the 'other more complicated stuff' {parallel installs & whatnot} are just a 'perm' really on your plan b - its this having no spare makes it hard !

How critical are they on downtime, can you get things done in any window?

[kato2274]

Oh my master plan blown by the boss again .. !

Well then you are left with plan A & b then per your opener as all the 'other more complicated stuff' {parallel installs & whatnot} are just a 'perm' really on your plan b - its this having no spare makes it hard !

How critical are they on downtime, can you get things done in any window?

I'll be working in off hours probably from right at close until done. they expect no downtime. it has to be functional the next morning. I'm leaning toward plan b (promote VPC server, demote existing server, promote new server, demote vpc server)

I'm installing a 2k server on vpc right now......

if this plan will work then I'll go with it. it's just sometimes, my logic sounds logical to me, then I start actually working and realize I've made a critical miscalculation......don't want that to happen here, since I've got about 5 hours to get it right and still get a good nights rest.

[emr]

I'll be working in off hours probably from right at close until done. they expect no downtime. it has to be functional the next morning. I'm leaning toward plan b (promote VPC server, demote existing server, promote new server, demote vpc server)

I'm installing a 2k server on vpc right now......

if this plan will work then I'll go with it. it's just sometimes, my logic sounds like logical to me, then I start actually working and realize I've made a critical miscalculation......don't want that to happen here, since I've got about 5 hours to get it right and still get a good nights rest.

I reckon your logic is logical here.

Easiest and quickest way to get the job done. You don't have to touch the workstation's, it is all going to be work on the new server.

emr

[CeeBee]

I have done a similar operation using VMware, worked perfectly. Just make sure you have a safe copy of the virtual server and a good backup of the old DC (maybe a ghost image) in case $hit hits the fan...

[confus-ed]

..if this plan will work then I'll go with it. it's just sometimes, my logic sounds logical to me, then I start actually working and realize I've made a critical miscalculation......don't want that to happen here, since I've got about 5 hours to get it right and still get a good nights rest.

So I'm with everyone else & you, go with this idea imho, but maybe do the first one on a weekend as a dry run, to cut yourself some slack ? (you sound unsure ? practice makes perfect etc & thats got to be at extra rate too !) measure timings etc ? - I'd authorise o/t for that as a boss ..

[kato2274]

So I'm with everyone else & you, go with this idea imho, but maybe do the first one on a weekend as a dry run, to cut yourself some slack ? (you sound unsure ? practice makes perfect etc & thats got to be at extra rate too !) measure timings etc ? - I'd authorise o/t for that as a boss ..

thanks guys. it's good to have a sounding board, and even better when the sounding boards says my idea will work.

thanks again.