This is for Hyper-V 2012 servers under Windows 2003 domain. CredSSP is not supported.

This command works:

move-vm  -name vm1  -computername hypervA  -destinationhost hypervB

This one is not working:

$pss = new-pssession -computername hypervA
invoke-command -session $pss {move-vm -name vm1 -destinationhost hypervB}

The error is "You do not have permission to perform the operation. Contact your administrator if you believe you should have permission to perform this operation."

Both hypervA and hypervB have delegation enabled for each other for "Microsoft virtual system migration service" and CIFS enabled for the SMB server.

What else needs be enabled for the powershell remoting?

Thanks.

Shaun

Hello,

Do you know can i add windows server 2012 hyper-v in domain which is on server 2003?

Andrej

I built a couple brand new Server 2012 Hyper-V hosts and I am in the process of rebuilding some of my servers on these new hosts.  But my print servers cannot print.  First I tried building a Server 2012 VM print server and it could not print to anything.  I figured it was something with the way Server 2012 handles drivers and gave up on it without having spent too much time on it and rebuilt it as a Server 2008 R2 server.  This server also cannot print.  My suspicion is that the issue lies somewhere in the Hyper-V host networking but I am not sure.  I am able to install the drivers and print by IP to the same printers from the Hyper-V host so the problem seems isolated to the VM.  On the VM I can add a printer shared from another print server on the network and print to it.  But when I try and add the printer directly and print to the IP it does not work.  What happens is the document or test page shows in the queue for the printer for a second and then disappears, exactly as it should in a successful print, but nothing ever prints.  I have tested to Xerox, HP, and Kyocera devices with the same results.

I have 3 other VM print servers on the network all using Server 2008 R2 hosts.  I also have multiple devices of the same type so drivers and devices are well tested on Server 2008 R2 and I think they can safely be eliminated as a cause.  I have not yet even installed the AV on this new print server so that is not the issue.  I tried allowing the management operating system to share the NIC in the Hyper-V virtual switch settings without effect.

Integration services are installed.

I have unchecked enable virtual machine queue and enable IPsec task offloading in the hardware acceleration section of the VM NIC without effect.

I am having a very frustrating experience trying to install a new Virtual Machine on my Hyper-V 2012 Server, the frustrating part is that this is the 4th machine I am trying to install on this system and the other 3 worked with no problems.

Basically, I have created a new VM, I have told it to boot from the physical DVD drive, if I connect to the machine and look at the media menu there is a check mark next to capture DVD, the bios setting for the VM is set to boot from CD. However, every time I try to start up this machine I am presented with "Boot failure, reboot and select proper boot device or insert boot media in selected boot device".

I have verified that no other VM has access to the DVD, I have verified that I can boot from the DVD on a physical computer and I have deleted and re-created the machine multiple times.

What would cause me to be unable to boot from an install CD on a brand new VM? (In case it helps, the media is a Windows 2008 R2 Server with SP1 install disk).

Thanks in advance.

We have several Server 2008 R2 environments all running Hyper-V.   Randomly on all of these boxes we will be unable to connect to certain VM's using the Hyper-V console.  The message comes up as "Cannot connect to the virtual machine.  Try to connect again.  If the problem persists, contact your system administrator."  I have searched through these forums and the internet and tried various things including restarting the Hyper-V Virtual Machine Management Service and the issue does not go away.   There are no errors in any of the Event Viewer logs that indicate an issue.   The affected VM's are usually never the same and will be fine when they are first turned on.  They start having this issue after being online for a while (usually the longer they have been up, the more likely the issue is to occur).    The Guest OS itself seems to continue to function fine, I can RDP to them (those that are setup as such) and they continue to operate, I just can't connect via the Hyper-V console.

So far the only solution has been to either shutdown and restart the VM, or do a 'Save' and then start it again and that will always fixes the problem, but it's far from a permanent solution.    All of the Guest OS's having this issue have the latest Integrated Services installed and do not have any snapshots.  Also the OS on the guest itself has been Windows XP, Windows 2000, Windows Server 2003, and I think even a Server 2008 R2 and Windows 7 VM did it.  The Host boxes have been rebooted and are patched (all SP1) and they continue to have the issue.    Any suggestions are appreciated.

After reading many posts, I am more confused than before.

I would know if Hyper-V (Win 2008 R2 or Win 2012) support or less "promiscuous mode".
In fact I would use a sniffer and monitoring VM inside Hyper-V, to monitor LAN trafic.
I have a dedicated nic of the server connected with a mirror port of a Cisco switch.
The same configuration run correctly with ESX 5.1, but not with Hyper-V.
I have seen posts where someone says that Hypr-V can support promiscuous mode and other that cannot.
Someone could tell me if it is possible and suggest me a document to follow?
Thanks in advance
Antonello

