次の方法で共有

ADM/ADMX Conversion Chart

  • [アーティクル]

A high-level mapping of ADM syntax to the ADMX equivalents. (A blank entry in the ADM to ADMX conversion chart implies there is no equivalent syntax used in that file.)

ADM to ADMX Conversion Chart

ADM language reference

ADMX equivalent

Comments

.admx

.adml

${ROWSPAN3}$Adm File Language Versions (#If Version)${REMOVE}$

revision

revision

Unlike ADM files, the ADMX file will have versioning built in and will not be tied to an operating system version.

resources minRequiredRevision

The resources minRequiredRevision attribute provides the coordination between the .admx and .adml file versions

schemaVersion

schemaVersion

The schemaVersion attribute specifies the ADMX schema version assumed when creating the .admx and .adml files. The Windows Vista ADMX files assume a 1.0 schema version number.

comments (;)

  • Annotation
  • <!-- -->
  • Annotation
  • <!-- -->

For ADM files, all text following the ";" is considered a comment. For ADMX files, either the Annotation element or the XML comments will not be processed by GP tools.

Strings reference (!!)

string

In ADM files, precede text with "!!" to reference a string

<Strings> section of the .Adm file

stringTable

CLASS

class

ADMX files provide the ability to classify the policy definition as being for user, machine, or both. The "both" classification will allow you to create a single policy definition that applies to the machine and user registry keys.

CATEGORY

  • categories
  • category
  • parentCategory

ADM files assume categories are nested within the definitions. ADMX files specifies a parentCategory element for each policy element defined in the .admx file. An individual category is defined within the "categories" element.

Duplicate Category Sections allowed in different ADM files.

Duplicate category sections are not allowed in different ADMX files.

If one .adm file includes a duplicate "CATEGORY" entry used in a different existing .adm file, the policy settings will merged when the Group Policy object Editor processes the ADM files. ADMX files have unique namespaces. Defining the same "category" element names in two different .admx files will cause the category to be displayed twice. Instead for .admx files, you must define the "category" element name once and then reference the category element name with the "using" element.

SUPPORTED

supportedOn

POLICY

  • policies
  • policy

In the .admx file, the "policies" element contains individual "policy" elements that correspond to a policy setting.

PART

elements

presentation

In ADM files, the PART statement specifies various policy setting options, such as drop-down list boxes, text boxes, and text in the lower pane of the Group Policy snap-in. ADMX files aggregate policy setting options for one policy setting into the "elements" element in the .admx file and the "presentation" element in the .adml file.

CHECKBOX

boolean

checkbox

TEXT

text

The "text" element in the .adml file provides the string used as the parameter text prompt.

EDITTEXT

text

textBox

NUMERIC

decimal

decimalTextBox

COMBOBOX

text

comboBox

DROPDOWNLIST

  • enum
  • item

dropdownList

LISTBOX

list

listBox

VALUEON

enabledValue

VALUEOFF

disabledValue

ACTIONLISTON

enabledList

ACTIONLISTOFF

disabledList

KEYNAME

key

EXPLAIN

explainText

VALUENAME

valueName

CLIENTEXT

clientExtension

END

XML syntax includes termination of all its elements. There is no need to use special syntax to terminate an element.

DEFCHECKED

defaultChecked

Line Breaks \n or \n\n

Use link breaks or blank lines within the string definitions.

Maximum string length for EXPLAIN text

Limited by available memory only.

Maximum string length for CATEGORY EXPLAIN text

Limited by available memory only.

Maximum string length for EDITTEXT string

Maximum string length for EDITTEXT string = 1023 characters.