Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

we have a new Windows Server Standard 2008 R2 (no domain, no AD) and I am tring to configure Terminal Services/Remote Desktop connection to allow start just single application and not entire desktop for cerntain users.

I am trying to do it by setting Start the following program on connection (Windows XP)/Start only the following Windows-based application... (Mac OS X Lion) in users RDP file. But it does not work as it worked with Windows 2003 server. And it always shows the entire desktop.

Remote Desktop role is installed on the server, licensing type was not yet selected.

share|improve this question
add comment

2 Answers

up vote 1 down vote accepted

You are looking for the RemoteApp feature in Windows Server 2008 R2. It will start a remote desktop session that appears as a single application window.

If your users are meant not to have access to other applications on the terminal server, certain Group Policy settings (including Software Restriction Policies) are necessary. By itself, RemoteApp is not designed to securely limit users to a single application.

share|improve this answer
    
I tried this. I added desired application to RemoteApp list and generated RDP file there. But it did not help. It again opened full desktop same as if I created RDP file by myself. –  tssk Jan 27 '12 at 6:57
    
You need to copy the generated RDP file to your client machine and open it there. Please ensure that your clients are running RDC 6.1 or newer. In other words, your minimum client OS requirement is XP SP3, Vista SP1, or Windows 7. –  Skyhawk Jan 27 '12 at 7:00
    
I did exactly this. But I needed to edit the generated file because I need to conect over different hostname than the one pregenerated. Could this be the problem? I tried from Windows XP SP3 and Mac OS X Lion with Remote Desctop connection 2.1.1. –  tssk Jan 27 '12 at 7:17
    
Please paste the generated RDP file, including your edits, as a code block in an edit to your original question. –  Skyhawk Jan 27 '12 at 7:31
    
I tested once more with the generated RDP file for RemoteApp. And it works with Windows XP SP3. But not with Mac OS X (RDP client 2.1.1). Any idea? –  tssk Jan 27 '12 at 13:15
show 4 more comments

Without a domain, and group policies, I think you will find this is very difficult.

If you were using group policies, I would suggest you set this policy.

User Configuration/Policies/Administrative Templates/System/Custom User Interface

Without group policy, You could force every session to a particular application by setting the shell in the registry.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell

The option when you are using 2008 R2 or above is to use a RemoteApp, but this does require that your a newer client. I don't believe your OSX client will support RemoteApps.

share|improve this answer
    
It suprises me that the functionality changed so much. Was very easy to set up and use with Windows Server 2003. –  tssk Jan 27 '12 at 7:36
    
Apparently it is possible to make it work on a Mac, but only by editing the generated RDP file with the current Mac RDP client: social.technet.microsoft.com/forums/en-US/winserverTS/thread/… –  Skyhawk Jan 27 '12 at 8:08
    
According to this link Mac client does not support RemoteApp, so I am confused. social.technet.microsoft.com/Forums/en-US/winserverTS/thread/… –  tssk Jan 27 '12 at 13:17
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.