[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 259
  • Last Modified:

Outlook 2003 after domain has changed

Hi All,

we have one Exchange 2007 server and many OUtlook 2003, which are using the Cache mode.
We want to migrate these Outlook clients to a new domain but I fear that all clients will
create a new .ost file after login to this new domain and starting outlook, because
a new profile will be created. That would ffaect the MPLS line and the whole network traffic.

Is there a workaround to setup outlook in this way that it will use the same .ost file as it is placed one each PC and profile. Is it possible to migrate the .ost file to the new user profile?

Is the .ost file encrypted and does it store old domain information, which can not be changed?

insi01
0
insi01
Asked:
insi01
  • 3
  • 2
2 Solutions
 
Alan HardistyCommented:
If you migrate the users mailbox to a new server / domain, then Outlook will need to create a new .OST file and this is going to hammer your MPLS line.

There is no way that the .OST file can be re-used.

If you can bring the clients in-house to suck down their .OST file, then that would save the MPLS line a lot of bandwidth.
0
 
insi01Author Commented:
Thanks for fast reply. May I asked you to give me a little bit more details about this.

That would be very fine.
0
 
Alan HardistyCommented:
Once you have migrated the users / mailboxes to the new domain, if you get the users to bring in their computers / laptops to the office with the new domain / Exchange server in, then open up Outlook and setup their profile locally, it will create the .ost file locally and populate it with mail much faster than it would down your MPLS connection.

Once completed, the users can take their computers away and only changes will need to be pushed / pulled from the server, so the MPLS line won't get flooded with data.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
insi01Author Commented:
Sorry for my confusing question. I mean if you maybe explain it, why it is not possible to use the same OST for the new domain profile.

:-)

insi01
0
 
Alan HardistyCommented:
I can't explain that more as I don't have that much technical knowledge about Outlook to that level - I just know that you can't do it.
0
 
CSIPComputingCommented:
Unfortunately an OST file contains information from the Exchange Server including the GUID (Globally Unique ID) of the mailbox.

You may find that there is a method of retaining this GUID during the migration, at which point it MAY be possible to re-use the OST, PROVIDED you do not create a new user profile and do no create a new mail profile (although you will need to update the Mail Server details in the mail profile).

Here's an overview "Understanding Mailbox GUIDs in Exchange"  Hope that explains the limitations of re-using an OST file, and why it's almost impossible to do!

http://technet.microsoft.com/en-us/library/aa996437(EXCHG.65).aspx
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now