Outlook and Exchange 2003
Printed From: ForensiT
Category: ForensiT Support
Forum Name: Move Computer
Forum Description: User Profile Transfer Wizard questions, suggestions, comments and bug reports
URL: https://forum.ForensiT.com/forum_posts.asp?TID=21
Printed Date: 27 Mar 2026 at 2:13am
Software Version: Web Wiz Forums 12.03 - http://www.webwizforums.com
Topic: Outlook and Exchange 2003
Posted By: dhurley
Subject: Outlook and Exchange 2003
Date Posted: 05 Apr 2007 at 2:56am
|
We tested the individual version to see how it would work before purchasing a business solution and we are wanting to move all of our computers to a new 2003 domain and new exchange 2003 server. The computer profiles move just fine, but Outlook 2003 does not connect to the exchange server. We use Cached Mode in Outlook, so it creates an OST file in the users profile. When we launce Outlook after the migration, and change the mail server to the new mail server on the new domain, everytime we launch Outlook now, it prompts us to work off-line or connect because Outlook is in "recovery mode". We cannot figure out how to get this to go away....
Any ideas on Exchange and Outlook 2003 after the migration?
Thanks ------------- Dan Hurley |
Replies:
Posted By: Support
Date Posted: 10 Apr 2007 at 11:58pm
|
Hi,
You've posted this in the "Move Computer" section. Does your question relate to the Transfer Wizard (moving profiles between machines) or User Profile Wizard (moving profiles between domains)? From what you say, it sounds like you are using User Profile Wizard, so we'll assume that's the case. (Let us know if it isn't
 )User Profile Wizard does not currently migrate Exchange Accounts. What will normally happen is as follows. User Profile Wizard will migrate the user's profile so that it can be used by their new domain account. The logon details for the existing Exchange Server will be retained. This means that if you are not migrating Exchange Servers, the user can continue to use Outlook without any problems. (The user will need to re-enter their password once, because Windows encrypts the password using their credentials.)
We don't know of any problems if you subsequently change the user's mail server. The user's new domain account will have the same access to the OST file as their original account; we don't think that will be the problem here.
|
Posted By: dhurley
Date Posted: 13 Apr 2007 at 4:03pm
|
Thanks, we are only using the user profile wizard as we are using the same machines, but wanrt to transfer the users profile to the new domain that the machine will be joining, that parts works great!
However, we do have a brand new exchange server (new server name and new IP address), but the same AD and mailbox names. The OST file is the real problem. The only fix I have found is to delete the local Outlook Profile and recreate it with the new AD and mailbox credentials. It really gets hung up using the old OST file since the SID is different on the new domain. Outlook becomes out os sync...many errors pop up
When we buy the corporate version and use a script, is there any switch settings that might help us with this?
We have to hit each desktop anyway as we have to change printers, etc. since our IP schema as changed as well. so, we can delete and Outlook profile and recreate no problem....
this is the only piece that can make this tool 100% solid....Outlook is the problem. ------------- Dan Hurley |
Posted By: Support
Date Posted: 16 Apr 2007 at 1:51pm
|
Hi Dan, Are you getting the error Exchange is currently in recovery mode. You can either connect to your Exchange server using the network, work offline, or cancel this logon? As you say, this error is caused when the locally cached copy of the mail file (the .ost file) and the Exchange mail file are out of sync - as of course they would be if you've moved Exchange server. One way to fix this is to disable "Cached Exchange Mode" in Outlook, restart, and then re-enable Cached Exchange Mode again with the new Exchange server. (It may well be possible to script this.) Although User Profile Wizrd doesn't currently support Exchange server migration, we are always trying to make it more solid. If you have any more details on the errors you're seeing, or you have any screenshots, please email mailto:support@ForensiT.com - support@ForensiT.com . This will help us to reproduce the problem. Many Thanks.
|