By default, Windows 2000 Server automatically creates hidden administrative shares (such as C$, ADMIN$ and print$) for remote administration. You want to prevent these administrative shares from being created on a particular Windows 2000 server computer. What should you do to disable the automatic creation of administrative shares?

Introduction / Context:
Windows 2000 Server automatically creates administrative shares such as C$, ADMIN$ and print$ to allow administrators to manage the system remotely. In some locked down environments, security policy may require disabling these hidden shares to reduce attack surface. Changing this behavior is not exposed through simple graphical options, so administrators must understand how to modify registry settings or apply system policies to prevent their creation.

Given Data / Assumptions:

• Server computers are running Windows 2000 Server.
• Administrative shares like C$ and ADMIN$ are created automatically.
• You want to prevent a specific server from creating these shares.
• You are evaluating whether this can be done through common graphical tools or requires registry changes.

Concept / Approach:
The automatic creation of administrative shares is controlled by registry values under the LanmanServer service in Windows 2000. Microsoft does not provide a simple check box in standard wizards or folder options to disable them. Therefore, you must use a registry editor such as Regedt32.exe or apply a System Policy that modifies the relevant registry values. This direct configuration is necessary because administrative shares are deeply integrated into the Server service and remote management architecture.

Step-by-Step Solution:
Step 1: Identify that administrative shares are created by the Server service when it starts.Step 2: Confirm that there is no option in Configure Your Server or Folder Options to disable these shares.Step 3: Recall that advanced configuration for the Server service is stored in the registry, under keys such as HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\LanmanServer.Step 4: Recognize that administrators use Regedt32.exe or similar tools to edit these registry values or rely on System Policy Editor to deploy the settings consistently.Step 5: Conclude that editing the registry directly or via policy is the only supported method in this question's context to prevent administrative share creation.

Verification / Alternative check:
Experimenting on a test Windows 2000 Server shows that changing the appropriate registry value and restarting the Server service or rebooting the machine results in administrative shares no longer being created. No amount of modification in Configure Your Server or Folder Options impacts this behavior. Microsoft support articles describe registry based approaches for disabling administrative shares, which confirms this method as the correct answer.

Why Other Options Are Wrong:
Claiming that nothing can be done is incorrect because registry modifications are possible. Configure Your Server provides role based configuration but does not expose a setting for administrative shares. Folder Options controls the display of hidden files, system files and Explorer behavior, but it does not alter the underlying Server service configuration. Therefore, only registry editing or System Policy changes meet the requirement.

Common Pitfalls:
Modifying the registry incorrectly can cause system instability or loss of functionality, so administrators should always back up the registry and test changes in a lab environment first. Another pitfall is believing that disabling administrative shares is always recommended; in some organizations it may interfere with backup or management tools that rely on these shares. Careful planning and understanding of operational impact is essential before applying such changes.

Final Answer:
To prevent administrative shares from being created, you must use Reged32.exe or the System Policy Editor to edit the registry on the Windows 2000 server.