¤Óá¹Ð¹ÓÊÓËÃѺ¡ÒèѴ¡ÒÃä¿Åìà·Áà¾Å·¡ÒèѴ¡Òà Group Policy (.adm)

º·¤ÇÒÁ¹Õé͸ԺÒÂÇÔ¸Õ¡Ò÷Óá¿éÁ ADM §Ò¹ ¡ÒõÑ駤èÒ¹âºÒ·Õè¾ÃéÍÁãªé§Ò¹¡ÒèѴ¡ÒáÒôÓà¹Ô¹§Ò¹ áÅФÓá¹Ð¹Óà¡ÕèÂǡѺÇÔ¸Õ¡ÒèѴ¡ÒÃà˵ءÒóì¡ÒèѴ¡ÒÃá¿éÁ ADM ·ÑèÇä»

ËÁÒÂà˵Ø:àÃÒ¢Íá¹Ð¹ÓãËé ¤Ø³ãªé Windows Vista à¾×èͨѴ¡ÒÃâ¤Ã§ÊÃéÒ§¾×é¹°Ò¹¢Í§'¹âºÒ¡ÅØèÁ' â´Â¡ÒÃãªéÃéÒ¹¤éÒ¡ÅÒ§ ¤Óá¹Ð¹Ó¹ÕéÂѧ¤§à»ç¹¨ÃÔ§áÁéÇèÒÊÀÒ¾áÇ´ÅéÍÁ¡Ò÷ӧҹ·ÕèÁÕ¡ÒüÊÁ¢Í§ä¤ÅàÍç¹µìÃдѺáÅÐà«ÔÃì¿àÇÍÃì àªè¹¤ÍÁ¾ÔÇàµÍÃì·ÕèÃѹ Windows XP ËÃ×Í Windows Server 2003 windows Vista ãªéÃٻẺãËÁè·Õè employs ADMX áÅÐ ADML á¿éÁ·Õè¨Ð¨Ñ´¡ÒÃáÁèẺ¢Í§¹âºÒ¡ÅØèÁ

ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁ â»Ã´ä»·ÕèàÇçºä«µìµèÍ仹Õé:¶éҤسµéͧãªé¤ÍÁ¾ÔÇàµÍÃì·Õèãªé Windows XP ËÃ×Íà«ÔÃì¿àÇÍÃì·Õèãªé Windows server 2003 㹡ÒèѴ¡ÒÃâ¤Ã§ÊÃéÒ§¾×é¹°Ò¹¢Í§ Group Policy ´Ù¤Óá¹Ð¹Ó㹺·¤ÇÒÁ¹Õé

º·¹ÓÊÙè¡Òà ADM á¿éÁ

á¿éÁ ADM à»ç¹á¿éÁáÁèẺ·Õèãªé§Ò¹ â´Â¹âºÒ¡ÅØèÁà¾×èÍ͸ԺÒÂʶҹ·Õè¨Ñ´à¡çº¡ÒõÑ駤èÒ¹âºÒ·ÕèãªéÃÕ¨ÔÊ·ÃÕã¹ÃÕ¨ÔÊ·ÃÕ ADM á¿éÁ¹Í¡¨Ò¡¹ÕéÂѧ͸ԺÒÂÍÔ¹à·ÍÃìà¿«ÊÓËÃѺ¼Ùéãªé·Õè¼Ùé´ÙáŵÑÇ㹡ÒÃá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁµÑǹÔéÇá¹»á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ¶Ù¡ãªé â´Â¼Ùé´ÙáÅÃкºàÁ×è;ǡà¢ÒÊÃéÒ§ ËÃ×Íá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ (GPOs) ·ÕèÁͧàËç¹

¡ÒèѴà¡çºá¿éÁ ADM áÅФèÒàÃÔèÁµé¹

