I had to run some routine security updates for a client yesterday on a host OS running Hyper-V. It was after hours, so I just shut down the two virtual machines and rebooted the physical server after the udpates. When it came back up, I went into Hyper-V Manager and tried to power on my VM's. Low and behold, where there were once two VM's, I now only saw one.
I tried and failed to create a new VM and import the VHD to it, receiving a cryptic unspecified error message with some information that seemed to suggested a network adapter issue. I deleted the virtual network adapter and tried to create a new one, but that only resulted in further error messages.
Turns out Trend Micro decided I was most definitely a threat to the system and was destroying my virtual network adapters and crashing Hyper-V processes left and right. Awesome.
Subscribe to:
Post Comments (Atom)
Red Flags and the Value of Experience
One of the things I hear often said, and something I subscribe to as well, is the idea that a lot of technical knowledge in the world of IT ...
-
UPDATE: Turns out this is a known issue during the 1.5 > 5.1 VSM upgrade and a fix should be released in an upcoming patch. That's ... -
After completing an Exchange 2007 > 2013 migration recently, I was left with one issue that was preventing us from stamping the project...
-
Because I'm a glutton for punishment, I recently started rolling out System Center Configuration Manager 2012 R2 SP1 and System Center E...
No comments:
Post a Comment