Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Making sure that scheduled changes to CIs do not impact business  services

The Finance department at Calbro Services processes payroll checks every Thursday. Allen Allbrook, the configuration administrator, wants to make sure that neither the payroll server nor the payroll printer are taken down for maintenance on Thursdays. He sets two blackout schedules to accomplish this-these key services are unavailable for maintenance on any Thursday.

The payroll server is having performance issues and needs more memory. When Mary Mann, the change coordinator, schedules the change request, she sees that the payroll server is unavailable on Thursday. To prevent conflicts, she creates another unavailable time segment, on Monday instead of Thursday.

The Calbro business process has predefined that this type of change request requires standard approvals to move the project forward.

BMC Asset Management and BMC Change Management must be installed to follow this user scenario. If you cannot find the correct CIs in the Calbro sample data, you must create a server CI and add it to the inventory to follow this user scenario. For more information about managing CIs, see Managing CIs in the BMC Change Management documentation.

The following table describes the typical steps involved in this user scenario:

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*