Comments on: Managing MS Office 2007 Quick Access Toolbar(s) with Roaming Profiles

By: jeremy

jeremy — Tue, 18 Nov 2008 10:30:50 +0000

Indeed you can Jamie, and I do agree that if you are starting out on a fresh deployment, Flex Profiles is the way to go. But whilst it’s a fantastic profile management mechanism, Flex Profiles isn't the solution for every deployment. It requires a lot of work up font, and you need to be confident that the customer has the skills to maintain it moving forward. This particular solution was simply implemented to clean up the mess that another Integrator implemented, something I wrote about here: http://www.jhouseconsulting.com/index.php/jhousec… . There was no time allowed for to revisit and implement Flex Profiles. However, the solution documented above will work in any environment, and requires little profile management skills to implement.

Cheers,

Jeremy.

By: Jamie Morrison

Jamie Morrison — Tue, 18 Nov 2008 07:13:01 +0000

Hi Jeremy,

You can also use flex profiles. e.g.

[IncludeIndividualFolders]

# Include Office 2007 Quick Access Toolbar shortcuts

Local SettingsApplication DataMicrosoftOffice

Cheers,

Jamie.

By: jeremy

jeremy — Sun, 24 Aug 2008 18:08:30 +0000

Hi Greg,

I saw your script whilst I was researching the issue. I guess that there were two main reasons why I didn't make use of it.

1) It would provide two copies…one as part of the roaming profile load and unload, and the other with your scripts. My script only provides the one copy. Therefore, it's more efficient, especially during those heavy logon/logoff periods of the day.

2) This particular customer has multiple profiles for different application silo's. For the most part we are trying to use a common "Application Data" folder, but a couple of conflicting applications require us to split this off. Once again, my script will centralise the QAT files to be used across all profiles.

Cheers,

Jeremy.

By: Galaxiom

Galaxiom — Tue, 19 Aug 2008 13:10:13 +0000

Rather than saving in the user's Home Drive simply use the Group Policy scripts to copy the QAT files to and from the user's permanent Application Data folder where Microsoft should have stored them in the first place. Here they are treated as part of their roaming profile. I have already posted the simple scripts required. http://www.technologyquestions.com/technology/mic...