VMware change control examples

Can you give some examples of changes to your Vcenter, or ESXi hosts, or virtualisation related issues to guests that go through change control, and those that typically wouldn’t require going through change control as they are low/lower risk?

I have been tasked with doing some change control compliance checks but a list of perhaps 5-10 issues that do need to go through change control and 5-10 that don’t for the above 3 categories, that would be a very good starting point. Maybe VMware has some suggestions for standard changes that don’t need to go through full change control, and others that do, but I couldn’t find such a list.  

I guess I am after higher risk changes vs lower risk changes as well. And frequency of how often both appear would also be interesting.
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Connecting to a CDROM/Floppy drive does not require change control, but the software installation does require change control.

All other changes we consider need to go through change control.

1. Addition of CPU - low
2. Addition of Memory - low
3. Adding Network Interface card - Medium
4. Updating VMware Tools - High

But each organization, will categories these differently.

Applicable to VM Guests that require change control

1. Newer versions of VMware Tools or Hyper-V integration tools.
2. Moving a VM from one Processor Vendor to another e.g. AMD to Intel or vice versa
3. Storage vMotion, moving datastores.
4. vMotion moving Hosts.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.