Office 2013 shows templates error after being Sysprepped

Here is my setup:

1. I installed Windows 7 Professional.
2. I entered Audit Mode (which automatically logged me in as the built-in Administrator user) and installed the entire Office 2013 Professional Plus suite.
3. In Audit Mode, I opened Word 2013 to get through the "new user" prompts, such as the opening movie that plays in all Office 2013 programs. I did this to ensure that any new users who log into the computer would not need to sit through these "new user" prompts.
4. I ran Sysprep with the CopyProfile setting in the Unattend.xml file, with the /generalize switch, and the /oobe switch. The CopyProfile setting copies settings from the built-in Administrator account to any new user who logs into the system.

Everything seemed to work, but there is a problem: when any user -- all of which are standard users rather than administrator users -- logs into the system and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally be listed:

"Sorry, we had trouble getting the featured templates and can't show them right now."

Below the error message is a link that reads “Work Offline.” If you click the “Work Offline” link, templates do appear as they should.

If I login as the built-in Administrator account, this problem does not occur at all when logging into Office 2013 programs.

Any ideas?

Thanks for the reply.

I cannot try this at the moment because my office is currently closed for the holidays.

However, will your solution work on a Sysprepped image before the Sysprep is initiated? If not, your solution will not work. Keep in mind that this problem does not to a single computer; instead, it is for creating a master image that will be deployed to over 3000 computers.

And won't resetting the Internet Explorer settings undo the settings that I made in my image (thus, negating the entire reason I would even make an image)?

loosus456 were you able to find a solution to this issue? I am having the same problem and have made a master image as you did with Sysprep and "copy profile".

I just saw this. Oops.

Our only solution was to recreate the image. We got frustrated because we could find no other solution. Obviously, something was broken in the old image, but only God knows what. Essentially, we gave up.

For anyone having this issue: if you can't find a solution pretty quickly, just give up and remake the image. We had the problem on only one image that we built. Rest assured that this is not normal and should not happen. We know nothing that we did differently on the subsequent image creations.