Yes, restart. It is a desktop computer. It does not matter to restart or turn off since it is not a laptop that can hibernate or suspend itself. Multi-user WORKS and multi-session does NOT work. The termsrv patch had always worked for me for years. It does not matter much either since what I usually use is multi-user. Multi-session I do not usually use it although it is rare that it does not work. The multi-session patch has changed since version 19041.84. Before it was in 18362.836: 58010000FF15F7 <=> 58000000FF15F7 (I have not found this string in 19041.84) and now in 19041.84: EC2033DBC7400801<=>EC2033DBC7400800
If you were a user of RDP Wrapper, that was one of the cool features. Never used it, but still. On the other hand, the RDP Wrapper did not allow print forwarding, so there's always a catch.
Never used RDP Wrapper, and I didn't know it had this function. Good to know, even if I still don't understand which can be a "street use"
One typical use case with even default Windows Server setups is the ability for 2 Administrator sessions in parallel. I often find myself logged via hypervisors console (especially when patching the termsrv.dll) and RD app. Another one - when user connected to his account faces a problem and instead of connecting to his terminal via Teamviewer, you can connect directly via RD and check the error or the problem. The wrapper had a very good approach to tackling the termsrv.dll. I'd say it's a very elegant and non-intrusive approach: instead of editing the file, it was hooking into it on load and doing the adjustments that we do via TinyHex on the fly. On the other hand, lack of printer forwarding, combined with the possibility of being locked out entirely (vs limited to one session in parallel) were significant bottlenecks. It'd be interesting to see that project picked up at some point, maybe by someone from this community.
Thanks for the help. After patching termsrv, I always check that it works both multiuser and multisession and both have always worked for me with all previous versions. I usually always use multiuser so I don't mind multisession not working. It was just strange to me that since 19041.84 it stopped working. Goodbye.
I download it and no porblems with Query@CDefPolicy The values are the same, as i said you: LocalOnlyPatch.x64=1 LocalOnlyOffset.x64=87611 LocalOnlyCode.x64=jmpshort SingleUserPatch.x64=1 SingleUserOffset.x64=0BF0C SingleUserCode.x64=Zero DefPolicyPatch.x64=1 DefPolicyOffset.x64=17ED5 DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
Can you just try replace patch with next? C706010000008BDF<=>C706000000008BDF The diference is first patch from CSessionArbitrationHelperMgr, but old instructions share another function CSessionArbitrationHelper
Thats why in my RDPWrap.ini on github i use the second value for newer builds Now changed for 19041.84 I'm not shure in wich place better... I hope a second. Can anyone try it??? - Multi-session: WORKS SingleUserOffset.x64 =0C012 SingleUserCode.x64 =Zero 00 Search: C706010000008BDF Write : ----00---------- File offset: B412h Write: 00 OR HERE - Multi-session: WORKS SingleUserOffset.x64 =0BFE2 SingleUserCode.x64 =Zero 00 Search: C70201000000393D Write : ----00---------- File offset: B3E2h Write: 00
Patch for termsrv.dll [10.0.19041.84] - Windows Professional (x64) - version 2004 (OS build 19041.264) 007444833D46BA <=> 00EB44833D46BA EC2033DBC7400801 <=> EC2033DBC7400800 39813C0600000F84D9510100 <=> B80001000089813806000090