windows terminal server 2019, windows terminal server, windows terminal server 2016, windows terminal server license, windows terminal server license cost, windows terminal server install mode, windows terminal server vs remote desktop, windows terminal server port, windows terminal server alternative, windows terminal server setup
Angela Cuevas on windows 2012 r2 terminal server license crack
Jan 4, 2020 — When you home lab and you don't have Microsoft license for RDS, you ... Normally you would need to activate the RDS/TS CAL License server and ... to deploy Terminal Server [Remote Desktop Session Host in 2012] for ...
Angela Cuevas on windows 2012 r2 terminal server license crack
Jun 8, 2005 — Make sure you've installed "Terminal Services Licensing". By the way, this ... This trick is not working on windows server 2008 R2. ReplyDelete.. Jan 23, 2020 — When attempting to remote into a Windows Server 2012 R2 server there is an error “Remote session was disconnected because there are no ...
Angela Cuevas on windows 2012 r2 terminal server license crack
Sep 17, 2019 — Activate Licensing Server: Now the RD Licensing role is installed we need to activate it with Microsoft. Windows Server 2012 R2 Remote Desktop .... Windows Server 2008/R2 Terminal Server Licensing - Page 24. Remote Desktop. Home » Documentation » Activating your support license file. delivery of Update .... Oct 7, 2020 — RD Licensing Manager, select the server name is not .... Below is the step by step for how to crack remote desktop license Server 2008 R2. 1.
Angela Cuevas on windows 2012 r2 terminal server license crack
7349985fb1 52 Jan 21, 2020 — Activating a Remote Desktop Services license server and installing the appropriate client access licenses in Windows Server 2008 R2 and 2012.. This video is about how to remove concurrent sessions on Windows Server 2008 R2. This method is also .... universal termsrv.dll patch windows 10 concurrent rdp .... “The Remote Desktop Session Host server is in Per User licensing mode and ... Product version: Windows Server 2008 or Windows Server 2008 R2 ... which is essentially a crack to allow the server to have unlimited licensing.
When you home lab and you don't have Microsoft license for RDS, you have two options. Reinstall the server [redeploy the VM] or cheat a bit. Yes, in fact, there is cool hack which allows you to reset the 120 day grace period on Windows Server 2012 R2 RDS, and we'll show you how. I like doing posts which shows some cool hacks, and this is exactly this kind of post – How To Reset 120 Day RDS Grace Period on 2012 R2 Server.
Normally you would need to activate the RDS/TS CAL License server and point the Server to License server with User/Device License and will resolve the problem. However, we don't want to do that because we have no license from Microsoft, in our lab. [and many other IT pros who test stuff in the lab too].
What we will do is simply reset the default timer which is 120 days grace time, when you first add the RDS role. In fact, you do not need to reboot the server either. Simply log out and back in and the message changes from let's say 54 days left to 120 days left. And that's it.
Note: This tip works also on Windows Server 2016
For every admin who runs homelab or has a cloud lab, this is a must known hack.
Obviously, you won't do this in a production environment, because your production environment is covered with a proper license. Right? Ok, this is clearly for labs, tests, cloud tests etc…
How To Reset 120 Day Grace Period on 2012 R2 Server RDS – The Steps
Step 1: Connect to your RDS Server as an admin and open regedit.
Navigate to the following key:
The solution is to delete the REG_BINARY in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
It's called a “TimeBomb” … -:]
Note: You must first take an ownership and give admins the full rights.
Like this:
*********************************************************************
DC Scope for VMware vSphere – optimization, capacity planning, and cost management. Download FREE Trial Here.
- Tracks the performance of VMs with a summary view of the resources and metrics in degradation.
- Easily improve the performance of your infrastructure.
- DC Scope is affordably priced per VM.
*********************************************************************
Go to menu Edit > Permissions
Once you delete the Registry key you must reboot the host. Some users have reported that when not rebooting the host you will see the message changing, but no connections are possible.
Update: Well, in fact, you can just restart the Service “Remote Desktop Services” which will momentarily disconnect all the active sessions and then after a minute or so you can reconnect to the sessions.
You should see the message changing at the taskbar area….
Note that you have also a possibility to check how many days its left… Go to the command prompt and enter this command [not tested].
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE [__CLASS !=””] CALL GetGracePeriodDays
Apparently, you can delete this key every time it expires ….. indefinitely. Wow. That's good to know too.
This is it my friends. Today's tip for home labs.
Second Tip:
Update: The Microsoft's script was taken down. I have been contacted by someone [look at the comments section] who has published an alternative. Get it here.
Download a PowerShell script from Microsoft allowing you to reset the RDS grace period.
Quote from Microsoft Technet:
The PowerShell script can be used to query and reset terminal server grace period to default 120 days if it is nearing to the end. We often need to deploy Terminal Server [Remote Desktop Session Host in 2012] for testing purposes in development environments allowing more than 2 concurrent Remote Desktop Sessions on it. When it is installed, by default if no RDS or TS Licensing server is specified via either GPO or Registry, it is in default Grace period which is 120 days and it works fine until then.
Once Grace period expires, the server does not allow even a single Remote Desktop session via RDP and all we are left with is to logon to the Console of machine using Physical/Virtual console depending on Physical or Virtual machines or try to get in using mstsc /admin or mstsc /console, then remove the role completely and restart the terminal server [RDS Server] and post that it starts accepting default two RDP sessions.
In the comment section, there was a user who affirmed that he verified it on Windows Server 2016 as well and it works just fine. With that, stay tuned for more.
More from ESX Virtualization:
Subscribe to RSS, and social media channels [Twitter, FB, YouTube]
The licensing mode for the Remote Desktop Session Host server is not configured. The Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server. Configuring Windows Server 2012 Remote Desktop Services Licensing involves 2 step process. Activating a Remote Desktop Services license server and installing the appropriate client access licenses in Windows Server 2008 R2 and 2012.
Tuscani wrote: So how does all this come into play for an MSP with SPLA licensing. Do we just use a SPLA key for Windows 8 VMs that are connected to via the RDS gateway?
The Windows VDA license [or through Windows Client SA] is the license required to access a Windows desktop OS VM from a server. The Windows VDA/SA license is not available under SPLA [as to provide a Windows desktop OS VM from a sever as a service]. However, you can provide a Windows Server VM as a server to a customer through RDS. More info on the. Tuscani wrote: Gotcha.
Any idea what the VDA license costs compared to say a retail copy of Windows 7 or 8? I like the idea of just handing users a server based VM, but we know that many apps will not run on server based OSs. The Windows VDA license is about $100/device/yr. You can find an OEM version of Windows 8 Pro for $150. However, the OEM/FPP license is not to be used as a VM license for a server.
Technically you can 'assign' it to a server, it would be for local use only and any client devices that accesses the VM would require the Windows VDA license. Tuscani wrote: Unless I missed somehting, why not just buy a one time retail copy of Windows 8 for each VDI VM? Lol because, it is not allowed. Only the primary user of the licensed device may remotely access his/her device.
With server hardware, there is no primary user, therefore is considered a shared device. If you were to assign a retail copy of Windows desktop OS [XP, Vista, W7, W8, etc] to a server - the retail copy of Windows could only be used on the device. The retail license does not permit remote access from any user other than the licensed user. The Windows VDA would be the license required.
The Windows desktop OS EULA states this:. Remote Access Technologies You may access and use the software installed on the licensed computer remotely from another device using remote access technologies as follows. Remote Desktop. The single primary user of the licensed computer may access a session from any other device using Remote Desktop or similar technologies.
A “session” means the experience of interacting with the software, directly or indirectly, through any combination of input, output and display peripherals. Other users may access a session from any device using these technologies, if the remote device is separately licensed to run the software. You dont have to have RDS licenses if you used windows 8.1 VMs on the Server 2012 R2 Datacenter edition and connected with those VM's using those VM's built in Remote Desktop service and not through the server's services. You can change the listening RDP ports to 3391, 3392, 3393, 3394 etc for the VMs and call them directly from your devices with RDP client [windows or Mac]. Just dont use any Remote deskto services of the server Incuding Remote FX.
Windows 8.1 Pro should already have a CAL to be connected to, and to connect to the server [a device CXAL that is]. Am i Off anywhere?? After all we need a phd degree in windows licensing to use microsoft stuff:[. Tleavit wrote: I hate to drag this back up but the one question I have is still not answered. If I have 5 Windows 7 VM's on a Server [that is backed by Server 2012 R2 Datacenter which does not matter], then how do you license.those. virtual machines?
I understand the access rights licenses for example say my user has a win 8.1 upgrade with SA assigned to them.If the user connecting has SA assigned to their DEVICE [There is no SA assigned to a user] then they can connect to them. There is NO user CAL [this is the reason Brian Madden left the Microsoft MVP program in anger.]. John773 wrote: tleavit wrote: I hate to drag this back up but the one question I have is still not answered. If I have 5 Windows 7 VM's on a Server [that is backed by Server 2012 R2 Datacenter which does not matter], then how do you license.those. virtual machines?
I understand the access rights licenses for example say my user has a win 8.1 upgrade with SA assigned to them.If the user connecting has SA assigned to their DEVICE [There is no SA assigned to a user] then they can connect to them. There is NO user CAL [this is the reason Brian Madden left the Microsoft MVP program in anger.] While not a user CAL, but a VDA license kinda acts the same - allows a user to connect from an unlimited number of devices to the VM that the VDA is assigned to - right? Dashrender wrote: John773 wrote: tleavit wrote: I hate to drag this back up but the one question I have is still not answered. If I have 5 Windows 7 VM's on a Server [that is backed by Server 2012 R2 Datacenter which does not matter], then how do you license.those. virtual machines?
I understand the access rights licenses for example say my user has a win 8.1 upgrade with SA assigned to them.If the user connecting has SA assigned to their DEVICE [There is no SA assigned to a user] then they can connect to them. There is NO user CAL [this is the reason Brian Madden left the Microsoft MVP program in anger.] While not a user CAL, but a VDA license kinda acts the same - allows a user to connect from an unlimited number of devices to the VM that the VDA is assigned to - right?
VDA isn't really flexible like User or Device CALs. With those if you have users with multiple devices you can choose to to the User CAL rate and it make compliance easy, as well as much cheaper [1 CAL for EVERYTHING a user connects from]. Its a one year license that is attached to a device. So lets say I connect to VDI from a company issued Macbook Pro, A thin Client, a work issued iPad, and my Windows Desktop. In order to license this properly we would need 4 VDA [or alternatively 3 VDA licenses and 1 software assurance for my desktop]. Now to make it REALLY FUN, since the iPad is mine personally, BUT it touches the office, I would need to get a CDL License to attach to my SA on my work desktop. Now as long as my Macbook Air that I personally own stays in the parking lot and never connects from the office it can be used under home use because I have SA on my desktop, however if It was my only device then it would need a VDA [can't put SA on a personal device].
2012 R2 Remote Desktop Licensing
Which now that I think about it, I don't think you can get a CDL license without SA, so I think in that case my personal iPad would just be illegal under any situation that it touched the company network. Does everyone now see why 1. Brian Madden quit the Microsoft MVP program. Why VDI compliance is really something that 99% of shops have committed some violation on accident [unless they completely ban non-company devices from connecting in]. Why there is ZERO software [Microsoft included] in the VDI space that can track this.
I've cleaned up a LOT of bad VDI licensing situations [Customer's trying to use OEM, customers, not buying SA] but there comes a point where even I give up, and just explain this stuff and then walk away. The one thing I can say is I've never actually seen what happens when Microsoft/BSA tries to audit someone. I suspect if they have VDA for the work devices, or SA for at least one device for every person they just walk away rather than attempt from logs to reconstruct where someone's iPad was physically located when they connected. Again, I'm not advocating people deploy or do anything out of compliance, just pointing out that this mess is so bad [and adding CDL to the fire didn't help] that Microsoft has invented something more complicated than IBM Mainframe licensing. Honestly I wish they would just Sell a 'user CAL' for 300 a year [hell it could be a 1000, just something] and maybe a USER Office CAL for another 400 and we just move on. Great thread here and I need to ask a very specific question in relation to RDS CAL requirement with a VDI solution. Customer is using a Server 2012 R2 w/Hyper-V role and web services role installed.
RDS Role is not installed and none of the RDS Services are running - no connection broker or RDS gateway, etc. Server has 10 Windows 7 Pro VM's running on the server and they use thin-client via RDP connection straight to the VM desktop and it works great. So no 3rd party services and not using any of the RDS services on the main server.
In this scenario is an RDS CAL required? They are currently buying qty-10 VDI subscriptions and qty-10 RDS CAL's but they are not using the RDS CAL's and have been told there is no reason to buy them. Can someone confirm are the RDS CAL's required? Chris [Microsoft] wrote: Dashrender wrote: Chris, Let's assume I only want to deploy Windows 7/8 desktops from Hyper-V, do I need RDS licenses as well as VDA [or SA] licensing? How are you delivering the desktops VMs from the server to the clients?
If you are using to deliver the OS to the client - yes you need a RDS CAL on top of the Windows VDA license. However, if you are using VMware View or XenDesktop - both of those solutions do not require RDS CALs but would require Windows VDA licenses.Basically if your using Microsoft as a Session broker you have to pay for an RDS CAL [or license View, or Citrix]. Didn't there used to be a different license for this [something you added to SA?] Lota different versions of this over the years. Kenmarlin wrote: Great thread here and I need to ask a very specific question in relation to RDS CAL requirement with a VDI solution. Customer is using a Server 2012 R2 w/Hyper-V role and web services role installed.
RDS Role is not installed and none of the RDS Services are running - no connection broker or RDS gateway, etc. Server has 10 Windows 7 Pro VM's running on the server and they use thin-client via RDP connection straight to the VM desktop and it works great. So no 3rd party services and not using any of the RDS services on the main server. In this scenario is an RDS CAL required? They are currently buying qty-10 VDI subscriptions and qty-10 RDS CAL's but they are not using the RDS CAL's and have been told there is no reason to buy them.
Can someone confirm are the RDS CAL's required?In this case I don't see why you would need RDS, that said I'd strongly recommend using a Session Broker of some kind as manually doing VDI this way is just painful to manage/deploy etc. It seems silly to me.
Whats the point of VDI if all it is is just a regular, non-linked clone desktop sitting on a server somewhere? I can buy desktops that are more powerful for $200 off lease, and grab a copy of ghost to image.
Kenmarlin wrote: Great thread here and I need to ask a very specific question in relation to RDS CAL requirement with a VDI solution. Customer is using a Server 2012 R2 w/Hyper-V role and web services role installed. RDS Role is not installed and none of the RDS Services are running - no connection broker or RDS gateway, etc. Server has 10 Windows 7 Pro VM's running on the server and they use thin-client via RDP connection straight to the VM desktop and it works great. So no 3rd party services and not using any of the RDS services on the main server. In this scenario is an RDS CAL required?
They are currently buying qty-10 VDI subscriptions and qty-10 RDS CAL's but they are not using the RDS CAL's and have been told there is no reason to buy them. Can someone confirm are the RDS CAL's required?I'm going to take a crack at this one. RDS CAL's and VDA CALs are required for each VM in use and the use of OEM licenses on a shared server is a violation of the EULA because a session on a server is not a single primary user remoting in to a licensed device. It is an instance of a virtual device and the remote computer [the client terminal] would have to be licensed with a VDA and the connection with an RDS CAL [because the single port RDS in the OEM licensed W7 wasn't intended to be used in that manner]. Thank you Pete for taking the time to answer. Question where did you get that an OEM license is in use?
I didn't say anything about using any OEM licenses. They are using VDA subscriptions for the Windows 7 Pro - ohhh you took Pro as being OEM vs Win 7 Enterprise - that's it isn't it? Sorry should have said Win 7 Enterprise VM's. Makes sense now. I'm in agreement with all the feedback so far - aka they need a VDA subscription and an RDS CAL however - I can't find anywhere in any licensing guide or website or document from Microsoft that says they need an RDS CAL even when not using RDS Services Role. I've also explained to them that this model is not common and not the suggested path so they ask for a document that compares this method to a full RDS pooled method of which I can't find anything either so anyone with any details on comparing this single non RDS Services method against an RDS pooled method would be helpful.
Windows Server 2012 R2 Enable Remote Desktop
Thanks again everyone! Kenmarlin wrote: Yes VMware View is a great product and acts as a connection broker. My company is a VMware distributor but we also support Citrix and the full Microsoft solution. Again my question is more about not using a 3rd party connection broker.Unless the licensing changed, I thought that Windows 7 [and presumably windows 8] included RDS rights when connecting to a server.
It was licensed when connecting to Terminal Services, which is/was a RDS license, I'm not sure if it applies here or not. Now, if you are connecting from an iPad, from a home computer, etc.
Then you definitely need a RDS license. Dashrender wrote: kenmarlin wrote: Yes VMware View is a great product and acts as a connection broker.
My company is a VMware distributor but we also support Citrix and the full Microsoft solution. Again my question is more about not using a 3rd party connection broker.Unless the licensing changed, I thought that Windows 7 [and presumably windows 8] included RDS rights when connecting to a server. It was licensed when connecting to Terminal Services, which is/was a RDS license, I'm not sure if it applies here or not. Now, if you are connecting from an iPad, from a home computer, etc. Then you definitely need a RDS license.
Windows 7 [or any Windows desktop OS] does not include a Windows Server - Remote Desktop Services CAL. RDS CALs are an add-on to Windows Server. Chris [Microsoft] wrote: Dashrender wrote: kenmarlin wrote: Yes VMware View is a great product and acts as a connection broker. My company is a VMware distributor but we also support Citrix and the full Microsoft solution.
Again my question is more about not using a 3rd party connection broker.Unless the licensing changed, I thought that Windows 7 [and presumably windows 8] included RDS rights when connecting to a server. It was licensed when connecting to Terminal Services, which is/was a RDS license, I'm not sure if it applies here or not. Now, if you are connecting from an iPad, from a home computer, etc. Then you definitely need a RDS license.
Windows 7 [or any Windows desktop OS] does not include a Windows Server - Remote Desktop Services CAL. RDS CALs are an add-on to Windows Server.
Was it XP that included it then?