I would like to p2V a Windows 2000 SP4 running on a Dell PE 750. I have searched many forums and no one seems to have an answer to do this and suggest other ways to get around this, right on MS documentation it shows that an offline conversion is supported. I don't plan on upgrading Server software and I do not want to do a backup/restore to new image.

Information I am looking for

What Host OS and Hyper-V version do I need to do this with?

Where can I find step by step instructions?

Hi ,

We have 2 server running Hyper-v Server 2012 R2 and we are able to RDP and remotely manage it through server manager from a windows 8 system. But unable to see the Device manager.

I am getting the below attached error.

Did anyone face this issue. Please suggest ?

Thanks

We are setting up 4 VM's with Windows 7 OS for staff access on a Dell PowerEdge R320.

We had all of the VM's working as specified above but had to re-install Server 2012 Standard because the factory tech setup the Raid 5 to only give the server OS 40 GB of space.

Installed Windows Server 2012 Standard with the following Roles and Features:

• File and Storage Services
• Hyper-V
• Network Policy and Access Services - Network Policy Server - Health Registration Authority
• Web Server (IIS) - Web Server (Defaults)
• Management Tools (Default)

We will be joining this server to a Domain Controller on another server.

This server will need to have mapped drives to a third party software database and storage file installed in it for business management.

For setup purposes the NIC1 has been disabled to reserve it for iDRAC.

The NIC2 is set to a static IP address for RDP and DOES have internet access.

An External virtual switch has been installed in Hyper-V on the NIC2 named "Virtual Switch NIC 2" All of the guset VM's have the Virtual Switch "Virtual Switch NIC 2" installed (without VLAN ID and Bandwidth Management checked).

The guest OS does show the network adpater as a device and is also set to a static IP for RDP. The networking and sharing window shows "No Internet Access" and cannot repair or resolve the issue. The Guest OS also does not see the Host files shared or the Host in Network. It displays as an unidentified network.

Please advise and thank you in advance for your assistance.

Current app only works on Windows 2003 & 2008- app currently in beta for 2012, expected october, so we want to ride it out!

We have a SBS 2003 installation with flaky hardware

Would be able convert a SBS 2003 installation - P2V

I know VMWare has a P2V convertor but I don't see one for hyper-v

does existing SBS license allow me to do this ?

JK

Hi, I cannot seem to find a good answer to this.

I have Windows Server 2012 R2 installed on a new server. I have enabled HyperV on the server and already have 3 VM's running on it, including an Exchange 2013 server.

Can I enable Bitlocker on the HyperV server while there are already VHDX's on the data drive?

What would be the best way to enable HyperV in this scenario?

Thanks for reading

On Win 2008r2 I have Hyper-V running Exchange 2010sp3. The .vhd and snapshots in Hyper-V point to the Q: drive. I don't have any snapshots. The .vhd is indeed on Q:. Hyper-V is set to save state on shutdown. However the saved states are saved to the E: drive. I don't want the .bin and .vsv files on E: because it is running out of space. Why are they saving to E: when everything else points to Q: ? 

Also, E and Q have identical folders \exch2010\virtual machines\84BB95CD-A450-49F1-90B4-8220AAD594XF but the one on Q: is empty. There is an 84BB95CD-A450-49F1-90B4-8220AAD594XF.xml file in Q: as well but it dates to 4/30/2012. The 84BB95CD-A450-49F1-90B4-8220AAD594XF.xml file in E: is from the last reboot for updates. 

Was Hyper-V originally setup on E? Can i just drag the .bin and .vsv files to Q: every time i reboot Exchange? I'd prefer to change the saved state location but see nowhere to do it. Thanks!

Hi,

I used to be able to get this to work. But, I'm not able to anymore.

I have two network cards in my PC.

#1 Is what I use for everyday use and it's configured to use :

IP: 192.168.0.2

GW: 192.168.0.1

DNS : 192.168.0.1 (Router address)

#2 Is setup to use

IP: 192.168.0.3

GW: 192.168.0.1

