Outlook 2016 creates new OST every logon

[stanleyj]

I have a strange issue with Outlook 2016 and OST files.

 

We have recently migrated all users to Office 365 and we have Office 2016 installed on every computer.

 

I have set Group Policy to turn on cached mode and download 3 months of data as users were complaining it was slow in Online mode. I also have a policy to specify the OST file path: c:\Outlook Data Files.

When a user logs onto a computer and opens Outlook 2016 for the first time it obviously takes a little while whilst it downloads the emails to the OST file.

If the user logs off the computer and back on again and opens Outlook, it then creates another OST file and downloads all the emails again! The new OST file has (1) on the end.

 

A new OST file gets created every time, ending in (2) .... (3) etc

 

I can’t seem to work out why Outlook isn’t remembering that it already had an OST file on the computer.

I assume this information would be kept in AppData which we don’t currently redirect due to lack of disk space so gets stored in their profile in C:\users The profiles do not get deleted on log off.

If someone could point me in the right direction I would be very grateful.

[victory2015]

where is the location of the ost file is it on the local drive? you may need to redirect ost files to the home directory (network) there is group policy for this. when i used cached mode this is what i had happen as well.

[HereIGoAgain2601]

Did you manage to find a resolution to this? We are having the same problem but direct the OST files to the user's home directory on the network.

[robjduk]

Any one have an update on this? It is driving me totally nuts.

 

There is GP to say "Do not create new OST file on upgrade" which some forums pointed me towards however it did nothing.

[robjduk]

Just been digging deeper and it only happens to me with mandatory profiles set. I switched the user to roaming and it used the same OST every time. I would prefer to use roaming but then of course you loose all the Windows 10 start...

 

Exchange 2013 (installed most recent CU last night).

Office 2016 x64 (installed latest service pack today to rule that out)

Windows 10 LTSB 2016

 

Why do they make this as had as they can?

[HereIGoAgain2601]

That's strange, we have the issue on Office 365 with Windows 10 Education and Windows 7 x64.

Happens to us with Roaming profiles and local... not tried mandatory.