WORKS ONLY=> Windows 7 Enterprise, Windows 8 Enterprise, Windows Server
To enable RemoteApp on the host, install the hotfix, then configure the
The simplest method of discovering the required registry keys for
each RemoteApp entry is to configure the applications on Windows XP Mode
or Windows Server 2008 running Remote Desktop Services.
The important entries for connecting to Windows XP and Windows Vista, that you may need to add manually, are
An .RDP file to connect to a RemoteApp program then looks like this (the added lines are highlighted):
If the RemoteApp 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 configurecredential pass-through (single sign-on) to make connecting seamless. You must first enable CredSSP 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 RemoteApp. 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.
Configure the RemoteApp 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 RemoteApp on the host, install the hotfix, then configure the
TsAppAllowList
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.|
1
2
3
4
5
6
7
8
9
10
11
12
13
|
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList]"fDisabledAllowList"=dword:00000001[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList\Applications\calc]"CommandLineSetting"=dword:00000000"RequiredCommandLine"="""IconIndex"=dword:00000000"IconPath"="%windir%\\system32\\calc.exe""Path"="C:\\Windows\\system32\\calc.exe""VPath"="%SYSTEMDRIVE%\\Windows\\system32\\calc.exe""ShowInTSWA"=dword:00000001"Name"="Calculator""SecurityDescriptor"="" |
Creating RemoteApp Connections
I’ve originally based the .RDP file on those created by the RemoteApp Manager in Windows Server. There is documentation on TechNet on how to configure RemoteApp programs and creating the .RDP file for each application here: Configuring RemoteApp 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.exe). These were the only additional entries I need to
add the .RDP file to get this working. DisableRemoteAppCapsCheck fixes
the ‘remote computer does not support RemoteApp’ error, and Alternate
Shell makes sure you actually get a published application and not a
remote desktop.An .RDP file to connect to a RemoteApp program then looks like this (the added lines are highlighted):
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
redirectclipboard:i:1redirectposdevices:i:0redirectprinters:i:1redirectcomports:i:1redirectsmartcards:i:1devicestoredirect:s:*drivestoredirect:s:*redirectdrives:i:1session bpp:i:32prompt for credentials on client:i:1span monitors:i:1use multimon:i:1remoteapplicationmode:i:1server port:i:3389allow font smoothing:i:1promptcredentialonce:i:0authentication level:i:2full address:s:winxp1.domain.localremoteapplicationprogram:s:||calcremoteapplicationname:s:calculatorremoteapplicationcmdline:s:alternate full address:s:winxp1.domain.localdisableremoteappcapscheck:i:1alternate shell:s:rdpinit.exescreen mode id:i:2winposstr:s:0,3,0,0,800,600compression:i:1keyboardhook:i:2audiocapturemode:i:0videoplaybackmode:i:1connection type:i:2displayconnectionbar:i:1disable wallpaper:i:1allow desktop composition:i:0disable full window drag:i:1disable menu anims:i:1disable themes:i:0disable cursor setting:i:0bitmapcachepersistenable:i:1audiomode:i:0redirectdirectx:i:1autoreconnection enabled:i:1prompt for credentials:i:0negotiate security layer:i:1remoteapplicationicon:s:shell working directory:s:gatewayhostname:s:gatewayusagemethod:i:4gatewaycredentialssource:i:4gatewayprofileusagemethod:i:0use redirection server name:i:0 |
RemoteApp in Action
When launching the RemoteApp program, the UI isn’t quite as seamless as you get with the XenApp client. 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 RemoteApp 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 configurecredential pass-through (single sign-on) to make connecting seamless. You must first enable CredSSP 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 RemoteApp. 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.
No comments:
Post a Comment
Dear Friend ♥