Rdp run program login

Thanks a lot. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English.

Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Remote Desktop Services Terminal Services. This is called "seamless" mode. From the manpage:. See mentioned Cendio website for more information. The current shell should be Explorer.

Change it to YourApp. That will change the shell for all users who log on to the machine. This is called RemoteApp. I think Citrix does that kind of thing. Though I'm not sure on specifics as I've only used it a couple of times. I think the one I used was called XenApp but I'm not sure if thats what you're after.

The basic idea is to create a virutal channel that sends the windows position of the app s you want to show, then only render that part of the window on the client. At least on R2 if the accounts are only used for RDP and not for local logins then you can set this on a per-account basis.

That should work for thin clients. If the accounts are also used on local desktops then this would also affect those logins. On that tab, check "Start the following program at logon" and specify the path and executable for the program.

As other answers have said -- you'll need to do some scripting and make policy changes as a kludge to make it hard for RDP logins to run anything but the intended application. However, as of , Microsoft has released application virtualization technology via Terminal Services that will allow you to do this seamlessly.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 12 years, 5 months ago. Active 1 year, 11 months ago. Viewed k times. Richard Dorman Richard Dorman Improve this question. You could place a user-tailored. This will eliminate the need for them to doubleclick the icon themselves. They will still be prompted for their password a second time.

It sounds like a thin client would also take care of you. The size of the remote office and the other demands on your time will determine if you want to spend the time to do it yourself or roll-out a thin client solution. Lots of students and part time. So I'd like to keep it as simple as I can for them. I may pickup one thin clint to see how it well it works.

Add a comment. Active Oldest Votes. You should be able to accomplish this pretty easy. Setup the client to auto start, use one of these methods. Drop an RDP file or shortcut in their startup group or the system startup group. Improve this answer. Zoredache Zoredache k 39 39 gold badges silver badges bronze badges. Thanks, I figured it would be pretty straight forward, I'll work on it this weekend.

I like the 3rd option that logs them out of the local desktop on disconnect actually. A computer of issues, using the set mstsc as the windows shell it did auto start. However when logging out of the remote computer, the local computer sits at a blank screen until I crtl-alt-del and logoff that way. Is there anyway around this? I was able to figure out a work around for these. For the logout issue, I am using a batch file as the Customer User interface, which starts mstsc with the command line for the server in full screen.