ã¹â¿Åà´ÍÃì Sysvol ¢Í§áµèÅеÑǤǺ¤ØÁâ´àÁ¹ áµèÅÐâ´àÁ¹Çѵ¶Ø¹âºÒ¡ÅØèÁâ¿Åà´ÍÃìà´ÕÂÇ·Õèà¡çºÃÑ¡ÉÒ áÅÐâ¿Åà´ÍÃì¹ÕéÁÕª×èÍÇèÒ Group Policy áÁèẺ (GPT) GPT à¡çºá¿éÁ ADM ·Ñé§ËÁ´·ÕèãªéµÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁàÁ×èÍ gpo ¶Ù¡ÊÃéÒ§ ËÃ×Íá¡é䢤ÃÑé§ÅèÒÊØ´

Ãкº»¯ÔºÑµÔ¡ÒÃáµèÅÐÃÇÁ¶Ö§ªØ´Áҵðҹ¢Í§á¿éÁ ADM á¿éÁÁҵðҹàËÅèÒ¹ÕéÁÕá¿éÁàÃÔèÁµé¹·Õè¨ÐâËÅ´µÑÇâ´Âá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ µÑÇÍÂèÒ§àªè¹ Windows Server 2003 ÁÕ ADM ·ÕèµèÍ仹Õéá¿éÁ:

• System.adm
• Inetres.adm
• Conf.adm
• Wmplayer.adm
• Wuau.adm

á¿éÁ ADM Ẻ¡Ó˹´àͧ

¤Ø³ÊÒÁÒöÊÃéÒ§á¿éÁ ADM Ẻ¡Ó˹´àͧ â´Â¹Ñ¡¾Ñ²¹Òâ»Ãá¡ÃÁ ËÃ×Í IT ¼ÙéàªÕèÂǪҭ´éÒ¹¡ÒâÂÒ¡ÒÃãªé¡ÒõÑ駤èÒ¹âºÒÂÃÕ¨ÔÊ·ÃÕâ´Âãªéâ»Ãá¡ÃÁãËÁèáÅФÍÁâ¾à¹¹µìä´é

ËÁÒÂà˵Ø:â»Ãá¡ÃÁáÅФÍÁâ¾à¹¹µìµéͧ¶Ù¡Í͡Ẻ áÅÐ coded ¡ÒÃ¨Ó áÅСÒõͺʹͧµèÍ¡ÒõÑ駤èÒ¹âºÒ·Õè͸ԺÒÂäÇéã¹á¿éÁ ADM

âËÅ´á¿éÁ ADM µÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ:

1. àÃÔèÁµÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ
2. ¤ÅÔ¡¢ÇÒáÁèẺ¡ÒôÙáÅÃкºáÅéÇ ¤ÅÔ¡à¾ÔèÁ/àÍÒáÁèẺ¡ÒÃÍÍ¡.
   
   ËÁÒÂà˵Ø:áÁèẺ¡ÒôÙážÃéÍÁãªé§Ò¹ÀÒÂãµéÍÂèÒ§ã´ÍÂèҧ˹Ö觤ÍÁ¾ÔÇàµÍÃìËÃ×Í¡ÒáÓ˹´¤èÒ¼Ùéãªé. àÅ×Í¡¡ÒáÓ˹´¤èÒ·Õè¶Ù¡µéͧÊÓËÃѺµé¹áºº¡Ó˹´àͧ¢Í§¤Ø³
3. ¤ÅÔ¡add.
4. ¤ÅÔ¡á¿éÁ¢éÍ ADM áÅШҡ¹Ñé¹ ¤ÅÔ¡OPEN.
5. ¤ÅÔ¡»Ô´.
6. µÑé§áºº¡Ó˹´àͧ ADM á¿éÁ¤èÒ¹âºÒÂ㹵͹¹Õé¨Ð¾ÃéÍÁãªé§Ò¹µÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ

»ÃѺ»Ãاá¿éÁ ADM áÅÐ timestamps

