encountered an error while parsing - admx

Discussion in 'Active Directory' started by Steven Cools, Nov 25, 2008.

  1. Steven Cools

    Steven Cools Guest


    i recently removed (demoted) a new 2008 server (a DC) from our domain.
    so now it's back to just 2K and 2K3 DC's.
    i made sure everything was replicated before demoting and everything went
    fine, no errors.

    today -while testing the new WSUS3 install- i ran the RSOP on my vista
    laptop to see whether the GPO with the wsus settings came through and i got
    an error for every possible admx file saying "encountered an error while

    as far as i know, the admx files are only used in 2K8 server, so why are
    they still being looked for?
    then i thought about the adprep operations i had to do before making the 2K8
    a DC.
    is there some reverse adprep i need to do now maybe? run the adprep from 2K3
    again? or is there another way to clear these admx remnants?

    Steven Cools, Nov 25, 2008
    1. Advertisements

  2. Steven,

    Did you create the Central Store? Have a look at your remaining DCs'
    SYSVOL folder - under "Policies". Is there a "PolicyDefinition" folder?
    No, you can't revert those changes (there's actually no need to do
    that). Adprep makes changes to the AD Schema you cannot revert.


    Florian Frommherz [MVP], Nov 25, 2008
    1. Advertisements

  3. Steven Cools

    Steven Cools Guest

    hey florian,

    yes, i do have the policydefinitions folder under my sysvol\domain\policies
    (on all dc's). in it are the admx files and the folder nl-NL with adml files.

    about the central store, i tested it on one of my 2k3 dc's, following

    "open the Group Policy Management console. Now, navigate through the console
    tree to Forest | Domains | your domain | Group Policy Objects | Default
    Domain Controller Policy. Upon selecting this policy container, the pane on
    the right side of the console should display a series of tabs. Go to the
    Settings tab, and look at the Administrative Templates section. It should
    confirm that the policy definitions (the ADMX files) have been retrieved from
    the central store."

    i got an error while opening the "Default Domain Controller Policy" saying
    that there was something wrong with permissions not being similar to those of
    the sysvol, pressing OK would solve this, which is what i did, but when
    running the rsop on my vista i still had to click through what seems like
    20000 admx errors ;-(


    Steven Cools, Nov 26, 2008
  4. Steven,

    The machine you're running rsop from - is that an nl-NL machine, too? Is
    the default en-US folder there, too? If not, try to create it.


    Florian Frommherz [MVP], Nov 26, 2008
  5. Steven Cools

    Steven Cools Guest


    copied the admx folder for "en-us" from my vista
    (c:\windows\policydefinitions) to the sysvol and rsop works fine now!

    thanx a bunch!


    Steven Cools, Nov 26, 2008
  6. Steven Cools

    johny log Guest

    Hello guys,

    Do you encounter errors while deleting files in Windows? I'm here to provide a solution. I've been reading several threads on this topic on different forums where computer users were asking about this popular error "The filename you specified is not valid or too long".

    My research helped me to find a tool for you guys.

    Its LONG PATH TOOL, a very easy to run but highly powerful software.

    Follow the link to read more about this error.

    johny log, Nov 5, 2010

  7. To solve issue simply remove admx/adml file from the PolicyDefinitions folder.

    suryavanshi.santosh, Apr 14, 2014
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.