Updating outlook mailbox of user

Hello Stephane,

Thanks for the info.

We always start that activity at night, but when users logon to outlook in the morning they see that their mailbox is updated.

Because this is the first time that the local ost file makes contact with the Exchange server. It sometimes takes as much as 2 hours before the mailbox is updated. What does this mean for archiving large groups of users with limited bandwith.  I thought that users only see the impact of the archiving when you start the second activity ( delete-historical or shortcut-historical)

What properties are added and how can I see this?

With kind regards,

Dennis

Hello DS1972,

When an Archive Activity is ran against a users mailbox it will add some proprieties to the messages it archives.

We often recommend, for users that are on low bandwidth or limited bandwidth, that the Archive tasks be run at Night, thus minimizing the impact.

Hopefully this answers your concerns.

Regards

Stephane

Stephane,

Thanks for your info.

This does mean that our migration time is going to be increased dramatically.

I really thought and I was always informed by EMC and their partners that we could do the archive - historical activity first, without any user impact.

And that the second activity, in our case the shortcut-historical activity was done with smaller groups of users.

Is this going to be improved in newer versions?

Is it also true that their is no direct link between AD and the EMC SourceOne Environment.

Kind regards,

Dennis

Dennis,

Your observations are correct and unfortunately this is how it works.

When we archive a message we add the following 3 Message Propreties :

ExArchivedFodlers
EXLastAccessedTime
EXMD5

To see these propreties, you would need a program like MFCMAPI.

See this URL :

http://support.microsoft.com/kb/291794

The workaround that I can suggest at this time would be to archive in smaller date range. Instead of doing everything older than XX Days, you would do a Date Range using the "Dated" radio button when creating the activity. This would minimize the OST updates required for the users.

Hopefully this answers your questions/Concerns.

Stephane.

Dennis,

You were informed correctly that it does not impact users. However, I would add "on Normal/High Bandwith Networks"

The Propreties added to the messages are required for the basic functianlity of Source One and these propreties cause Outlook to see these as new messages thus forcing the OST updates. There is no plan to change this, mainly because there is no way to change this.

Regards

Stephane

Stephane,

Thanks for your information. This really going to slow down our migration and we also need to update all our current activities.

Do you have a document to show hidden properties via the MFCMAPI?

With kind regards,

Dennis Streefland

Dennis,

I understand the impact on your deployment, What other customer in your situation have done, is warn the users ahead of time of the OST updates. For example, your user community would receive an e-mail say 1 week ahead of time letting them know that on the morning of X of July the may experience slowness of Outlook while the OST file refreshes due to maintenance. A follow up e-mail is done the day before and one more e-mail is sent once the maintenance is over.

The above scenario has worked well for many customer in your situation and was well accepted by the user community as it is a one time event.

As for the documentation of the hidden proprieties, we don't have this readily available at this time. The previously mentioned proprieties are the Only ones Source One adds at the time of Archival.

Regards

Stephane