BKGarry Posted February 11, 2008 Posted February 11, 2008 OK so i am moving my exchange 2003 to a different server, and i have read most details, but i have two questions. 1. Do I make the exchange server a DC or not? 2. Can I make two manual DNS records in win 2003 to point the name of both the new and old mail servers to the IP address of the server? Not too bad ay, Gaz
PiqueABoo Posted February 11, 2008 Posted February 11, 2008 1) Not. 2) There are several answers. What are you trying to achieve?
FN-GM Posted February 11, 2008 Posted February 11, 2008 Nerver put Exchange on a DC, can cause lots of problems. I would make your exchange server a member server.
djones Posted February 11, 2008 Posted February 11, 2008 Why not? I have installed and used (hammered in a couple of cases) Exchange 2000 & 2003 on several DCs and never had an issue. Small Business Server incorporates Exchange and this is an all-in-one-box type solution. Admitedly, there are some config changes that could/should be done to ensure optimum performance when installed on DCs but 'Exchange on DCs' isn't a major issue per se. I suppose it all boils down to level of use - if it is going to get/have to deal with significant throughput and abuse then it makes sense to be on its own dedicated, appropriately specced server that does nothing else - it is a significant database app after all. I would make your exchange server a member server. At the end of the day though, if you have the capacity (dedicated server), I agree with @FN-Greatermanchester's comment above. Dave.
djones Posted February 11, 2008 Posted February 11, 2008 (edited) Some bed time reading on the matter... http://hellomate.typepad.com/exchange/2004/02/exchange_on_a_d.html http://books.google.com/books?id=qtpnogWGbp0C&pg=PA30&lpg=PA30&dq=exchange+dc&source=web&ots=tKJzybGpiU&sig=fTrozePBd6uavUq1x7Toe9r-BR0 These next two relate to rectifying the only really significant 'issue' that I have come up against with having Exchange on a DC: http://www.msexchange.org/articles/Automating-Quicker-Exchange-2000-2003-DC-reboot.html OR (very similar article to the previous one) http://www.msexchange.org/articles/Speed-up-Exchange-2000-2003-DC-reboot.html Hope that helps! Edit: Sorry, I've just reread this thread and realised that this post doesn't really help the OP's questions but could be of use to others who do have a single server setup I suppose! Dave. Edited February 11, 2008 by djones
BKGarry Posted February 12, 2008 Author Posted February 12, 2008 Ok so no to DC, make sure i will make sure i install the AD connector, On the DNS side, The server needs to take the same IP as our old one (ISP rules) but all our staff are configured individually and i do not fancy redoing outlook on all of them, so if i can keep the old name and the new name pointing to the same static IP address it saves a hell of a lot of messing around
Kyle Posted February 12, 2008 Posted February 12, 2008 I've had Exchange 2003 on a DC for years. It was forced on us because it was the only hardware we had at the time. But according to Microsoft you should not install it on a DC. Its the same for 2007, they recommend you do not install it on a DC again. But this time its more important. If you install Exchnage 2007 on a member server you are no longer able to promote it to a DC. Likewise if it is already a DC you will not be able to demote it.
BKGarry Posted February 12, 2008 Author Posted February 12, 2008 So the DC question is answered, do not install it on a DC (AT ALL) and install it on member server with the AD connector. But what about my DNS question, i want to point both my old server name and new server name to the new server so i do not need to reconfigure all the staff PCs and Laptops. Gaz
Gatt Posted February 12, 2008 Posted February 12, 2008 I've had to install it on a DC here due to the lack of hardware to support it.. But yeah ideally i would have it on its own server.
gaz350 Posted February 12, 2008 Posted February 12, 2008 ofc Microsoft are going to say not to install it on a DC...... extra software costs, its how they rape you for even more money!!! Ofc if you want the best system every Major Service should have its own Host OS to itself. but ofc this is not always practical for budget constraints.
FN-GM Posted February 12, 2008 Posted February 12, 2008 So the DC question is answered, do not install it on a DC (AT ALL) and install it on member server with the AD connector. But what about my DNS question, i want to point both my old server name and new server name to the new server so i do not need to reconfigure all the staff PCs and Laptops. Gaz You don’t need to do that. When you move your mailboxes over to the new server it will automatically change the settings on the clients, that have been moved over. You don’t need to install AD connector it will sort its self out when you install. Z 1
BKGarry Posted February 12, 2008 Author Posted February 12, 2008 are you telling me all my mandatory and local (staff) profiles will autmatically update for outlook even if i turn the old MAIL server offline?
FN-GM Posted February 12, 2008 Posted February 12, 2008 Thanks for the thanks! Yes that’s correct. I am not sure but you might need to leave your old server online for a while so it knows its moved. Once everyone has been moved over simply turn it off. That’s what I did and it worked good for us. If you are running a script to configure outlook with the mandatory profiles make the alterations to the script. Z 2
BKGarry Posted February 12, 2008 Author Posted February 12, 2008 So let me get this right (Dummy Steps) 1. Install New Exchange server (anything special requiredd) 2. Use Exchange tools to move the mailboxes in AD (can't remember the other tool) 3. Let the new exchange server take on the new roles (i will recreate the madatory profile with the new server) 4. allow staff to connect to new exchange server (should automatically work) 5. after about a week, turn off the old exchange server (well uninstal exchange, runt DCPROMO /Demote and then switch off ready for formating) Is that it? Anything i should watch out for, both servers will be exchange 2003 enterprise. Gaz
FN-GM Posted February 12, 2008 Posted February 12, 2008 Sounds right. "2. Use Exchange tools to move the mailboxes in AD (can't remember the other tool)" The tools will be built in exchange. If you go to view all the mailboxes in system manager and move the mailboxes in there it will be easier. How many DC's do currently have now?
BKGarry Posted February 12, 2008 Author Posted February 12, 2008 4, 2 GCs (one was the exchange but moved that GC) so 3 will be enough once demoted
BKGarry Posted February 12, 2008 Author Posted February 12, 2008 Thanks for the help, roll on half term, it is going to be awsome
zag Posted February 14, 2008 Posted February 14, 2008 Dont forget when you decomission the old server to give the new server its public IP address Otherwise you wont get any incoming mail flow! 1
BKGarry Posted February 14, 2008 Author Posted February 14, 2008 I was going to do that anyways, the other question is that our mail comes in over a relay so should i point the new server straight to that Relay or the old server then change it when i change the IP? Gaz
BKGarry Posted February 14, 2008 Author Posted February 14, 2008 New one isn't installed yet (lol) Current one points to the relay, with our ISPs Static IP assignment for recieving the mail. Do i commect the new one straight to the relay then once i have installed it?
BKGarry Posted February 14, 2008 Author Posted February 14, 2008 no worries, i will point it straight to the relay and hope for the best!!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now