Hello,

My terminal server config is lacking performance with RDP connections and im searching through some possible faults.

I figured NUMA was enabled and want to disable it to see if performance is better.

Let me explain my setup:

I have a ML350 G6 with dual E5606 2.13GHz and 32GB memory.

My host has Hyper-V installed as role with nothing more to do.

My VM's consist of:

DC (Single CPU) with static 3072MB memory.

TMG (Single CPU) with static 3072MB memory.

TS (4 CPU) with static 12288MB memory.

Im unable to add more static memory as the TS VM then wont start.

Let me calculate:

3072+3072+12288= 18432MB

meaning i should have 14336MB free memory.

NUMA is diabled.

My question is, why cant i add more static memory then the 12GB? Is that used for pagefile purpose?

The reason im going for a static memory setup is to see if preformance will be better.

With kind regards, René de Meijer. MIEGroup.

Hi,

Can I setup HyperV replica with 2012 HyperV host servers in a 2008 R2 domain or I have to upgrade the DC and/or functional levels?

Regards,

Dvijne

Hi,

I have been testing Hyper-V Replica and all has been going quite well in a test environment.

When applying the same knowledge to a production environment i'm seeing strange results.  I have a Windows Server 2012 Hyper-V server in a workgroup running a guest SBS 2011 VM with two drives, one is 131GB and the other is 314GB.  I have moved the pagefile onto a third vhdx which isn't being replicated over to our replica partner.   

Looking into the VM's, there is minimal file structure change but yet i see lot's of big .hrl files being queued up for replication.  I've been through the majority of the files on the SBS server to make sure file changes are a minimum, i.e. IIS / Exchange logs and having kept an eye on the server throughout the day i can't see any big increases in storage consumption on the partitions.  within 7 hours today i can see that i have 11.5GB of .hrl files waiting to ship over to the replica partner.  The SBS server is running on an ADSL line is being crippled due to the upload.

From my test environment, after moving the pagefile onto a drive that wasnt being replicated i was seeing average .hrl files of KB's rather than GB's.  Does anybody have any advice on where the huge file sizes can be coming from ?

This is already my third seed and i'm still seing the same problem.

Alex

Having an issue when moving Virtual Machine Storage on a Clustered vm is breaking (corrupting?) the vhdx.

Setup:

2-node Hyper-V Server 2012 (the free one) Cluster connected to an EqualLogic PS6100E using a CSV.  (2) Teamed (Hyper-V) LAN nics and (3) iSCSI MPIO nics each.

Starting Location:

• VM named "vv-2012" is built from an ISO and running on a server in the node - NOT added to Failover Cluster Manager as a role yet.
• Disk lives at "C:\ClusterStorage\volume1\vv-2012\Virtual Hard Disks\vv-2012.vhdx"
• VM lives at ""C:\ClusterStorage\volume1\vv-2012\Virtual Machines\xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xml"
• Machine is Running at Login Screen directly after setting the local Administrator password
• Running current Integration Services

Test 1 - From Starting Location - Move VM Storage using Hyper-V Manager - Move just the vhdx one folder up ("C:\ClusterStorage\volume1\vv-2012\vv-2012.vhdx")

• SUCCESS - vhdx moved and machine still running

Test 2 - From Starting Location - Import into Failover Cluster Manager - Move VM Storage using Failover Cluster Manager - Move just the vhdx one folder up ("C:\ClusterStorage\volume1\vv-2012\vv-2012.vhdx")

• FAILED - Disk Read error in the running VM as soon as the move starts (see below image)

Test 3 - From Starting Location - Import into Failover Cluster Manager -SHUT DOWN RUNNING VM - Move VM Storage using Failover Cluster Manager - Move just the vhdx one folder up ("C:\ClusterStorage\volume1\vv-2012\vv-2012.vhdx")

• SUCCESS - Started VM - no errors

Working on the, now, broken vhdx:

- Searching technet (and the Internet - Google/Bing) returns almost exclusively P2V conversions using disk2vhd.exe from Sysinternals.  That is NOT the case here - reading these posts talks about partitions not being imported (boot partition) or incorrect IDE/SCSI settings on imported vhd's.

- Attaching the vhdx to another vm (or my local machine using Disk Management) and running chkdsk returns "Corrupt master file table. Windows will attempt to recover master file table from disk."  "Windows cannot recover master file table.  CHKDSK aborted." (also tried with /F even though screenshot does not show that - same result) - I see the 2 partitions (boot and system) but cannot browse them - marked as RAW

- Running TestDisk returns invalid MFT (I think, not an expert on this program).

