You can also try this:
1. Download and install the Group Policy Management Console (GPMC) with SP1
http://www.microsoft.com/downloads/...24-8CBD-4B35-9272-DD3CBFC81887&displaylang=en
2. This must be installed on atleast 1 server which processes your GPOs and
any administration machines you are going to use to edit the GPOs. I highly
recommend that you install this on all machines and all servers just to be
safe.
3. Download and install the proper hotfix for each of your servers from KB
article 842933.
http://support.microsoft.com/default.aspx?scid=kb;en-us;842933
4. Open each GPO in the GPMC to update their version.
5. Follow recommendations in KB Article 816662.
In excerpt from KB Article 816662:
"Use Policy Settings to Control ADM File Updates
Two policy settings area available to help with management of ADM files.
These settings make it possible for the administrator to tune the use of ADM
files for a specific environment. These are the "Turn off automatic updates
of ADM files" and the "Always use local ADM files for Group Policy Editor"
settings.
Turn Off Automatic Updates of ADM Files
This policy setting is available under User Configuration\Administrative
Templates\System\Group Policy on Windows 2003, Windows 2000 and Windows XP.
When this policy is enabled, updating an existing GPO does not result in ADM
files from the local computer being sent to the GPT.
In Windows 2000, the first time a GPO is edited, the local ADM files are
uploaded to the GPT, without regard to how this policy was set.
Note The first time the GPO is edited may or may not be when the GPO is
created.
In Windows XP, ADM files are not uploaded when a GPO is first edited if this
policy is enabled."
6. Replicate the GPO changes to all domain controllers by using the
dssite.msc snap-in.
7. Force a GPO Update on a client machine by using GPUPDATE /FORCE in the
run box.
8. Keep your fingers crossed and if this doesn't work goto the Service Pack
2 web chat site and talk to them.
http://support.microsoft.com/default.aspx?pr=Wxpsp2chat