Crack Activar Licencias De Terminal Server 2003
Como instalar terminal server en server 2003 Aqui teneis el codigo que hay que poner en el archivo de texto. Net stop 'Directorio de sesiones de Terminal Server'. Terminal Server 2003 crack. Para activar mas sesiones de terminal server en windows 2003 server. Especificare un servidor de licencias dentro de 120 dias. Como obtener licencias CAL de Terminal Server gratis. Es muy importante que sigan los pasos tal y como se muestra en el tutorial. Debes instalar el servicio/componente de terminal server en agregar o quitar programas / agregar componentes de Windows.
About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like- ' href='https://www.remkoweijnen.nl/blog/'>Home
Como Activar Licencias De Eset Nod32
31AugAs you might know Windows 2003 Server accepts at most 2 concurrent Terminal Server sessions (and 1 console session) in Remote Administration mode (which is the default). Of course if you switch to Application Mode you can have an unlimited number of sessions but this requires licenses and a license server.
When Terminal Server creates a new session it checks if the new session is either a console session or a help assistant session and if not it allocates a license. The function that performs this check is called CRAPolicy::Logon
So if we want to bypass this license allocation we simple change it to:
Obd auto doctor pro. The license key will be emailed to you as soon as your order completes. You can use new versions of the software released within 1 year after the purchase. After the first year, you may purchase updates for a reduced price if you wish.!!! This is usually within seconds or few minutes. A license key will last indefinitely (forever) and allows you to diagnose any number of vehicles.
the binary diff is:
0002A894: 8B 31
0002A895: FF C0
0002A896: 55 C2
0002A897: 8B 04
0002A898: EC 00
If you are going to replace termsrv.dll please note that it’s protected by Windows File Protection so you need to replace it in the following order:
- Replace termsrv.dll in c:windowssystem32dllcache
- If you have the installation cd/dvd (i386) folder copied to your harddrive replace (use the compress command) or remove it there as well
- Now rename the original file in your system32 folder and place the patched version
- Reboot
VPatch file: Windows Server 2003 VPatch file (49437 downloads) (of termsrv.dll build 5.2.3790.3959 English language)
Share this:
Like this:
LikeLoading..Related
Please consider donating something (even a small amount is ok) to support this site and my work:Filed under: Terminal ServerRSS feed for comments on this postTrackBack URI
So great to see your win2003 terminal server patch. Does it work on win2003 R2 SP2 as well? Thanks again.
@ghost2k: There aren’t any functional differences between 2003 and 2003 R2 as far as Terminal Services is concerned. What build number of termsrv.dll does your r2 have?
You are right. R2 is the same build no. Tested with positive result. Btw, will you work on windows 2008 as well? Thanks again.
This is the greatest patch in a long time – Thank you!
I need it just for 1 person – Sometimes I log in on multiple machines and don’t want to constantly have to log out to keep my balance at 2 or less.
The only thing missing is a Server 2008 patch, but I know not everyone has upgraded yet (including us).
@2008 patch: I have begun looking at this, unfortunately the structure of 2008 Terminal Server is really different so I need to find where the check is done.
I’ve tried to patch the termsrv.dll with your patchdata.pat using vpatchprompt.exe, and the new termsrv.dll dated at march 2008, (old termsrv is feb 07). Copied to dllcache, rebooted and checked that the patched file with new date still intact in system32 folder. i still restricted to 2 connection. may i have your pacthed termsrv.dll? thx.
it worked, apparently when copying the patched file, we must login on safe mode. thank you very much.
Excuse my ignorance, but how do i patch the file with vPatch?
Thanks
Hi Same question,
In order to use the patch file, I have to rename from “PatchData.pat” to “termsrv.dll” ?
or I have to do somthing else?
Do yo think it works in spanish version
Hi same question…
How do I use the .pat file?
thanks in advance…
How to use the pat file:
1) install v-patch
2) from the vpatch directory launch vpatchprompt.exe
3) vpatchprompt will ask you for the following files:
– Patch file (the .pat file).
– Source file (termsrv.dll).
– Destination file (the patched termsrv.dll).
4) now replace termsrv.dll as instructed in the post & reboot
hey loyz could you send me the new dll…
my email is… edgar.pajuelo@gmail.com
tks…
Hey Remko… i got the message “No suitable patches were found” I follow all the instructions carefuly…
PLEASE could you send me the patched .dll…
i would appreciate it.
edgar.pajuelo@gmail.com
Thanks in advance.
Edgar
Edgar, I just retested and it works nicely for me. Are you using another build of termsrv.dll of perhaps another language (then English)?
Remko, the version is 5.2.3790.3959 and the language is Spanish std edt. 2003 R2.
I tried with english and work fine!!!
Can I repleace my new patched english version intead of my original spanich version to work it out?… or just install the server in english.
I’ve used this patch succesfully on a Server2003 x86. It’s working great! Thank you for that!
I also planned to use this patch on a server 2003 x64, but it won’t work out on x64? Keeps saying “No suitable patches were found”
Version of termsrv.dll: 5.2.3790.3959
Windows Server 2003 R2 SP2 x64
Does anyone have a link to “termsrv.dll” build 5.2.3790.3959
i am running 5.2.3790.0 and the patch is not working.
Thanks
Hi, tried to follow the directions to install this patch. I’m a little lost and it did not work on my 2003 server. Please verify if I followed your directions correctly:
How to use the pat file:
1) install v-patch VPatch.exe and the
[I download both the VPatch.exe and vpatch32.zip file from your Vpatch link at the top, and the PatchData.pat file]. I executed the VPatch.exe
2) from the vpatch directory launch vpatchprompt.exe
[From the Vpatch folder created by the vpatch32.zip, I executed vpatchprompt.exe]
3) vpatchprompt will ask you for the following files:
– Patch file (the .pat file).
[I pointed it to the PatchData.pat file]
– Source file (termsrv.dll).
[I pointed it to this file which I found in c:windowssystem32]
– Destination file (the patched termsrv.dll).
[I entered termsrv.dll and saved it on my desktop.
4) now replace termsrv.dll as instructed in the post & reboot
[I renamed the original termsrv.dll in the system32 folder to oldtermsrv.dll, then I copied over the termsrv.dll file from my desktop into the system32 folder.
It doesnt work. Im sure Im missing something here. I couldnt really couldn’t understand these directions:
Replace termsrv.dll in c:windowssystem32dllcache
If you have the installation cd/dvd (i386) folder copied to your harddrive replace (use the compress command) or remove it there as well
Now rename the original file in your system32 folder and place the patched version
Reboot
Please provide a bit more detail to the procedure. Im sure Im pretty close and I really need to have this patch installed.
Thanks,
Octavious
Never mind… I guess I just needed to read the entire thread and found that all I had to do was login in SAFE MODE and replace the file. IT NOW WORKS!
Thanks so much!
Octavious
[…] https://www.remkoweijnen.nl/blog/2008/08/31/patch-windows-2003-terminal-server-to-allow-more-than-2-concurre.. […]
A patch for server 2008 can be found here: https://www.remkoweijnen.nl/blog/2008/10/21/patch-windows-2008-terminal-server-to-allow-more-than-2-concurrent-sessions/
Remko,
I love this patch and have tried it and it works great!
I was wondering if you could help me with a problem I’m having with terminal services. I have a windows Xp pro client trying to connect to a windows 2000 terminal server. i get the following error…
The remote computer disconnected the session because of an error inthe licensing protocol. Please try connecting to the remote computer again or contact you server administrator.
I have tried the following…
1) deleted HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing. (http://support.microsoft.com/kb/187614/en-us).
2)http://support.microsoft.com/kb/921045/en-us
3)http://support.microsoft.com/kb/315277/en-us
My license server is windows 2003 and the terminal servers are windows 2000.
on my windows xp pro i was missing the license000 HHKLMSoftwareMicrosoftMslicensingStorelicense000
I added the key and it still did not work.
here are the event logs from the windows 2000 terminal server…
Event Type: Information
Event Source: TermService
Event Category: None
Event ID: 1003
Date: 10/27/2008
Time: 3:05:11 PM
User: N/A
Computer: PINKTSERVER1
Description:
The terminal service client ‘NETADMIN’ has provided an invalid license.
Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1004
Date: 10/27/2008
Time: 3:05:10 PM
User: N/A
Computer: PINKTSERVER1
Description:
The terminal server cannot issue a client license.
I would be grateful for any help you can give.
Thanks
You can also use Replacer to bypass Windows File Protection:
http://www3.telus.net/_/replacer/
Simply drag and drop the old file with the new file. I had to use this because restarting in safe mode was not an option for me due to the server being remotely hosted (which also hosted a remote KVM).
Terminal serves on windows 2003 server is kind of a pain in the butt, because it looks more complicated then it actually is. I got it working by just installing the services in the add windows components. Then selected the terminal services under administrative tools. Then activated the server, then installed CALS. Basically it was a hunt and peck affair. Dont give up. Tampa Computer Repair
Please. Anybody help me with the patch for the Spanish version????
Thanks so much! I installed this onto SBS 2003 (with SP2) and it worked a treat. (as I was rather annoyed the way they changed the remote desktop model between SBS 2000 and 2003 and removed application server mode…)
I had a couple of issues initially as there were some other termsrv.dll files floating around so I created a small batch file for future use (run it from the same folder as your patched termsrv.dll)
copy termsrv.dll %systemroot%ServicePackFilesi386 /y
copy termsrv.dll %systemroot%system32dllcache /y
ren %systemroot%system32termsrv.dll termsrv.dll.orig
copy termsrv.dll %systemroot%system32 /y
Hey Remko…
i still got the message “No suitable patches were found” I follow all the instructions carefuly and did it on safe mode
the version original termsrv.dll 5.2.3790.1830
PLEASE could you send me the patched .dll…
hwisnu@gmail.com
Thx.
Wisnu
@wisnu: you have the wrong version of the dll, you need to update with latest 2003 service pack.
If you do want to patch this version you can try this:
Open in in a hex editor and look for these hex byte sequence:
8bff558bec568b7508578bf98bcee831feffff
and replace with this:
31c0c2040068b7508578bf98bcee831feffff
I tried to edit and replace the hex byte, but i got this message “Hex String Invalid”
Is there missing number on replacement hex byte ?
Thx,
WSN
hello Remko
I’m trying with no avail to get this patch working. i keep getting the “No suitable patches were found” when i run the patch. Do i have the wrong version of the patch file?
Any help would be hugely appreciated. Thank you.
@shannon: same as the other guys with problems: you are trying to patch a dll of another version/build or language. VPatch checks the MD5 hash of the file and refuses to patch if it’s not the same.
You should either update or see if you can replace the hex bytes with hex editor (see comments above and diff in post)
Remko,
I followed your instructions , Installed Service Pack 2 on my Server 2003 and patched the DLL.
Current termsrv.dll version 5.2.3790.3959
It’s Works.
Thx so much,
WSN
thank so much,
Thanks ever so much. It appears to be working perfectly. Great work Remko!
Remko,
First of all, I’d like to appreciate what you have already done with Terminal Services!
Now I’m looking forward for windows x64 patch or dll. And if you don’t have enough time to make it, would you be pleased to explain how to modify the dll?
I tried to find similar subroutine in disassembled x64 dll, but I failed. I used IDA program to do the task. It was my first attempt to do smth. about disassembling.
Instead of rebooting, can you just stop the “Terminal Services” service before updating the file and then restart the service afterwards — like with the patch for Server 2008?
hi friend
i try patch my file and dosn´t work, everytime say “No suitable patches were found”
please how to patch the file correctly o somebody have a patched termsrv.dll?
please write me o send me a file or help
hernan@hrd.com.ar
thanks
@Hernan: No suitable patches were found simply means you are trying to patch another build or language than mine. Try to replace the hex bytes with a hex editor.
@Rick: You really need to reboot on 2003!
@Pol@r1s: I have already done the X64 patch and it’s working. It will be published soon.
Remko. Hello, yes it’s true, my windows 2003 is in spanish… Can i use the dll file for a windows in english?
thanks people !!!
@Renko, yes, though I think that’s only because the TS service is one of the few marked as “NOT_STOPPABLE.”
It is killable, however, since it is in its own svchost.exe.
You can find its PID with this:
tasklist /m term*
You can kill it (stop the service) with this:
taskkill /pid xxxx /f
(Where you substitute the PID number for xxxx)
Then upon starting the service back up, I would think it would read the patched version of the DLL.
Thanks for figuring out the patch, btw, since this is the only place I could find how to do it.
Did you have to use a debugger to find it (which I assume is what the code above is from)?
Please, somebody help me, realy need this dll patched. If your termsrv.dll patches is working, send me it for mail.
hernan@hrd.com.ar
Thanks for ever !
Dear Remko! You wrote on November 29th to Pol@r1s
“I have already done the X64 patch and it’s working. It will be published soon.”
Could you please put it to download section. I think it will make your site super popular! Because it is really helpful stuff for Windows XP x64 users who wanted concurrent sessions in it. And many people are waiting for it since Windows XP x64 was released. Thank you in advance dear friend!
Dear Remko!
I’m so glad that you have done the patch for x64 versions! I can’t wait for downloading it! 🙂
Thanks a lot for your works!
Dear Remko! We’re all hoping that you will place it to your download section! Thank you in advance!
Windows 2003 X64 patch is online here: https://www.remkoweijnen.nl/blog/2008/12/09/windows-2003-x64-terminal-server-patch/
btw: there is a Paypal Donate button in the top right corner if anyone wishes to donate something…
I’ve SBS 2003.
With the original termsrv.dll, the first two clients connected successfully, the third connected but when hit enter after have typed username and password, the max connection error appeared.
I’ve applied the patch: now two connections are working well like before, but the third client has a connection refused.
Do you have any ideas?
[…] while ago I published a patch for Windows 2003 Terminal Server that allows more than 2 concurrent sessions in Remote Administration […]
@Logan: please check this registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server, value UserSessionLimit. What is it’s value?
Also check if you have a MaxInstanceCount value.
Dear Remko,
I just wanted to confirm that there are really many people who are awating for Windows XP SP2 x64 patch, and that I am amongst them. Thanks a lot for what you are doing, and look forward to seeing (and getting!) your work done regarding XP x64 as soon as possible.
How can this be done under Windows 2000 Server?
Thanx for the hard work.
I’ve read all the comments and can’t wait get it going, however
– my termsrv.dll is old 5.2.3790.0 and I couldn’t find the mentioned hex-string in my dll (allthough there was some partial occurrence)
? is there another way for me to patch (a hex string for my version), without an update, or can I just replace mine with a newer version without updating the whole system – will that work ?
(maybe this might help – I found an occurance of 08578bf98bcee8 at 21fb9, part of the code starting at 21f90 is: B813000AC05EC20400568BF1C7061853
1375E82AFAFFFFF644240801740756E8
96ECFFFF598BC65EC20400568B742408
578BF98BCEE86BFEFFFF84C075176A00
FF36E840E8FFFF85C0750A568BCFE87F)
Thanx in advance!
@salalex: I don’t think you can just replace termsrv.dll with a newer version. There are other (dependant) files like winsta.dll and so. I would advise to update to service pack 2. Regarding this specific build I well sent you a personal msg.
Remko,
thank you VERY MUCH for the 5.2.3790.0 patch !!!
@Remko & salalex
How u patched this ver 5.2.3790.0 please?
Regards
Please send me patch for this this ver 5.2.3790.0
to my mail
mostafa_mandrake@yahoo.com
Regards
Thaxxxx,
I installed SP2 and apply patch then
Successfully
Thaxx
Regards
Does this patch also works for Remote Desktop or it’s only suitable for the Terminal Services role?
Cathing up on some old comments (been busy):
The patch for 5.2.3790.0 is on request, I might publish it but I think one should upgrade to sp2 anyway 😉
@trendy: The patch is for Remote Administration mode (the default) and not for Application Mode/Terminal Services role
Please Do No Forget to Assign Password to Administrator User.
I spent alot of time to test but finally just found out that I was using Blank Password for Administrator. As it was saying “Unable to connect due to user restrictions…”
I hope it will be useful advice for experts.
Please, can anybody send the patched termsrv.dll for Windows Server 2003 to my e-mail address: flopezf@jccm.es?
Thanks a lot.
Dear Remko,
I have windows 2003 server sp2 & version of termsrv is 5.2.3790.2825 after updating its still the same version of termsrv so above patch not suitable for this version I hope if you had a plenty of time to help me…many thanks