This is basically true. If you are supporting older clients or unpatched servers, make sure you only edit the GPO's from a machine running XP SP2 or 2003 SP1. Otherwise, you need to install a patch from MS http://support.microsoft.com/default.aspx?kbid=842933
2000, XP SP1, and 2003 RTM cannot view the newest ADM files without popping up about 100000000000 error messages. The patch resolves this issue, but it requires a reboot on 2000. The new features included in an updated ADM will either work with older clients, or they will only take effect on the clients that can support it. You will usually see a message that goes something like "Requires Windows XP or 2003". -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Turner Sent: Wednesday, September 06, 2006 9:41 AM To: [email protected] Subject: [ActiveDir] adm file management quick question (hopefully not too daft) ref ADM file management it seems different OS's ship with different versions of the 'standard' ADM files that include conf.adm / interes.adm / system.adm ... say if you are maintaining policies that link to containers holding say XP , 2000, 2003 computers it would not be unreasonable to manage them all from a single host on which you edit policies. am i correct to say that in maintaining the settings in these files are always cumulative - if that's the right word if so then it is correct working practice to always use the MOST RECENT version of an ADM file with no fear of breaking previously functional GPO's ??? GT List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx
