re-vamp of server setups

[johng75]

firewall:
sonic wall 2040, DHCP, gateway for the company

Server1:
windows server 2000 SP4, running SQL, and acting as a file server

Server2:
windows 2003 server, running AD(main), DNS, Exchange2003

Server3:
running windows 2003 server, running AD, VPN access

Server4:
windows 2003 server

Server5:
windows 2003 server


we currently have servers 1-3 inhouse and running, in the very near future we will be purchasing servers 4 and 5.

the intent is to use server 4 as our new SQL/Reporting server and move the SQL data off of server1 to it.

server5 is going to be used as our security server, and have ISA2006 installed

i would like to get the AD off of server2, and move it over to server1 after SQL has been taken off of it, and its just a file server at that point.... but it is windows 2kSP4, and the current AD machine is windows 2003.....what kind of problems could i be running into with the conversion? should i look into updating that server to windows 2003 after SQL has been removed, and before i attempt to move the AD?
i would also like to turn on DNS on this server....



once the AD and DNS are fully up and running on server1, i would like to take down our exchange server, reinstall windows2003, and then reinstall exchange 2003... what kind of issues could i be runing into with reattaching the database on a fresh machine, and making sure all the boxes still point to the correct users....
this server will ONLY be exchange2003 after this....




wondering, once i have server5 up and running, we dont really need 2 firewalls, as apposed to just enabling the proxy settings on the users machines, would i be better off just making the ISA server the gateway/DHCP for the company? that way incase something does happen with it, i could just move the cable back over to the sonicwall? i would also be moving over the VPN responsibilities from server3 to this machine, because server3 is in bad shape and needs to be removed from the infrastructure, thus losing it as an AD server




any insight will be greatly appreciated.







Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"

 

[johng75]

i would also like to deply WSUS, im thining of server1 once the SQL is off, and the AD and DNS are moved to it thus making it

AD/DNS/File Server/WSUS




Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"

 

[noveyron]

I dont know about the other servers, but you do need to do a bit of research on demoting an Exchange Server, it breaks if you do.You would probably be better off installing Exchange on one of the new servers, swing the mailboxes and PF's accross, then demoting.

Like I said, you do need to look into this particular issue more deeply, this is by no means the definitive answer to the problem, more of a heads up

 

[johng75]

i know that to demote an AD server, it totally has to be taken back to ground 0....that is an interesting idea though, move exchange over to the new machine, delay the ISA deployment and then do the demoting... think ill look at the specs for the new machine and see if i make it hearty enough to take on that role....

Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"

 

[Zelandakh]

AD and Exchange on the same box is a bad idea so I agree with noveyron.

You ideally need 2 DCs, both GCs on a physical site. I don't like SQL and file server on the same box as the network load is usually too great but it depends on usage.

 

[58sniper]

i would like to get the AD off of server2

Not going to happen with Exchange running. Doing so will permanently break Exchange. And, doing so is unsupported by Microsoft. (Essentially, you'll break it really bad, and they're not going to help you fix it.)

As johng75 said, you should move Exchange to one of the new servers. Once fully moved and all Outlook clients have autoupdated, remove Exchange from server 2, remove DNS, demote it, reinstall Exchange, move the mailboxes back.

I'd also move DHCP to a Windows server, and I'd upgrade that Windows 2000 box.

Pat Richard
Microsoft Exchange MVP
Contributing author The Complete Reference: Microsoft Exchange Server 2007

 

[Zelandakh]

All of Pat's steps are good.