none
[MS-GPOL] incorrect description for gPCMachineExtensionNames (and maybe gPCUserExtensionNames) RRS feed

  • Question

  • Hi,

    The field gPCMachineExtensionNames and gPCUserExtensionNames are described in [MS-GPOL] 2.2.4.

    It is said "A directory string with the format: [<CSE GUID1><TOOL GUID1>][<CSE GUID 2><TOOL GUID2>]

    where <CSE GUIDn> is a CSE GUID and <TOOL GUIDn> is a tool extension GUID, and the "[" and "]" characters are to be interpreted literally. The CSE GUID and tool extension GUID are each a 38-character "curly braced GUID string" as defined in [MS-GLOS]."


    When you modify a group policy programatically, you have to add the CSE Guid to the gPCMachineExtensionNames (or the other one) and according to the "2.2.8.2 GPO Extension Update Message" you have to update "versionNumber" and gPCMachineExtensionNames at the same time.

    If you create the attribute gPCMachineExtensionNames from scratch for a new policy, you don't have a problem (see http://support.microsoft.com/kb/885009 for an example)

    If you edit add a CSE to an existing policy, it doesn't work all the time. My finding is that the CSE GUIDs must be alphabetically ordered ([{B0 .... before [{B1) else you new GUIDs you are appending are ignored. An edit with the editor fixes the problem if a CSE is not applied.

    (tests done with "live GPO" and gpresult)

    Exemple :

    [{00000000-0000-0000-0000-000000000000}{BEE07A6A-EC9F-4659-B8C9-0B1937907C83}][{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}{53D6AB1B-2488-11D1-A28C-00C04FB94F17}{53D6AB1D-2488-11D1-A28C-00C04FB94F17}{D02B1F72-3407-48AE-BA88-E8213C6761F1}][{827D319E-6EAC-11D2-A4EA-00C04F79F83A}{803E14A0-B4FB-11D0-A0D0-00A0C90F574B}][{B087BE9D-ED37-454F-AF9C-04291E351182}{BEE07A6A-EC9F-4659-B8C9-0B1937907C83}][{B1BE8D72-6EAC-11D2-A4EA-00C04F79F83A}{53D6AB1B-2488-11D1-A28C-00C04FB94F17}{53D6AB1D-2488-11D1-A28C-00C04FB94F17}] => OK

    [{00000000-0000-0000-0000-000000000000}{BEE07A6A-EC9F-4659-B8C9-0B1937907C83}][{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}{53D6AB1B-2488-11D1-A28C-00C04FB94F17}{53D6AB1D-2488-11D1-A28C-00C04FB94F17}{D02B1F72-3407-48AE-BA88-E8213C6761F1}][{827D319E-6EAC-11D2-A4EA-00C04F79F83A}{803E14A0-B4FB-11D0-A0D0-00A0C90F574B}][{B1BE8D72-6EAC-11D2-A4EA-00C04F79F83A}{53D6AB1B-2488-11D1-A28C-00C04FB94F17}{53D6AB1D-2488-11D1-A28C-00C04FB94F17}][{B087BE9D-ED37-454F-AF9C-04291E351182}{BEE07A6A-EC9F-4659-B8C9-0B1937907C83}] => Not OK

    Please confirm my findings and update the documentation if my findings are correct.

    Vincent

    Friday, June 20, 2014 8:25 AM

Answers

  • Hi,

    According to our offline discussion :

    I had a discussion with Product Group and they confirmed that the CSE guids need to be in sorted order otherwise processing stops at the one that is out of sequence. I’m logging a technical document issue (TDI) to get this documented and update you with the updated text once this TDI is serviced. Does this answer your query and is it OK to close the case ?

    So I'm marking this thread as "answered".

    Thanks for looking up on that.

    regards,

    Vincent

    • Marked as answer by vletoux2 Friday, June 27, 2014 11:56 AM
    Friday, June 27, 2014 11:56 AM

All replies

  • Hi Vincent:

    I have alerted the open specifications team regarding your inquiry. A member of the team will be in touch soon.


    Regards, Obaid Farooqi

    Friday, June 20, 2014 5:11 PM
    Owner
  • Hi Vincent - I'm researching this for you.

    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Friday, June 20, 2014 9:10 PM
  • Hi,

    To get more context, I was trying to add a new registry key in HKLM\SYSTEM.

    I make a registry.xml file, added the CSE GUID ([{B087BE9..) at the end, updated the versionNumber and trigger a IAdsContainer->SetInfo.

    The registry key was not added and gpresult didn't mention the "Registry CSE", but only the normal Registry in the report. The "Registry CSE" was added in the report after I edited the GPO.

    I discarded any Registry.xml malformation because if you remove this file when the "registry CSE" is referenced in gpresult, you get an error when applying the GPO. It is not the case when I add the CSE GUID at the end : no error is produced if the registry.xml file is removed.

    To reproduce :

    Add a registry key using the CSE registry utility (this will produce a registry.xml), update the version on GPT.ini, edit gPCMachineExtensionNames and versionNumber at the same time but put the registry CSE GUID at the end so the GUID will not been alphabetically ordered.

    regards,

    vincent

    Monday, June 23, 2014 8:18 AM
  • Thanks Vincent for the additional information. Can you please drop me a mail at - dochelp at Microsoft dot com so that I can take traces from your machine and analyze further ?

    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Monday, June 23, 2014 11:56 PM
  • Thanks Vincent for reaching out to us thro' dochelp. We will circle back and update this thread once our investigation is complete.

    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, June 24, 2014 7:57 PM
  • Hi,

    According to our offline discussion :

    I had a discussion with Product Group and they confirmed that the CSE guids need to be in sorted order otherwise processing stops at the one that is out of sequence. I’m logging a technical document issue (TDI) to get this documented and update you with the updated text once this TDI is serviced. Does this answer your query and is it OK to close the case ?

    So I'm marking this thread as "answered".

    Thanks for looking up on that.

    regards,

    Vincent

    • Marked as answer by vletoux2 Friday, June 27, 2014 11:56 AM
    Friday, June 27, 2014 11:56 AM