Avamar Backup of a Windows VM fails with the error: Protocol error from VMX

Recently on a new install of Avamar version 6.1; I had a VMware Image based backup fail with error 10007. Upon further investigation of the backup job log I noticed that the snapshot failed with: A general system error occured: Protocol error from VMX. This is a good example of two very vague errors on both the backup system and the virtual infrastructure. So to further investigate we needed to look deeper into the vmware.log file…

DNS name does not exist Error Code 0x8007232B – Windows 8 Enterprise

I just installed my first GA instance of Microsoft Windows 8 in my lab, and I’m fairly impressed so far. I did however run into an issue where Windows would not activate. When I tried to activate I received the following error: DNS name does not exist Error Code: 0x8007232B

It appears that windows was looking for (by default) a Key Management Service (KMS) host on my internal lab network. Since my lab is merely a testing ground, I have not setup the KMS on any server.  So the solution in this scenario is to change the product key to a Multiple Activation Key (MAK).