Below is the step by step for how to crack remote desktop license Server 2008 R2
1. Download and save to your Desktop PsExec.exe
2. Click Windows Key then type CMD
3. Right click on Command Prompt click Run As Administrators
4. Type “%userprofile%desktoppsexec” -i -d -s c:windowsregedit.exe
5. Enter
6. After Enter the Regedit window will popup
Microsoft Windows Server computers feature a remote desktop service called Terminal Services that enables remote client computers to access and run applications on the server as. Hi, I have a server running Foundation 2012 R2 and i'm setting up Remote Desktop Services. According to the licensing datasheets and various other things i've read.
7. Delete any value in this location -> HKEY_LOCAL_MACHINESYSTEMCurrentControlSetContro lTerminal ServerRCMGracePeriod
8. Restart
9. Done!!!! injoy 🙂
Related Posts
This question already has an answer here:
- Can you help me with my software licensing issue? 5 answers
I want to use a Windows Server 2016 instance as a Hyper-V host. This server should provide several Windows 10 VMs to users which connect via RDP onto the machines.Is this only possible with a RDS role configured on the server? And do I need a CAL for each connecting user (or respectively device) to be correctly licensed?Thank your for your answer.
marked as duplicate by yagmoth555♦, kubanczyk, womble♦Jul 9 '18 at 0:17
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
1 Answer
With Server 2016 as Hyper-V host you have additional right to license 2 VMs per license running Server 2016 if you have Standard and unlimited VMs per license if you are running Datacenter edition. If you put Windows 10 in VM you must license it separately. Other thing is, Windows 10 is client OS meaning it can't be part of RDS farm. From what we have from information here, ii suggest you to use Windows Server 2016 as Hyper-V host, create needed VMs with Server 2016 image eliminating Windows 10 licensing, deploy farm and add CAL licenses depending on number of users/devices you have. Regarding licensing, you must license either each user or device you access RDS farm from.
BTW, you can make something like workaround scenario where you have VM running RDS roles except session host and edit policy to allow connection to your Windows 10 machine through RDP gateway, but again, in that case your Windows 10 machines are still not part of farm, so management and licensing for those machines are separated.