DNS : 192.168.0.1 (Router address)

Then I create a Virtual Switch in Hyper V Virtual Switch Manager and bind it to Network Card #2.

This creates the Hyper V Virtual Ethernet Adapter that I bind my VM's to.

But for some reason none of my VM's can get a connection to the internet. There is an exclamation mark over the network icon.

When I go back and look at the TCP/IP V4 properties of the Virtual Ethernet Adapter, I release that it has no DNS settings.

But when I put any settings in there it gives me a warning about setting multiple default gateways, and do I want to continue, yes or no?

What could I be doing wrong?

Thanks

Hi Guys,

I'm having some serious performance issues with Converged Fabrics in my Windows Server 2012 R2 lab. I'm planning on creating a Hyper-V cluster with 3 nodes. I've built the first node, building and installing/configuring OS and Hyper-V pretty straight forward.

My issue is with Converged Fabrics, I'm absolutely getting very slow performance in the sense of managing the OS, Remote Desktop connections taking very long and eventually times out. Server unable to find a writable domain controller due to slow performance. If I remove the converged fabric everything is awesome, works as expected. Please note that the cluster hasn't even been built yet and experiencing this poor performance.

Here is my server configuration:

OS: Windows Server 2012 R2

RAM: 64GB

Processor: Intel I7 Gen 3

NICS: 2 X Intel I350-T2 Adapters, supporting SRIOV/VMQ

Updates: All the latest updates applied

Storage:

Windows Server 2012 R2 Storage Spaces

Synology DS1813+

Updates: All the latest updates applied

Below is the script I've written to automate the entire process.

########################################################################################################################
# Script: Configure Hyper-V
#
#
#
# Version: 1.0.2
#
# Description: Configures the Hyper-V Virtual Switch and
#              Creates a Converged Fabric
#
#
# Version 1.0.0: Initial Script
# Version 1.0.1: Added the creation of SrIOV based VM Switches
# Version 1.0.2: Added parameters to give the NLB a name, as well as the Hyper-V Switch
#
########################################################################################################################

param
(
    [Parameter(Mandatory=$true)]
    [string]$TeamAdapterName="",
    [Parameter(Mandatory=$true)]
    [string]$SwitchName="",
    [Parameter(Mandatory=$true)]
    [bool]$SrIOV=$false
    
)

#Variables
$CurrentDate = Get-Date -Format d
$LogPath = "C:\CreateConvergedNetworkLog.txt"
$ManagmentOSIPv4="10.150.250.5"
$ManagmentOS2IPv4="10.250.251.5"
#$CommanGatewayIPv4="10.10.11.254"
$ManagmentDNS1="10.150.250.1"
$ManagmentDNS2="10.150.250.3"
$ManagmentDNS3="10.250.251.1"
$ManagmentDNS4="10.250.251.3"
$ClusterIPv4="10.253.251.1"
$LiveMigrationIPv4="10.253.250.1"
$CSVIPv4="10.100.250.1"
$CSV2IPv4="10.250.100.1"



#Set Excution Policy
Write-Host "Setting policy settings..."
Set-ExecutionPolicy UnRestricted

