Remote. App for Windows XP and Windows Vista, the missing pieces. You may recall from my last post on Remote. How to Enable Missing Hibernate Option in Windows Start Menu? One of the most common problem in Windows is the missing "Hibernate" option in Start Menu. It is very common these days to be using Windows 2000/XP/Vista and have your CD/DVD drive stop functioning. There are various causes; from loose power or IDE cables.
App, that we can get Remote. App for Hyper- V works on other platforms too. While it was straight- forward publishing applications from a Windows 7 host, the client would report this error when connecting to Windows XP and Windows Vista hosts: Kind of annoying, because the original Remote. App for Hyper- V post on the RDS blog, showed us something cool but left out the important part on how to get it working. Well, thanks to Justin and this comment, I’ve been able to fix the issue and get Remote. Open RegEdit is a freeware utility that opens RegEdit (the Registry Editor) and goes straight to the Key you want. Open RegEdit also will read a Registry Key. This method shows you how to Start/Stop Windows Modules Installer from Services.msc. Please perform the following steps. App running on XP and Vista (unfortunately I can’t take any of the credit). Liam Westley has already done a great job of documenting the complete process for setting up Remote. App, so for full details go there – I’ll just summarise and fill in the missing pieces. What You’ll Need. First up there is a set of minimum components that will need to be in place: Configure the Remote. App Host. When configuring the host, I’ve been using been using a 1- to- 1 setup, I haven’t tested this with pooled virtual desktops yet. To enable Remote. App on the host, install the hotfix, then configure the Ts. App. Allow. List key in the registry. In this example, I’ve configured the required entries for running Calculator. Here’s a listing of the registry values I added with the pertinent values highlighted. There is documentation on Tech. Net on how to configure Remote. App programs and creating the . RDP file for each application here: Configuring Remote. App Programs. The important entries for connecting to Windows XP and Windows Vista, that you may need to add manually, are disableremoteappcapscheck (set to 1) and alternate shell (set to rdpinit. These were the only additional entries I need to add the . RDP file to get this working. Disable. Remote. App. Caps. Check fixes the . You will first see a warning prompt if the . RDP file is not signed, and then a dialog box while the client connects: If the Remote. App host is Windows XP, the user will be required to click the Details button to see the remote login dialog box and enter their credentials: If the client is Windows XP or above and the host is Windows Vista or above, you can configure credential pass- through (single sign- on) to make connecting seamless. You must first enable Cred. SSP on Windows XP SP3 clients. Pass- through won’t work for Windows XP hosts – although you may be able to save the username and password in the . RDP file instead. So finally with all of the pieces in place, here’s what you’ll see with applications running via Remote. App. In this screenshot I have Calculator running remotely from Windows XP and Windows Vista next to the local version. One thing to note is that the remote applications are all group together on the taskbar; in this screenshot, the two remote Calculators are grouped with Remote Desktop Connection – users’ won’t see separate remote buttons as you get in competing products. So What’s Left? Use of Remote. App is not restricted to the brand of hypervisor – Remote. App will be available on Windows XP+ regardless of where it is running. You could, for example, use blade PCs as hosts. If you have Citrix Xen. App or Quest v. Workspace, you already have tools to publishing applications from virtual desktops, so where would this actually be useful? SMBs without either product would benefit (although I have had one enterprise customer ask me about this feature) or perhaps this would work as a replacement for Windows XP Mode if you don’t like Windows Virtual PC (and who does?). Deploying and managing the . RDP files could be fun. A simple method of deployment would involve the use of Windows Installer packages adapted from those generated by Remote. App Manager. You could also use your user environment management tool of choice; however the option that holds most promise is extending RD Web Access. Custom code will be required, but it would replace copying . RDP files to users’ desktops and could even support pooled virtual desktops. Ultimately it would be nice to see this documented on Tech. Net. Apparently though, the RDS team are working on a follow up post that should give us all the info we need and more. Update (October 2. Kim Knight has written a GUI tool to configure the Remote. App application and create an RDP file to deliver to clients. This will automate the entire process for you. Remote. App Tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2018
Categories |