áµèÅÐàÇÔÃì¡Ê൪ѹ¼Ùé´ÙáÅ·ÕèÁÕãªé¡ÒÃàÃÕ¡ãªéµÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁà¡çºá¿éÁ ADM ã¹â¿Åà´ÍÃì %windir%\Inf àÁ×èÍÊÃéÒ§ áÅÐá¡é䢡è͹ gpo á¿éÁ ADM ¨Ò¡â¿Åà´ÍÃì¹Õé¨Ð¶Ù¡¤Ñ´ÅÍ¡ä»Âѧâ¿Åà´ÍÃìÂèÍ Adm ã¹áºº GPT «Öè§ÃÇÁ¶Ö§á¿éÁ ADM ÁҵðҹáÅÐá¿éÁ ADM Ẻ¡Ó˹´àͧ·ÕèÁÕà¾ÔèÁ â´Â¼Ùé´ÙáÅ

ËÁÒÂà˵Ø:¡ÒÃÊÃéÒ§ GPO â´ÂäÁèµéͧ¡ÒÃá¡éä¢ GPO ·Õèã¹ÀÒÂËÅѧÊÃéҧẺ GPT â´ÂäÁèÁÕá¿éÁã´ æ ADM

à»ÃÕº â´Â¤èÒàÃÔèÁµé¹ àÁ×èÍÁÕá¡éä¢ gpo µÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁà·Õº timestamps ADM á¿éÁã¹â¿Åà´ÍÃì %windir%\Inf ¢Í§àÇÔÃì¡Ê൪ѹ·ÕèÁÕ·Õèà¡çºäÇéã¹â¿Åà´ÍÃì Adm GPTs ¶éÒá¿éÁ¢Í§àÇÔÃì¡Ê൪ѹãËÁè¡ÇèÒ ¤Ñ´µÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁÅÍ¡á¿éÁàËÅèÒ¹Õéä»Âѧâ¿Åà´ÍÃì Adm GPT à¢Õ¹·Ñºá¿éÁã´ æ ·ÕèÁÕÍÂÙè¢Í§ª×èÍà´ÕÂǡѹ ¡ÒÃà»ÃÕºà·Õº¹Õéà¡Ô´¢Öé¹àÁ×èÍâ˹áÁèẺ¡ÒôÙáÅ(â¤Ã§¤ÍÁ¾ÔÇàµÍÃìËÃ×ͼÙéãªéẺ) ÁÕàÅ×Í¡µÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ ¤Ó¹Ö§¶Ö§ÇèÒ¼Ùé´ÙáÅÃкº·Õèá·é¨ÃÔ§áÅéÇá¡éä¢ GPO

ËÁÒÂà˵Ø:á¿éÁ ADM ·Õèà¡çºäÇéã¹ GPT ÊÒÁÒö»ÃѺ»Ãا ´éÇ¡Òô٠GPO µÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ

à¹×èͧ¨Ò¡ÁÕ¤ÇÒÁÊӤѭ timestamps 㹡ÒèѴ¡ÒÃá¿éÁ ADM ¡ÒÃá¡é䢨ҡÃкºá¿éÁ ADM äÁèá¹Ð¹Ó If a new policy setting is required, Microsoft recommends that you create a custom ADM file. This prevents the replacement of system-supplied ADM files when service packs are released.

Group Policy Management Console

By default, the Group Policy Management Console (GPMC) always uses local ADM files, regardless of their time stamp, and never copies the ADM files to the Sysvol. If an ADM file is not found, GPMC looks for the ADM file in the GPT. Also, the GPMC user can specify an alternative location for ADM files. If an alternative location is specified, this alternative location takes precedence.

GPO replication

The File Replication Service (FRS) replicates the GPTs for GPOs throughout the domain. As part of the GPT, the Adm subfolder is replicated to all domain controllers in the domain. Because each GPO stores multiple ADM files, and some can be quite large, you must understand how ADM files that are added or updated when you use Group Policy Object Editor can affect replication traffic.

Use policy settings to control ADM file updates

Two policy settings area available to help with management of ADM files. These settings make it possible for the administrator to tune the use of ADM files for a specific environment. These are the "Turn off automatic updates of ADM files" and the "Always use local ADM files for Group Policy Editor" settings.