try
{
    # Get existing network adapters that are online
    if($SrIOV)
    {
        #$sriov_adapters = Get-NetAdapterSriov | ? Status -eq Up | % Name # Get SRIOV Adapters
        $adapters = Get-NetAdapterSriov | ? Status -eq Up | % Name # Get SRIOV Adapters
        Enable-NetAdapterSriov $adapters # Enable SRIOV on the adapters
    }
    else
    {
        $adapters = Get-NetAdapterSriov | % Name
        #$adapters = Get-NetAdapter | ? Status -eq Up | % Name
    }

    
    
    # Create NIC team
    if ($adapters.length -gt 1)
    {
        Write-Host "$CurrentDate --> Creating NIC team $TeamAdapterName..."
        Write-Output "$CurrentDate --> Creating NIC team $TeamAdapterName..." | Add-Content $LogPath
        #New-NetLbfoTeam -Name "ConvergedNetTeam" -TeamMembers $adapters -Confirm:$false | Add-Content $LogPath
        New-NetLbfoTeam -Name $TeamAdapterName -TeamMembers $adapters -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false | Add-Content $LogPath
    }
    else
    {
        Write-Host "$CurrentDate --> Check to ensure that at least 2 NICs are available for teaming"
        throw "$CurrentDate --> Check to ensure that at least 2 NICs are available for teaming" | Add-Content $LogPath
    }

    # Wait for team to come online for 60 seconds
    Start-Sleep -s 60

    if ((Get-NetLbfoTeam).Status -ne "Up")
    {
        Write-Host "$CurrentDate --> The ConvergedNetTeam NIC team is not online. Troubleshooting required"
        throw "$CurrentDate --> The ConvergedNetTeam NIC team is not online. Troubleshooting required" | Add-Content $LogPath
    }
        
    # Create a new Virtual Switch
    if($SrIOV) #SRIOV based VM Switch
    {
        Write-Host "$CurrentDate --> Configuring converged fabric $SwitchName with SRIOV..."
        Write-Output "$CurrentDate --> Configuring converged fabric $SwitchName with SRIOV..." | Add-Content $LogPath
        #New-VMSwitch "ConvergedNetSwitch" -MinimumBandwidthMode Weight -NetAdapterName "ConvergedNetTeam" -EnableIov $true -AllowManagementOS 0
        New-VMSwitch $SwitchName -MinimumBandwidthMode Weight -NetAdapterName $TeamAdapterName -EnableIov $true -AllowManagementOS 0
        $CreatedSwitch = $true
    }
    else #Standard VM Switch
    {
        Write-Host "$CurrentDate --> Configuring converged fabric $SwitchName..."
        Write-Output "$CurrentDate --> Configuring converged fabric $SwitchName..." | Add-Content $LogPath
        #New-VMSwitch "ConvergedNetSwitch"-MinimumBandwidthMode Weight -NetAdapterName "ConvergedNetTeam" -AllowManagementOS 0
        New-VMSwitch $SwitchName -MinimumBandwidthMode Weight -NetAdapterName $TeamAdapterName -AllowManagementOS $false
        $CreatedSwitch = $true
    }

    if($CreatedSwitch)
    {
        #Set Default QoS
        Write-Host "$CurrentDate --> Setting default QoS policy on $SwitchName..."
        Write-Output "$CurrentDate --> Setting default QoS policy $SwitchName..." | Add-Content $LogPath
        #Set-VMSwitch "ConvergedNetSwitch"-DefaultFlowMinimumBandwidthWeight 30
        Set-VMSwitch $SwitchName -DefaultFlowMinimumBandwidthWeight 20

        #Creating Management OS Adapters (SYD-MGMT)
        Write-Host "$CurrentDate --> Creating and configuring virtual NIC for Management OS"
        Write-Output "$CurrentDate --> Creating and configuring virtual NIC for Management OS" | Add-Content $LogPath
        Add-VMNetworkAdapter -ManagementOS -Name "SYD-MGMT" -SwitchName $SwitchName
        Set-VMNetworkAdapter -ManagementOS -Name "SYD-MGMT" -MinimumBandwidthWeight 30 -VmqWeight 80
        Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SYD-MGMT" -Access -VlanId 0

        #Creating Management OS Adapters (MEL-MGMT)
        Write-Host "$CurrentDate --> Creating and configuring virtual NIC for Management OS"
        Write-Output "$CurrentDate --> Creating and configuring virtual NIC for Management OS" | Add-Content $LogPath
        Add-VMNetworkAdapter -ManagementOS -Name "MEL-MGMT" -SwitchName $SwitchName
        Set-VMNetworkAdapter -ManagementOS -Name "MEL-MGMT" -MinimumBandwidthWeight 30 -VmqWeight 80
        Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "MEL-MGMT" -Access -VlanId 0


        #Creating Cluster Adapters
        Write-Host "$CurrentDate --> Creating and configuring virtual NIC for Cluster"
        Write-Output "$CurrentDate --> Creating and configuring virtual NIC for Cluster" | Add-Content $LogPath
        #Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "ConvergedNetSwitch"
        Add-VMNetworkAdapter -ManagementOS -Name "HV-Cluster" -SwitchName $SwitchName
        Set-VMNetworkAdapter -ManagementOS -Name "HV-Cluster" -MinimumBandwidthWeight 20 -VmqWeight 80
        Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "HV-Cluster" -Access -VlanId 0

        #Creating LiveMigration Adapters
        Write-Host "$CurrentDate --> Creating and configuring virtual NIC for LiveMigration"
        Write-Output "$CurrentDate --> Creating and configuring virtual NIC for LiveMigration" | Add-Content $LogPath
        Add-VMNetworkAdapter -ManagementOS -Name "HV-MIG" -SwitchName $SwitchName
        Set-VMNetworkAdapter -ManagementOS -Name "HV-MIG" -MinimumBandwidthWeight 40 -VmqWeight 90
        Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "HV-MIG" -Access -VlanId 0

        #Creating iSCSI-A Adapters
        Write-Host "$CurrentDate --> Creating and configuring virtual NIC for iSCSI-A"
        Write-Output "$CurrentDate --> Creating and configuring virtual NIC for iSCSI-A" | Add-Content $LogPath
        Add-VMNetworkAdapter -ManagementOS -Name "iSCSI-A" -SwitchName $SwitchName
        Set-VMNetworkAdapter -ManagementOS -Name "iSCSI-A" -MinimumBandwidthWeight 40 -VmqWeight 100
        Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "iSCSI-A" -Access -VlanId 0

        #Creating iSCSI-B Adapters
        Write-Host "$CurrentDate --> Creating and configuring virtual NIC for iSCSI-B"
        Write-Output "$CurrentDate --> Creating and configuring virtual NIC for iSCSI-B" | Add-Content $LogPath
        Add-VMNetworkAdapter -ManagementOS -Name "iSCSI-B" -SwitchName $SwitchName
        Set-VMNetworkAdapter -ManagementOS -Name "iSCSI-B" -MinimumBandwidthWeight 40 -VmqWeight 100
        Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "iSCSI-B" -Access -VlanId 0

                
        Write-Host "Waiting 40 seconds for virtual devices to initialise"
        Start-Sleep -Seconds 40

        #Configure the IP's for the Virtual Adapters
        Write-Host "$CurrentDate --> Configuring IPv4 address for the Management OS virtual NIC"
        Write-Output "$CurrentDate --> Configuring IPv4 address for the Management OS virtual NIC" | Add-Content $LogPath
        #New-NetIPAddress -InterfaceAlias "vEthernet (SYD-MGMT)" -IPAddress $ManagmentOSIPv4 -PrefixLength 24 -DefaultGateway $CommanGatewayIPv4
        New-NetIPAddress -InterfaceAlias "vEthernet (SYD-MGMT)" -IPAddress $ManagmentOSIPv4 -PrefixLength 24
        Set-DnsClientServerAddress -InterfaceAlias "vEthernet (SYD-MGMT)" -ServerAddresses ($ManagmentDNS1, $ManagmentDNS2)

        Write-Host "$CurrentDate --> Configuring IPv4 address for the Management OS virtual NIC"
        Write-Output "$CurrentDate --> Configuring IPv4 address for the Management OS virtual NIC" | Add-Content $LogPath
        New-NetIPAddress -InterfaceAlias "vEthernet (MEL-MGMT)" -IPAddress $ManagmentOS2IPv4 -PrefixLength 24
        Set-DnsClientServerAddress -InterfaceAlias "vEthernet (MEL-MGMT)" -ServerAddresses ($ManagmentDNS3, $ManagmentDNS4)

        Write-Host "$CurrentDate --> Configuring IPv4 address for the Cluster virtual NIC"
        Write-Output "$CurrentDate --> Configuring IPv4 address for the Cluster virtual NIC" | Add-Content $LogPath
        New-NetIPAddress -InterfaceAlias "vEthernet (HV-Cluster)" -IPAddress $ClusterIPv4 -PrefixLength 24
        #Set-DnsClientServerAddress -InterfaceAlias "vEthernet (HV-Cluster)" -ServerAddresses $ManagmentDNS1

        Write-Host "$CurrentDate --> Configuring IPv4 address for the LiveMigration virtual NIC"
        Write-Output "$CurrentDate --> Configuring IPv4 address for the LiveMigration virtual NIC" | Add-Content $LogPath
        New-NetIPAddress -InterfaceAlias "vEthernet (HV-MIG)" -IPAddress $LiveMigrationIPv4 -PrefixLength 24
        #Set-DnsClientServerAddress -InterfaceAlias "vEthernet (LiveMigration)" -ServerAddresses $ManagmentDNS1

        Write-Host "$CurrentDate --> Configuring IPv4 address for the iSCSI-A virtual NIC"
        Write-Output "$CurrentDate --> Configuring IPv4 address for the iSCSI-A virtual NIC" | Add-Content $LogPath
        New-NetIPAddress -InterfaceAlias "vEthernet (iSCSI-A)" -IPAddress $CSVIPv4 -PrefixLength 24
        #Set-DnsClientServerAddress -InterfaceAlias "vEthernet (iSCSI-A)" -ServerAddresses $ManagmentDNS1

        Write-Host "$CurrentDate --> Configuring IPv4 address for the iSCSI-B virtual NIC"
        Write-Output "$CurrentDate --> Configuring IPv4 address for the iSCSI-B virtual NIC" | Add-Content $LogPath
        New-NetIPAddress -InterfaceAlias "vEthernet (iSCSI-B)" -IPAddress $CSV2IPv4 -PrefixLength 24
        #Set-DnsClientServerAddress -InterfaceAlias "vEthernet (CSV2)" -ServerAddresses $ManagmentDNS1

        #Write-Host "$CurrentDate --> Configuring IPv4 address for the VMNet virtual NIC"
        #Write-Output "$CurrentDate --> Configuring IPv4 address for the VMNet virtual NIC" | Add-Content $LogPath
        #New-NetIPAddress -InterfaceAlias "vEthernet (VMNet)" -IPAddress $VMNetIPv4 -PrefixLength 24
        #Set-DnsClientServerAddress -InterfaceAlias "vEthernet (VMNet)" -ServerAddresses $ManagmentDNS1

        
        Write-Host "$CurrentDate --> Hyper-V Configuration is Complete"
        Write-Output "$CurrentDate --> Hyper-V Configuration is Complete" | Add-Content $LogPath
    }


}
catch [Exception]
{
    throw "$_" | Add-Content $LogPath
}

