Skip to main content

Outlook 2013 OST File

Outlook 2013 introduced many improvements into the most famous e-mail client. Some of these are around Outlook data files (OSTs).

By default, when Outlook 2013 is installed, a new compressed version of the OST is created. I say “compressed” because apparently Outlook compresses several data fields/values in order to reduce the size of the OST file. This new compressed version is, allegedly, up to 40% smaller than OST files created by earlier versions of Outlook.

If you don’t want Outlook 2013 to create a new compressed OST file across the workstations in your environment when you upgrade your users’ Outlook client, use the Outlook Group Policy template (Outlk15.admx) to enable the Do not create new OST file on upgrade policy. You can find this setting under User Configuration\Administrative Templates\Microsoft Outlook 2013\Account Settings\Exchange.

A big change is that when running in Cached Exchange Mode, Outlook 2013 will only cache 12 months’ worth of data from the Exchange server by default! This is part of the new Sync Slider feature, which allows users to limit the number of e-mails that are synchronized locally into the OST. Users will be able to view messages that were removed (or not synced) by scrolling to the end of an e-mail list in a folder and clicking the message Click here to view more on Microsoft Exchange.

Note that this setting does not affect the number of items synchronized in Calendar, Contacts, Tasks, Journal and Notes.

Obviously, users can change how much e-mail to keep offline. To do this:
  • Start Outlook;
  • Click Account Settings on the File tab, and then click Account Settings;
  • In the Account Settings dialog box, double-click your Microsoft Exchange account on the E-mail tab;
  • In the Change Account dialog box, drag the Mail to keep offline: slider to the desired number of months;
  • Click Next;
  • Click OK when advised you have to restart Outlook to complete the configuration change;
  • Click Finish;
  • Restart Outlook.


On the other hand, administrators can change this setting on behalf of their users. The cached mode Sync Slider setting is maintained in the Outlook profile settings in the Windows registry. To administer this setting via group policy, you can use the Outlk15.admx and Outlk15.adml group policy templates available from the Microsoft Web site. Outlook uses the following registry data:
  • Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\Cached Mode
  • DWORD: SyncWindowSetting
  • Value: integer value (Decimal) with the following values:

o   0 = All (entire mailbox)
o   1 = One month of mailbox items
o   3 = three months of email items
o   6 = six months of email items
o   12 = twelve months of email items
o   24 = twenty-four months of email items

Another improvement is the Fast Access feature that brings the “instant access” of Online Mode into Cached Mode and improves the robustness of syncing. If, for example, a user was on a slow connection, he/she would typically need to wait a while for the mailbox to be updated to then start working. However, when users start Outlook 2013, they will almost immediately see the most recent e-mails and a completely up-to-date calendar as Outlook prioritizes these while caching the remaining items in the background.

Comments

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net