After an RFC has passed the initial screening, the change manager must classify and categorize the RFC. The priority level set for a particular RFC determines how quickly the change advisory board (CAB) will review the request for change.
This task provides guidance to the change advisory board emergency committee (CAB/EC) on processing an emergency request for change. The number of emergency change requests should be kept to a minimum because they typically involve high risk and require a great outlay of time and resources. An emergency RFC is different from a standard RFC because it goes through the deployment phase of Microsoft Solutions Framework (MSF).
Emergency changes to DHCP services can have a great impact on a large number of users or can affect business processes that depend on the DHCP server. For this reason, it is very import to create a change request process that emphasizes prioritizing and attending to urgent problems associated with DHCP services. The Infrastructure Role Cluster is responsible for this task, but the request for emergency change can be initiated by any of the MOF role clusters. An emergency change request could involve the release of updates to the operating system, third-party applications, or configuration changes.
● Applying service packs or hotfixes.
● Adding a new DHCP server.
● Adding a new network subnet/route/path/costing values.
● Adjusting thresholds and scope settings above policy.
● Changing backup and restore procedures.
● Modifying and applying policies.
● Changing a process or script used to administer servers.
Along with change type, collect the configuration item that will be affected by the change. Configuration items are objects that are subject to change. Any item that has the possibility of changing falls under change management. For DHCP servers these items include:
Base DHCP Windows Server 2003