I would really like to know why I'm getting absolutely poor performance. Any help on this would be most appreciated.

I need to convert a 12 TB fixed VHDX to Dynamic. Right now there is only about 1.2 TB of data on the vhdx. When I convert will it automatically shrink the vhdx file to 1.2 TB. Or do I need to run something else on the converted vhdx?

Thank you for your time.

The configuration is a Windows 2012 server running two 2012 servers as VMs. Dell server with PERC 170 controller and 4 disks in One VM seems fine, but the other is throwing a lot of ntfs errors, not all the time, but ongoing bursts of "delayed write failure" and "failed to flush data to the transaction log".

Each VM uses a single VHD file, not compressed, the drive it is on is not fragmented. When I look at the disk manager in the VM, there are two drives shown

TThis problem seems to have occurred recently, the system has been running happily since installation last August. The vhd is about 32GB in size, and the VM provides RDS for remote users.

I did notice that write caching is enabled on the virtual hard settings, but I think this is the default.

Any ideas or suggestions welcome!

Hugh

I made an astounding discovery this morning.

I have an hp ML350 server with three RAID 1+0 drive arrays that offer three logical disks for use. There is no clustering or SAN involved, just three simple disks. The first is used for the OS, and the other two to hold VHD files for Hyper-V.

I installed Windows Server 2012 R2 fresh with Hyper-V and attempted to use Windows Server Backup to backup the entire server to an external USB drive. The Hyper-V application portion of the backup constantly failed. The Hyper-V VSS Writer returned state 5, Failure Result 80042336, with the Component Message'Could not create the backup checkpoint...; the system cannot find the file specified."

