Microsoft Word Hardware Reconfiguration Methodology V final2

Rollout

The deployment should proceed according to the deployment plan. The deployment plan should be developed in terms resource availability as well as organizational policy and procedure. It is here that the actual modifications to operational systems are made.

Due to extensive laboratory testing, few unknown problems and other issues should be encountered during the operational deployment although the possibility of this occurring exists. This is because laboratory testing cannot take everything into account that is to be found in operational settings. It is conceivable that a deployment could have interacted in unforeseen ways with the operational network. These inevitabilities cannot be taken into as they tend to be random in nature and can potentially caused by many difficult to pinpoint sources of origin (i.e. electrical short-circuit, cosmic rays, solar flare, etc.).

Regardless of the potential for failure (which should be relatively low), the deployment should follow as closely as possible the development plan put together in the previous section. The rollout phase should be documented just as has been done for all of the previous steps because should failure(s) occur then using well-written documentation it may be possible to track the root cause of the problem or failure.

4. Reconfiguration and migration

As stated in Section 4.6.14, a reconfiguration or migration is necessary only if hardware changes have been made to one or more of the underlying systems present on the operational network or infrastructure. If no hardware changes have been made then neither a reconfiguration nor migration is necessary. However, if changes have been made then in order for that new hardware to function correctly the operating system will have to recognize it. However, each distribution is unique and each operating system will have its own mechanism for detecting hardware changes and make them available to the operating system. It is beyond the scope of this report to directly examine or detail the specifics concerning reconfiguration and migration; more information can be found in Report [1].

5.