Turn off automatic updates of ADM files

This policy setting is available under User Configuration\Administrative Templates\System\Group Policy in Windows Server 2003, in Windows XP, and in Windows 2000. This setting may be applied to any Group Policy-enabled client.

Always use local ADM files for Group Policy editor

This policy setting is available under Computer Configuration\Administrative Templates\System\Group Policy. This is a new policy setting. It may be successfully applied only to Windows Server 2003 clients. The setting may be deployed to older clients, but it will have no effect on their behavior. If this setting is enabled, Group Policy Object Editor always uses local ADM files in the local system %windir%\Inf folder when you edit a Group Policy object.

ËÁÒÂà˵Ø:If this policy setting is enabled, theTurn off automatic updates of ADM filespolicy setting is implied.

Common scenarios and recommendations

Multilanguage administration issues

In some environments, policy settings may have to be presented to the user interface in different languages. For example, an administrator in the United States may want to view policy settings for a specific GPO in English, and an administrator in France may want to view the same GPO by using French as their preferred language. Because the GPT can store only one set of ADM files, you cannot use the GPT to store ADM files for both languages.

For Windows 2000, the use of local ADM files by Group Policy Object Editor is not supported. To work around this, use the "Turn off automatic updates of ADM files" policy setting. Because this policy setting has no affect on the creation of new GPOs, the local ADM files will be uploaded to the GPT in Windows 2000, and creating a GPO in Windows 2000 effectively defines “the language of the GPO”. If the "Turn off automatic updates of ADM files" policy setting is in effect at all Windows 2000 workstations, the language of the ADM files in the GPT will be defined by the language of the computer that is used to create the GPO.

For administrators that are using Windows XP and Windows Server 2003, the "Always use local ADM files for Group Policy editor" policy setting can be used. This makes it possible for the French administrator to view policy settings by using the ADM files that are installed locally on his or her workstation (French), regardless of the ADM file that is stored in the GPT. Note that when you use this policy setting, it is implied that the "Turn off automatic updates of ADM files" policy setting is enabled to avoid unnecessary updates of the ADM files to the GPT.

Also, consider standardizing on the latest operating system from Microsoft for administrative workstations in a multi-language administrative environment. Then configure both the "Always use local ADM files for Group Policy editor" and "Turn off automatic updates of ADM files" policy settings.

¶éÒÁÕ¡ÒÃãªéÊ൪ѹ 2000 Windows ãªé¡ÒõÑ駤èÒ¹âºÒ "»Ô´¡ÒûÃѺ»ÃاÍѵâ¹ÁѵԢͧá¿éÁ ADM" ÊÓËÃѺ¼Ùé´ÙáÅ áÅÐãËé¾Ô¨ÒóÒä¿Åì ADM ã¹ GPT à»ç¹ ÀÒÉÒÁռźѧ¤ÑºãªéÊÓËÃѺàÇÔÃì¡Ê൪ѹ·Ñé§ËÁ´¢Í§ Windows 2000

ËÁÒÂà˵Ø:àÇÔÃì¡Ê൪ѹ¢Í§ windows XP ÍÒ¨Âѧ¤§ãªé¢Í§µ¹ÀÒÂã¹ ÀÒÉÒ੾ÒÐÃØè¹

Ãкº»¯ÔºÑµÔ¡ÒÃáÅкÃÔ¡ÒúÃèØÍÍ¡ÇÒ§¨Ó˹èÒÂ