Summary:

- Moving vm vhdx's that are turned off either through Hyper-V Manager or Failover Cluster Managerwork fine

- Moving vm vhdx's that are running through Hyper-V Managerwork fine

- Moving vm vhdx's that are running through Failover Cluster Managerbreaks (corrupts?) the vhdx.

So my questions are 3 fold:

1. Can anyone else reproduce this?
2. Is it a Hyper-V / Cluster bug?
3. Can I recover the vhdx?

Wasn't sure if I should post here or Cluster forum?  Both?

:) -Andrew

Images:

Hi,

 When trying to snapshot a VM i get:

I looked around on the web, and found that the 'Virtual Machines' group isn't on my server, and therefor isnt on the security tab for my snapshot folder.

Taken from this post: http://joesitblogandotherstuff.blogspot.com/2010/01/could-not-initiate-snapshot-operation.html

How do I manually create the 'Virtual Machines' group, so I can make snapshots work again?

I have 2 hyperv hosts in a cluster in Site A. 1 standalone host in site B.

Vms in site A are on CSV volume, and replicate to site B just fine.

but If I live migrate a VM to another cluster node in Site A, replication stops and I have to manually right click the vm and choose resume replication. How can I automate the resync ?

Anand_N

Hi all,

I seem to have an issue preventing me to use Hyper-V Manager to manage a server in particular for some weird reason, did anyone see this before?

A few weeks ago, I upgraded a Windows Server 2008 R2 to SP1, things were working fine until a few days ago.

I switched off a machine to increase its dynamic RAM (new feature in SP1), however, it seems like this caused (or happened with an intriguing coincidence with) some issue with Hyper-V Manager where I am no longer to manager Hyper-V on that particular server. I tried restarting the server without luck. I also am able to manage other Hyper-V servers using Hyper-V on that same that machine. I am not able to use Hyper-V Manager from other machines to manage that machine.

I was able to use http://pshyperv.codeplex.com/ to work around the Hyper-V issue on that machine.

 I see the following error message when trying to refresh the connection to the affected machine using Hyper-V manager:

[Window Title]
Hyper-V Manager

[Main Instruction]
An error occurred while attempting to refresh the computer localhost.

[Content]
The operation failed because the WMI object being accessed cannot be found on computer localhost. Please ensure that the 'Virtual Machine Management', 'Hyper-V Image Management Service', and 'Hyper-V Networking Management' services on the computer are running.

[Close]

I inspected the event logs and didn't see anything obviously related to Hyper-V, I only see this error from WMI but did some research and it seems it could be safely ignored according to a KB article (http://support.microsoft.com/kb/950375).

Log Name:      Application
Source:        Microsoft-Windows-WMI
Date:          5/6/2011 3:40:49 PM
Event ID:      10
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.subdomain.domain.com
Description:
Event filter with query "select * from MSFT_SCMEventLogEvent" could not be reactivated in namespace "//./root/subscription" because of error 0x8004100e. Events cannot be delivered through this filter until the problem is corrected.

Thanks,
Firaz.

Dear Team,

I am developing an application which show Hyper V host (Windows 2008 R2) and all the VM running in that host. 

For each VM that runs on that host I have to show the CPU Utilization, Disk Utilization, Memory Utilization and Network Utilization.

I am able to retrieve the hardware details from root\virtualization classes.  But their corresponding performance counters ( root\cimv2).

For example

Msvm_LogicalDisk gives all disks and can be grouped for each VM.  But based on Tony's sugggestions ( part 1 to part 5).

http://blogs.msdn.com/b/tvoellm/archive/2008/05/04/hyper-v-performance-counters-part-one-of-many.aspx

I tried to retrieve performance counters of each VM for disk  Win32_PerfRawData_StorageStats_HyperVVirtualStorageDevice

I am not able to relate Msvm_LogicalDisk and Win32_PerfRawData_StorageStats_HyperVVirtualStorageDevice.

Please let me how to associate performance counters of each of the above components to their respective VM's.

Thanks,

Edwin.

Hi.

I've been searching both the web in general and this forum in particular in order to find out how I calculate the correct number of VMs to put on a LUN in Hyper-V 2012.

The reason I want to know is because a colleague of mine asked me - I normally don't worry about this.

He mentions SCSI locks and other hardware related issues that could limit the number of VMs that you can/should put on one single LUN but I haven't seen any information regarding this from Microsoft.

This is of course related to a specific set of storage - an old EVA is probably a lot worse off than a brand new VNX - but I'm hoping that one of you can point me in the right direction, if nothing else.

Thanks in advance.

I'm trying to troubleshoot a slow network connection problem.

