I have a single Windows 2012 Server and trying to configure it for 2 independent purposes:
(1) DB Server MSSQL-2012
(2) VDI for about 5 clients.
I understand more or less how everything works but I'm little uncertain how the VM's should be nested into a single server. Should the Base Server manage the VDI Pools OR should a separate VM be created to manage VDI??
Base Install -- Windows 2012 Server with Hyper-V Role Enabled
(VM) - Windows 2012 Server with MSSQL
(VM) - Windows 2012 Server to Manage VDI Pool
(VM) Client VDI
(VM) Client VDI
(VM) Client VDI
The best thing to do is review Microsoft's LAB setups for various (and clearly defined) VDI scenarios. VDI QuickStart
Related
Ok, I know what is basically a Hyper-V is.
Simple, a virtual machine. Well, good for testing application and development usage.
Ok, so far so good for the understanding. and here the main question:
Why do you need to install servers in a Hyper-V on a real server?
Isn't that running a server os on the real machine is somehow better performance than running it in a virtual environment?
for example, database server. Install it in a virtual machine? why not on the real machine?
One example of its use would be to create the perfect developer environment if you want to run many different versions of SQL Server on the same physical box.
SQL Server 2005 isn't compatible with Windows 10 so a virtual server running Windows 2003 is better to house it. Windows 2008 for SQL Server 2008 and so on.
This also gives you the flexibility to allocate resources to different VMs and prioritise RAM to the instance that your currently developing against. Giving you server level options with client tools running on the host OS as intended.
Check out this blog post on setting up such a dev environment.
http://www.purplefrogsystems.com/paul/2016/05/using-hyper-v-and-powershell-to-create-the-perfect-developer-workstation/
I am new to Server and VM things. I recently have the following scenario:
I have 1 physical server that has server 2012 R2 installed on it.
My task is to setup two windows 7 VM environment by hyper-v for testing.
Since there are more than two people accessing the VMs in the future. I know the existing user is kicked when another user login to the VM. Is there any ways to configure this such that both users can access without being kicked? (without violating the terms)
I heard about remote desktop service and did some research on it. However, I do not know if it would fit on this scenario. If it fits, can you explain how it will work?
If none of that work, I am thinking my last plan will be setting up more VMs for the group to use.
Thanks
You will have to first add Hyper-v role in your server from server manager.
Since you are planning to add two virtual machines, you must assign 2 static IPs to each of the VMs.
To run concurrent two RDPs in windows 7, you can install this patch in your VM that has windows 7 OS. Once you have added the patch restart the VM and you will be able to access VM with 2 different user concurrently.
Anyone know why the below "net use" command gets varied results depending on the machine OS even though I am logged on as an admin in all cases? Fails or works based on the OS within PowerShell or Cmd whether the shell is run as Administrator or not. The share is setup in Azure File Services and can be accessed on my Win10 machine just fine using Azure PowerShell cmdlets.
# mount azure share as a drive
net use x: \\[myaccount].file.core.windows.net\davesdata /user:[myaccount] [my secondary key]
Runs fine on Server 2012
Gets “access denied” on Server 2008
Gets “path not found” on Windows 10
Azure File Storage supports the following Windows / SMB variants: Windows 7 SMB 2.1, Windows Server 2008 R2 SMB 2.1, Windows 8 SMB 3.0, Windows Server 2012 SMB 3.0, Windows Server 2012 R2 SMB 3.0 and Windows 10 SMB 3.0.
If you are connecting from a VM within the same Azure region you can connect using SMB 2.1 or SMB 3.0. If you are connecting from outside of the Azure region you need to ensure that Port 445 outbound is open. Many ISP's / corporate filewalls will block this. This wiki contains a list of ISP's that allow / disallow Port 445.
To map a drive to Azure File Storage from on-prem/outside the Azure region hosting it you need SMB 3.0 which comes with Windows 8/2012 or higher. For a machine inside Azure on the same Azure region you need SMB 2.0 or higher which comes with Windows 7/2008 or higher.
Definitely works on Windows 10 using the syntax you showed, double check for typos in the path/key or more detailed error messages in the event log. The mapped drive won't survive a reboot unless you persist the credentials.
cmdkey /add:storage_account_name.file.core.windows.net /user:storage_account_name /pass:storage_account_key
Port 445 was open on my router. It took me some time to find an additional option in the router: Netbios must be set to "allowed".
Then, Windows 10 works fine for me.
I am new to Hyper-V and Server Core but I am stumped as to how to install a guest OS from an ISO using only PowerShell.
I have downloaded the Hyper-V Server ISO and installed it on my server. It only installs Server Core and does not give me the option for a full GUI option. I configured its network settings, etc and all looks ok. So Server Core installed properly and Hyper-V feature is enabled. I can use PowerShell to create a VM with VHDX and link my Guest OS ISO to it. When I start the VM there is no console UI to install the OS.
How are you supposed to install a guest OS with no console interface to setup the OS?
Note, there is no option under this configuration to enable the OS GUI as some posts have suggested.
First, please don't confuse "Server Core" with "Hyper-V Server". "Server Core" is an installation mode of Windows. Among other things, it can be converted to GUI mode, which is why people keep telling you to just turn the GUI on. Hyper-V Server looks like Server Core but it is not Server Core.
For your actual problem, you're not going to find a simple out-of-the-box solution. You could work up a complete unattended installation process. You could set up a Windows Deployment Services server and have it install via PXE boot. I think some of the third-party Hyper-V management solutions allow you to connect to the console of a VM from within the local Hyper-V Server.
Hyper-V Server was designed with headless operation in mind. It was expected that you would use it to configure and perform maintenance on the management operating system and, if desired, the virtual machines as containers. The guest operating systems themselves were not really meant to be managed from within Hyper-V Server. What it's expected that you'll do is use a full GUI, whether another copy of Windows Server or a Windows desktop operating system running Remote Server Administration Tools to remotely connect to Hyper-V Server and manage its VMs.
I'm looking to test some of the new features in Hyper-V 2012 (v3).
Hyper-V v3 can be downloaded as a "free" version "Hyper-V Server 2012", or it can be purchased as part of Windows Server 2012 Standard or datacenter. However, as usual licensing is unclear.
On the one hand MS talk about their free edition in several (many) sites. On the other hand, when you go to the actual download site it talks about a trial. To me a trial has an expiry date so it makes me nervous.
I could use my Windows Standard 2012 license as part of my Microsoft Action Pack Subscription (MAPS), but I'm not sure what I'm actually entitled to.
So my question is:
What are the real differences between the free (trial) download of Hyper-V Server 2012 and the paid-for Windows Server Core 2012 where you have to install with a key.
Does the "trial" version actually expire?
No, Hyper-V Server 2012 doesn't expire.
Hyper-V Server is quite a bit like Server Standard Core with all of the roles except Hyper-V (and other supporting roles and features) removed.
Now, in Server 2012, you can add the full UI back to the Server Core editions, but that's not an option with Hyper-V Server 2012 - it will always just be a command-line. That also means that the typical management UI tools won't run on Hyper-V Server 2012, so you'll need a machine that you can manage it from remotely (the PowerShell cmdlets for Hyper-V actually do work on Hyper-V Server, though).
Hyper-V Server isn't really for people who want to "play around" with Hyper-V - it's really designed for people who want to boost their Hyper-V infrastructure with more physical hosts, and who want to run a very lightweight OS in the root partition, leaving the most resources available for the VMs.
If you just want to get used to Hyper-V or test some things out with it, but you don't have experience with managing Hyper-V remotely already, stick with a full version of Windows Server (or Windows 8 Pro/Enterprise x64, which also have Hyper-V).