ÃØ蹪شáµèÅÐÃкº»¯ÔºÑµÔ¡ÒÃËÃ×ͺÃÔ¡ÒÃÃÇÁ¶Ö§ superset ADM á¿éÁ·ÕèÁÒ¨Ò¡ÃØ蹡è͹˹éÒ ¡ÒÃÃÇÁ¶Ö§¡ÒõÑ駤èÒ¹âºÒ·ÕèÁÕ੾ÒÐã¹Ãкº»¯ÔºÑµÔ¡Ò÷Õèᵡµèҧ仢ͧÃØè¹·ÕèãËÁè µÑÇÍÂèÒ§àªè¹ á¿éÁ ADM ·ÕèãËéÁҡѺ Windows Server 2003 ÁÕ¡ÒõÑ駤èÒ¹âºÒ·Ñé§ËÁ´ÊÓËÃѺ Ãкº»¯ÔºÑµÔ¡Ò÷Ñé§ËÁ´ÃÇÁ·Ñ駷ÕèÍÂÙè·Õèà¡ÕèÂÇ¢éͧ¡Ñº Windows 2000 ËÃ×Í Windows XP Professional à·èÒ¹Ñé¹ «Öè§ËÁÒ¤ÇÒÁ ÇèÒ ¡Òô٠GPO ¨Ò¡¤ÍÁ¾ÔÇàµÍÃì·ÕèÁÕÃкº»¯ÔºÑµÔ¡ÒÃÃØè¹ãËÁèà·èÒ¹Ñé¹ ËÃ×Íà«ÍÃìÇÔÊá¾ç¤ upgrades á¿éÁ ADM ÍÂèÒ§ÁÕ»ÃÐÊÔ·¸ÔÀÒ¾ à»ç¹ÃØè¹·ÕèãËÁè¡ÇèÒä´éâ´Â»¡µÔ superset á¿éÁ ADM ¡è͹˹éÒ ¹Õé¨ÐäÁèÁÑ¡¨ÐÊÃéÒ§»Ñ­ËÒ ÊÁÁµÔÇèÒ á¿éÁ ADM ·Õè¡ÓÅѧãªé§Ò¹ä´éäÁè¶Ù¡á¡éä¢

㹺ҧʶҹ¡Òóì ÂèÍ service pack Ãкº»¯ÔºÑµÔ¡ÒÃËÃ×ͺÃÔ¡ÒÃÍÒ¨ÃÇÁ¶Ö§ªØ´ÂèÍ¢ͧá¿éÁ ADM ·Õè¹ÓàʹÍãËé¡ÑºÃØ蹡è͹˹éÒ âÍ¡Òʢͧ¡ÒùÓàʹͪشÂèÍÂà»ç¹ÃØ蹡è͹˹éҢͧá¿éÁ ADM à»ç¹¼Å㹡ÒõÑ駤èÒ¹âºÒ·ÕèäÁè¶Ù¡ÁͧàËç¹¼Ùé´ÙáÅÃкºàÁ×è;ǡà¢Ò¨ÐãªéµÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ¹Õéä´é ÍÂèÒ§äáçµÒÁ ¡ÒõÑ駤èÒ¹âºÒ¨ÐÂѧ¤§·Ó§Ò¹ÍÂÙèã¹ GPO ੾ÒÐáÊ´§¼Å¢Í§¡ÒõÑ駤èÒ¹âºÒµÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁä´éÃѺ¼Å¡Ãзº ãªé§Ò¹ÍÂÙèã´ æ (à»Ô´ãªé§Ò¹ËÃ×ͻԴ¡ÒÃãªé§Ò¹) ¡ÒõÑ駤èÒ¹âºÒÂäÁè»ÃÒ¡¯µÑÇã¹á¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ áµèÂѧ¤§·Ó§Ò¹ÍÂÙè à¹×èͧ¨Ò¡¡ÒõÑ駤èÒ·ÕèäÁèÊÒÁÒöÁͧàËç¹ä´é äÁèà»ç¹ä»ä´éÊÓËÃѺ¼Ùé´ÙáÅàÁ×è͵éͧ¡Òô٠ËÃ×Íá¡é䢡ÒõÑ駤èÒ¹âºÒÂàËÅèÒ¹Õé àÁ×è͵éͧ¡ÒÃá¡é䢻ѭËÒ¹Õé ¼Ùé´ÙáÅÃкºµéͧ¨Ð¤Øé¹à¤Â¡Ñºá¿éÁ ADM ·ÕèÁÕÍÂÙèã¹áµèÅÐÃкº»¯ÔºÑµÔ¡ÒÃËÃ×ͺÃÔ¡ÒêشÂèÍ¡è͹·Õè¨ÐãªéµÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ·ÕèÃкº»¯ÔºÑµÔ¡Òà ¡Òà ÃÑ¡ÉÒâ»Ã´ÃÐÅÖ¡ÇèÒ ´Óà¹Ô¹¡Ò÷Õè´Ù GPO äÁèà¾Õ§¾Í㹡ÒûÃѺ»Ãاá¿éÁ ADM ã¹ GPT àÁ×èÍà»ÃÕºà·Õº¡ÒûÃзѺàÇÅÒ¡Ó˹´ÇèÒ ¡ÒûÃѺ»ÃاàËÁÒÐÊÁ

