Group Policy - ADM Files - I am totally confused!

Discussion in 'Windows Small Business Server' started by Alan, Sep 27, 2006.

  1. Alan

    Alan Guest

    Hi All,

    I am trying to understand how to ensure that the ADM files we are
    using are up to date.

    My confusion stems from the fact that we seem to have many copies of
    the same ADM files on our SBS 2003 Prem DC (I will post a reply to
    this post with the file listing in case you need to know).

    My questions are:

    1) Should we have these multiple copies on the DC?

    2) How do I ensure that I am using the most up to date versions? I
    can download the latest versions from MS (seem to be MSI files), but I
    don't want to install them without understanding what I already have.

    3) Can I delete any of the (replica) files that we have on the
    server? It would seem reasonable to assume that we only need one copy
    of each ADM file rather than the multiple copies we seem to currently
    have.

    4) Once the DC is up to date, what do I do about my own workstation?
    I seem to have

    Thanks,

    Alan.
    --

    The views expressed are my own, and not those of my employer or anyone
    else associated with me.

    My current valid email address is:



    This is valid as is. It is not munged, or altered at all.

    It will be valid for AT LEAST one month from the date of this post.

    If you are trying to contact me after that time,
    it MAY still be valid, but may also have been
    deactivated due to spam. If so, and you want
    to contact me by email, try searching for a
    more recent post by me to find my current
    email address.

    The following is a (probably!) totally unique
    and meaningless string of characters that you
    can use to find posts by me in a search engine:

    ewygchvboocno43vb674b6nq46tvb
     
    Alan, Sep 27, 2006
    #1
    1. Advertisements

  2. Alan

    Alan Guest

    Listing of ADM files on our DC. There are 145 files as follows:

    1 copy each of:

    AER_1025.ADM
    AER_1028.ADM
    AER_1031.ADM
    AER_1033.ADM
    AER_1036.ADM
    AER_1040.ADM
    AER_1041.ADM
    AER_1042.ADM
    AER_2052.ADM
    AER_3082.ADM
    common.adm
    inetcorp.adm
    inetset.adm
    windows.adm
    winnt.adm


    26 copies each of:

    conf.adm

    inetres.adm

    system.adm

    wmplayer.adm

    wuau.adm


    as listed below by path.

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    C:\WINDOWS\assembly\GAC\Microsoft.UpdateServices.Administration
    C:\WINDOWS\inf\AER_1025.ADM
    C:\WINDOWS\inf\AER_1028.ADM
    C:\WINDOWS\inf\AER_1031.ADM
    C:\WINDOWS\inf\AER_1033.ADM
    C:\WINDOWS\inf\AER_1036.ADM
    C:\WINDOWS\inf\AER_1040.ADM
    C:\WINDOWS\inf\AER_1041.ADM
    C:\WINDOWS\inf\AER_1042.ADM
    C:\WINDOWS\inf\AER_2052.ADM
    C:\WINDOWS\inf\AER_3082.ADM
    C:\WINDOWS\inf\common.adm
    C:\WINDOWS\inf\conf.adm
    C:\WINDOWS\inf\inetcorp.adm
    C:\WINDOWS\inf\inetres.adm
    C:\WINDOWS\inf\inetset.adm
    C:\WINDOWS\inf\system.adm
    C:\WINDOWS\inf\windows.adm
    C:\WINDOWS\inf\winnt.adm
    C:\WINDOWS\inf\wmplayer.adm
    C:\WINDOWS\inf\wuau.adm
    C:\WINDOWS\system32\GroupPolicy\Adm\conf.adm
    C:\WINDOWS\system32\GroupPolicy\Adm\inetres.adm
    C:\WINDOWS\system32\GroupPolicy\Adm\system.adm
    C:\WINDOWS\system32\GroupPolicy\Adm\wmplayer.adm
    C:\WINDOWS\system32\GroupPolicy\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\system.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\domain\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{11B079B5-16DA-4DF0-80DC-6792AC54585E}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{16C9D394-4309-4456-BD4C-62700142E482}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{2F33588C-8B64-4C9E-9B73-C9D9914F446A}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{45576165-E328-4011-B55D-7BAAC4E11D15}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{487D3E2F-094B-485A-8A92-B6B03F1BFEDB}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{7A2FD259-8C5E-470B-BF82-3B1C6F25FCBB}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{8B4578F0-BB04-4A9F-9957-F7B125F8D376}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{ABD5A03C-AF51-4341-AF5A-E7C9059F6116}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D30D5864-DF3C-4B91-9819-1657FED01A40}\Adm\wuau.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\conf.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\inetres.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\system.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\wmplayer.adm
    C:\WINDOWS\SYSVOL\sysvol\KDB.local\Policies\{D320DE7F-01DD-4691-AD4A-A19CF90899DA}\Adm\wuau.adm


    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     
    Alan, Sep 27, 2006
    #2
    1. Advertisements

  3. The copies in the Policies\<GUID> path are there to support the Policies
    (this is where the GPOs are actually stored). They're irrelevant for what
    you see in the Group Policy Management Console.

    %windir%\system32\GroupPolicy is the primary repository for installed ADM
    files. And this is where GPMC will look first when you want to add a new
    ADM to it. If new GPOs are then created, the additional ADM will be copied
    to the Policies\<GUID>\Adm folder along with the others.
     
    Steve Foster [SBS MVP], Sep 27, 2006
    #3
  4. Alan

    Alan Guest

    Hi Steve,

    Thanks for your reply.

    If I download the most up to date ADM files from Microsoft, they come
    as MSI files.

    If I install those MSI files I don't know exactly what they are going
    to do. Can I safely do that, and they will replace / update the ones
    on the server in the correct locations without causing any problems
    with my GP settings?

    Thanks,

    Alan.

    --

    The views expressed are my own, and not those of my employer or anyone
    else associated with me.

    My current valid email address is:



    This is valid as is. It is not munged, or altered at all.

    It will be valid for AT LEAST one month from the date of this post.

    If you are trying to contact me after that time,
    it MAY still be valid, but may also have been
    deactivated due to spam. If so, and you want
    to contact me by email, try searching for a
    more recent post by me to find my current
    email address.

    The following is a (probably!) totally unique
    and meaningless string of characters that you
    can use to find posts by me in a search engine:

    ewygchvboocno43vb674b6nq46tvb
     
    Alan, Sep 28, 2006
    #4
  5. Well, the MSI installer should tell you what it's going to do when you run
    it.

    The most likely scenario is that the ADMs will simply be unpacked
    somewhere on the machine, without touching any of the standard locations.

    I've never seen changes to the ADMs break any policy, though if there's a
    policy item that exists in the policy for which the ADM doesn't have
    information, you will see references in the GPMC and other management
    tools to "extra registry settings", and you may not be able to update
    those elements in the GPO.

    An example of this is My Pictures Folder Redirection, which was a Windows
    2000 supported GPO policy element, but is only supported for backward
    compatibility in 2003, and the 2003 ADM doesn't have the element.
    Therefore, in a domain that was 2000-based, where that policy was set,
    that is upgraded to 2003 doesn't show the My Pictures redirection settings
    properly, nor can the setting be manipulated with the 2003 ADM.
     
    Steve Foster [SBS MVP], Oct 1, 2006
    #5
  6. The ADMs are not critical to the functioning of the GPOs, they're there
    (AIUI) to facilitate remote GPO management.

    I'd expect the GPMC and other management tools to replace the ADMs in the
    GPO folders any time the GPOs are amended. An existing GPO with an out of
    date ADM probably won't get the new ADM until it's edited.
     
    Steve Foster [SBS MVP], Oct 1, 2006
    #6
  7. Alan

    Alan Guest

    You are correct - it did.
    Absolutely spot on.
    I am now in the situation where I have the following files in two
    sub-folders:

    conf.adm
    inetres.adm
    system.adm
    wmplayer.adm
    wuau.adm

    One set for WindowsServer2003SP1 and one set for WindowsXPSP2.

    Now, I can 'link' each of those ADM templates from within each GPO.

    However, I don't know quite how to do that. For example, we have a
    (standard) GPO called:

    Small Business Server Users

    That policy applies to all our (non domain admin) users.

    Should I then link the WindowsXPSP2 ADM files to that GPO? But what
    happens when those users are logged in to the Win 2003 Server using
    TS?

    On the other hand, I could link those two sets of ADM file to the
    SBSWorkstation and SBSServers GPOs respectively. However, that still
    leaves the Users GPO?

    When I ran the MSI files, there was a 'recommendation' that I don't
    replace the existing ADM files in C:\Windows\Inf with the 'reference'
    files I was installing. What does that mean? Why are these files I
    got from the MS Website today 'reference' ADM files and in what way
    are they different in nature to the ones already on my workstation and
    server?

    Thanks,

    Alan.



    --

    The views expressed are my own, and not those of my employer or anyone
    else associated with me.

    My current valid email address is:



    This is valid as is. It is not munged, or altered at all.

    It will be valid for AT LEAST one month from the date of this post.

    If you are trying to contact me after that time,
    it MAY still be valid, but may also have been
    deactivated due to spam. If so, and you want
    to contact me by email, try searching for a
    more recent post by me to find my current
    email address.

    The following is a (probably!) totally unique
    and meaningless string of characters that you
    can use to find posts by me in a search engine:

    ewygchvboocno43vb674b6nq46tvb
     
    Alan, Oct 3, 2006
    #7
  8. You have multiple ADMs because the supported GPO policy elements vary
    across OS and service pack (eg none of the Windows Firewall policies mean
    anything to an XP machine that's pre-SP2).
    No, you can't. The ADMs define what the GPMC and Group Policy Editor
    "know" - ie they describe policy settings. Any GPO can use any policy
    setting that exists, but it may only be editable with the GPO tools if
    that policy setting is in one of the ADMs.

    If you're editing a policy that will only apply to a specific OS/SP
    combination, it's useful to be using an ADM that describes those elements.
    An ADM for a different OS/SP combination may not include those, and the
    settings would therefore be uneditable with that ADM in use by the GPO
    tools.
    The ADM isn't relevant for *application* of policy - it's only relevant
    for *editing* of policy. Whether a particular policy has an effect depends
    on whether the OS on which it's applied supports the setting or not (see
    earlier comment about Windows Firewall and XP SP2).
    Newer ADMs may not include descriptions for older policy elements that
    have been deprecated in later releases (the My Pictures Folder Redirection
    GPO setting is an example - it's included in Win2K ADMs, but not in WS2003
    ADMs). So having all the various ADMs available to "power" the GPO editing
    tools is useful. You need Win2K era ADMs to be able to manage a My
    Pictures Folder Redirection GPO - such a policy just shows "Extra Registry
    Settings" if edited with the GPO tools when using WS2003 ADMs.
     
    Steve Foster [SBS MVP], Oct 3, 2006
    #8
  9. Alan

    Alan Guest


    Thanks Steve.

    I will have to just get into it and make one change at a time to see
    what effect it actually has on the users / machines.

    I suspect I will be back with more questions, but hopefully better
    informed ones!

    Alan.

    --

    The views expressed are my own, and not those of my employer or anyone
    else associated with me.

    My current valid email address is:



    This is valid as is. It is not munged, or altered at all.

    It will be valid for AT LEAST one month from the date of this post.

    If you are trying to contact me after that time,
    it MAY still be valid, but may also have been
    deactivated due to spam. If so, and you want
    to contact me by email, try searching for a
    more recent post by me to find my current
    email address.

    The following is a (probably!) totally unique
    and meaningless string of characters that you
    can use to find posts by me in a search engine:

    ewygchvboocno43vb674b6nq46tvb
     
    Alan, Oct 4, 2006
    #9
    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.