Can't get multiple sessions with the same user for the first time

[TooYoungTooSimp]

I have installed and upgraded rdpwrap to the newest version with "single session per user" unchecked.
What I am trying is to get multiple sessions with the same user.
But unfortunately, it can't work for the first time.
Here are the steps for me to reproduce it:

1. Login a account in the console.
2. Try to login the same account from another device.

Then the console sessions disconnects and it seems being attached to the remote device.
But when I try to login again from console, a new session starts and the remote session is still running.
Logout from remote device and login again can reproduce it too.

[binarymaster]

What is your TermService version?

[TooYoungTooSimp]

[deorth-kku]

emmmm, why does it work on your machine. I'm on 16299 too but it says 'not listening' and 'fully supported'.
Which edition is it? Is it win10 pro or home?
And your ID? Excited!
----update----
I've read though some old issues, and it seem RDPWapper won't work on WIN10 home since 14997. I'd better just wait for update.

[binarymaster]

@deorth-boffin

I'm on 16299 too but it says 'not listening' and 'fully supported'.

There is a solution in #194.

[TooYoungTooSimp]

@deorth-boffin Windows 10 16299 Enterprise

[nikoutsoukos]

I also have Windows 10 Enterprise with termsrv.dll version 10.016299.15 and it has the same behavior after the last update.
But I found a workaround.
When I login from a remote desktop application I do not give the password. So it take me to the login screen at the computer that I want to connect (and runs the rdpwrap) At that screen I give the user and the password and it opens a new session even if that user is alredy open localy.

You can also force Always to prompts the client for a password upon connection by changing a setting in group policy editor
Right click at start menu and run gpedit.msc and then you go
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Always prompts the client for a password upon connection
and you enable it

When I enable the above setting in group policy editor I can connect without problem from rdp app of my andoid phone. I Just write the password every time.

[TooYoungTooSimp]

@nikoutsoukos I have tried what you said.
Well... It is a tricky solution, but it does work.
If the password of the computer in my class were not so long, this would be a great solution.

[josh900]

I am also having this issue,
after updating windows 10 enterprise, version 1709, updating from 15063 to 16299.

It seems to work at sometimes.. but not sure of the details. maybe some type of authentication thing?

I have tested that when connecting over the rdp.exe app,
If the credentials are saved (after checking 'remember me' while logging in) multiple concurrent sessions can be opened with no problem.
Also, as mentioned above, multiple concurrent sessions work if logging in via the standard login, not the rdp.exe prompt.

seems to be related to #353 #326 #416

[josh900]

Thought maybe this was related to #194 #373 ?
I tried the script provided in #194, but no changes
I also tried changing the rfxvmt.dll owner to an admin user, but no changes.

I also found that if 2 sessions of the same user are logged in, using one of the methods above to open 2 sessions, then concurrent users are open with no issues.

Does anyone know what is going on here? or can point to any info?
Everything was working fine on version 15063, and all the above has started after updating to 16299. Verified on multiple computers.

[josh900]

It seems the behavior is, when a new session is opened, if only one session for the user is already opened, it will connect to the existing session. While if more than one existing session is open, then a new session is created.
This seems different than the behavior in previous windows versions, where a new session is opens every time, if multiple concurrent sessions is enabled.

Is there a way to force always create new session.?

I guess a workaround would be to open 2 sessions (rdp/local or rdp/rdp) on startup or similar, and then multiple concurrence users should open without issue. Obviously not the best option.

[lolvince]

same problem here # 513

[sebaxakerhtc]

There is a solution in #194.