Example List of Changes by type

STANDARD CHANGE EXAMPLES:
  • Install a new printer
  • Move a user physically to another building
  • Reset a password in Campus
  • Set up a new computer for a new employee
  • Relocate a printer
  • Install new software on a desktop
  • Running a script in Campus pre-approved by analyst/developer
  • Reset a network password for a user
  • Reset a password for a user of PeopleSoft or FMS
  • Create a new user in Lotus Notes
  • Close out a Lotus Notes account due to retirement of user
  • Install a Service Pack to a workstation
  • Reset a viewpoint password
  • Apply a minor patch which does not change business functionality
  • Apply a patch to a low impact server
  • Move user to a new OU
  • An upgrade to an application we support that affects less than 25 people
  • Add a user to a security group
  • Create a share
  • Install software on a low impact server
  • Set home drive
  • User imports
  • Replace a router (if during change window)
NORMAL CHANGE EXAMPLES:
  • Install a new printer that is high impact for a mission critical function (payroll check printer)
  • Move a user to another building (one of 100 users in the request.  This would thus represent a high impact change as it affects so many users)
  • Implement a new application that requires more bandwidth thus has high impact
  • Create a new program that changes business functionality for a SPPS enterprise system
  • Move new development projects into production
  • Create a new image for a large number of computers with the goal to use this image throughout the enterprise
  • An upgrade to the Campus application which affects functionality for the users
  • Install a new Service Pack to a high impact server due to issues many users are experiencing
  • Upgrade the database software on a high impact server
  • Decide to roll out a new version of Lotus Notes to the enterprise
  • Changes to Active Directory which have high impact
  • New projects or new development that is adding new or changed business functionality
  • New functional versions of software
  • Putting a new custom report into a file system or into production with a project
  • An upgrade to an application we support if it affects 25 or more people
  • Apply a functional or a technical patch to an enterprise system with a high number of users
  • Any change to Active Directory (high impact as it affects a large number of users)
  • Add a new server
  • add a new Domain Controller
  • Adding new application
  • Implementing a new domain policy
  • Upgrading a domain controller
EMERGENCY CHANGE EXAMPLES:
  • A security breech requiring a patch to an enterprise server or a large number of workstations
  • Data corruption determined on payroll night requiring call to vendor support and a recommended update to data
  • Website is down for payroll advice view and new server needs to be quickly installed
  • Concurrent Manager processes are down, need to restart or reconfigure server agents
  • Hardware malfunction has required a SQL database to be restored to another server
  • Corrupt data from an interface requires the database to be restored from backup
  • Reboot of a domain controller in a network outage situation