Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hello. Would it be a good idea to Install VMware on a Domain Controller and install Exchange Server in there? I am trying to run everything on one server box. My server is a Pentium D 3.0 GHz and I might be upgrading the processor to a E6600 Core 2 Duo, if that is going to be necessary for this operation.
Is this a production server, or something you're playing around on for learning purposes? Does this server utilize RAID and if yes, what configuration are you using (ie: RAID 1 - OS with RAID 5 - data etc)
If it's a production server, you need to keep in mind that you don't install vmware on the existing OS. You flatline the box, install vmware, then start installing things like your DC into a virtual machine.
The following is just my opinion but, if it were me, I'd get a second server and set it up with vmware and run exchange on that. You don't want to load up a DC with too many services...........especially if it's the only DC in your domain.
In fact, if it were me, I'd build a second DC and I'd make it redundant and then I'd worry about a vmware server running exchange.
0 
I suspect you already purchased your software? That is a shame.
You could have just bought SBS [small business server] and it would be installed as a DC with exchange. No vmware [esx] for servers required.
0
Curt, This is for production use, not playing around for learning. If I want to do that, I can just use my Quad Core Desktop with 4 GB of RAM and run Virtual Machines for that.
"you don't install vmware on the existing OS. You flatline the box".
^ I don't get what you are trying to say. Are you trying to say that I don't install VMware Server For Windows on the Windows Server 2003 Domain Controller, or else the Domain Controller will lock up, freeze and crash? What about if I install a Core 2 Duo or a Core 2 Quad? My primary server has only 2 GB of Server RAM and My secondary server, which has a Pentium 4 3.00 GHz server has PC 3200 1 GB of RAM. The secondary server has 2 NIC's, where I am trying to make it the Internet Gateway as well as the Terminal Server.
How much servers will I be needing to be running for 24/7? I am trying to get one machine to be a Domain Controller, Another Machine to run Exchange Server and another server to be a Terminal Server. I only have 2 Server Machines. I can use a Chaintech Full Tower Desktop Machine as well as a server.
Running 3 Machines in Parallel in my opinion sounds good and is the way to go, but Power Consumption is main issue. Will 3 Servers waste a lot of power?
This is in a house, only hosting 4 people internally, plus more than 25 more remotely via Terminal Services and VPN.
Also Keep In Mind. I need one server to be a file server because I store everything on the server, large video files, audio files, etc. I also store my files in my 500 GB hard drive on my Quad Core system. The point I am trying to make is that I do not use RAID since I need all the space on the server and I need full gigabit speed to access the files stored on the server.
0
Curt, This is for production use, not playing around for learning. If I want to do that, I can just use my Quad Core Desktop with 4 GB of RAM and run Virtual Machines for that.
I wasn't asking if it was going to be a production server, I was asking if it is a production server. As in, is it presently in production and in use?
I don't get what you are trying to say. Are you trying to say that I don't install VMware Server For Windows on the Windows Server 2003 Domain Controller,
I was saying, you don't install vmware on the OS (as in after it's installed) but instead, install vmware on a blank hard drive.
However, you just said "VMware Server for Windows" and that's a little different than what I've used. I didn't realize you could get vmware that installs on the OS so please excuse my ignorance (I googled 'vmware server for windows' and did a little reading). I should have realized that you could but I've only looked at the package you install on a blank server.
Regardless, I don't believe you would want to install this on a DC. In my own experience I've learned you don't want to load too much on a DC. If you can run this on another, member server, I would go that route. At least this way if it does mess up at some point, it doesn't shut down your domain.
I'm just looking over your list of things you wish to accomplish. If you have 3 machines you could use, I would leave the DC as just a DC. I would put exchange on it's own server as well. I would likely put TS and VMware on a 3'd.
You might want to consider making the exchange server a DC as well and make it redundant.
Basic file server services could be supplied by the DC as well.
0
"The point I am trying to make is that I do not use RAID since I need all the space on the server "
You backing this up????
There are a number of layers you employ to protect your data. No raid means you are down to only backups. If you don't backup you have no protection at all.
no protection is begging for wholesale failure
0
Curt, The server isn't in production. Someone has it right now and I am going to get it in a few weeks and right now, I am just using a Pentium 2 450 MHz system with 384 MB of RAM as a DC and a Pentium 4 3.00 GHz with 1 GB of RAM as a Domain Controller with a Terminal Server VM on it (the terminal server performance is terrible on this machine).
I excuse your ignorance, I also never knew VMware could run without an operating system and now I know what you mean. I thought running a Domain Controller under a VMware would not make any sense since the Host won't know where the DC is at, i.e. the VMware is at, but since you mentioned VMware to be its own operating system, I may consider that. I just hope using the VMware for filesharing for both the Exchange and Domain server will be fast over a single Gigabit Ethernet off the server and that I can also directly map a 500 GB hard drive for file storage.
How does this sound?
Wanderrer, I take your concern that I should at least be using RAID or Backup, I will consider investing on more 500 GB or 1 TB hard drives for this operation. I want to consider though that I've been using 200 GB hard drives in these servers and they have NEVER failed since 2006. One server's hard drive is actually from 2003. I may take your advice though.
UPDATE: Oh another thing Curt, My server only has 2 GB of RAM. Should I upgrade to 4 GB before installing VMware ESX Server?
0
I'm on Curts side in this. The better solution is usually to run vmware ESXi on a blank drive and run your o/s on top of that. It makes no sense at all to install vmware on win2003 and then a virtual machine on top of that in this specific case, your system will get really slow (at least with my standards), the load on the hardware will be constantly high, so it's like asking for trouble. Plus, the routing in vmware for windows is a bit f-ked up in some versions so you'd be better off with anything else.
If I were you I'd keep the load as low as possible, i.e. no extra o/s running that are not needed, especially with a Pentium D CPU. If you're setup were dual XEON quad cores it would have been different.
But even better, you can run win2003 with exchange on one stand-alone server, and you don't need to get the SBS version. Just read a little on petri.co.il where he explains it all, I think the article is called 'Configure Exchange on single server scenario' or something like that.
You've been lucky with your harddrives, but statistics talk against you, sooner or later you'll have a crashed drive and when you do you'll love yourself for setting up that RAID1 array, trust me. With backups only it's still a days work to get everything back to where it was.
Good luck.
0
I even found the article. It's for setting up web access to exchange, but if you don't need web access you only need to install exchange and you're done.
0
Pentium D CPU. If you're setup were dual XEON quad cores it would have been different.
^ Thats what I am trying to ask. Should I upgrade to a E6600?
I asked the same question in overclock and they say that my setup is fine:
http://www.overclock.net/servers/58...
I am also thinking of tossing my Server Class 2 GB PC 5300 RAM to Desktop PC 6400 Memory, which is 4 GB of RAM.
0
drive from 2003 and no backups? Apparently your data is not important. Fast car on a short pier.
Do be clear backup and raid are not the same things. For example raid protects you if a drive fails but you remain operational. Backup doesn't do that.
Backup helps if someone overwrites a critical file with a blank one. Raid doesn't help you with that.
0
Lots of opinions here. To the original poster:
You CAN run Exchange on a DC. BUT this isnt a recommended configuration from MS for a number of reasons. (fairly ironic taking into account SBS.. hey ho..) Exchange will run happily on a DC. But if you are ever in a DR scenario whereby you need to move Exchange to another server you will run into many problems. That said if its servicing 30 users or less and speced up well there should be no foreseable problems. Just ensure your solution is scalable for your users requirements. If you anticipate growth then use seperate servers.
Additionally stick with ESX or ESXi. ESXi is free. But is limited in comparison to ESX/Vsphere. Going by your requirements ESXi will be fine. Note ESXi is its own proprietary Linux/Unix kernel that runs on a barebones system that allows you to get full use of the underlying hardware. Dont put VMware Server on top of an existing windows installation as you wont get full use of the hardware and additional server resources will need to be dedicated to the Operating System underneath VMware Server.
0
To Phatsta
I even found the article. It's for setting up web access to exchange, but if you don't need web access you only need to install exchange and you're done.
http://www.petri.co.il/how-can-i-co...
-----------------------------------------------------------------------------------------
Thats not web access. OWA is part of the Exchange suite. That link is for RPC over HTTP(s) which is essentially a MAPI connection to Exchange from Outlook over the internet over SSL/HTTP to Exchange. In other words run your outlook client native to Exchange without having to use a VPN. Its a popular solution amongst Exchange managed services. Im not sure how that fits into the original posters requirements?
0  |
 |
 |
| Login or Register to Reply | |
| Login | Register |
| Ads by Google |
