Hi there, we're in the middle of merging two networks, or better put, migrating 2 separate old networks to 1 new network. Currently the new network has users from one of the 2 old networks. In the new netwerk exchange has already been configured, but it's not currently being used. They still use KPN Online Exchange (very similar to BPOS). Outlook 2007 thus connects through RPC over HTTPS to an external party (and this is the only configured exchange account). Exchange 2007 already has the email address configured for the users as well, but since the MX records don't point here, nothing comes in. Outlook seems to function fine, with the exception that it nags about a password for the local exchange server (or so it seems, the password prompt dialog has the local exchange server name in it) every 30 seconds. This is extremely annoying. I presume it has to do with autodiscovery. Anyone know how to solve this? I don't want to tear down the entire exchange environment now just to rebuilt it in a couple of months. Since there are no easy ways to export all 70+ mailboxes, they will be running next to each other for quite some time too, since we'll need to export individual mailboxes to PST and import them again.

As you say this is a temporary requirement. Try adding a HOST entry for the KPN Online exchange on the local desktop and verify. Once done , reconfigure outlook pointing to the Hosted exchange server address. Thanks SumanthSumanth G

I don't quite get your comment. The hostname of the KPN online exchange resolves fine, it also connects just fine (to KPN online exchange). Whilst connected it whines for a password for the local exchange server, which is not configured on the client and I presume gets automatically detected. The password prompt dialog has the name of the local exchange server in the titlebar. This is double strange to me. First off, the local exchange server isn't configured on the client, I presume autodiscover through the AD domain or something causes it to want to connect to it. Secondly... the user has a mailbox there and is signed in to the domain, so basically it should just use it's kerberos ticket to authenticate to it.

The behavior is expected when you do a migration or in a coexistence phase with bpos and with an on premise Exchange server. Even though you're on premise Exchange server is not being used, the fact that it's installed has created the autodiscover SCP records in AD and will take priority over bpos. The workaround until the migration is over is to configure clients registy to disable autodiscover or use localxml to point to bpos. Potential Autodiscover Issue During E-Mail Coexistence http://social.technet.microsoft.com/Forums/en-US/onlineservicesmigrationandcoexistence/thread/d6c69c69-6524-493b-a0c6-21c79e146ce7 James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Thanks James :) Not a too descriptive subject on that article but it surely covers the issues :D.