After a 5 day expedition through permissions, registered DLLs and a ton of other stuff, I found the problem.

The VHD files CANNOT be located in the root directory of local disk drives. They MUST be in a folder off the root directory. I confirmed this through multiple A-B tests with the files in the root of a drive, and then in a folder off the root.

Oddly enough, the permissions on the root folder are identical to the folder off the root, so that's not the problem.

On Windows Server 2008 R2 Standard I constantly located my VHD files on the root folder of a drive with no issue.

I hope this spares someone a lot of trouble!

Theokrat

I have a Windows 2012 R2 Hyper-V Host server that has been performing perfectly up until one week ago. This is a lab environment, but it is an important lab for testing deployments of Exchange, SCCM, ADFS, as well as desktop deployment scenarios using ADK 8.1. The point is its an important lab environment for my consulting firm.

The problem: About a week ago I fired up the host server and thevirutal machine manager service will not start. The error is as stated in the post above. 

The host is nowhere near out of disk space and the disk is not corrupted. All file checks and disk checks pass with no errors. The files have all been verified for accuracy. The available disk space on the system disk is 40GB. All of the VM Guests and the default machine configuration files as well as Vhdx files are stored on a separate disk that check out good as well with over 400GB free space.

The event log shows the error posted above and the only other error in the event log is Event ID: 46

