Answered by:
Exchange 2007 and OST outlook 2010 advanced problem

Question
-
Dear All,
We have 3 offices.
The main office is in the UK and the others are remote sites in Europe and Israel. (connected with 15mb line) (all SMB offices)We have Exchange 2007 and outlook 2010.
For the 2 remove offices we have a lot of OST problems
The OST from time to time is getting “stuck” emails are not synced and we need to reopen outlook.
How can I know if my Exchange server is having the right traffic / communication (from bandwidth prospective it is ok because the line is 15 mb and we use 8 in the picks).
How can I guaranty that the OST file will be ok in the future?Thanks.
AlanThursday, February 16, 2012 12:21 PM
Answers
-
Cached mode, big mailboxes, and constrained bandwidth are a recipe for frustration, and there's no good fix that I know of.
The bigger the mailbox gets, the bigger the OST file will be. The bigger the OST file is, the more likely it is to get corrupted. When it gets corrupted you have to fight the bandwidth constraints to get it rebuilt.
IMHO.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
- Marked as answer by Terence Yu Friday, March 2, 2012 8:43 AM
Tuesday, February 21, 2012 3:14 AM -
For Outlook Anywhere Profile I wouldn't allow more than 512 MB on a mailbox and rest I will let them use via Archive.
You have to educate the users and ask them what emails are important to them, they will say current and that is the reson for commuters you do not want them to allow large mailboxes.
When you say 20MB internet line is enoguh, again i would compare it to how many users connect to the Exchange via Outlook Anywhere?
Where Technology Meets Talent
- Marked as answer by Terence Yu Friday, March 2, 2012 8:42 AM
Tuesday, February 21, 2012 5:12 PM -
90MS is not a bad ping time for OL Anywhere, but I have to wonder how "OK" that line speed is.
Line speeds are measured in bits per second. Mailbox sized in bytes. At 3GB it would take the entire capacity of that line over 20 minutes to rebuild an OST.
PS C:\> ((3GB * 8) /(20mb)) / 60
20.48Running in contention with other traffic, I think it could easily take hours to finish.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
- Marked as answer by Terence Yu Friday, March 2, 2012 8:42 AM
Tuesday, February 21, 2012 5:42 PM
All replies
-
How many total mailbox do you have?
How many mailbox in the remote offices?
Are you using MAPI or Outlook Anywhere?
Do you implement mailbox quota on the mailboxes?
What is the SP level of your Exchange?
What is the SP level of your Outlook?
Where Technology Meets Talent
Thursday, February 16, 2012 4:57 PM -
aroung 400
20 in Europe and 20 in Israel.
MAPI
No quota
Exchange 2007 SP3
Outlook 2010 SP1
Thanks
Sunday, February 19, 2012 7:30 AM -
outlook anywhere is chekckedSunday, February 19, 2012 7:49 AM
-
Monday, February 20, 2012 12:47 AM
-
How big are these mailboxes?
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Monday, February 20, 2012 1:17 AM -
aroung 3Gb per mailbox
Monday, February 20, 2012 7:57 AM -
Cached mode, big mailboxes, and constrained bandwidth are a recipe for frustration, and there's no good fix that I know of.
The bigger the mailbox gets, the bigger the OST file will be. The bigger the OST file is, the more likely it is to get corrupted. When it gets corrupted you have to fight the bandwidth constraints to get it rebuilt.
IMHO.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
- Marked as answer by Terence Yu Friday, March 2, 2012 8:43 AM
Tuesday, February 21, 2012 3:14 AM -
Thanks.
We have archaive solution.
1) in case the OST is no larger than 3 GB the OST will remain ok?
2) is the distance from the Exchange server itself make diffrents to the OST?
the bandwidth is ok (20MB direct to the main site) but it is still it a bit far , ping wlll reply time=90ms.
Tuesday, February 21, 2012 6:21 AM -
For Outlook Anywhere Profile I wouldn't allow more than 512 MB on a mailbox and rest I will let them use via Archive.
You have to educate the users and ask them what emails are important to them, they will say current and that is the reson for commuters you do not want them to allow large mailboxes.
When you say 20MB internet line is enoguh, again i would compare it to how many users connect to the Exchange via Outlook Anywhere?
Where Technology Meets Talent
- Marked as answer by Terence Yu Friday, March 2, 2012 8:42 AM
Tuesday, February 21, 2012 5:12 PM -
90MS is not a bad ping time for OL Anywhere, but I have to wonder how "OK" that line speed is.
Line speeds are measured in bits per second. Mailbox sized in bytes. At 3GB it would take the entire capacity of that line over 20 minutes to rebuild an OST.
PS C:\> ((3GB * 8) /(20mb)) / 60
20.48Running in contention with other traffic, I think it could easily take hours to finish.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
- Marked as answer by Terence Yu Friday, March 2, 2012 8:42 AM
Tuesday, February 21, 2012 5:42 PM