Part four of my weekend project is to add the Hyper-V management applications to Terminal Server web access. Let’s see just how easy that is. Of course, I could have left it at the point of “TS’ing” to the Hyper-V machine directly like in the screenshot below, but we’re so close to having the management applications remoted, let's finish it off.
The first thing I need to do is to make the Hyper-V management applications available on the Terminal Server machine itself. Let’s go a small step further (after all, I’ll want to manage much more than just Hyper-V) and put all the management applications for Windows Server 2008 onto the Terminal Server machine.
Start up Server Manager, and select features. From here, click Add Features
Here I’m making sure all Remote Server Administration Tools are selected.
Just let the Add Features Wizard run through it’s stuff to the end and restart the machine when prompted. You’ll notice that the Administrative Tools menu now has a wealth of options including Hyper-V Manager.
Let’s startup the TS RemoteApp Manager application to start adding applications to the TS Web Access page. You’ll notice the messages saying that there are currently no remote applications configured.
Click Add RemoteApp Programs from the Actions pane on the far right, and the RemoteApp Wizard starts. When you get to “Choose programs to add to the RemoteApp Programs list”, you’ll notice that the Hyper-V Manager application isn’t listed. We can just browse to virtmgmt.msc which (in Hyper-V Beta) is located under %Program Files%\Hyper-V\virtmgmt.msc. Note that you have to change the file filter on the browse dialog to “All Files” as by default, only executables are shown.
Simply click through to the end of the wizard, and that’s pretty much it.
Now I’ll log back on to the TS Gateway and verify that Hyper-V Manager is now available as an application.
Simply log on with appropriate credentials to connect to your Hyper-V machine, and it “just works”. The following screenshot was a little difficult to capture, as I was trying to show you that the Hyper-V Manager really is running remotely on a Vista SP1 machine - notice a few sidebar applications open. You’ll have to take my word for it, I really am not running any Hyper-V components locally (in fact, they’re not available in the Hyper-V Beta anyway, apart from on Windows Server 2008). Of course, you can open VM settings, connect to the interactive console using Virtual Machine Connection and so forth as you can see. Least surprising is that it’s cold and raining in Seattle - absolutely nothing out of the ordinary there for this time of year!
So in summary, it’s pretty straightforward to bring up a 64-bit Windows Server 2008 virtual machine under Hyper-V, configure it with Terminal Services and expose both direct RDP and TS Web Access securely onto the Internet through ISA Server 2006.
Hope this helps someone!
PingBack from http://www.leadfollowmove.com/archives/virtualisation/jhoward-hyper-v-and-terminal-services-stuff
Sorry for the dearth of posts - I have been rather busy lately.  As such I thought I would quickly
I read the your 4 parts of terminal services web accessing.Its really Good topic.Now iam working on same model.Can you please mail me detailed installation document.
<Removed for privacy>
Naresh - the closest there is to an install document is what I posted.
Thanks for reply.I have 10 virtual machines inside terminal server(Host OS).i want to open one virtual machine depending upon the usercredentials while logging into terminal server remote access.kindly help me how to solve this issue.
As I mentioned in my first post in this series, I'm far from pretending to be any expert in Terminal Server I did some quick experimentation, and this may provide a workaround. However, you really need to find a TS expert to get a more in-depth and complete answer.
In TS RemoteApp Manager, create a new RemoteApp application which points to vmconnect.exe but select "Always use the following command-line arguments". In the parameters enter "HVServer VMName". HVServer is the DNS name of the server with the Hyper-V role where the VM being connected to resides. VMName is the name of the VM to connect to as displayed in Hyper-V Manager.
This can then be exported as a .RDP file to clients (or left exposed on the TS Web Access gateway portal). Repeat as necessary for each VM.
I don't know whether the TS portal can display different applications according to who logged in though.
Thank you for reply.Its working fine but iam facing problem like if multiple users connect to one virtual machine at a time the same things reflecting to all users like same application reflecting.Is it possible to connect to one virtual machine using different authentications like terminal server?Waiting for reply........
There is a company called Expand Networks that has a unique solution to improving the performance of RDP, Citrix and other thin clients used in Virtualization environments where data is sent to distributed network environments.
I managed to do the same thing with one small nuissance. Before the hyperv management console starts I get an UAC prompt on the windows desktop. I don't really mind the UAC prompt, but because the prompt isn't in a seamless window it is really too small to read. And if I didn't know it was uac it would be pretty tough for a user to identify what he needs to do.
How did you get around this prompting issue? Did you just disable UAC for admins?
Actually the Expand box gives the best results on congested terminal services, citrix and the remote desktop solutions based on the ICA and RDP protocols. Jason the free evaluation link is handy but I need more meat before I pull the trigger.
To get the best benefit you will need to turn off compression and step down encryption as you can't accelerate traffic that is already compressed and encrypted.
Try here first
Ok, I'm going back a few years now (2 - 3), but I was involved in a large roll our of expand devices (across 15 + sites) for a Citrix solution.
We ended up getting a full refund from the guys at Expand after we were able to prove that while, yes, you're right, you need to turn off ICA encryption and compression for the Expand devices to be able to perform, they DO NOT out perform the native Citrix compression that comes free... in fact the expands performed less well than native compression (this was PS 3.0)
I do apologize for some reason I was not notified of your comment in February. Actually that eval was 2004/2005. And it is true you will need to turn off compression and step down encryption on a congested Citrix link and typically we do deliver better performance than Citrix compression. But if the line is not congested we have so far been unable to improve upon the speed of light. I don't have full knowledge of your old situation and find it difficult to debate conditions taking place over 4 years ago. but with over 2000 customers currently using Expand, the solution has proven to be successful And not only with congested Citrix, RDP, PC over IP and ALS but Zen Desktop and Vmware View as well.