I'm actually getting ready to write a script for this, in the next couple of days, as this also comes up in Exchange 2003 -> Exchange 2010 migrations (the old URL becomes invalid).
What the PRF file is doing, actually, is creating a new profile, the old one is renamed. That's why you get a new OST (new GUID in the profile). What you WANT to do is just edit that entry in the user's existing profile. I've got the beginnings of a script here <http://theessentialexchange.com/blogs/michael/archive/2009/07/21/mapi-in-the-registry-or-setting-the-quot-use-http-first-quot-boxes-via-vbscript.aspx> which should just need minor tweaking to fit your needs. Without even looking it, it seems likely you'll have to edit three values in the profile: the certificate common name (strictly speaking this is the "Mutual Authentication Principal Name"), the name of the RPC proxy server, and the Exchange server internal name. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Damien Solodow [mailto:[email protected]] Sent: Friday, February 05, 2010 2:47 PM To: MS-Exchange Admin Issues Subject: Update RPC proxy in Outlook profiles Got a bit of a fun one. Outlook 2007 mostly on XP, connecting to Exchange 2003 in a Windows 2003 forest. I need to update the RPC Proxy (aka Outlook Anywhere) settings on the Outlook clients as the current URL will be invalid within a few months. I've tried creating a PRF file from the Office Customization Wizard and it does change the profile, but... The PRF creates a backup copy of the default profile (annoying but not major) but it also causes a new OST file to be created. This I would rather avoid as all our users rebuilding their OSTs might have a minor negative impact on the WAN links. Any suggestions? DAMIEN SOLODOW Systems Engineer 317.217.6881 (office) 317.217.6851 (fax) HARRISON COLLEGE 603 East Washington Street Suite 600 Indianapolis, IN 46204-2646 www.harrison.edu
