An administrator is planning an upgrade of a major software package on an application server. The software has been tested successfully in a test environment and it is ready to go into production…

Identifying necessary OS updates is a planning and testing phase activity that should have already been completed before the software was approved for production.

Implementing the change without first scheduling downtime bypasses change management process and risks impacting users without notice.

Documenting the change is required, but documentation of the implementation details occurs during or after the change, not before scheduling the maintenance window.

Even after successful testing, deploying a major software upgrade to a production application server requires a scheduled maintenance window to communicate impact to stakeholders, coordinate with affected users, and ensure the change is performed in a controlled manner. Scheduling downtime is a formal change management step that precedes implementation and prevents unplanned outages. Skipping this step risks disrupting active users and violating change management policy.