System Management

[rainit2006]

• Policies and Procedures
• Systems Management Best Practices

[rainit2006]

Policies and Procedures

Change Management several objectives: To maximize business value, To ensure that all proposed changes are both evaluated and recorded, To prioritize, plan, test, implement, document, and review all changes, To optimize overall business risk, To act as a control mechanism

several consistent :

• RFC(request for change) submitter: IT leadership, system administrator, end user
• change proposal, submitter: CIO or higher position
• change type; normal changes, standard changes, emergency changes
• change manager
• CAB (Change Advisory Board), ECAB(Emergency Change Advisory Board)

Configuration Management

• objectives of CM Identifying configuration items (CIs) Controlling CIs Protecting the integrity of CIs Maintaining CMS(configuration management system) Maintaining information about the state of all CIs Providing accurate configuration information

• configuration management process's benefit

• for each CIs -- Identify the instance of CIs -- Control changes to CIs through the use of a change management process -- Record all the attributes of CI in CMDB(configuration management Database) CMDB -> CMS CIs must contains one key attribute: ownership. -- Report on, periodically audit, verify

Capacity Management in design phase, the design of the configuration is import. The capacity management process includes producing and maintaining an appropriate capacity plan.

Life Cycle Management
from requirement to retirement

• Framework:
  ITIL(Information Technology Infrastructure Library):
  1. Service strategy
  2. Service design
  3. Service transition
  4. Service operation
  5. Continual service improvement each phase has input and output that connect the phase to one another.

MOF(Microsoft Operations Framework)

1. Plan
2. Deliver
3. Operate
4. Manage

[rainit2006]

Systems Management Best Practices

• Documentation
• Standardization
• Planning