First, some background. I have Hyper-V host with multiple WS2008R2 guests. The host server has 2 4 port 1Gbps Broadcom 5709C NICs. 

The guest in question runs a Dynamics CRM server. I've recently upgraded our ISP to 20Mbps Metro Ethernet connection.

My remote users have been expressing some disappointment about the new service because the were expecting a much more responsive experience from CRM because we were moving from a Cable based ISP with 3Mbps Up on a good day to the promise of close to 20Mbps Up.

I've been doing some testing to try to find where the problem is. If I do a speed test from the Hyper-V host, I get right at 20Mbps down and 16-20Mbps Up. However, from the CRM guest, I'm averaging around 16Mbps Down, and only around 5.8Mbps Up. This explains why the client isn't markedly faster, but I'm not sure what to do to fix it.

I've been searching the net for a couple of days. I've disabled IPv4 Checksum Offload, Large Send Offload, TCP Checksum Offload, UDP Checksum Offload on the Guest, and the equivalent settings on the vSwitch that this guest is using.

I have also increased the Receive and Send buffers on the NIC to 2MB in the guest.

None of this has helped, and nothing has really impacted the upload speed at all. I'm really at a loss for where to go from here.

Any help would be most appreciated.

I have built a Hyper-V failover cluster using Windows 2012 on 3 Dell PowerEdge M520 Blades connected to a Dell EqualLogic PS4100 array. The blades plug into Dell PowerConnect M6348 switches in the back of the chassis. The network cards are Broadcom. In total 12 cards, 4 are plugged into the iSCSI network. 4 are teamed using the inbuilt windows teaming with networks created to carry internal production vLANs, CSV, heartbeat, Live Migration and Management. The other 4 are used in a team for carrying external DMZ vLAN traffic.

All updates applied and all drivers and firmware are up to date.

I have migrated and now have 18 guest OS running on this cluster, Windows Server 2003r2, 2008r2 and 2012, a few client OS, XP and Windows 7.

The problem I am having is only with the 2 Windows Server 2003r2 and 1 XP VMs. Every 20-30 minutes the VMs lose the ability to connect to anything outside of the vLAN they are assigned too. They can ping each other but not the gateway. Looking in the ARP table of the switch the mac address for these VMs change and become 0000.0000.0000. Before they change to this they are the static assigned mac assigned to the VM. To get the VMs network to work outside of the IP range it is on I have to just simulate the network cable being unplugged. Be that repairing the connection on the VM, live migrate the machine to another host or just change the setting to not connected and back. 20-30 minutes later the mac address becomes 0000.0000.0000 again.

An ipconfig on the VM show the correct mac at all times. No events in the events logs at all when this happens, host or VM.

I have tried the following;

Fully patched the VMs

Update the host integration services

Removed the adapters and added new ones

Changed IP

Changed IP Range

Changed MAC address of VM

Removed hidden devices

Removed entries in the register for network adapters

Tried legacy adapter where possible

Disabling TCP Task Offload settings, physical and VM

Enable VMQ and disabling VMQ, physical and VM

Yet still after 20-30 minutes the VM lose connection outside of the IP range they are on, the MAC address in the switches ARP table changes 0000.0000.0000 hence the loss of network outside of the IP range.

I have check for rouge devices on the network, doubled checked all VMs to make sure no duplicated MAC address have been used. I have gone over our switch settings but cannot find anything here that would or possibly only affect VMs running 2003r2 or XP. I don't believe it is a switch network problem anymore as it is only these 3 VMs with 2003r2 or XP that are having this issue, the other 15 VMs that are 2008r2, 2012 or Win 7 are working great on the same hardware connecting to the same switches in the same IP ranage.

I am now at a total loss as to what to try next to get the 2003r2 and XP VMs.

Any ideas? 

Thanks

Barry

Hi.

I've been reading about Hyper-v on WS2012 and I have the following question.

Is it possible to have a WS2012 with Hyper-V role running virtual machines located on a iSCSI storage (eventually each VM on a dedicated LUN)? Any performance problems may occur?

I know that this scenario is often used with WS2012 clusters, but I'm asking just for curiosity.

BTW, if i use DPM 2012 SP1 to do backups of guest VMs, is it advisable to put all VM backups in the same iSCSI LUN?

Thanks.

Hello - I have a strange issue on my Server 2012 Hyper-V hosts.  Whenever I reboot, the ip address settings are lost.  When I go into the NIC settings, the correct IP info appears but if I do ipconfig, its APIPA  169.x.  It only happens with 2 out of 3 virtual switches.  The difference is that they are marked to "Allow management operating system to share this network adapter" in Hyper-V network manager.

Server Info - Server 2012 Datacenter.  All updates applied.

~David