BitLocker Network Unlock on Hyper-V Gen2 Virtual Machines

Need some help with just figuring out basic requirements here. I have read some mixed information.
Curious if a windows server 2012 R2 running as a Gen2 type VM on a Hyper-V server can be setup to use the new BitLocker Network Unlock feature. If so I am having a tough time getting it to work as the only instructions I can find are from the technet
article below, which I feel isn't the best. Any light that can be shed on this would be great.
http://technet.microsoft.com/en-us/library/jj574173.aspx

Hi Fishizza,
To use Bitlocker on VM, however, I haven't found an official document indicating this, and this is not supported on the older OS version.
These discussions on this issue is for your reference:
Enabling
Bitlocker on HyperV server after VM's in use:
Can Iuse
BitLocker to secure virtual machines?
And you can also refer to the comment on the second article:
“Hyper-V in Windows Server 2012 R2 introduces a new feature called the “Generation 2 Virtual Machine” (Or Gen2VM, for short). This new type is capable of UEFI. UEFI is a requirement for BitLocker
Network Unlock, which is the feature in Windows Server 2012 and Windows 8 I’m referring to. This feature (with some heavy requirements) allows for domain-joined machines to automatically unlock the BitLocker encryption on the system drive when (and only when)
they’re connected to the corporate network. (ie they see the Certificate Authority, the DHCP server, the WDS Server and Domain Controllers).
The UEFI requirement for BitLocker Network Unlock is the only one that couldn’t be met within VMs, but with Gen2VMs we can.
It would be interesting to see if Microsoft will support this configuration and make BitLocker in Generation 2 Virtual Machines with Windows Server 2012 R2 supported.”
For more detailed information about Bitlocker and network unlock, please also check this article:
BitLocker Frequently Asked Questions (FAQ):
Best Regards,
Anna Wang

Similar Messages

Bitlocker Network Unlock - How to setup and configure

Good Afternoon,
I have a home network running Windows Server 2012 R2 that is a domain controller. Currently the roles on the server are the following:
- Active Directory Certificate Services
- Active Directory Domain Services
- DNS
- DHCP
- Hyper-V
- WDS
I have a 1 test laptop connected to the domain that is currently running Windows 8.1 Professional.
I am trying to setup the Bitlocker Network Unlock feature for the laptop. I am currently following this guide posted on this link below.
http://technet.microsoft.com/en-us/library/jj574173.aspx
I have followed the guide as closely as possible and I have gotten to the part named "Step four : Create Network Unlock Certificate.
I can open certmgr.msc and can request a new certificate but it says in the guide the following
"Choose the certificate template created for Network Unlock on the Domain controller and select Enroll. When prompted for more information, add the following attribute to the certificate:"
Unfortunately I do not have anything that is remotely suitable to choose. Am I to create the certificate first so that I can access this? Can someone please advise where I should progress from here please?
Regards,

Hi,
Have you created certificate templates for Network Unlock usage?
To do that, we can duplicate an existed certificate template then make necessary changes on it.
More information about creating new certificate template for you:
Creating Certificate Templates
http://technet.microsoft.com/en-us/library/cc731705(v=WS.10).aspx
Create a new certificate template
http://technet.microsoft.com/en-us/library/cc740077(v=WS.10).aspx
You can also create a self-signed certificate for Network Unlock usage as the article you mentioned guides, which has less steps to perform.
Best Regards,
Amy Wang

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Why does increasing logical processors in Hyper-V for virtual machine increase performance.

To my understanding, virtual machines (assuming relative weight is even) get an equal share of the processor. When the VM is given some processing time, it shouldn't matter if the VM is seeing a single core for it to use or multiple cores, since
the processing comes out of an array of processors on the hyper-v host regardless. However, when I set the "logical processor" setting from 1 to 4 in hyper-v for a particular VM, I see a huge performance increase.
Specs on my current setup are approximately: Hyper-V host has 32 gb ram, 24 logical processors (wrong word?), a few TB of space.
VM's are allocated 6 gb ram, 1 or 4 cores, a few hundred GB of space and running 2008 R2.
I've experience a similar thing on past Hyper-V setups.

