Script to change Exchange Server address in Outlook 2010 on all workstations
We have recently recovered from a disaster and our Exchange servers are now active in our main office however, I can see that a number of users are still connecting to our disaster recovery Exchange servers.
Is there a way I can run a script or deploy a GPO that will automatically change all users Exchange Server address in Outlook 2010?
I can't find a simple way of doing this.
Is there a way I can run a script or deploy a GPO that will automatically change all users Exchange Server address in Outlook 2010?
I can't find a simple way of doing this.
You need to check which CAS server is you user mailbox database pointing to ...... and then see with restart of Outlook
Outlook 2010 should auto redirect .... what is the Exchange version ?
- Rancy
Outlook 2010 should auto redirect .... what is the Exchange version ?
- Rancy
www.richprofile.com
Automate Outlook Profile Creation Using PRFPATCH
http://technet.microsoft.com/en-us/library/cc768089.aspx
Check if one of these can help but i guess if its Exchange 2007 or 2010 with Outlook 2010 it would work automatically.
- Rancy
Automate Outlook Profile Creation Using PRFPATCH
http://technet.microsoft.com/en-us/library/cc768089.aspx
Check if one of these can help but i guess if its Exchange 2007 or 2010 with Outlook 2010 it would work automatically.
- Rancy
ASKER
sbrozinick, I cannot see where you can configure the Exchange server address in GPO. i do not think it's possible
rancy, im investigating your option now :)
rancy, im investigating your option now :)
Have you tried running the following and then have the users restart their machines:
Hope this helps!!
Set-MailboxDatabase DB1 -RpcClientAccessServer “mail.domain.com”Hope this helps!!
You cannot just change the RPC Client Access Server without having the RPC CAS Array in place. Furthermore, the clients will not pick up that change because the current system is live.
Going forward, an RPC CAS array is the best way round this issue, using a host name that does NOT resolve externally.
The problem with an RPC CAS array is that the clients will not pick it up automatically, so to use it you either need to repair the profile manually or use one of the above methods to update the profiles for you.
If you have a multiple site Exchange environment, then you need an RPC CAS array.
Simon.
Going forward, an RPC CAS array is the best way round this issue, using a host name that does NOT resolve externally.
The problem with an RPC CAS array is that the clients will not pick it up automatically, so to use it you either need to repair the profile manually or use one of the above methods to update the profiles for you.
If you have a multiple site Exchange environment, then you need an RPC CAS array.
Simon.
Rancy/the_omnific - the Office Administrative Template must be installled and the Office Customization Tool must be installed to configure a GPO for the Outlook configuration or other Office applications in the suite. I do not like to do it this way becuase I use images and then configure the profile once logging in as the user but it works. You can find the configuration and points at Microsoft.com and howto-outlook.com.
ASKER
Hi Simon
We do have a CAS array but we have only just recovered from a disaster. When the disaster happened everyone's Outlook profile automatically repointed to our Exchange servers in DR. Now that our servers in our production enviroment have been restored I would like to prevent users from connecting to the DR site.
Thanks
We do have a CAS array but we have only just recovered from a disaster. When the disaster happened everyone's Outlook profile automatically repointed to our Exchange servers in DR. Now that our servers in our production enviroment have been restored I would like to prevent users from connecting to the DR site.
Thanks
ASKER
At present there appears to be no way to force clients to use the RPC CAS Array. Manual intervention in the form of repair of Outlook profile is required (which we have been doing).
Microsoft's answer to this is to remove the old server completely from the domain and then allow autodiscover to kick in. Well, we are obviously not going there as the DR still exists.
Microsoft's answer to this is to remove the old server completely from the domain and then allow autodiscover to kick in. Well, we are obviously not going there as the DR still exists.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
"If you have Rollup 4 for Exchange 2010 SP2 installed and then stop all of the Exchange and IIS services on the second server, that should force Autodiscover to kick in."
I'm trying this next week!
I'm trying this next week!
Now,
1.Open GPMC
2.In the console tree, right-click Group Policy Objects in the forest and domain in which you want to create a GPO. For example, browse to Forest name, Domains, Domain name, Group Policy Objects.
3.Click New.
4.In the New GPO dialog box, specify a name for the new GPO, and then click OK.
5.Right click and click Edit. Then edit the GPO accordingly.
If you choose to use a script in the GPO or only a script this (http://www.howto-outlook.com/howto/deployprf.htm) will help. Because Oulook 2010 is very good with using autodiscover remember to stop the information store of the disaster recovery before deployment of the GPO, script, or both.