Monthly Archives: August 2018

Hyper-V File Server (Cluster)

Hi, we have a 4-host server 2016 datacenter cluster connected to a SAN, in which two LUNs are assigned (one where VM storage is assigned to hosts 1 & 2, the other to hosts 3 & 4, for load balancing).  We’re looking to create a Hyper-V fileserver
to host all user data.  My thought was to host a fileserver VM on the first LUN (and run on Host 1).  However I’m not sure what method is best to create the share space.  Would it make sense to add a VHDX with the 5TB (our current data requirement)
as a disk on the VM fileserver?  My other concern is since my understanding that CIFS is session based, that a failover to another host would break an active CIFS session.  That last concern isn’t exactly a dealbreaker as we may be able to accept
that risk, but wanted to know what my options are.

Short question here being would it make sense to add a VHDX with 5TB to a file services VM, or is there a better way to do this?

Read full post . . . .

Windows Server 2016 Hyper-V Host: Mounting ISOs in the settings of a VM from a CIFS/SMB share via Hyper-V Manager


after we did a switch from Windows Server 2012 R2 Core to Windows Server 2016 Core for our Hyper-V Hosts we were no longer able to mount ISOs from a SMB share with the Hyper-V Manager in the VM settings. For Server 2012 R2 we did configure constrained delegation
for all Hyper-V hosts which did do the trick back then. After some research we found out, that for Server 2016 we have to change the authentication method for the constrained delegation from Kerberos to "any protocol", as WINRM does use CredSSP for
authentication. We did change that for the Server 2016 Hyper-V Hosts, but we are still not able to mount the ISOs from the SMB share.

Error: User Account does not have permission to open attachment. (0x80070005)

I did configure an audit which monitors the share on the SMB Server for authentication and file access, and I see absolutely no activity when I try to mount a ISO into a VM. Which tells me, that the Hyper-V Host does not forward any authentication info or
file access request to the SMB server. So I did dig a little bit deeper into the whole problem using Powershell and "Invoke-Command … Set-VMDvdDrive …", and did find out that WINRM was not configured on our clients. After activating WINRM in
client mode and did add a Hyper-V Host as trusted host I still was not able to mount an ISO with Invoke-Command, so I added also the parameter "-authentication credssp"…. and finally it worked! (at least with the Powershell command)

But still no luck with the Hyper-V manager. I also tried to connect to a Hyper-V Host in the Hyper-V Manager with different credentials (which should force Hyper-V Manager to use CredSSP), with the same result.

So if anyone could maybe lead me in the direction what still could be missing to mount ISOs with the Hyper-V Manager I would be really happy 😉

Read full post . . . .

Issue in Sharing LUN between 2 VMs on Standalone Hyper-V Hosts

We have two standalone Hyper-V hosts running on Windows Server 2016 Datacenter Edition. On each Hyper-V host multiple VMs are created. For few VMs we want to configure
Failover Cluster i.e. one node from one Hyper-V host and another node from another Hyper-V host will be members of 2 Node Failover Cluster.

Now while configuring this Failover Cluster for 2 VMs, we have mapped 1 GB Quorum Disk LUN to each Hyper-V host and later on mapped it in both VMs as a Pass-through
Disk. Now this LUN is visible in both VMs as a disk and can be accessed. But while validating Cluster Configuration receiving error as "Failed while verifying removal of any Persistent Reservation on physical disk bca9b56b at node" and
Quorum Disk goes offline.

Also when checked found data written through Node 1 is not visible to Node 2. So this configuration is correct or do we need to use any other mechanism to resolve this issue?
Do we need to configure "Virtual SAN Manager" in Hyper-V host and later on we need to add "Fibre Channel Adapter" in those VM to assign this Quorum Disk LUN?

Read full post . . . .

Multiple Hyper-V clusters


To make multiple Hyper-V clusters (live migration and cluster network), do you have to use different vlans / another network segment or are you allowed to use the same network segment? I can not find this information anywhere.

Read full post . . . .

