The answer is a very clear "No".
ReFS only detects bit rot in user data if the file in question has "Integrity Streams" enabled (Sources: official TechNet docs, everyone's favorite blog post, and another spot). Oh, and you also lose COW (Copy-On-Write) when Integrity Streams are disabled. Since you cannot use a VHDX residing on a ReFS volume unless ...
It depends on how your configured your Virtual machines.
If you have your VMs configured to 'Turn OFF', then shutting down the host OS would be close to equivalent to pulling the power from the VMs. If your VMs are configured this way, and you want them to safely shutdown, then you need to shut them down first. You could also use the other options like ...
A third VM would, obviously, be the most desirable but, obviously, another Windows Server license costs money.
Active Directory will only disable write caching on volumes where the database files are located. Adding a dedicated volume for file service would be fine in that respect.
Of all the roles to "share" on a DC a file server is probably the least ...
How about turning this around:
The workstations are in a secured LAN, Internet access is restricted with a proxy to a number of white-listed sites that developers need - like StackExchange :). Developers have admin rights on the workstations.
For all other needs, they can connect to a VM and have (external) e-mail and possibly full Internet access, but no ...
For Hyper-V 2012:
Go into the BIOS by pressing F9. Go to "Advanced options > Processor Options" and enable these two sub-options:
No-Excecute Memory Protection and
Intel(R) Virtualization Technology
Save with F10.
For Hyper-V 2016 you're out of luck, as the DL380 doesn't ...
After a bit more searching it seems like this is a general problem with modern server CPUs, even unrelated to virtualization, and major server vendors as well as software vendors like Microsoft and VMWare ship their products with default settings that artificially limit your CPU performance. I still find that hard to believe.
The solution for anybody who ...
No, you should not be using AV software on the host to scan your VHD location. You can install AV software on the host but you need to exclude several Hyper-V related folders from the real time AV scanning engine and from any scheduled AV scans. You should then install AV software on the individual guest virtual machines.
You will need to enable the use of WinRM to connect to your Hyper-V server. To do this you will need to:
Open the Start menu
Click on All Programs and then on Accessories
Right click on Command Prompt and select Run as administrator
Type in winrm quickconfig and hit enter. You will then need to say ‘y’ (yes) to a couple of prompts
Type in: winrm set ...
You need to install AV which is specially designed for Hyper-V. It will install itself into host but it will scan VMs and their vRAM, on-disk images and also intercept traffic between VMs and host routed over vSwitch. 5nine has one (I'm not working for them it's just an example).
If you have the files, both the vhd(x) and the machine vmx file, and your system is configured the same with similar vSwitch names then you should be able to use the command Import-VM -Register path\to\the\file.vmx.
If you no longer have your VMX files then you should just re-create a new virtual machine and when asked about adding storage, use the existing ...
Sure, you can do this. You have two options:
Open PowerShell and run following command that will install only the Hyper-V Manager and it's dependencies:
Download and install RSAT (Remote Server Administration Tools) here that will provide you with all the server management tools including Server Manager, Hyper-V ...
This is an AVMA key from http://technet.microsoft.com/en-us/library/dn303421.aspx.
You can use it to activate server 2012 R2 datacentre on a properly-licensed Hyper-V host; it will activate against Hyper-V and not your KMS, SLIC, or Microsoft. However, it can be used only to activate server 2012 R2 datacentre.
If I'm reading you correctly, you are trying ...
Another way to do this is to go on the server and create a share. In my case, I ran:
net share "Downloads=C:\Users\Administrator\Downloads" "/GRANT:EVERYONE,FULL"
which is terribly insecure but fine if temporary and on a restricted network.
You can then access the ISOs you push in the Hyper-V Manager settings when you set the CD/DVD-ROM ISO.
Yes it will handle that just fine.
But I would recommend separating it from the DC. Setup one VM as just a domain controller and another as the fileserver.
It might also make sense, depending on your usage, to split the shares across multiple VHDXs, simple because large ones are more time consuming to move around and cant easily be split between storage ...
I'd use option #1, more host manageability.
I'd focus other efforts on making your remote sites more resilient...
Power is not difficult to protect in the branch office scenario. Buy batteries with extended-run capacity. E.g. my customers in volatile Los Angeles power conditions have between 60 and 240 minutes of battery runtime.
In the case of a site-to-...
Failover clusters require shared storage. Without it, if a machine dies, the data on them is inaccessible and there's no way to failover without the data.
I don't believe there is any built in fault tolerant method of using the local drives. For clustered virtual machines, you need shared storage, and internal drives don't qualify.
What you can do, ...
Not much to add here since StarWind and HP VSA are already mentioned!
Both products provide great value and do exactly what you're trying to accomplish.
Keep in mind, you won't be able to shuffle the VMs back to local storage if it's already provisioned as storage pool for either HP VSA or StarWind.
However, StarWind's storage is always available in ...
First of all, you should perform the OS installation using the latest OS ISO available from MSDN or VL; it already includes several update rollups (some of which are quite big), and it will save you a lot of update time and several check-update-reboot-recheck cycles.
Then install the latest .NET framework (currently 4.5.2): it also includes several updates ...
For Windows guests you'd use Sysprep to generalize the VM that you're using as your template. I don't know if something similar exists for Linux.
As for the MAC address, each cloned VM will have it's own unique MAC address, which is generated by Hyper-V so that shouldn't be an issue.
As for the ip address, if you use DHCP to assign ip addresses then this ...
You added space to the VHD. You didn't, however, change the partition table on that disk so that the file system on the disk can use the extra space. So, to the guest OS, it looks like a disk with one partition and some empty space that could be used for another partition. You can either add another partition (which would be an odd choice) and then format ...
Using command line:
First of all, list all the interfaces and note their names:
netsh interface ipv4 show config
Then configure each interface as following:
netsh interface ipv4 set address name="YOUR INTERFACE NAME" static IP_ADDRESS SUBNET_MASK GATEWAY
netsh interface ipv4 set address name="Wi-Fi" static 192.168.3.8 255.255.255.0 192.168.3.1
This kind of setup model is called hyper-convergence when compute and storage are running on the same hosts.
From my experience, I have never meet FC HBA that could run replication between 2 directly connected hosts. Check specifics of your FC, could it proceed with EoFC. If so, FC could be used for configuration of iSCSI shared storage between nodes since ...
How long is a piece of string?
Hyper-V is slower than bare metal, but just a couple of percent.
The critical point pretty much always is IO. For SQL Server also.
Hyper-V will not magically fix a bad disc layout.
I run a high performance SQL Server happily on Hyper-V, but it has 10 SSD and some HD attached ONLY to it (via pass through) to handle ...
Yes, but one exception - live migration works only on "compatible cpu's". There actually is a setting in CPU for forcing compatibility mode. If that is not set, and you mvoe for example from AMD to Intel, then - this is not possible in live migration, cluster or not.
StarWind Virtual SAN is pretty much everything you need. Unlike VM-running home-brewed solution GregL was mentioning this particular one is 100% native to Hyper-V as it's Windows app: simple to install and no VM patching mess. + performance. If you're fine with VMs take a look @ HP StoreVirtual VSA. It would be 1TB limited in capacity for their free version ...
Essentially, there are 2 registry values that need to be set before Bitlocker will allow a USB drive to be used to hold the startup/recovery keys. You don't need to edit a GPO via a GUI.
This is how I protected my c: drive with Bitlocker, storing my keys on a USB drive mounted as the k: drive. Step #3 is the part that replaces the need for using gpedit.msc. ...
Put the hosts on the domain. Otherwise management of them is more painful tham it needs to be. Its also a requirement if you ever want to cluster the two hosts.
However, since all your domain controllers are on there, if hyperv breaks badly you may have trouble logging in to fix it, if your cached credentials aren't valid.
Simple solution is to also have ...
Honestly, the short answer is that you need to switch to Intel nics. Broadcom has been trying to fix this problem for over a year and they still haven't licked it.
Avoid Networking Issues Hyper V
Virtual machines lose network connectivity when you use Broadcom
That second link brings you to a Microsoft site which will link you out again to driver pages ...