Unable to delete .vhdx files after VM replication removed


I am working with replication and have configured replication on several VMs for testing.  The testing is now complete, I have done several failovers both planned and unplanned, disabled replication then re-enabled it. I would now like to clean-up the
environment and I have deleted all the VMs and the replicas from both Failover Cluster Manager, and HyperV manager.  When browsing through File Manager I see several folders for the deleted VMs.  When I open the folders I see single .vhdx file which
I cannot delete due to permissions errors.  When I try to take ownership of this file it also replies that I don’t have permission.  Is there a proper way to remove replication and do a complete cleanup of the environment including the .VHDX files
which are left behind?


Read full post . . . .

Encrypted replication configuration


I am attempting to configure encrypted replication in a fairly large (10 hosts per site) HyperV environment.  I’m using the following article as a guide:


From what I am understanding I will require a certificate on each host.  I will also need to add the broker’s certificate to the trusted certificate store on each of the hosts that the broker will reside on. Due to the requirement of a certificate on
each host it makes a lot more sense to use auto-enrollment to ensure we don’t have to manually renew 20+ certificates on the regular basis.

I’m having a couple of challenges, for one our hosts are running W2K16 HyperV Core, so I cannot use the certificates MMC as described in the article.  Running the MMC remotely does not appear to give me the same options as described in the article. 
Can this (or should this) be done in PowerShell instead?  What would the syntax of the certificate request be?

Are there any other (hopefully better) articles that can help me do this other than the one I found above?


Read full post . . . .

Partial checkpoint – unable to merge, unable to take new checkpoints


Our backup team is reporting issues backing up two servers.  When checking the servers I am unable to take new checkpoints from either HyperV manager or SCVMM.  From HyperV manager if I go to settings and change the checkpoint type from Production
to Standard I am able to take checkpoints, however the backups are still failing.

I’m fairly certain that the issue is related to the fact that even though the VM does not appear to have a checkpoint if I look at the properties of VM it appears that the first disk does not have a checkpoint while the other two do:

Is there a way to force these checkpoints to merge?

Read full post . . . .

How do I configure Shared iSCSI storage across hyperv hosts?

I have two hyperV hosts which I would like to be able to move workloads across. They both are configured with iSCSI and have unique 1 TB drives allocated to each of them, however they do not share the same storage because my understanding is that Windows
hosts are not meant to share the same iSCSI share at the same time.

So if that’s the case, how exactly are they supposed to move VMs across the hosts with no shared storage?

I have tried selecting move and then pointing to a UNC path, but hyperv doesn’t seem to like that.

I have tried to map a drive letter to a UNC path, but my drive letter does not come up as one of the options when I select move.

I have tried connecting both hosts to the same iSCSI share, but assigning them the same drive letter and accessing the storage from two hosts at the same time simply doesn’t seem to work, and everything I’ve read seems to indicate that windows servers are
not meant to access the same iSCSI share simultaneously.

At this point I have no idea how this is supposed to work.  Do I need to create a Cluster and a Cluster Shared Volume?

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 53 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995