Multiple Hyper-V clusters


To make multiple Hyper-V clusters (live migration and cluster network), do you have to use different vlans / another network segment or are you allowed to use the same network segment? I can not find this information anywhere.

Read full post . . . .

RemoteFX locking up VM’s on boot

Here’s the host system:

Xeon E3-1220 v2 SLAT enabled.

32Gig of ram.

Adaptec 7805Q raid controller

Nvidia 1060.

Testing in order:

Windows 10 and Win2k16 Generation 1 VM’s.  Setup with RemoteFX added.  Tried to boot off of DVD image to install the OS.  Locked up at 10% with error 32788.  I then installed without RemoteFX added and the installs went fine.  Added
RemoteFX after shutting them down.  Went to restart them, issue; locked up at 10% on startup with error 32788.

Did this with Generation 2 VM’s.  Same exact steps, same exact results.

What am I doing wrong?

Read full post . . . .

windows 10 on usb virtual drive

I have a window server 2012 running hyper v. A virtual machine which is an external USB drive was added.  Now how do I install the windows 10 iso on that virtual (USB) drive (D).  It’s been formatted to NTFS.  I don’t want windows 10 to
wipe out server 2012 on C and am scared to try it without professional advice. Any good advice (pros and cons) would be appreciated.

Read full post . . . .

Windows Hyper-V Server 2016: Does it support containers?

I’m looking to enable containers on my infrastructure however looking when I run the Get-Windows Feature command I don’t see containers as an option. I’m no referring to Windows Server 2016 (core or GUI) then enabling Hyper-V, I’m running the free hypervisor
OS specifically.

however in order to resolve will I need to install windows server 2016 core activate it and then use the containers via the full OS and not the free hypervisor and yes I could use nested virtualisation however I don’t want to go down then route. Also dose
windows Hyper-V server 2019 support containers?

Option: (1) wait for windows Hyper-V server 2019, (2) upgrade to windows server 2016 or (3) ????

Thank you, God speed

Read full post . . . .

Per-file pausing in file transfer traffic

Over the past few days, I’ve observed an odd behaviour in my Hyper-V environment.

File share copying (to and from) shows a 30-60 second pause after completing each file transfer.  The file transfers themselves proceed quickly (normal speed), but between each file the transfer stops.

I originally thought Antivirus scanning might be at fault, but I’ve disabled it and the problem persists.  Also, this issue occurs for TFTP and HTTP transfers done by PXE and Linux Kickstart, which have no AV involved.

Can anyone suggest ways to gather information as to why this might be happening?

Read full post . . . .

Unable to create Windows 7 virtual machine

I am trying to virtualize a Windows 7 machine (Hostname = ESI) that has exactly 1 application running on it. Using Disk2vhd v2.01 I am successfully creating a Vhdx file. The Windows 7 machine only has a C drive and a Recovery drive so I’m doing the copy
of both filesystems to a remote file system on the server where it will run.

Opening the Hyper-V Manager I attempt to create a new virtual machine and I get the following error (from the Event Log):

‘ESI’ Microsoft Emulated IDE Controller (Instance ID 83F8638B-8DCA-4152-9EDA-2CA8B33039B4): Failed to Power on with Error ‘The requested operation could not be completed due to a virtual disk system limitation.  On NTFS, virtual hard disk files must
be uncompressed and unencrypted. On ReFS, virtual hard disk files must not have the integrity bit set.’ (0xC03A001A). (Virtual machine ID FFEDD93B-40B2-4957-A488-CA3E19636012)

The C drive on the Windows 7 machine is not compressed or encrypted. Both servers are using NTFS filesystems.

Windows 7 Professional machine is a Dell Vostro 2705 with an I3-3220 CPU, 64 bit

The server where I’m migrating to is running Windows 2012 Standard, 64 bit

The Vhdx file is just under 56GB and he drive I’m putting it on has 6.85TB free

Does anyone have any ideas as to why I’m getting the failure?

Read full post . . . .

Go Que Newsroom Categories

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