What should an administrator do FIRST when planning to apply a service pack on systems running critical applications?

When planning to apply a service pack on systems running critical applications, the first step an administrator should take is to submit a change control for the service pack deployment. Change control is a formal process used to ensure that all changes to IT systems are planned, documented, tested, and approved before they are implemented. This is especially crucial for critical applications because changes could introduce issues or downtime that significantly affect business operations.

Submitting a change control allows for a structured approach to risk management. It involves notifying all relevant stakeholders about the planned changes, evaluating the potential impact on operations, and creating a rollback plan in case the service pack causes unforeseen problems. This process helps maintain operational integrity and minimizes disruption to services that are essential to the business.

Other options may seem beneficial but do not encapsulate the best initial approach when dealing with critical systems. For instance, deploying to a single department or a non-critical application server serves as testing mechanisms but comes as subsequent steps after establishing a change control process. Upgrading the system based on the service pack's requirements is also necessary, but it should follow the approval and planning procedures established through change control.