I love the new Alternate Access Mappings feature in MOSS 2007 (not available in WSS) but it can be a major pain in the behind. One of the things you probably will stumble upon when installing MOSS is the need to expose some or all of the content to the outside. So far I've been lucky enough to deal with situations where it's all or nothing, making life somewhat easier. Still, there's quite a few things that can foul up the waters, including AAM. Now, if you're going to expose MOSS, or any web site, to the outside you will want to do this via https (at least not plain old http) which means that you'll need to make sure that MOSS understands https:/... access and, most likely, start using https internally as well. This involves, besides installing certificates, changing the AAM settings. The thing with AAM is that it (AFAIK, correct me if I'm wrong) controls all the automatic URL's generation throughout that collection. This means that if you need to change the My Site location from http://mysite.corporate.com to https://mysite.corporate.com you need to update the AAM to reflect this. To do this you change the Default mapping for the My Site AAM collection from http://mysite... to https://mysite... If you fail to change the AAM before you update the My Site location MOSS happily and without telling you changes back to http://mysite... If you're really lucky you'll get something along the lines of https://mysite.corporate.com:80 which, of course...