Microsoft KB Archive/260242

= HOW TO: Prevent Windows 2000 Upgrade from Modifying Custom Security =

Article ID: 260242

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition

-



This article was previously published under Q260242





IN THIS TASK
SUMMARY
 * Modifying Templates

REFERENCES



SUMMARY
The Windows 2000 upgrade process applies Windows 2000 default security settings to registry keys and file system objects. This process overwrites any custom permissions that you previously defined. If the Windows 2000 default security settings are in conflict with custom permissions, programs that rely on the custom permissions may not work properly.

Windows 2000 uses the following security templates to apply security settings during the upgrade process:
 * Dwup.inf (for Windows 2000 Professional upgrades)
 * Dsup.inf (for Windows 2000 Server upgrades)

back to the top

Modifying Templates
To prevent the upgrade process from modifying custom security settings, you can modify these text-based templates to ignore the specific folders, files, or registry keys that contain custom security settings using the following steps:  Copy the appropriate template file (Dwup.inf or Dsup.inf) from your Windows 2000 distribution share into the %WinDir%\Security\Templates folder on your local computer. Start Microsoft Management Console (click Start, click Run, type mmc.exe, and then click OK). From the Console menu, click Add/Remove Snap-in, click Add, click Security Templates, click Add, click Close, and then click OK. To open the template file you want to modify, expand the Security Templates node, expand the %WinDir%\Security\Templates folder, and then expand the appropriate template file (Dwup.inf or Dsup.inf). Click the security area that you want to modify (Registry or File System). In the result pane, a list of all of the registry keys or file system objects configured by the default upgrade template is displayed. Determine whether or not the object you want the upgrade to ignore is explicitly configured by the template, and then use the appropriate steps: If the object you want the upgrade to ignore is not explicitly configured by the upgrade template, you must add it using the following steps:

<ol style="list-style-type: lower-alpha;"> Right-click Registry or File System, and then click Add Key or Add File.</li> Browse the dialog box to select the key or file system object you want to protect (for example, Machine\Software\MyISV). If the key, folder, or file does not exist on your computer, you can type the path to the object in the available box.</li> Click OK to start the Access Control List (ACL) editor.</li> Click OK again to accept the default security provided by the ACL editor.</li> Click Do not allow permissions on this key\file to be replaced.</li> Click OK to add the object to the template, and then go to step 7.</li></ol>

If the object you want the upgrade to ignore is already explicitly configured in the upgrade template, modify it using the following steps:

<ol style="list-style-type: lower-alpha;"> In the result pane, double-click the object you want to protect.</li> Click Do not allow permissions on this key\file to be replaced, click OK, and then go to step 7.</li></ol> </li> In the result pane, the object you want the upgrade to ignore should now be listed with the Ignore property listed under both the permission and audit columns. Right-click the name of the template, and then click Save.</li> Copy the modified template back to the distribution share.</li></ol>

Future upgrades from this distribution share will not configure the ignored objects with Windows 2000 default settings.

back to the top

Additional query words: ACLs mmc

Keywords: kbenv kbhowto kbhowtomaster KB260242

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.