It will soon be time to renew our SSL cert for Exchange, used for OWA, Outlook Anywhere and Autodiscover, to name a few. I've already asked some questions about certs and as I'm waiting for our credit to become effective with the CA (we just purchased a renewal), I thought of another question I've actually been wanting to ask for a while. Should we rename Internal URLs to match External URLs (E2K7)? Now, I've already done this and do not intend to go back and redo everything. So, yes, my internal URLs, like the one for OWA, match the external URL. I'm more interested for future reference. I've heard of two reasons for: 1) Conceal the name of your internal servers, whose name would otherwise appear on the cert (if you know where to look). 2) Limit the number of names on your SSL cert 3) Possibly simplify access for users who enter the URL manually (assuming we are not using redirection). As for number 3, I simply modified a .vbs script, executed at logon, that creates a shortcut with the proper URL on the desktop of each user. For use from home, we created instructions on how to create such a shortcut manually (you only need to do it once). Working more recently with Exchange 2010 (for practice), I see that the setup wizard will configure all these URLs for you quite nicely, except that the Internal URLs reference the FQDN of the internal servers. So... Since the Exchange 2010 wizard takes care of this for you, is there a compelling reason to run Set-OWAVirtualDirectory, etc, etc, and change all these internal URLs so they match the external ones?