Windows XP Favourites Redirection – ADMX files

3 08 2010

One of the major disadvantages of still running XP in production is its lack of Internet Explorer Favourites directory redirection. If your users frequently roam between computers, the usual workaround is to enable Roaming Profiles to have the favourites roam with them. This usually works, until Windows Vista or 7 is introduced into the environment.

The newer Microsoft operating systems from Vista onwards do not support the old, legacy format of the XP profile. Instead, users logging on to a modern OS for the first time will be given a new roaming profile with “.V2” appended to their username in the roaming profile share. This is the version 2 profile, used by Vista up and totally isolated from the XP profile, including total isolation of the data it contains. In a phased roll-out of the newer Microsoft operating systems, you must follow best practices by using folder redirection to redirect user data on all systems to a common network location. This removes the data from the profiles, maintains consistency and ensures the user experience is the same on all network stations, without concerns over which OS is installed and therefore which profile and data the user will have access to. Plus, roaming profiles are just too slow for storing lots of user data anyway.

Unfortunately, Windows XP does not support redirection of the Favourites directory; this support was added in Windows Vista. One workaround I have seen is the built-in Vista redirection configured to redirect user favourites folders on newer systems to the legacy XP roaming profile share. This works, but it’s not particularly clean; redirecting data to a profile share rather than a user (home folder) share just isn’t right. It also causes data loss issues if a user’s profile must be reset; I work by the principle that only disposable data – stuff the users could live without – should be put into a user’s profile for precisely this reason.

Implementing Favourites redirection in Windows XP is a logical alternative; it isn’t particularly difficult either. I developed the following ADMX files to supplement the older ADM solutions which are available through a search on a popular web search engine. With 2008 or 2008 R2 Domain Controllers, the ADMX format is available for your use and I would highly suggest you make use of it. ADMX is XML-based and much, much easier to use than the legacy ADM language.


<policyDefinitions revision="1.0" schemaVersion="1.0">
    <target prefix="customFavorites" namespace="Microsoft.Policies.Favorites" />
    <using prefix="inetres" namespace="Microsoft.Policies.InternetExplorer" />
  <resources minRequiredRevision="1.0" />
      <definition name="SUPPORTED_IE5" displayName="$(string.SUPPORTED_IE5)" />
    <policy name="IE_Favorites" class="User" displayName="$(string.IE_Favorites)" explainText="$(string.IE_Favorites_Location_Explain)" presentation="$(presentation.IE_Favorites)" key="Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders">
      <parentCategory ref="inetres:InternetExplorer" />
      <supportedOn ref="SUPPORTED_IE5" />
        <text id="IE_Favorites_Location" key="Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" valueName="Favorites" required="true" expandable="true" />

XPFavouritesRedirect.adml (name this the same as the ADMX file and dump it in the language folder in your PolicyDefinitions directory)

<policyDefinitionResources revision="1.0" schemaVersion="1.0">
      <string id="IE_Favorites">Location of Internet Explorer Favorites</string>
      <string id="IE_Favorites_Location">The path to the favorites folder</string>
      <string id="IE_Favorites_Location_Explain">Specify the path to the location of your Favorites folder. This is stored in an expandable registry string value, so you can use environment variables, such as %HomeDrive%%HomePath%.</string>
      <string id="IE_Favorites_Location_Tip1">Specify the UNC path to the favorites location</string>
      <string id="InternetExplorer">Internet Explorer</string>
      <string id="SUPPORTED_IE5">at least Internet Explorer v5.01</string>
      <presentation id="IE_Favorites">
        <textBox refId="IE_Favorites_Location">

The above is standard ADMX/ADML format which can be dumped in the correct locations of your Central Store (if you don’t have one, why not? Set one up, otherwise you will need to store them in the local store on each DC). In the GP Editor, it will appear as a policy in the standard Internet Explorer area under the User Configuration / Windows Components node.

The Favourites registry value in HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders is of type REG_EXPAND_SZ. The ADMX implements this with the expandable=”true” syntax, meaning from your perspective, you can specify environment variables in the GPO and these will be properly expanded by the system to their full paths. I personally use %HomeDrive%%HomePath%\Favourites to direct them to a subfolder of the user’s defined home folder location in their Active Directory user account properties.

This does not move any existing Favourites out of the profile and into the redirected location. However; this is fairly easy to script in a logon script or one-time operation. For new users, the Favourites directory will be created automatically, assuming the home drive exists, the user has permissions, quota is not fully used and so on.

It is a good idea to set the XP Favourites redirection policy in its own GPO object, then apply a WMI condition to filter the policy to XP/2003 and older systems only. Windows Vista and above support native redirection of Favourites, so you should use a separate, WMI filtered policy for Vista+ computers to redirect their Favourites to the same location as defined for XP clients.




13 responses

23 10 2012
Adam Craig

Matt, Great advice. What about the Appdata (or Application Data) folder for XP. Microsoft state it can’t be redirected but can it? Using your method (ADMX/ADML) would this work or will the XP logon process not support this?

Something else that puzzles me is the sharing of the AppData between OSs. Should all software be the same version on both XP and Vista/Win7? This would ensure the AppData folder is shareable otherwise data is written differently by different versions of software. What then happens to Microsoft software which must be different versions by virtue of the fact you are using a different OS?

I am trying to acheive some sort of consistent experience between XP and Win7 roaming user profiles and folder redirection by following:

Kind Regards

2 11 2012

Hi Adam,

Redirection of the AppData folder is actually built right into the Folder Redirection extension of Group Policy, in XP, Vista, 7, 8 and all those OSes. It’s supported across them all, so there is no need to implement this ‘hack’ for that OS. AppData redirection is native. 🙂

Now, just because it’s there doesn’t necessarily mean it’s a good thing to use! There are different schools of thought when it comes to redirecting AppData. Different arguments for and against – performance improvements at logon time (smaller roaming profiles if it’s redirected) vs. performance issues for some applications which use it heavily (so better if on the local disk of the machine). “Conflict” issues with multiple accesses on multiple PCs if redirected.

My personal preference at the present time is not to redirect AppData, because doing so caused us headaches with several Line-of-Business applications. We still use Roaming Profiles in conjunction with Folder Redirection of all the folders which store user data, and this works well. A consistent user experience roams with this setup and we rarely get any issues. The only potential downside is the odd user whose AppData gets bloated, which can then cause performance problems at logon/logoff, so be mindful of this.

Microsoft User Experience Virtualisation (UE-V) should set about resolving the problem of Roaming Profiles once and for all, but it is yet to be released. In addition, current documentation indicates it will not support Windows XP at release (XP is considered legacy now), so this does pose a potential limiting factor to those of us still struggling to get the whole network up to Windows 7. (And I am yet to plan a migration to Windows 8 for any of my customers, not least the large ones!)


%d bloggers like this: