How to deploy QAT toolbars in Office 2007


How to deploy QAT toolbars in Office 2007.


*Important Note*

By default Office 2007 QAT files are stored Office folder that is in the “local” profile.
In Windows Xp this location = "%userprofile%\local settings\application data\Microsoft\office
In Vista\Windows 7 this location = %appdata%\local\Microsoft\Office

When adding QAT files to the “add files” section of the OCT the default dropdown location that you should choose is “[AppDataFolder]\Microsoft\Office”. The problem with this however is that “[AppDataFolder]\Microsoft\Office” from the OCT actually ends up pointing to these “roaming” locations:

In Windows Xp this location = "%userprofile%\application data\Microsoft\office
In Vista\Windows 7 this location = %appdata%\roaming\Microsoft\Office

This is a problem, because the OCT is placing the QAT files in the roaming section of the users profile, but Office looks in the “local” section of the users profile by default.

To fix this, Microsoft has provided a hotfix that forces Office to use the “roaming” folder in the users profile instead. This hotfix is from KB955142 This hotfix has since also been superseded by Sp2. These instructions for deploying the QAT files assumes that you will be applying the hotfix, or pushing Sp2 with your Office 2007 deployment. If you are pushing Sp2 with your deployment you do NOT need the hotfix from KB955142. Installing the Hotfix or Sp2 to resolve this problem is the first part of the solution. The next part of the solution is to also add a reg key that tells Office to use the Roaming folder.

1. Create the QAT files

a.            Go to a machine with office 2007 installed and modify the Quick Access Toolbar.
b.            The folder that contains the .QAT file is hidden so we must show hidden files and folders. To do this, open my computer, click tools, folder options, then click on the view tab. Put a dot in "show hidden files and folders"
c.            Browse out to the "%userprofile%\local settings\application data\Microsoft\office" folder. In here you will see a .qat file for each app.

2. Add them to the OCT in the “add files” section. For the destination path choose  “[AppDataFolder]\Microsoft\Office”

Should look like so..


3. Add the following “dword” registry key to the “Add reg keys” section. (This step tells Office to use the roaming folder rather than the local folder for QAT files.) 

QuickAccessToolbarRoaming =1

Like so..


4. Save and close the custom.msp

5. Extract the MSP files from the following private hotfix KB955142 or Sp2 and place them in the updates folder of your office 2007 installation source.

To extract Office 2007 patches use the following syntax: office-kb955142-fullfile-x86-glb.exe /extract

6. Install Office.

Comments (3)

  1. CareyLynn Flaugher says:

    I am deploying Office 2007 SP2 and this is still not working.  Any other suggestions on how to resolve?

    Amin Comment – The steps in this article are correct. You may want to open a ticket with Microsoft. (Did you forget to add the reg key?)

  2. Chris Termini says:

    Unfortunately this only works for the user that actually runs the MSP as it only changes the registry for the current user, not all users on a machine.  When you are using automated deployment tools like Altiris or SCCM they usually run under a system or service account and the registry changes do not get applied to all of the users on a machine.


    The steps in this article are correct.

    Please keep in mind that while any HKCU keys that you add to the “ADD REG KEYS” section of the .msp WILL apply to all users, the key doesn’t get written to each user’s HKCU hive until their first launch of an Office app after the MSP has been run. If you check the a user’s HKCU hive prior to them opening an Office app you will not see the key. 

    This is discussed in this blog post:

    How do CMW files in Office 2000-2003 work? How to maintenance MSP files work in Office 2007-2010?

  3. Chris Termini says:

    My mistake.  After testing this does in fact work as you described.  I figured there was no way that the Office install held the registry setting in memory for each user starting Office for the first time.  Thanks for the great post.

Skip to main content