Thomas
asked on
Question on Exchange Install
Hi,
I have a question on an exchange install. This is the first time I do this and I am looking for a best practice kind of tip. I have just upgraded to Windows Server 2003 Enterprise from a Win SBS 2003. I had to do this because I bought a fast new budget server that has a quad Core processor and SBS did not like this for some reason. Since I found out that the 3 times more expensive Enterprise version that not even come with Exchange as the SBS does, I did go out and coughed up another Grand to buy Exchange 2007 to install. Turns out that exchange does not want to run on my new $700 server either because it has 4 cores. This is very frustrating since I specially purchases one of the cheapest servers with a good CPU not thinking that MS now want to charge premium for my 4 User network.
Well I do not have to budget to buy now the enterprise exchange which has a few extra features that we do not need at all. So I will probably end up reusing the old server which is a dual Pentium 1GH to run exchange.
This brings me to the question which is: what is better to install the exchange on the SBS and making the SBS a domain which is then joined as a secondary domain to the enterprise server or should I make it a simply file server as part of the main domain.
Also is there any issue running this on a separate server (pro/con). Is there anything special I need to watch out for? I guess if I would make it a sub domain I would need to manage 2 active directorys?
Thank you for the assistance on this. Any tip is welcome. maybe there is even a way to get exchange installed on my 4 core cpu without spending another 2 grand.
Best wishes,
thom
I have a question on an exchange install. This is the first time I do this and I am looking for a best practice kind of tip. I have just upgraded to Windows Server 2003 Enterprise from a Win SBS 2003. I had to do this because I bought a fast new budget server that has a quad Core processor and SBS did not like this for some reason. Since I found out that the 3 times more expensive Enterprise version that not even come with Exchange as the SBS does, I did go out and coughed up another Grand to buy Exchange 2007 to install. Turns out that exchange does not want to run on my new $700 server either because it has 4 cores. This is very frustrating since I specially purchases one of the cheapest servers with a good CPU not thinking that MS now want to charge premium for my 4 User network.
Well I do not have to budget to buy now the enterprise exchange which has a few extra features that we do not need at all. So I will probably end up reusing the old server which is a dual Pentium 1GH to run exchange.
This brings me to the question which is: what is better to install the exchange on the SBS and making the SBS a domain which is then joined as a secondary domain to the enterprise server or should I make it a simply file server as part of the main domain.
Also is there any issue running this on a separate server (pro/con). Is there anything special I need to watch out for? I guess if I would make it a sub domain I would need to manage 2 active directorys?
Thank you for the assistance on this. Any tip is welcome. maybe there is even a way to get exchange installed on my 4 core cpu without spending another 2 grand.
Best wishes,
thom
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SBS 2008 will be 64bit only too.
ASKER
Thanks for the info, so it will be version 2003 that we keep using.
ASKER
I guess that a 64bit windows can only be installed on computers with a specific 64bit CPU?
I wonder how small business can afford systems like this if you have to upgrade everything just to use this stuff.
Thank you for the assistance on this, I now have to find some solutions for this but I think I keep the SBS and use Exchange 2003. I simply need a email server that works with MSCRM so 2003 should do the trick I hope.
Best wishes,
thom