Hot answers tagged hyper-v
One rationale for retaining one physical DC per domain is if there is a major incident that affects the host or trashes the frame storage for the virtualized DC's, you would have at least one physical DC with local storage to perform recovery and maintain continuity. Microsoft continues to perform this check and make this recommendation during Active ...
I too wouldn't make the Hyper-V host a DC. As for whether or not you should have a physical DC, my opinion is that with the changes Microsoft has implemented regarding virtualized Domain Controllers in general and DC-less cluster bootstrapping specifically, I don't personally see the need for, nor do I advocate having a physical DC. Maintaining a physical ...
I feel like you're looking for a one line answer, so here it is: You should have a physical DC if you do not trust your virtual environment's ability to withstand failure. We could wax on about the peculiarities and exceptions with each scenario, but I think this strikes the root of the question.
Let's take clusters out the equation and focus on the one line in your question that makes me shudder. Should I still be considering having a physical DC along-side my single, non-clustered 2012/2012R2 Hyper-V host that has a single virtualised DC on it? Why, why, why, would you want a single DC? In any given environment we try to avoid having single ...
PowerShell Remoting and Windows Credential Delegation are two different things. Most of the remoting you do is done without credential delegation. Delegation lets the computer you connect to remotely take your credentials and reuse them to hop to a 3rd server. This has security implications, but is sometimes necessary, especially when managing groups of ...
If you've changed the defaults then simply change them back. Right click the title bar, select Defaults and set the Window Size:Height to 25.
You would have to either establish a trust between the two domains, or, use Powershell Remoting and establish a remote PS session to hyperv01.test.local using test.local credentials, and then run Get-VM in the context of that WinRM session.
See https://social.msdn.microsoft.com/Forums/azure/en-US/62d03380-41e5-4be8-a742-431a980bc318/csupload-produces-unknown-error-unsupported-virtual-size?forum=windowsazuredata Looks like it needs to be a whole number in MB. Dividing your number by 1024 two times (to reduce to KB, and then MB) doesn't result in a whole number. According to the thread you ...
VMware Server 2.0 is kind of old, and had little or no remote management capabilities as we see in ESXi today. It was one of VMware's evolutionary dead ends. Nevertheless this ought to be possible. What I would do is the following. Note that the VM must be powered off. Locate VMware Server's datastore. The datastore details will tell you where the files ...
Turn off and delete the failed DC. Perform a metadata cleanup. Rebuild the failed DC. https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx
You also need to extend the volume in the guest using disk management. (Screenshot shows shrink, but you must extend)
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, ...
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 ...
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 ...
Heard about Disk2Vhd? This little tool here will convert your machine (physical or virtual) to a vhd disk on the fly. https://technet.microsoft.com/en-us/library/ee656415.aspx
I would leave the second DC RW. In case of hardware failure, the SBS server might be down for [a day/four hours/whatever your support contract says] while you get the replacement part.
Only top voted, non community-wiki answers of a minimum length are eligible