Virtual machines in every hypervisor that I know of are able to use additional virtual CPUs on which to schedule additional concurrent threads of execution.
It's exactly that layer of abstraction between physical machine and virtual machine that makes it not work the way you describe. The VM is
not aware of how many cores the physical machine has. The VM does not "see" the physical CPUs (or cores) on the physical machine. The hypervisor gives the VM how ever many virtual CPUs, and the guest OS uses those virtual CPUs to schedule additional concurrent
threads... The total number of virtual CPUs the hypervisor hands out to the virtual machines can even exceed the number of physical CPUs/cores in the machine.
Said another way, a virtual machine, when assigned a single vCPU, schedules its threads as if it only had one CPU. It doesn't matter how many cores are in the underlying physical machine. (Though it is worth noting that the physical machine may schedule that
one VM thread on one physical core for one thread quantum, or time slice, and then run it on a different physical core the next time it's scheduled to run. The virtual machine has no idea any of that is happening though. All it knows is that it can only schedule
one thread at a time, one after the other, because it only has one virtual CPU.)
And let's be very clear about our terms here. You assign vCPUs, or virtual CPUs, to VMs, not "cores". Cores (by which I assume you mean physical processing units that share a single physical socket) do not equal vCPUs. There is a layer of abstraction between
them. If a VM only has 1 vCPU assigned to it, it can only schedule one thread to run at a time. That is why your VM runs faster with 2 -4 virtual CPUs assigned to it - because it is now able to schedule more than one thread to run concurrently.
However, there is definitely a law of diminishing returns here, as an excessive number of virtual CPUs incur a higher and higher overhead cost in
things like synchronization, etc.
There are slight differences between how Hyper-V and VMware hypervisors schedule virtual machine threads for execution, and they differ in their approach to physical resource "oversubscription," but this is a good general concept to start with.

How does Sharepoint 2013 Server farm using BLOB data, Hyper-V with virtual machines storing the BLOB data?

Hello Community
    A Sharepoint 2013 Server farm created on a physical server
stores it's documents in SQL Server according to how SQL Server is setup.
    If a Sharepoint 2013 Server farm is using Hyper-V and Virtual machines
how is BLOB data stored ?
    Thank you
    Shabeaut

Are you looking to use Remote Blob Storage? or RBS of SQL with SP?
It is going to be same way as it is configured for physical server.
Thanks, Ashish | Please mark a post helpful/answer if it is helpful or answer your query.

Win8 Pro Hyper-V Error : Virtual machine could not be started because the hypervisor is not running

Hello,
Recently in Dec I bought a new desktop PC.
HP ENVY Desktop h8-1420t
CPU & ChipSet: Intel Core i7 Intel Z75
I have Windows 8 Pro and installed Hyper V but cannot start the virtual machines. I get the following error message: Virtual machine 'zzzz' could not be started because the hypervisor is not running
I followed these steps to enable Hyper-V:
1. Upgraded to Windows 8 Pro
2. Tried to add Hyper-V feature but Hyper-V Platform was grayed out
3. Enabled Virtualization in the BIOS - security configuarion
4. Cold booted Computer
5. Added the Hyper-V Platform Feature
6. During the restart machine was in forever state spinnign state, did a manual reboot
7. Disabled Virtualization in the BIOS again
8. Successfully Re-Booted the Computer now Hyper V manager was available
9. Configured Hyper V network to use external network
10. Created a new VM through the Hyper-V Manager
12. Tried to boot up teh newly Created VM and I get this error message:
Virtual machine 'zzzz' could not be started because the hypervisor is not running
Any solutions for the error I am seeing above?
Similar problems are discussed here:
http://h30434.www3.hp.com/t5/Desktop-Lockups-Freezes-Hangs/Cannot-boot-if-HP-ENVY-Bios-Virtualizatio...
Thanks!!

Same Problem Here - did you discover any answers? I may have to return the system if it can't do hyper-v

Create image server operating system with Hyper-V and virtual machines

Friends,
Need to replicate the environment they currently have, but wanted to optimize this operation by creating an image of windows server with Hyper-V and virtual servers already installed, what tool do I use? Can someone guide ???
Dreyher

I recommend you separate the task of protecting the host from the task of protecting the guest VMs.
By "replicate the environment", do you mean backup the VMs in a recoverable state? or do you intend on migrating the VMs to another environment like another physical location? How much down time can you tolerate if any?
To backup the VMs use a VSS based backup solution. There's plenty out there, including Windows Server backup, Altaro, DPM, Veeam, and many more. This does not require installing agent on any of the VMs, and will not down the VMs during backup. Here's an
example Powershell script to backup all VMs on the local host:
Install-WindowsFeature -Name Windows-Server-Backup
$BackupTarget = "\\server\share"
$WbTarget = New-WBBackupTarget -NetworkPath $BackupTarget
$WBPolicy = New-WBPolicy
Add-WBBackupTarget -Policy $WBPolicy -Target $WbTarget
Add-WBVirtualMachine -Policy $WBPolicy -VirtualMachine (Get-WBVirtualMachine) # Add all VMs on localhost
Start-WBBackup -Policy $WBPolicy -Async
If the intent is VM migration from one location to another, there are plenty of tools to do so with minimal or no down time. Just bing it..
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

