Branch offices on Windows 2000 Server need automatic notifications when new Microsoft updates (including drivers) are available upon admin logon. What should you install/configure to provide these alerts?

Introduction / Context:
In the Windows 2000 era, Microsoft provided an optional component called Critical Update Notification to alert administrators when new updates from Microsoft were available. This was a precursor to later services like Automatic Updates and WSUS and could notify at logon so admins in branch offices were prompted to obtain and apply relevant updates.

Given Data / Assumptions:

• Each branch has a Windows 2000 Server but no dedicated network administrator.
• Admins log on locally and should be notified automatically when new updates exist.
• Goal: prompt awareness without manual polling of Microsoft sites.

Concept / Approach:
The Critical Update Notification tool periodically checks Microsoft's update catalog and prompts users at logon or on a schedule when critical updates and certain drivers are available. Installing it on each branch server ensures that local technical staff receive timely prompts to download and apply updates, closing security and reliability gaps.

Step-by-Step Solution:

Verification / Alternative check:
Log on after installation and confirm that update notifications appear when new items are available; check the tool’s configuration for last check time and status.

Why Other Options Are Wrong:

• The Resource Kit contains utilities but does not provide update notifications.
• System File Checker and Windows File Protection monitor protected system files locally; they do not poll Microsoft for new updates or drivers.

Common Pitfalls:
Assuming this tool automatically installs updates; it only notifies. Ensure administrative procedures handle testing and deployment appropriately.

Final Answer:
Install Windows Critical Update Notification