Have primary exchange server 2003 on server "Kumu". Have installed second server "Huli" with exchange server 2003, added service packs to windows server 2003 standard and exchange server 2003. Am running Native mode on exchange.
Intent is to move all users to new server, leave it as exclusive exchange server. Kumu also hosts IIS and some other things besides being a BDC.
I can see both servers in the Exhange administration view.
Select a mailbox, exchange tasks, move mailbox, successful with no errors with move.
User logs in, tries to open Outlook and gets message: "Cannot start microsoft outlook. Unable to open the outlook window. The set of folders could not be opened."
Can ping both Huli and Kumu from workstation. (happens on different workstations as well) Opening Control panel, mail, modify existing profile and can see fully qualified path for huli.localname.ourdomain.com
If delete profile, can create a new one, using huli as the server name (need not be FQDN) and entering the username and check name results in it finding correct account. If I enter kumu as servername, after check name, it shows FQDN for huli as the exchange server for that user. Still gets same error message.
I've tried moving three different users, all with the same problem. In any of the test cases, moving them back to Kumu results in being able to access the mailbox (after delete and create mail profile).
I'm almost embarrassed to ask this because I probably forget something simple during the setup of the new server. Any ideas on what is wrong?
Thanks
--Rick
Intent is to move all users to new server, leave it as exclusive exchange server. Kumu also hosts IIS and some other things besides being a BDC.
I can see both servers in the Exhange administration view.
Select a mailbox, exchange tasks, move mailbox, successful with no errors with move.
User logs in, tries to open Outlook and gets message: "Cannot start microsoft outlook. Unable to open the outlook window. The set of folders could not be opened."
Can ping both Huli and Kumu from workstation. (happens on different workstations as well) Opening Control panel, mail, modify existing profile and can see fully qualified path for huli.localname.ourdomain.com
If delete profile, can create a new one, using huli as the server name (need not be FQDN) and entering the username and check name results in it finding correct account. If I enter kumu as servername, after check name, it shows FQDN for huli as the exchange server for that user. Still gets same error message.
I've tried moving three different users, all with the same problem. In any of the test cases, moving them back to Kumu results in being able to access the mailbox (after delete and create mail profile).
I'm almost embarrassed to ask this because I probably forget something simple during the setup of the new server. Any ideas on what is wrong?
Thanks
--Rick