You say you have a 2012 RDS server. What RDS roles do you have setup? RDS in 2012 is not for the faint of heart, it's not straight forward and the documentation is lacking severely.

• Remote Desktop License Expired

Jun 09, 2014  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). The Remote Desktop Session Host Configuration Tool has been removed in Windows Server 2012 R2. So you will have to specify licensing mode and licensing server through other means. Activating a 2008 R2 Remote Desktop License Server. Deploy and configure a Windows Server 2012 R2 RD License Server; Configuring certificates in 2012/R2 Remote Desktop Services (RDS) Creating RDS Session Collections in Windows Server 2012/R2; Installing Remote Desktop Services (RDS) in Windows Server 2012/R2. The Remote Desktop Session Host Server is in Per User licensing mode and No Redirector Mode, but the license server dc01 does not any installed licenses with the following attributes: Proiduct Version: Windows Server 2008 or Windows Server 2008 R2.

It's like it thinks I installed Windows 2008 RDS Cals. But, when I run the RD License Diagnostics, I get the below. Hi Guys, The common solution is to delete the “grace period” key from the registry which is essentially a crack to allow the server to have unlimited licensing. What we found to be a working solution to the below error is the following: The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server ServerName.domain.com does not have any installed licenses with the following attributes: Product version: Windows Server 2012 Licensing mode: Per User License type: RDS CALs The fix: Inside of RDS licensing manager right click the server and select the manage licenses option.

On the RD Connection Broker server, use Server Manager to verify or configure licensing settings. As stated i don’t have any RD connection broker server and all my other servers are Win2012r2. Oh, how confusing RDS has become:/ So much easier before, I miss a way of doing the config like on a 2003 or 2008 server. I don’t get it, I have done as this article describes but yet I get two errors stating that: 1.

In deployment Overview page, select on Tasks and click ‘Edit Deployment Properties’ b. In the ‘Deployment properties’ applet, click on the ‘RD Licensing’ page. Here you will see the License server is already added i.e., License.contoso.com in our case, however, the Licensing mode is not selected.

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.

Is the 2012 server really looking for 2008 RDS CALs??? I didn't think that was possible. ---------------------------------------------------------------------------------------- The Remote Desktop Session Host Server is in Per User licensing mode and No Redirector Mode, but the license server dc01 does not any installed licenses with the following attributes: Proiduct Version: Windows Server 2008 or Windows Server 2008 R2 Licensing mode: Per User License type: RDS CALs ----------------------------------------------------------------------------------------- Any help would be greatly appreciated.

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.

The license server list can be found here: HKLM SOFTWARE Wow6432Node Policies Microsoft Windows NT Terminal Services The entry you need to modify is: LicenseServers I added the missing license server to the list and rebooted. The warning message about licenses went away and I verified multiple users could access the server. Time to crack open the 2012 books and papers!

RDS Architecture vBoring Blog Series: • • • Installing the Remote Desktop Licensing Role: First the licensing role needs to be installed. On your license server go to Manage -> Add Roles and Features Click Next Select Role-base or feature-based installation and click Next Select the license server from the server pool.

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. Thanks again everyone! Kenmarlin wrote: Yes VMware View is a great product and acts as a connection broker.

The eminem show torrent itunes. You say you have a 2012 RDS server. What RDS roles do you have setup?

I also edited the Deployment Properties to point the RD License to DC01. I get the below error when I do so. It's like it thinks I installed Windows 2008 RDS Cals. But, when I run the RD License Diagnostics, I get the below. Hi Guys, The common solution is to delete the “grace period” key from the registry which is essentially a crack to allow the server to have unlimited licensing. What we found to be a working solution to the below error is the following: The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server ServerName.domain.com does not have any installed licenses with the following attributes: Product version: Windows Server 2012 Licensing mode: Per User License type: RDS CALs The fix: Inside of RDS licensing manager right click the server and select the manage licenses option.

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.

Remote Desktop License Expired

You not only have to configure the license server on the overview page but in the deployment properties as well. Have you setup a RD Session host collection yet? I've been working on this for several weeks now, so I'm sure we can work it out.

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? Free download n-gage games full version. 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.