Hyper v manager: "virtual machine connection has stopped working", when connect to VM

Hello,
cannot find any info on web and View problem details in VIRTUAL MACHINE CONNECTION error box:
"virtual machine connection has stopped working".
I get this error when click Connect in HV Manager. The machines are on and are accessible through RDP.
This is a lab host after restart it randomly works. I have this problem during last week.
Just interesting to know what could cause the problem and if other were seeing something like that...
Also, can connect to machine from SCVMM.
Thx.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

I have the same problem.. Running hyper-v manager from win7 x64 client...
Problem details:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: vmconnect.exe
Problem Signature 02: 6.1.0.0
Problem Signature 03: 4ce75fbd
Problem Signature 04: vmconnect
Problem Signature 05: 6.1.0.0
Problem Signature 06: 4ce75fbd
Problem Signature 07: 107
Problem Signature 08: 29
Problem Signature 09: System.ArgumentException
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
I have the exact same issue (running windows 2008 R2 Enterprise). I can RDP to any of the VM but simply cannot connect using console. This is causing me grief since I have to create few more VMs and work with the existing VMs. Without console
access, I cannot create and do any config changes for new VMs. Can someone help. Things that I have tried so far.
1. Exported VMs
2 uninstalled .NET 4 & 3.5.
3. Hyper-v role removed.
4. Reinstalled Hyper-v, reinstalled .NET 4 & 3.5, patch current as of today.
5. Imported the VMs back and still cannot connect. Exactly same error. No errors in any logs in event viewer or Hyper-v logs.
6. Navigated to c:\Program Files\Hyper-v and manually run the VMCONNECT.EXE app (choosing the localhost/server and appropriate VM from the list) but no dice. The app just sits there for ever without any connection.
7. I am baffled and surprised no one has a solution. Tried multiple search engines.
8. The host machine is patch current as of today and there are no patches available to try. Reading through some forums, I have also installed some hotfixes with no luck.
9. Finally, I can see the little graphic for each VM changing as windows is loading or stopping in server manager for hyper-v.
Hoping someone has a solution. The error that pops up is exactly similar and no clues of the faulting module.
Appreciate your time and help.

Monitor bandwidth utilization for Hyper-V's Virtual Machines

Hi,
I'm wondering, if SCOM is capable to monitor incoming & outgoing traffic (current and total over time) of VMs in Hyper-V?
Tried to search about it, and found only 3rd party tools or the monitoring is only available for Router, not VMs.
Thanks.

Hi Andre,
Also you can use performance monitor to monitor the VM's bandwidth through counter "Bytes Received/sec" and "Bytes Sent/sec" under Hyper-v virtual network adapter :
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

No external network access from virtual machine

Hello:
I'm configuring a Windows Server 2012 Standard with Hyper-V and want to share a network card so that both the virtual machine and the host access a LAN using the same wire.
HOST SYSTEM:
OS: Windows Server 2012 Standard
IP: 192.168.50.1
VIRTUAL MACHINE: Windows XP
IP: 192.168.50.4
PHYSICAL SWITCH (CISCO):
IP: 192.168.50.6
I've configured an external virtual switch, assigned to it a physical card and activated the sharing between host and virtual machine.
With this configuration:
ping from HOST to VM and viceversa: OK
ping from HOST to REAL SWITCH: OK
ping from VM to REAL SWITCH: FAIL
If I configure the network card to work exclusively with the VM, it can access the external switch from the VM, but I lose any connection with the host.
I could solve the problem installing another physical card and using one for the host and one for the VM, but I can't get both working with the same card, even though they are in the same subnet, see each other, share files between VM and host... I'm not
trying to connect to the internet.
Any idea? Thanks.

Hello again,
Sorry for the delay.
After system update, the problem has not been solved. The external switches do not limit the number of MACs, so this is not the problem either.
After updating the system I deleted the virtual switch and created it again. I also rebooted the VM and even the server. It just doesn't share the access: only the VM or the server can access to the net at the same time, even if both see each other all the
time (server and VM).
Apart from that, every time I delete the virtual switch and create a new one, I reconfigure the VM as well (I delete the network card at the VM and create it again). When I do that I have to assign an IP address to the network card in the VM (no DHCP
installed, so this is normal), but I can use the same IP I was using before deleting the virtual switch. When I do so, a message appears saying the IP is used in a virtual network adapter, but this is hidden because it is not in use anymore. I haven't found
a way to see and delete these hidden network adapters either.
I think I'll install VMWare, because Hyper-V is more a problem than a solution.

