hckynt
asked on
New Server Implementation
Server Implementation/Best Practices.
I just purchased a new server running Enterprise Server 2008 x64 and am seeking clarification/advise on a couple of issues. Any help is greatly appreciated!
A couple points to consider&.
1. I would like to virtualize (I have Virtual Server 05) as much as possible to get best utilization of the new hardware.
2. My existing DC is also my Exchange and print server (MS Standard Server 2003) which will be formatted and redeployed.
3. Part of my implementation includes a migration to Exchange server 2007.
4. I dont like working weekends.
My first thought was to first setup a VS (virtual server) on the new server as a second DC then make it a master and then take the original DC off-line and setup a new second for redundancy. Should I attempt doing this on a VS or not? Then I was thinking I would setup a second VS and make it the new Exchange server. Once that is done and mailboxes moved, it could go off line. Should I attempt making the Exchange server a VS or not?
What would be the recommended way to transfer all the print functions to another server and get the clients updated? If I am heading into trouble, what are my options? I am sure I will have more questions. Thanks for all your help.
Our Current DC and Exchagne server is Standard Server 2003.
I just purchased a new server running Enterprise Server 2008 x64 and am seeking clarification/advise on a couple of issues. Any help is greatly appreciated!
A couple points to consider&.
1. I would like to virtualize (I have Virtual Server 05) as much as possible to get best utilization of the new hardware.
2. My existing DC is also my Exchange and print server (MS Standard Server 2003) which will be formatted and redeployed.
3. Part of my implementation includes a migration to Exchange server 2007.
4. I dont like working weekends.
My first thought was to first setup a VS (virtual server) on the new server as a second DC then make it a master and then take the original DC off-line and setup a new second for redundancy. Should I attempt doing this on a VS or not? Then I was thinking I would setup a second VS and make it the new Exchange server. Once that is done and mailboxes moved, it could go off line. Should I attempt making the Exchange server a VS or not?
What would be the recommended way to transfer all the print functions to another server and get the clients updated? If I am heading into trouble, what are my options? I am sure I will have more questions. Thanks for all your help.
Our Current DC and Exchagne server is Standard Server 2003.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If they are virtualised in separate Virtual Machines within the same host then that won't be a problem, provided the host machine is powerful enough to support both an Exchange and DC Virtual Machine. You are correct - Exchange and a DC role on the same server isn't a recommended situation, if you can avoid it then do so.
You need to first make the server a member server in the domain by joining it to the domain, the same way as you join a workstation to the domain. For this the only DNS server in the server should be the IP of your current DC - and that IP should be contactable and pingable. Once the server is a member server, you then log in to the domain as the Administrator account and run dcpromo from there.
-tigermatt
You need to first make the server a member server in the domain by joining it to the domain, the same way as you join a workstation to the domain. For this the only DNS server in the server should be the IP of your current DC - and that IP should be contactable and pingable. Once the server is a member server, you then log in to the domain as the Administrator account and run dcpromo from there.
-tigermatt
ASKER
Another question. I am assuming you are suggesting Hyper-V for Server 2008 since that is what Exchange will have to be installed on becasue they are both 64x-bit. So with that said, maybe the best bet is to NOT virtualize Exchange 2007, nor make the new server the DC but virtualize the dc on the new server and use server 2003???
ASKER
This is a brand new HP server with 16GB of RAM, 4 drives, RAID 6, two partitions (system and data) and over 200GB of data room. Thanks !
I don't understand your reason behind not using virtualisation and going back to Server 2003? I would recommend you do use Hyper-V for virtualisation as opposed to Virtual Server - it is much better performance-wise since, provided your hardware supports hardware-assisted virtualisation, it will use the CPU to do some of the virtualisation. If your CPU doesn't support this though, your only option is to use Virtual Server.
You can virtualise Exchange 2007 and a DC on the same server - if you have other servers you could use, then you could either use that as a Domain Controller or Exchange server - but otherwise, virtualisation is the way to go. Your server should be powerful enough (you didn't say the speed of the processor though!).
You can virtualise Exchange 2007 and a DC on the same server - if you have other servers you could use, then you could either use that as a Domain Controller or Exchange server - but otherwise, virtualisation is the way to go. Your server should be powerful enough (you didn't say the speed of the processor though!).
ASKER
The two processors are Quad Core, 3GB. I am a bit worried about hte whole bet deal Hyper-V. I were to virtualize both the DC and Exhange on the new server and something Microsoftish went wrong I could be really hosed, but you are fine with the risk?
At the moment Hyper-V is still in beta, so I would recommend you do at least one test installation using Hyper-V on the new server before you were to proceed. However the new Server versions are pretty robust, so provided a test installation or two went according to plan, I wouldn't hesitate virtualising the environments.
Backups of both the entire DC (including all file data) and the Exchange databases are key in any environment, don't forget.
Backups of both the entire DC (including all file data) and the Exchange databases are key in any environment, don't forget.
ASKER
OK, thanks for all your help!
Thanks, hckynt!
--tigermatt
--tigermatt
ASKER