How to Handle Windows Updates

Windows Update Technical Notes

The below outlines the mandatory procedures for managing Windows Updates across the system. To maintain the stability of the Visability platform, updates must be handled differently depending on the role of the machine.

1. System Manager and Display Node Servers

The System Manager and Display Nodes are the most critical components of the Visability ecosystem. Because these servers manage real-time data and high-resolution rendering, their update cycle must be strictly controlled.

Automatic Windows Updates: Disabled

Automatic Windows Updates must be permanently disabled on all System Manager and Display Node servers.

• The Risk: An unmanaged update can trigger an automatic reboot or a service restart at any time. This would result in an immediate loss of the display wall output and a disconnection of all active Visability services.
• The Policy: All Windows Updates must be performed manually by a qualified administrator.

Update Schedule & Scope

• Frequency: Windows Updates should be applied once per month.
• Maintenance Window: Updates must only occur during the weekend, at night, or during a pre-approved maintenance window coordinated with the system owners.
• Security Priority: Maintenance should focus exclusively on Security Packs and critical operating system patches. Do not install optional feature updates or "preview" builds.

Graphics Driver Restriction (Crucial)

The GPU (Graphics Processing Unit) drivers on these machines must never be updated through Windows Update.

• The Policy: Windows must be configured to exclude hardware drivers from its update process.
• Reasoning: Visability performance is tuned to specific driver versions. An automated driver change can lead to rendering failures, loss of hardware acceleration, or total system instability.

1. Operator Workstations

Operator PCs serve as the interface for content creation and sharing. Their update strategy is more proactive to ensure both security and performance.

Pushing Windows Updates

Unlike the core servers, it is often critical to push Windows Updates to Operator PCs via centralized management tools.

• Content Sharing Reliability: When an Operator PC shares its screen or specific application windows to the Visability system, the stability of that "content stream" depends on the health of the operating system. Outdated OS components can cause lag, stuttering, or application crashes during live sharing sessions.
• Security Perimeter: Because these machines are used for daily tasks (such as web browsing or document handling), they are higher-risk entry points. Keeping their Windows Security definitions and patches current is vital to protect the integrity of the wider network.

Implementation Summary

Post-Update Verification

After performing Windows Updates on any core server:

1. Manually restart the machine.
2. Confirm that all Visability services have successfully initialized.
3. Verify that the Display Nodes are communicating correctly with the System Manager before returning to live operations.