àÁ×è͵éͧ¡ÒÃÇҧἹÊÓËÃѺ¹Õéã¹ÊÀÒ¾áÇ´ÅéÍÁ¡Ò÷ӧҹ¢Í§¤Ø³ Microsoft á¹Ð¹Ó·Õè¤Ø³à»ç¹:

• ¡Ó˹´¡ÒÃÁҵðҹÃкº»¯ÔºÑµÔ¡ÒÃ/à«ÍÃìÇÔÊá¾ç¤·Õè·Ñé§ËÁ´´Ù áÅÐá¡é䢢ͧ gpo à¡Ô´ ·ÓãËéá¹èã¨ÇèÒ á¿éÁ ADM ·Õè¡ÓÅѧãªéÃÇÁ¶Ö§¡ÒõÑ駤èÒ¹âºÒÂÊÓËÃѺ·Ø¡á¾Å·¿ÍÃìÁ
• ãªé¡ÒõÑé§ "»Ô´¡ÒûÃѺ»ÃاÍѵâ¹ÁѵԢͧá¿éÁ ADM" ¹âºÒ¤èÒÊÓËÃѺ¼Ùé´ÙáÅ'¹âºÒ¡ÅØèÁ'·Ñé§ËÁ´à¾×è͵ÃǨÊͺãËéá¹èã¨ÇèÒ á¿éÁ ADM ¨ÐäÁè¶Ù¡à¢Õ¹·Ñºã¹ GPT ·Õèà«ÊªÑ¹µÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁã´ æ áÅеÃǨÊͺãËéá¹èã¨ÇèÒ ¤Ø³¡ÓÅѧãªéá¿éÁ ADM ÅèÒÊØ´·Õè¾ÃéÍÁãªé§Ò¹¨Ò¡ Microsoft

ËÁÒÂà˵Ø:¹âºÒ "ãªéàÊÁÍá¿éÁ ADM ÀÒÂã¹à¤Ã×èͧÊÓËÃѺµÑÇá¡é䢹âºÒ¡ÅØèÁ" â´Â·ÑèÇä»ãªé¡Ñº¹âºÒ¹Õé àÁ×èÍÁÕʹѺʹع â´ÂÃкº»¯ÔºÑµÔ¡Ò÷ÕèÁÕ¡ÒÃàÃÕ¡ãªéµÑÇá¡éä¢Çѵ¶Ø¹âºÒ¡ÅØèÁ

àÍÒá¿éÁ ADM ¨Ò¡â¿Åà´ÍÃì Sysvol