Add network card to virtual machine and all available virtual networks aren't showing

Have a Hyper V 2012 cluster....we have a network card cabled for our DMZ network ...it's enabled.
Under a host in cluster in Virtual Switch Manager we have the virtual switch configured as external and it matches up with NIC number in the OS network connections...NIC 9. It's configured like the other virtual switches that are showing.
On our Hyper V Mgr console...under VM Networks..the DMZ network shows...I checked...settings same as other networks.
Still on our Hyper V Mgr console..under Logical Networks...the DMZ network shows...I checked...settings same as other networks.
When we go into Virtual Machine Mgr...hardware configuration for VM we created...add network adapter...the DMZ network doesn't show up in the list for VM networks so we can't assign IP or really add NIC in general.
I was able to go to an actual Hyper V host...under Hyper V Mgr that the VM was running on this particular host and I was able to add a network card/virtual switch..VM can ping devices...however if I go into the Hyper V Mgr in the Hyper V Mgr server and go
to properites of VM...a NIC is not listed.

Have a Hyper V 2012 cluster....we have a network card cabled for our DMZ network ...it's enabled.
Under a host in cluster in Virtual Switch Manager we have the virtual switch configured as external and it matches up with NIC number in the OS network connections...NIC 9. It's configured like the other virtual switches that are showing.
On our Hyper V Mgr console...under VM Networks..the DMZ network shows...I checked...settings same as other networks.
Still on our Hyper V Mgr console..under Logical Networks...the DMZ network shows...I checked...settings same as other networks.
When we go into Virtual Machine Mgr...hardware configuration for VM we created...add network adapter...the DMZ network doesn't show up in the list for VM networks so we can't assign IP or really add NIC in general.
I was able to go to an actual Hyper V host...under Hyper V Mgr that the VM was running on this particular host and I was able to add a network card/virtual switch..VM can ping devices...however if I go into the Hyper V Mgr in the Hyper V Mgr server and go
to properites of VM...a NIC is not listed.

No longer able to view virtual machine from Hyper-V Manager

From the Windows 2008 R2 host machine, I can run the Hyper-V Manager and 'connect' to the Virtual Machine. The window pops up with nothing but a gray background (clearly the same gray background of the log in screen), but no 'ctrl-alt-delete' prompt
and no ability to log in. This was previously working fine.
Note that I can still make a Remote Desktop connection to the Virtual Machine and it works fine.
Thanks.

Hi,
I never seen this issue before, base on my experience, it may cause by your AV soft block some critical components of Hyper-V host, please try the following exclude specific
directories or process with your AV soft.
•Default virtual machine configuration directory (C:\ProgramData\Microsoft\Windows\Hyper-V)
•Custom virtual machine configuration directories
•Default virtual hard disk drive directory (C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks)
•Custom virtual hard disk drive directories
•Custom replication data directories, if you are using Hyper-V Replica
•Snapshot directories
•Vmms.exe (Note: This file may have to be configured as a process exclusion within the antivirus software.)
•Vmwp.exe (Note: This file may have to be configured as a process exclusion within the antivirus software.)
The related KB:
Virtual machines are missing, or error 0x800704C8, 0x80070037, or 0x800703E3 occurs when you try to start or create a virtual machine
http://support.microsoft.com/kb/961804/en-us
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Vhd has the sama function as virtual machine or hyper-v in windows 8

hi,
is VHD has the same function as hyper-v or virtual machine. if yes then I can make virtual machine from windows 7 home premium if the hardware support it.
thanks
johan
h.david

All VHDs are Virtual Machines and have the same function since they emulate a hardware environment, but they are not compatible between the different VM software. They each have their own structure and are not directly compatible. There are utilities
that can be found on the internet that claim to export or import VMs from varies different VM software.
Windows 7 XP Mode and Virtual PC use the same structure, but Hyper-V is a different structure.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Hyper-V - 'Failed to start the virtual machine 'test' because one of the Hyper-V components is not running.'

Hi all,
Having a bit of a nightmare with Hyper-V on my Windows 8 Pro laptop - Whenever I create a new VM and try to start it I receive the following error;
'Failed to start the virtual machine 'test' because one of the Hyper-V components is not running.'
I sometimes also receive an error saying something along the lines of 'Unable to change virtual machine state'
I have done a lot of searching a seen two common answers - The first is to try removing the Hyper-V role and re-adding it - I have tried this several times to no avail. (Intel VT and all virtualisation capabilities are enabled in BIOS). The second issue
it would seem
some people have had relates to editing the VMX configuration file and adding the line
hypervisor.cpuid.v0 = "FALSE" - I thought VMX files were only present in VMware Virtual Machines...
Any help would be greatly appreciated.
Many thanks in advance.
James

