airplane

Scenario: SCCM 2012 R2 SP1 CU2 Primary Site server starts having a bad day, puking up hairballs of component status alerts, inboxes are piling up, memory and processor are pegged.  Now, instead of actually troubleshooting the source, you turn off the VM guest which hosts it (not a shut-down; a powering-off).  And then… (drum roll please…)… revert the VM guest to a snapshot from two (2) months earlier.  Power back on, and boom!  It’s broken.

Shocker.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s