I have a single Hyper-v host and running two VM's.All the VM's are sitting in local storage
My local storage specs- (Lenovo 600 GB Hard Drive - SAS (12Gb/s SAS) - 3.5" Drive - Internal 15000rpm - Hot Swappable) drive with Raid 5.
My hosting OS Server 2016 running on 128 GB Lenovo Solid State Drive - SATA (SATA/600) - Internal - M.2.

I tried to create a Fixed 1TB VHDX drive and it took me 9-10 hours.

Just wanted to find out is this normal or something to do with my storage.

Hi,
 
 I created a VHDX file from Windows 2012 Server running as VM on ESXi Host. Then I copied the VHDX file into the Virtual Hard Disk folder in Hyper-V 2016 Server and created  a VM using existing VHDX file, assigned RAM, CPU  and Virtual Network Adapter. When I start this VM, it only shows a blinking cursor at the beginning and stays that way.
 I have tried Legacy Network Adapter and tried to press [F8] to start in safe mode, but to no avail.
 What else can I try?

Thanks.

Hi,

I have a Windows 2012 R2 Hyper-V server with 3 VMs.  One of the VMs is setup for Remote Desktop Services and we have about 13 users connect into this server to work.  Most of them connect to it from within the office.  Some of the users connect from outside of the office.  The managers asked me if there's a way that I can restrict remote access for some of the users.  They would be able to work at their computer within the office but if they go home and feel like they want to remote into their session, they would be restricted from logging into their session when they're out of the office.  What's the best and most simple way to accomplish this?  Thanks in advance for your help!

I need to make backups of my system state on my windows 2016 server hyper-v domain controller. The only way for this to work is thru power shell. I am only able to run this for one time. How do I write this t run every 4 hours in PowerShell?

# Runs  from PS on DC1
Register-ScheduledJob -Name “System State Backup” -Trigger @{Frequency = “Daily”; At = “2:00”} -ScriptBlock {
	# Create new Backup Policy
	$Policy = New-WBPolicy

	# Add System State to the policy
	Add-WBSystemState -Policy $Policy

	# Set Backup Location
	$BackupLocation = New-WBBackupTarget -VolumePath "\\bugsbunny\svrA"

	# Add backup location to policy
	Add-WBBackupTarget -Policy $Policy -Target $BackupLocation

	# Start Backup Using Policy
	Start-WBBackup -Policy $Policy
}

Select all Open in new window

Hi,
 I have two Hyper-V servers - W2012 (running Windows Server 2012, 192.168.1.139) & W2016 (running Windows Server 2016, 192.168.1.145) on the same network.  When I select the VM on W2012 and go thru replication, I get an error.
(1) I can ping W2016 from W2012 and ping W2012 from W2016.
(2) Both Hyper-V servers are "Enabled as a Replica server" using "Kerberos port 80" and chose "Allow replication from any authenticated server".
(3) I tried to replicate the VM in W2016 onto W2012, but it failed because I could not replicate 2016 VM to older version of HyperV.
(4) so I tried to replicate the VM in W2012 onto W2016, but I am getting this error. (please see the screenshot).
(5) On both Hyper-V servers, I enabled "Hyper-V Replicate HTTP and HTTPS Listeners" and rebooted the servers.
(6) Both Hyper-V servers have the same administrator password.


What can I do?

I just installed a new Office PC (Win 10 Enterprise). I have an old billing program on my prior Win7 Pro PC that I want to keep using. Created a VM of the Win7 PC using Macrium viBoot, installed the Hyper-V role in Win10 and am able to boot / use the VM without issue. Great!

But what about backup? I have Macrium setup to image my Win10 PC daily. Would restoring my Win7 VM (if needed) be a simple matter of restoring all the files in the Macrium viBoot folder (where all VM files are stored I believe).

I realize (and use) VM backup software (Altaro) at my Server clients. But Altaro, Veeam, etc. programs require the Host to be running Server software. Looked at BackupChain but that would need a Server license as well.

I'm hoping just a simple backup of the VM files will suffice in this scenario.

Anyone have experience with Hyper-V backup on a Win10 host?

Hi,
 
 I am trying to convert Windows 2003 Server running virtual machine "FS1_W2003-recovered"  in VMWare ESXi server into Hyper-v virtual machine using Microsoft Virtual Machine Converter and have some questions:
 (1) In Connection option screen, I am not sure if the message means or applies to my situation?
 (2) In Connection option screen, why I can't select "On" for "Final state of source virtual machine"?
 (3) In Summary Screen, should I be concerned about the warnings (1. OS not supported  2. having one USB device) ?
(4) In Completion screen, I see "Uninstall tools" on the 3rd line. I assume it will uninstall VMWare tools? If so, why does it do that? Will it alter or harm existing VMWare VM in any shape or form?  This is where I CANCELLED the conversion because I was not sure what would happen to source VM.

Hi,
  I have a HyperV  virtual machine that has two disks (P...K1-0.vhdx & P...K1-1.vhdx) - C drive and E drive. Each drive carries three files (vhdx, vhdx.mrt vhdx.rct).
 But then there are extra files of avhdx (4AD ...avhdx & B59...avhdx) seen on the screenshot and I like to get rid of it.
 Here is how they are created.
 I created new virtual machine using first disk - P...K1-0.vhdx. But when I tried to add 2nd disk (P...K1-1.vhdx), I added it to the wrong existing virtual machine (called TS1).
 When I eventually added 2nd disk (P...K1-1.vhdx) to the right virtual machine and started the VM, it complained about "file being currently used ...".
 So I rebooted the hyper-V server and was able to start my virtual machine with P...K1-0.vhdx & P...K1-1.vhdx. But my TS1 VM would not start saying "file being currently used ..." and it was put in "saved state". I deleted "saved state" from TS1 and now TS1 is working now.
 However during this process, two sets of extra avhdx, MRT and RCT  files were created and I like to delete them because they are not used and not intended.
 But I just wanted to check to make sure that I can delete them without casuing problems. Fyi, I have not created any snapshot for any VMs in Hyper-V server.

 Can I just delete them?

Hello everyone,

I have a scenario in which there are:
3 x Ex2010 Mailbox Server in DAG (on vSphere cluster)
2 x HT and CAS with NLB configured (on Hyper-V cluster)
2 x UM server
and also hybrid configuration.

I am not really an expert in O365 / hybrid configurations.

As per refresh cycle, I have to move VMs from existing Hyper-v and vmware (all above roles) to new vSphere cluster.

For Mailbox I have planned to create new MailboxServer VMs with new name,IP and add them in DAG, add a copy of each databases to new VMs, remove copy from old VMs and uninstall Exchange from old VMs.
Also will be updating the RPCClientaccessserver, move arbitration mailbox

For HT-CAS and UM, I am planning to use vmware converter to move VMs from hyper-V one at a time to vSphere cluster.
I believe I will have to retain the mac address of NICs from hyper-v vms

I am here for some advice, suggestions and caution I must take, specially with hybrid setup.
appreciate your comments.

Thank you.

we have an ongoing issue with cloudcare where we cannot log on to our vm servers.
we have 2 vms, 1 our 2016 dc and the other our 2016 exchange server.

once we get into this “lock out” situation we try closing down the servers but they just hang, so the only way we have been able to resolve this is to hard reset the server.

we have just done this again and now both vms are stuck starting up, where the status shows "merge in progress", but the progress is just sat at 26% for our dc and 7% for our exchange server.

we really need these servers back online, so does anyone know how we can tidy this up and get them operational?

any help much appreciated - desperate!!

thanks