The hypervisor event log message is generated only at boot - so this would be expected. Also vmbus should not be running on the host (I was looking at a VM yesterday)... This error message is generated only when the vid is determined not to be
running or cannot communicate with the hypervisor.
I have seen this due to anti-virus software in the past or due to driver verifier being configured. Since it looks like you checked driver verifier already do you have anti-virus software installed? If so have you followed the best practices
and exempted the Hyper-v services?
http://technet.microsoft.com/en-us/library/dd283088(WS.10).aspx
To resolve this problem, configure the real-time scanning component within your antivirus software to exclude the following directories and files:
Default virtual machine configuration directory (C:\ProgramData\Microsoft\Windows\Hyper-V)
Custom virtual machine configuration directories
Default virtual hard disk drive directory (C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks)
Custom virtual hard disk drive directories
Custom replication data directories, if you are using Hyper-V Replica
Snapshot directories
Vmms.exe (Note: This file may have to be configured as a process exclusion within the antivirus software.)
Vmwp.exe (Note: This file may have to be configured as a process exclusion within the antivirus software.)
-Taylor Brown<br/> -Program Manager, Hyper-V<br/> -http://blogs.msdn.com/taylorb

Hyper-V virtual machines disappearing

Running W10 Enterprise TP with no security software, nothing fancy.
Twice now my Virtual Machine running locally in Hyper-V Manger have disappeared after a reboot. They are still running in the background by their VHDs being in use, but I can't see them to do anything.
Last time this happened, I had to remove Hyper-V, reboot, re-add Hyper-V, and the VM appeared. However, there was something wrong with the VM so I deleted it and started over.
Any ideas?
My idea of a party is a virtualization server and a room of TechNet DVDs

@ThrashZone, Thank you but this is an issue that occurs after it has already been up and running.
@h_vHE I'm running Windows 10. Interesting: Everything has disappeared from C:\Users\Public\Documents\Hyper-V\. However, the virtual machine "IMAGEBASE" appears in C:\ProgramData\Microsoft\Windows\Hyper-V\. Here's a dir /b /s:
C:\ProgramData\Microsoft\Windows\Hyper-V\data.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Groups
C:\ProgramData\Microsoft\Windows\Hyper-V\Groups Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE
C:\ProgramData\Microsoft\Windows\Hyper-V\Persistent Tasks
C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Snapshots
C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Snapshots Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines
C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\UndoLog Configuration
C:\ProgramData\Microsoft\Windows\Hyper-V\UndoLog Configuration Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines
C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache
C:\ProgramData\Microsoft\Windows\Hyper-V\Groups\groupregistry.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Groups Cache\groupregistry.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Hard Disks
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Hard Disks\IMAGEBASE.vhdx
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54.VMRS
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\06FF76FA-2D58-4BAF-9F8D-455773824F37.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\118C3BE5-0D31-4804-85F0-5C6074ABEA8F.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\146C56A0-3546-469B-9737-FCBCF82428F4.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\19839BFF-6F04-4B24-B4B5-1AFCCBE729DE.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\353B3BE8-310C-4CF4-839E-4E1B14616136.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\4764334E-E001-4176-82EE-5594EC9B530E.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\4EA4F71F-16E6-4250-99A8-A2315332CC64.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\6A45335D-4C3A-44B7-B61F-C9808BBDF8ED.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\70BB60D2-A9D3-46AA-B654-3DE53004B4F8.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\72027ECE-E44A-446E-AF2B-8D8C4B8A2279.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\78AA0C27-B2BD-45BA-83D1-5F2A8C4C6656.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\7951A5ED-8DC5-42D7-AA8C-9F14C54CEB84.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\B637F347-6A0E-4DEC-AF52-BD70CB80A21D.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\BDE5D4D6-E450-46D2-B925-976CA3E989B4.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\D45268DA-37C5-44DA-B827-B0C55CCB3BDC.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\D92D268E-9AA8-49DD-8C7D-821CEFB5F597.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\DACDCF3F-6F67-4EB8-A4D0-5D93B48A2468.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\ED28BF6C-B698-4513-B8F4-7BDD01E006A2.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\F6293891-F32F-4930-B2DB-1A8961D9CB75.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups\groupregistry.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups Cache\groupregistry.vmcx
C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54
C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54.vmcx
My idea of a party is a virtualization server and a room of TechNet DVDs

BitLocker Network Unlock on Hyper-V Gen2 Virtual Machines

Similar Messages

Maybe you are looking for