Can someone make a patch for Server 2019, 17763.771 ? original file is here -> h ttps://mega.nz/file/zNFWjYbY#4L4PKKPReO8nnFwzKgVDtfLGerZ_bsNoW8SQmIAX9Fg -----------------NOT WORKING multisession---------------------- C706010000008BDF ==>C706000000008BDF 007418488D15D6DF ==>00EB18488D15D6DF 4883EC2033DBC740080100 ==>4883EC2033DBC740080000 39813C0600000F84CB2B0100 ==>B80001000089813806000090 with this settings working only multiuser...
with RDS Host settings works great... thx @sebus Тhank you both, will try later only with @wyxchari offered offsets
What are the pros and cons of using a straight hack of termsrv.dll vs the rdpwrap approach? From what I have gathered so far it seems that RDPwrapper has some advantages that straight patching does not, but does lack some printing functionality. I was curious about some remarks that were made about server: why would one want to use a k'd termsrv.dll on Windows Server 2019 with RDS and CALs from eBay at an affordable price? Are there reasons and what are they if so? Also why do we have 2 forks? https: github.com asmtron rdpwrap (last commit 11 days ago and from 2014 edtrejo) https: github.com sebaxakerhtc rdpwrap (last commit dec 2018 and from stascorp)
It's open source and it's GitHub, If you have a GitHub account you can fork it too with the click of one button
I'm not asking what this is, I'm asking why are there two forks from what appears to be the same member of the forum but with two different GitHub accounts. I have no problem with this being done, I simply am trying to understand why it's being done since I've seen both being referred to...... Is there a reason? What's the reason? What do we need to be aware of so we use the right version? And so forth.
stascorp is the original, some people fork it just to have a backup. Just recently the stascorp rdpwarp github got locked but reopen as of now.