choldsworth
asked on
Changing Outlook Exchange Server Settings automatically
Hi Guys,
I'm going to be replacing my Exchange 2003 server. All clients are running Outlook 2003. Once everything is moved from the old Exchange server to the new one, the old one will be taken offline, and rebuilt and branded as something else.
My question is, what is the best way to change the Exchange Server settings in Outlook for all of the clients? Is there a way to do this in group policy, or with a logon script? Or will Outlook automatically pick up where the mailboxes are?
I had also read on here someone's suggestion of using a CNAME value in DNS to point the old name to the new server. This seems like a good idea and one that would work for me... but is there a better way?
Thanks,
Chris
I'm going to be replacing my Exchange 2003 server. All clients are running Outlook 2003. Once everything is moved from the old Exchange server to the new one, the old one will be taken offline, and rebuilt and branded as something else.
My question is, what is the best way to change the Exchange Server settings in Outlook for all of the clients? Is there a way to do this in group policy, or with a logon script? Or will Outlook automatically pick up where the mailboxes are?
I had also read on here someone's suggestion of using a CNAME value in DNS to point the old name to the new server. This seems like a good idea and one that would work for me... but is there a better way?
Thanks,
Chris
ASKER
The old one is running Exchange 2003 as well.
To add to the story, most of our employees are out at client sites. They only visit the office a few times per month (some of them not even that often), and either check their mail through webmail (which won't be a problem) or RPC over HTTP.
Also, management has decided that the old server needs to be redeployed by the middle of next week in a new role (new name as well). I will be moving mailboxes, etc. on Saturday. I had originally planned to take the old server down on Saturday, but I suppose I could leave it up until Monday.
If I did take the old server down on Saturday, would the clients still pick up on the new server, or would they begin to fail when trying to connect? In this case would I then need to go to the CNAME method?
Chris
To add to the story, most of our employees are out at client sites. They only visit the office a few times per month (some of them not even that often), and either check their mail through webmail (which won't be a problem) or RPC over HTTP.
Also, management has decided that the old server needs to be redeployed by the middle of next week in a new role (new name as well). I will be moving mailboxes, etc. on Saturday. I had originally planned to take the old server down on Saturday, but I suppose I could leave it up until Monday.
If I did take the old server down on Saturday, would the clients still pick up on the new server, or would they begin to fail when trying to connect? In this case would I then need to go to the CNAME method?
Chris
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
cname might work, but I've never heard of it before. You could try it I guess, just by turning off the old exchange server for a while during the process. If it fails, turn it back on...
D
D
ASKER
Hey, I learned something new :)
Good luck!
Good luck!
How many clients do you have? and make sure of the server name on the Outlook. The reason I am asking this is because for my migration I did the rerouting from the client side.If the number of clients is small then that is the best option. I will work and It worked for me.
This is the procedure I followed.
1) After installing the new server with exchange 2003(with a different name) and migrating the mailboxes from the old server, I let the two servers run simultaneously for a day.
2)Just disconnected the old server, reconfigured the outlook clients (safer I suppose) to point to the new server and checked if the are able to send and receive mails bot internally and externally.
3) After confirmation I removed the old server.It is now my windows update server.
regards,
Einy
This is the procedure I followed.
1) After installing the new server with exchange 2003(with a different name) and migrating the mailboxes from the old server, I let the two servers run simultaneously for a day.
2)Just disconnected the old server, reconfigured the outlook clients (safer I suppose) to point to the new server and checked if the are able to send and receive mails bot internally and externally.
3) After confirmation I removed the old server.It is now my windows update server.
regards,
Einy
I learned something new too :). If the CNAME method works, that's great.
either way, at least you have your options. be sure to read through that article so you don't miss anything.
let us know how it turns out.
kris.
either way, at least you have your options. be sure to read through that article so you don't miss anything.
let us know how it turns out.
kris.
ASKER
We only have approx. 50 users, but the problem is that about 40 of them are out at client sites. This means that I wouldn't be able to physically do it myself, I would have to trust them to change their own settings (which for some reason I don't feel comfortable with - nor do I want 50 phone calls on Sunday morning :)
And thanks for the article Kris, it looks like it will be a good roadmap for ensuring that I don't miss anything.
I'll let you guys know how it goes :)
And thanks for the article Kris, it looks like it will be a good roadmap for ensuring that I don't miss anything.
I'll let you guys know how it goes :)
ASKER
Hey Guys ... one other question that comes to mind that I'm wondering if I'll have problems with is OWA.
Is there anything special I need to do in order to get OWA to work properly on the new server?
I know I'll have to make Firewall / DNS adjustments, and setup the SSL certificate in IIs, but is there anything on the Exchange server(s) itself that I will need to worry about?
Thanks!
Chris
Is there anything special I need to do in order to get OWA to work properly on the new server?
I know I'll have to make Firewall / DNS adjustments, and setup the SSL certificate in IIs, but is there anything on the Exchange server(s) itself that I will need to worry about?
Thanks!
Chris
ASKER
FYI everyone, the exchange migration went well, with very few hiccups. Thanks for all the help!
I'm going to give the points to kristinaw for that link, as it was very very helpful.
Thanks!
Chris
I'm going to give the points to kristinaw for that link, as it was very very helpful.
Thanks!
Chris
thanks, but did you wind up creating a cname record or leaving the old server up? just wanted to know if cname worked.
kris.
kris.
and glad it went well!
kris.
kris.
ASKER
I did the migration on Saturday, and took the old server down on Tuesday. This allowed some people (mainly those who actually come into the office) to have their office settings changed automatically. When I took down the old server on Tuesday, I implemented the CNAME entry and I'm assuming that no complaints means it's working :).
what version of exchange is the old one running?
kris.