I've got quite a bizarre issue here that I believe might actually be a bug in Outlook 2013.  Here's what I've got going on:

We're applying a variety of AutoArchive settings to our clients via a GPO using the Office 2013 ADMX templates from a Central Store.  As I'm sure everyone here knows, a GPO is just an easy, fancy way to make a change to a registry setting.  Each of these registry settings are detailed in the "office2013grouppolicyandoctsettings.xlsx" file that is included when you download the Office 2013 ADMX files.  According to this file, the AutoArchive settings from the GPO go here:

HKCU\Software\Policies\Microsoft\office\15.0\outlook\preferences

The GPO is working properly, as I can see the values being populated in this key.  In fact, I've even deleted the entire "preferences" key, forced a gpupdate, and then watched as the "preferences" key gets repopulated from the GPO.  This is NOT an issue of the GPO not being applied.  

Best I can tell, Outlook is just simply ignoring these registry keys for some reason on some computers.  I've got a few computers that are inheriting this same GPO that are working just fine.  In fact, I can even delete the preferences key, open Outlook, and see the archive settings go back to default.  I can then reapaply the GPO (or simply reimport the preferences key), and everything goes back to our custom settings.  This is NOT happening on a few computer though (this the reason for this post).  Seemingly only on newly configured laptops does this seem to be a problem, as the computers it's working on have been inheriting this GPO for several weeks now.  

Any thoughts on what to do here?  What's the best way to get this reported to Microsoft without being charged for a support incident?

 

Thank you for your feedback.

I can reproduce the hehavior in my Outlook 2013 and I would escalate the thread as your request.

Tony Chen
TechNet Community Support

That's great news actually!  When I didn't get a response to this last week, I went ahead and opened up a ticket with Microsoft Professional Support.  So far, the only suggestion has been to uninstall Office and then reinstall, which I'm going to try this morning.  I doubt it is going to make a difference.  

If it would be helpful to provide a case number for my open ticket with MPS, please let me know and I can provide a case number.  

Hi arp.parker. I've got almost the same issue here: AutoArchive and Junk email prefences are not applied on Outlook 2013 (tried with 4 installations, all I have - Win7Pro 64-bit and Office 2013 H&B), but for example other policies are applied (eg disallow to add new accounts).
It happened only a couple of times that the policy applied, but then it disappeared at the next gpupdate or GPO change. If I run a gpresult or a rsop.msc, policy looks applied, but effects actually don't.
I would really appreciate if you could keep this topic updated. Thanks!

Most definitely, will do!  Your scenario sounds very, very similar indeed.  We too are using Junk Mail settings (in a different GPO though), and I discovered while I was on the call with MS Professional support that most of those weren't being applied as well (but our macro security settings were--in the same GPO!).  

I've been working with MPS this week, and they collected some ProcMon logs yesterday.  Appears they are moving it up the chain, so as soon as I have an answer I'll be sure to update here.  

Hi,

Any update from Microsoft on this yet?

Thanks

Sort of, but nothing substantial.  They've collected a lot of data from the computer and I've sent countless screenshots and registry/logging info over to them as they continue to run it up the chain.  

At this point they've narrowed it down to affecting only Click To Run installs of Office 2013 (which I believe is likely a majority).  We have an MSDN version of Office 2013 installed that works perfectly, and the folks at Microsoft have been able to replicate this.  I just sent an email over this morning requesting an update, as it's been several days since I've heard anything from them myself actually.  

Ultimately, I still haven't received a hotfix or gotten any kind of confirmation this is going to be fixed in any future updates.  It's supposedly with their development group now, so hopefully this isn't much further away.  

News about this ? I have same scenario with same problem !

Thanks for the reminder actually!  I had received a call a few weeks ago advising they'd have more information in a few days, but realized I still hadn't heard back.  I just got off the phone with the Technical Lead on the case.  

It has now been officially classified as a bug.  There isn't yet any formal documentation on the issue or a hotfix/update to correct it.  There is also no ETA on when this might happen, but the bug has been logged with the "Product Team".  The Technical Lead advised that there it can be a time consuming process to get an update integrated into the release schedule and approved, so it may very well be months for all I know before an actual fix is available.  

The case I opened with MPS is associated to the bug, so I should get an automated notification when it is resolved.  I was also reassured that I can contact any of the few technicians I've been working with periodically to check on the status.  

I'll try to remember to update this thread when I hear some good news!  

you know if there is an official document that says this is a Bug?

As of last week about this time, no, there is not yet any official documentation.  It's supposed to be coming soon though, and the case I opened with MPS has been associated to the bug internally, so I should receive a notification when further information is available.  If I haven't heard anything in another week or two, I'm going to follow-up with the technical lead who was handling the case to inquire about the status.  

Thanks, let me know when it is solved !

thanks again