IDSNET
asked on
Windows 2012 virtual "terminal server"
I want to virtualize a new terminal server (yes I know the name changed) on a windows 2012 server, this server, along with three other clustered servers, has 6 other virtual machines.
When installing on a VM I get an error about the hardware is not supported. Is this possible?
When installing on a VM I get an error about the hardware is not supported. Is this possible?
Cliff Galiher
Well, you didn't give the exact error or details about your environment, but since you set one of the topics as Microsoft Virtual Server, we'll go with that. And no, not possible. Virtual Server didn't support 64-bit OSes so neither 2008 R2 or 3012 can be installed with that product. Microsoft's current virtualization platform is hyper-v. Virtual Server is long retired.
We can give a better answer if you use proper terminology or clarify where you don't know proper terminology.
ASKER
Thank you for the replies.
I have Windows 2012 with 3 Fail Over Clustered servers. I need a virtual machine that will run a remote desktop server currently running at Windows 2012 Standard OS.
Running the Remote Desktop Service installation, using Quick Start and Virtual machine-based desktop deployment I cannot install the Broker I get an error:
Hardware-assisted virtualization is not present on the server.
So I ask, is this not possible? Do i need to install the Broker on the Clustered Servers? I have done a virtual machine (hyper-v) Remote Desktop servers with 2008 R2 with no problem.
I have Windows 2012 with 3 Fail Over Clustered servers. I need a virtual machine that will run a remote desktop server currently running at Windows 2012 Standard OS.
Running the Remote Desktop Service installation, using Quick Start and Virtual machine-based desktop deployment I cannot install the Broker I get an error:
Hardware-assisted virtualization is not present on the server.
So I ask, is this not possible? Do i need to install the Broker on the Clustered Servers? I have done a virtual machine (hyper-v) Remote Desktop servers with 2008 R2 with no problem.
If I understand what you've done, hat you are trying to do is not possible, and for clarity, was not possible in 2008 R2 either.
You are running a VM on some (still unnamed) virtualization platform. Fair enough. Somehow your platform is clustered. Also fine.
You are running the remote desktop deployment wizard on a guest VM. Also fine.
You are choosing the "virtual machine based desktop deployment" option. This *cannot* be done in a VM. This option is meant for VDI deployments and sets up a physical machine to host VMs, such as many windows 7 or windows 8 VMs, for virtual desktops. Since you are *in* a VM, it would basically try to create and nest a VM host inside another VM host, and this has never been supported or allows. You cannot, for example, enable Hyper-V on 2008 R2, create a guest VM, install 2008 R2 in the guest, and enable Hyper-V in that guest. It would also fail for the same reason.
If you are trying to set up a traditional terminal server, you want to choose the "session based" option. Not the virtual machine option. Terminal servers have always been session based.
You are running a VM on some (still unnamed) virtualization platform. Fair enough. Somehow your platform is clustered. Also fine.
You are running the remote desktop deployment wizard on a guest VM. Also fine.
You are choosing the "virtual machine based desktop deployment" option. This *cannot* be done in a VM. This option is meant for VDI deployments and sets up a physical machine to host VMs, such as many windows 7 or windows 8 VMs, for virtual desktops. Since you are *in* a VM, it would basically try to create and nest a VM host inside another VM host, and this has never been supported or allows. You cannot, for example, enable Hyper-V on 2008 R2, create a guest VM, install 2008 R2 in the guest, and enable Hyper-V in that guest. It would also fail for the same reason.
If you are trying to set up a traditional terminal server, you want to choose the "session based" option. Not the virtual machine option. Terminal servers have always been session based.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.