\Device\HarddiskVolume7

Volmgr - Crash dump initialization failed. 

Disk 7 has nothing to do with the Windows Server installation or Hyper-V files.

The only other thing I did on this machine is create 2 separate partitions on a separate disk and install Windows 8.1 and Windows 7 as a dual-boot option. The problem did seem to occur after doing this but not immediately. I also, cannot make the connection as to why this would have caused the service to fail. The Windows 8.1 and Windows 7 files are on a completely different disk with the BCD boot options being the only configuration change that was made to the system disk or C:\Root drive.

Please help! It's important to get this fixed as soon as possible.

David Cook

dshcook@itsaboutsolutions.com

David Cook

After a scare this past weekend, I decided to test out my backups by doing a restore of a Hyper-V guest. Good thing, because I'm running into an issue. 

We have two Windows Server 2012 servers acting as Hyper-V hosts. Both of these machines backup using Windows Server Backup to a shared drive on a Windows 7 Pro computer.

That shared drive is physically a Tandberg Data Quikstor. If you've never seen a Quickstor, it's a box that hooks up to a computer via USB and uses little ejectable hard drives for storage. Think tape drive, but little hard drives instead of tape carts.

I wanted to test a scenario where one of our Hyper-V guests was completely hosed and needed to be restored from a backup. I set up a new Windows 2012 server, installed the Hyper-V and hooked up the Quickstor directly to the server.

I fired up Windows Server Backup and tried to do a restore of one Hyper-V guest. The restore immediately fails with the error "You can only recover entire volumes from backups stored on DVDs or removable media. File recovery is not supported."

I guess the error is self explanatory but it took me by surprise. Because I stored my backups on what amounts to a removable hard drive I lose the ability to restore individual files? That seems like a strange restriction, just about any offsite backup is going to involve removable storage.

Are there any workarounds to this issue? What if I backed up directly to the hard drive of the Windows 7 machine? Could I then use that backup to restore individual files?

I'm planning the deployment of a Windows Server 2012 R2 domain and need some virtualization advice, particularly when it comes to RAM and disk configuration.

My current plan is to purchase one copy of Windows Server 2012 R2 and install it on bare metal with just the Hyper V role enabled (will not be joined to the domain). I will then be using the virtualization rights to install one guest Windows Server 2012 R2 with the Essentials Experience role enabled (so DC/AD/DNS) - we will have over 25 users so cannot take advantage of the Essentials SKU - and one other guest Windows Server 2012 R2 to run as a member file server. I know I will need CALs for Essentials. I will be using local storage on the host.

