locked
Start application at user log in fails RRS feed

  • Question

  • Hello.

    I have two domain users that need to use an application at a remote server. To do this, they connect by Remote Desktop to the server. I had configured these users on the Active Directory user configuration (environment tab) to execute the application automatically when they log in, so they could only use that application and don't have access to the desktop, and log off automatically by closing the application.

    This was working fine before, when this server was an 2000 Server. Now it have been replaced by a new 2008 R2 Server and it doesn't work anymore. When the users log in, they enter the desktop and the program doesn't start automatically. It seems that the server is ignoring this configuration.

    I verified the applications path, tried with local users instead of domain users, same happens. I also tested many variants of the problem. The current DC is an 2000 server, I replicated the problem in other domain with 2003 Server DC logging in also to a 2008 server and had the same result. If I log in to 2000 or 2003 server (if the path exists), it works fine! What could be wrong?

    These users can't be allowed to use the desktop at this server so I have to work out a solution fast. Please help.

    Thank you.

    Thursday, April 22, 2010 9:47 AM

Answers

  • Hi there,

    You can use RemoteApp User Assignment feature in order to provide the app specifically to those two users.

    In regards to the app functionality, you can test it with TS App Compat

    http://connect.microsoft.com/tsappcompat

     


    ~Cheers Visit my Blog@ http://blog.helpforsure.info
    Thursday, April 22, 2010 1:03 PM

All replies

  • Hi there,

    You can use RemoteApp User Assignment feature in order to provide the app specifically to those two users.

    In regards to the app functionality, you can test it with TS App Compat

    http://connect.microsoft.com/tsappcompat

     


    ~Cheers Visit my Blog@ http://blog.helpforsure.info
    Thursday, April 22, 2010 1:03 PM
  • Hi.


    Thank you for the help. It works!

    I had to install the Terminal Services role so I could use RemoteApp User Assignment. Otherwise, it is not available. On the other side, the Terminal Services require the Licences Server service to be installed as well, otherwise looks like it will only work for 120 days (but since I didn't installed any CALs, I hope that it will not expire in 120 days anyway). In the end, I was able to reach the desired functionality.

    I don't really need any of the main functions of these roles and services I had to install. All I wanted is to auto-start an application when logging in remotely, as I used to do in windows server 2003 and 2000. But thanks to this "innovation", I have to install it all otherwise the Windows 2008 completely disregard the start program option, on the rdp client or on the users settings on the AD.
    I really can't understand why Microsoft does things this way. This is not the only issue of this kind I've detected...

    Thank you.
    Monday, June 21, 2010 5:08 PM