[tweetmeme source=”stalehansen” only_single=false]In Exchange 2010 you need to set the Internal URLs for various services on the Client Access Server. Outlook 2007/2010 uses Autodiscover to connect to the Exchange server. If the Internal URLs are configured wrong you could get certificate errors when logging on to Outlook as well as errors when using free busy and oof services internally. Also when deploying Outlook Anywhere you need to configure the External URLs correct for the same services to work.
This script may come in handy in the following scenarios:
- Initial configuration, avoid typos
- Expansion in the infrastructure with load balanced CAS
- Change in internal FQDN if you change certificate name
- When you have a total disaster on site 1 and need to fail over to a second site with a passive DAG server that holds all server roles
Please keep in mind:
- The Script is developed for Exchange 2003 coexistence and migration scenarios
- The script must not be run in an Exchange 2007 coexistence and migration scenario
- For InternalURL the script will look for a CASArray (It is recommended to create a CASArray in any scenario)
- The script assumes there is only one ADsite
About the script:
- First you will be presented with som choices on what to do
- InternalURL will autoconfigure based on CASArray
- ExternalURL will prompt for public FQDN and assume one external address
- Will use same FQDN for OWA, ActiveSync, Autodiscover and so on
- Will prompt for Exchange 2003 URL
- All configuration will output the changes made
Update 27.05.2010:
- Added support for Exchange 2007 and Exchange 2007/2010 coexistence scenarios.
- The script will check for Exchange version before applying any settings.
- When applying Exchange 2010 Internal URL the script will match the CAS servers to the correct CASarray in the correct ADsite
Update 28.05.2010
- Added option for checking current configuration
- Corrected some errors on the Exchange 2007 configuration and listing of URLs
- Tested in Exchange 2007 only deployments and Exchange 2010 and 2007 coexistence deployments
The Script can be viewed and downloaded here: https://msunified.net/exchange-downloads/script-internalexternalurls-ps1/
msunified.net 
[…] is the PowerShell script which can be found on Stale’s blog here https://msunified.net/2010/05/07/script-for-configuring-exchange-2010-internal-and-external-urls/ or a direct link […]
Maybe add in the script the possibility to set the OOF Url:s to?
Otherwise very handy and good script.
/JB
Hello JB, This is already included by this script… the EWS url is the one you’re looking for !
Enjoy
Achille
that’s excellent job, thank you so much!
but I couldn’t understand this, “It is not recommended to have the same name for cas array and internal/external url”
our cas array and internal/external url are the same. is it microsoft recommendation?
Yes, this is a microsoft recommendation
Thanks Stale, do you have any idea as to why?
As far as I have heard there is no good explanation. I think this was commented at the last TechEd North America, and they did not come up with a good explanation. Its one of those cases where you need to accept it, and avoid the unforseen issues regarding this.
[…] Remember Exchange Web services and autodiscover for the full integration. I recommend using A record for each mailsipdomain in your deployment. Also remember to specify internal urls on Exchange […]