While performing a P2V with SCVMM 2012 I got the following error message:
There is not enough disk space on the available volumes.
Maximum disk space on the most appropriate volume, accounting for the host resource utilization (in megabytes): 103450
The virtual machine requirement (in megabytes): 744776
The maximum available space at the time of evaluation, after considering the virtual machine requirements (in megabytes): 103450
ID: 3501 Continue reading P2V using SCVMM error’s because of disk space requirement
I’ve got a multiple node cluster running Windows Server 2012 with Brocade 415/815 4G/8G FC HBA’s connecting to a VX SAN. I am trying to get the virtual HBA’s working in Hyper-V Guest running Windows 2008 R2 (SQL Cluster). I first created 2 virtual SAN Switches one connected to each port on my physical HBA (each physical port connects to a separate fabric). I add two Virtual HBA’s in my Guest, one to each VSAN Switch. When I go to Zone the HBA’s I only see side A of the virtual HBA’s not both A and B. On each fabric I should see two (A and B) WWPN but I only see one, to solve this you must shut down the Guest OS and twist the address set name (copy Set Address A to Set Address B and Set Address B to Set address A) I can add disk and everything works, however when I go to Live migrate I get the following error due to side B not being zoned. Live migration of ‘Virtual Machine Win2012_01’ failed. Continue reading Windows Server 2012 Failover Cluster Virtual Fibre Channel Adapter Live Migration Error
After migrating a standalone Windows domain controller to a Hyper-V environment, I noticed that some group policy objects weren’t being enforced. It turned out some of the GPOs were missing from the SYSVOL share because it wasn’t replicating on the newly virtualized DC. After checking the directory service event logs I found repeated entries for event ID 13359, stating
Continue reading Fix event ID 13559 problem on a Windows server
When you try to set up Microsoft Exchange Server 2010 on a Hyper-V virtual machine, the setup process may fail. Additionally, you receive the following error message:
“An error occurred with error code ‘2147504141’ and message ‘The property cannot be found in the cache.'”
This problem occurs because the guest virtual machine is set to a different time zone than the physical machine. Therefore, the Hyper-V time synchronization on the virtual domain controllers makes the Active Directory Service Interfaces (ADSI) cache invalid.
To resolve this problem, disable time synchronization in the Hyper-V Manager console. To do this, follow these steps:
- Open the Hyper-V Manager console.
- Right-click the virtual machine on which you want to install Exchange Server 2010, and then click Settings.
- On the Settings tab, click the Management section, and then click Integration Services.
- Click to clear the Time synchronization check box, and then click OK.
- Install Exchange Server 2010 on the virtual machine.