I did toy with the idea of installing the Essentials server on bare metal, but because I'm going for the W2012R2 standard SKU, it seems silly not to take advantage of the virtualization rights seeing as it won't cost any more money... Is my assumption a good one? I have previous VMWare ESXi experience but no MS Hyper V experience.

I know this type of question is frequent, but it seems hardware sizing rules are different for hypervisor hosts and I'm a bit lost.

RAM

I'm looking at Dell hardware with 32GB RAM - I will be allotting at least 16GB to the Essentials VM. One thing I'm unsure of is how the hypervisor is alloted RAM? How much RAM should it be given? is there some rule of thumb linked to the number of VMs?

Disk config

I've read a lot about the disk configuration and the consensus seems to be to use a hardware RAID 10 configuration for the VM storage and hardware RAID1 for the host OS. Is this overkill? Instead, can everything reside on the RAID10 config? Or is there some other way i'm not aware of?

NIC config

Should the host have its own dedicated NIC and the VMs use another?

Replica DC

I would like to introduce a replica DC for redundancy - cost wise the easiest thing would be to make the second guest VM a DC (no need for second W2012R2 license etc), but opinion seems to differ as to the usefulness of putting a replica DC on the same hardware as the PDC - if the host goes, then everything goes....  Opinions?

thanks for any advice.

I am studying for my Installation and Configuration of server 2012r2. I am trying to create a lab environment using Hyper-V on windows 8.1 pro.

First problem I'm having is the program becomes Non-responsive on Exporting the VM, sounds fairly common . Can I copy the VM files manually or with another program ?

Matthew Eden

A couple of weeks ago we had an outage that prevented a replica from sending changes.  When the outage was resolved, the guest required a resync.  The changes were so large that upon starting the resync the disk filled and resync stopped, and the guest paused.  I fixed the disk space issue and started the guest and resync operation.  However, the resync never fully completed.  Upon review of the eventlogs I found the following events:

Event 33618:  Change tracking for VHD'xxxxx.avhdx' of virtual machine 'guest' is in error state: %%3493462049 (0xD03A0021). (Virtual machine ID xxxxxxxxxxx)

Event 29270:  Resynchronization failed for VM 'guest'. Resynchronization needs to be started again. If this error occurs repeatedly, you can remove replication for this virtual machine, delete the Replica virtual machine, and enable replication again. (Virtual machine ID xxxxxxxxxxx)

Event 32326:  Virtual machine 'guest' requires resynchronization to get back into an operational state. (Virtual machine ID D62FB3F1-BC01-45E2-BF49-xxxxxxxxxxx).

After attempting resync several more times and getting the same result, I removed replication for the guest, and then set it back up. The initial seed using external media import was successful, but the guest now requires resync and it is having the same issue where it never seems to complete and the same 3 events are written to the eventlogs.

Anyone know how I can get this working again?

Thanks in advance for you help!

On Win 2008r2 I have Hyper-V running Exchange 2010sp3. The .vhd and snapshots in Hyper-V point to the Q: drive. I don't have any snapshots. The .vhd is indeed on Q:. Hyper-V is set to save state on shutdown. However the saved states are saved to the E: drive. I don't want the .bin and .vsv files on E: because it is running out of space. Why are they saving to E: when everything else points to Q: ? 

Also, E and Q have identical folders \exch2010\virtual machines\84BB95CD-A450-49F1-90B4-8220AAD594XF but the one on Q: is empty. There is an 84BB95CD-A450-49F1-90B4-8220AAD594XF.xml file in Q: as well but it dates to 4/30/2012. The 84BB95CD-A450-49F1-90B4-8220AAD594XF.xml file in E: is from the last reboot for updates. 

Was Hyper-V originally setup on E? Can i just drag the .bin and .vsv files to Q: every time i reboot Exchange? I'd prefer to change the saved state location but see nowhere to do it. Thanks!