â´Â¤èÒàÃÔèÁµé¹ ADM á¿éÁ·Õèà¡çºäÇéã¹ GPT áÅЫÖè§ÊÒÁÒöà¾ÔèÁ¢¹Ò´¢Í§â¿Åà´ÍÃì Sysvol ÁÒ¡ ¹Í¡¨Ò¡¹Õé ºèÍ æ á¡éä¢ gpo ÍÒ¨Ê觼Å㹨ӹǹ·ÕèÊӤѭ¢Í§¡ÒÃÃѺÊ觢éÍÁÙÅ¡ÒèÓÅͧẺ â´ÂãªéªØ´¢Í§ "à»Ô´»Ô´¡ÒûÃѺ»ÃاÍѵâ¹ÁѵԢͧá¿éÁ ADM" áÅÐ "·éͧ¶Ôè¹ãªéàÊÁÍ ADM á¿éÁÊÓËÃѺµÑÇá¡é䢹âºÒ¡ÅØèÁ" ¡ÒõÑ駤èÒ¹âºÒ¡ÒÃÅ´¢¹Ò´¢Í§â¿Åà´ÍÃì Sysvol áÅÐÅ´»ÃÔÁÒ³¡ÒÃãªé§Ò¹·Õèà¡ÕèÂǡѺ¹âºÒ¡ÒèÓÅͧẺ·ÕèËÁÒÂàÅ¢·ÕèÊӤѭ¢Í§¡ÒÃá¡é䢹âºÒÂà¡Ô´¢Öé¹ä´éÍÂèÒ§ÁÒ¡¢Öé¹

ËÒ¡»Ñ­ËÒ¢¹Ò´¢Í§ä´Ã¿ì¢éÍÁÙÅ Sysvol ËÃ×Í¡ÒÃÃѺÊ觢éÍÁÙÅà¡ÕèÂǡѺ'¹âºÒ¡ÅØèÁ'¡ÒèÓÅͧẺ ãËéÅͧãªéÊÀÒ¾áÇ´ÅéÍÁ·Õè Sysvol ¨ÐäÁèà¡çºá¿éÁ ADM ã´ æ ËÃ×;ԨÒóҡÒúÓÃاÃÑ¡ÉÒá¿éÁ ADM º¹àÇÔÃì¡Ê൪ѹ·Õè¼Ùé´ÙáÅ ¡Ãкǹ¡ÒùÕéÁÕ¡ÒÃ͸ԺÒÂäÇéã¹ÊèǹµèÍ仹Õé

àÁ×è͵éͧ¡ÒáàÅÔ¡àÅ×Í¡â¿Åà´ÍÃì Sysvol ¢Í§ ADM á¿éÁ:

1. ¡ÒõÑé§ "»Ô´¡ÒûÃѺ»ÃاÍѵâ¹ÁѵԢͧá¿éÁ ADM" ¹âºÒ¤èÒÊÓËÃѺ¼Ùé´ÙáÅ'¹âºÒ¡ÅØèÁ'·Ñé§ËÁ´·Õè¨ÐÊÒÁÒöá¡éä¢ gpo ·Õèà»Ô´ãªé§Ò¹
2. Make sure that this policy has been applied.
3. Copy any custom ADM templates to the %windir%\Inf folder.
4. Edit existing GPOs, and then remove all ADM files from the GPT. àÁ×è͵éͧ¡Ò÷Óàªè¹¹Õé ¤ÅÔ¡¢ÇÒáÁèẺ¡ÒôÙáÅÃкºáÅéÇ ¤ÅÔ¡Add/Remove Template.
5. Enable the "Always use local ADM files for Group Policy Object Edit" policy setting for administrative workstations.

Maintain ADM files on administrative workstations

When you use the "Always use local ADM files for Group Policy editor" policy setting, make sure that each workstation has the latest version of the default and custom ADM files. If all ADM files are not available locally, some policy settings that are contained in a GPO will not be visible to the administrator. Avoid this by implementing a standard operating system and service pack version for all administrators. If you cannot use a standard operating system and service pack, implement a process to distribute the latest ADM files to all administrative workstations.

ËÁÒÂà˵Ø:Because the workstation ADM files are stored in the %windir%\Inf folder, any process that is used to distribute these files must run in the context of an account that has administrative credentials on the workstation.

ËÁÒÂà˵Ø:Windows XP does not support editing GPOs when there are no ADM files in the Sysvol folder. In a live environment, you must consider this design limitation.

For more information about Group Policies in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base: