2

I have 2 accounts on my machine one is the foreground account (console) that runs media center software.

The other account runs other programs I use in a remote desktop session.

I have enabled group policy to force 1 account per RDP session to stop applications starting multiple times.

But I cannot create a startup task to login the 2nd user when the 1st account autologin takes place on boot.

Is there a way to create a user session without RDP?

Everytime I try to RDP to the machine locally with or without console flag i get this error "Your computer could not connect to another console session"

Improve this question
4
  • What OS are we talking here?
    – Kip
    Aug 14, 2009 at 9:23
  • I think you need to explain what your trying to do here, does this relate to the other question you post about only running an application once?
    – Nick Kavadias
    Aug 14, 2009 at 13:43
  • Why can't you just let Windows create the session when you first connect to it when you want to use it. Like you normally do.
    – Mark Henderson
    Aug 16, 2009 at 21:47
  • In terms of the username/password thing - Windows only allows for storing one username/password combination for logging into a server. So if you need two profiles to automatically ogin concurrently, unfortunately I'm not aware of a way to do that.
    – Mary
    Jul 24, 2015 at 23:24

5 Answers 5

Reset to default
2

I am in the same position as you. I have my media center login which logs in automatically and which starts uTorrent up as well.

Now I am able to login as a remote user using another account, but I am unable to configure/view uTorrent.

The simplest solution is to give the hostname as 127.0.0.2 in mstsc. This will allow you to logon to another RDP session on the same machine.

However, I am stuck trying to run it from a command line. The first login works, but it is unable to save the username/password in a saved session.

Hope this works for you. Please revert if you have any suggestoins on this,

Improve this answer
1
1

You want stuff to be running locally on console & then RDP remotely & not affect the console session? Or
You want to have 2 login accounts that can RDP remotley into the desktop & take over the console?

For the latter, then RDP should do the job, make sure you have firewall rules setup to have exceptions for TCP 3389 which RDP uses.

Applications like winVNC and tightVNC always log you into the console session, maybe try these? RDP has much better performance if you can get it to work.

If you want the former, then your out of luck. I think MS has put this in as a limitation on windows desktops like XP/Vista so you dont end up using them as terminal servers.

You could do with with windows server? There may be OS level hack to get this to work in a desktop OS, but i have never had the need to do it.

Improve this answer
0

Is this something you are looking for?

Improve this answer
3
  • Sort of, I have already completed this step, but now I want one user to create an RDP session to localhost as the second user.
    – bleevo
    Aug 14, 2009 at 10:36
  • you want to rdp into your own computer?
    – Nick Kavadias
    Aug 14, 2009 at 13:42
  • Yes so I can create 2 sessions.
    – bleevo
    Aug 16, 2009 at 12:20
0

So this is a bit of a stretch, but have you looked at something like AutoIt (https://www.autoitscript.com/site/autoit/) for this? Basically autologin your console account per what you are doing now, then make a startup script in that profile that will RDP to itself with the other account. Have no idea if this will actually work, but that's the only way I can think of to bootstrap the way you are describing.

Improve this answer
-1

Maybe I'm missing something but to me RDP to localhost doesn't make sense and shouldn't even be possible, because it would allow the creation of an infinitely recursive process.

Improve this answer
3
  • Makes no less sense than a terminal session as another use or a virtual machine, I want to have 2 sessions running on the 1 pc. I can do this if I connect from another PC.
    – bleevo
    Aug 16, 2009 at 12:19
  • 1
    I guess it would work if you logged in as a 2nd user and thus the startup script didn't exist in the 2nd user...
    – Mark Henderson
    Aug 16, 2009 at 21:46
  • You can't login from a localhost to itself with the same account. You can login with a different account. Works fine. (I use that feature all the time as defacto sudo-type functionality on some Windows servers usually unprivileged but need to level up, rdesktop to same server, do task, exit back out.) If you do try to login to the same username locally, it blocks the login and throws an error.\
    – Mary
    Jul 24, 2015 at 23:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .