Error with Custom GPO

[TomBain]

Ok, this is wierd. At least wierd for my experience with writing GPO's. I have 3 GPOs. One to create an Outlook profile, and two to disable Stationery and Themes with Outlook 2003. Everything has worked great with them. Until I installed SP1 last week on one of my Domain Controllers. Since then I noticed network issue, so I disabled the GPO and tried editing it. As soon as I tried editing it I got: "The following error occured in \\domain\sysvol\policies\adm\stationery.adm on line 14: Error 51 Unexpected keyword

Found: CATEGOR
Expected: CATEGORY
The file can not be loaded.

So I went to look at the file but it is fine, it does not have CATEGOR, it has CATEGORY at the end. Anyone have this happen to them besides me?

[rooky]

Hi Tombain,

unfortunately this error didn´t "yet" occure but maybe it had something to do wit changing or refreshing te original ADM File in de sysvol\Policy\xxx

Do you use Windows server 2003? and did you update it with SP1?

perhaps you can start from the next link to work your way into te right site for the solution of the problem that you are searching for;
I saw that their are some knowledgebase links included.
http://support.microsoft.com/default.aspx?kbid=842933

their is a lot of info on this matter in different adm template errors but maybe it is possible for you to restore the original template that you used in the first place before the update?

Let me know i would like to learn why this is happening

Tom:

Be sure to read my newsletter on this subject:

http://boutell.com/pipermail/gpanswers/2004-August/000007.html

"ADM Trouble..."

[TomBain]

Jeremy,

I read it but don't see how it applies to me. The server itself is where I do all my GPO work, and you cannot apply the patch because SP1 is installed.

Gotcha..

Okay.. I think there's problem with that specific ADM file then.

I would kill the GPO and re-put in the settings.

Let me know if that clears it up...

[TomBain]

Finally got it. I thought it was my GPOs, it was actually KB 898060 that needed to be applied. Nice to see though. SP1 just came out and broke my two main servers. Nice.