Windows Server 2012 R2 Remote Desktop License activation under Microsoft Azure subscription. Ask Question 1. So this is with some of my Windows Remote Desktop License Servers, which I am using with Microsoft Azure Cloud Subscription. The issue I am facing is related to the license expiry. A fully functional and activated 2012 Remote Desktop. Sep 23, 2012 - You installed the RD Session Host role on one or more servers, and make your users happy, especially those working from distance; you.
- Windows Server 2012 R2 Remote Desktop License Crack Free
- Windows Server 2008 R2 Remote Desktop Licensing Crack
0xc004f015: The Software Licensing Service reported that the license is not installed. SLEPRODUCTSKUNOTINSTALLED This error is absolutely normal because the legacy KMS server version knows nothing about new OS versions from Microsoft and doesn’t recognize the new KMS client keys. Microsoft company release special KB 2885698 update for full support of Windows 8.1 and Windows 2012 R2 on KMS servers which are working under control of previous Windows versions.
It is available at this service. KB 2885698 update is designed for the following OS with installed KMS activation server:.
Windows Vista SP 2. Windows Server 2008 SP 2. Windows 7 SP 1. Windows Server 2008 R2 SP 1.
Windows Server 2012 R2 Remote Desktop License Crack Free
Windows 8. Windows Server 2012 The order of KB2885698 installation and KMS server activation. Using the link above download and install KB2885698 update on KMS server and restart server. OS Edition KMS key Windows 8.1 Professional GCRJD-8NW9H-F2CDX-CCM8D-9D6T9 Windows 8.1 Professional N HMCNV-VVBFX-7HMBH-CTY9B-B4FXY Windows 8.1 Enterprise MHF9N-XY6XB-WVXMC-BTDCT-MKKG7 Windows 8.1 Enterprise N TT4HM-HN7YT-62K67-RGRQJ-JFFXW Windows Server 2012 R2 Server Standard D2N9P-3P6X9-2R39C-7RTCD-MDVJX Windows Server 2012 R2 Datacenter W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9 Windows Server 2012 R2 Essentials KNC87-3J2TX-XB4WP-VCPJV-M4FWM Using these keys you can activate Windows as usual by these commands.
I have 2 new 2012 serveers. One is a DC (with dns, dhcp, etc).
The other is an RDS. On the RDS server I installed everything but the Gateway and Licensing roles. These I installed on the DC. I got licensing setup on the DC so it's all green.
But on the RDS server when I try to tell it to look to the DC for its licenses, I get the message 'The license server specified is not valid. Verify the server name and specify a valid server name before saving the settings.' I can ping the DC from the RDS by NetBIOS and FQDN.
I even tried disabling the firewall on both servers. No A/V software is yet installed. The RDS is on the DC's domain. I'm doing all this with a Domain Admin account. Why can't I get the RDS to recognize the DC as a valid license server? Is it because the license server role is on a DC? I know you can't use a 2012 DC as a Session Host.
But all I want is for it to hold the license and gateway roles. Can it not even do that? I tried once again, but this time with a different setup. I'm reusing the license server from the previous installation but this time adding a separate RD session host. This should be pretty similar to your scenario except I'm not running the Licensing Server as a DC also. On the new RD Session host Through Server Manager I choose Add Roles And Features Remote Desktop Services Installation Standard Deployment Session Based Deployment Then I choose the current server for all three roles, Connection Broker, Web Access and RD Session Host After the wizard has finished I go to All Servers in Server Manager, click Manage - Add Servers and I add the other server where I have already installed and activated the License Server so that it is now managed in Server Manager. Don't add the second server to Server Manager before this step.
(The wizard didnt work for me if I did) I go back to Remote Desktop Services Overview tab in Server Manager and on the green cross for RD Licensing within Deployment Overview I choose the license server which is now available. Next, on the same screen next to deployment overview I click Tasks - Edit deployment Properties. On the RD Licensing tab I specify Per User licensing (or Per device if you prefer that) and the license server was already pre-populated in the licence server box. If not try to add it and this time it should not complain that it is not valid.
Windows Server 2008 R2 Remote Desktop Licensing Crack
Next, click the collection tab in Remote Desktop Services Overview in Server Manager and follow the wizard to create a collection. When this is done, check the licensing diagnoser. It now works for me.
I should point out I'm pretty sure this is not the 'correct' way to configure RDS in Server 2012 but atleast I got it working. I really miss the RD Session host tool from Server 2008 R2. Ok, as soon as I create a Collection it seems to be working.
From Server Manager select Remote Desktop Services. You should now get to the 'deploy scenario screen'. Note that this only works if you choose the Remote Desktop option while installing the roles in Server Manager. If you just installed the roles traditionally it doesnt work (for me at least).
In the deployment overview, specify all the roles which will occur on which server. Choose Tasks - Edit Deployment Properties and choose the type of licensing you want to do (per user or per device). Then you can create a 'Collection' and as soon as I did this the Licensing Diagnoser finally says it can connect to my Licensing Server (which is located on the Session Host) Hope this solves your problem or let me know otherwise. That isn't the same in my case. The various roles in that Overview are installed when the icon is gray, whereas the icons with a color such as green indicate that role is not installed on that server. So on my RDS server, I click Tasks then Edit Deployment Properties and try to add the DC as the license server, I get the error that the license server specified is not valid. If I click on the green RD Licensing icon, it runs me through a wizard to install the license server role.
If I pick the DC, it errors out. I don't know if that is because the role is already installed or if it's because it's a DC. So I'm still stuck at wondering if a 2012 DC cannot be used for any type of RDS role, whether it be gateway or licensing or what have you. I do know, per Microsoft documentation, that a 2012 DC can NOT be used as an RD Session Host, unlike with earlier versions of Server. Hi, Please see the following link. The Rdweb services, gateway and licensing role are supported on the dc but the connection broker is not. Best regards, Thanks for the link Ryan.
That in fact is just what I did. However, from the RDS server hosting the session hot role, it won't connect to the DC hosting the license server and gateway roles. That is why I'm asking if those 2 roles can be installed on a DC without breaking any rules since now that the roles are all installed, the session host server can't see the license server to use the licenses installed on it. Hi, Have you added the server to the server manager on each server or created a server group for rds on each server Best regards, No I didn't create a group for rds anywhere. Things look very good on the RDHS server but it just won't connect to the license server. On the DC side, things are looking bad.
I made the mistake of trying to 'fix' it by running the Add wizard again and this time choosing the Remote Desktop Services installation. Now I have red all over Server Manager and I can't add or remove roles as the wizard can't read what the list of roles is. I'm starting to think I'm going to have to blow the DC away (fortunately it's an add-on DC) and start over from scratch. But when I do, I'll be right back where I was with just the license server and gateway roles installed and I'm afraid the RDHS server still won't see the license server. I tried once again, but this time with a different setup. I'm reusing the license server from the previous installation but this time adding a separate RD session host. This should be pretty similar to your scenario except I'm not running the Licensing Server as a DC also.
On the new RD Session host Through Server Manager I choose Add Roles And Features Remote Desktop Services Installation Standard Deployment Session Based Deployment Then I choose the current server for all three roles, Connection Broker, Web Access and RD Session Host After the wizard has finished I go to All Servers in Server Manager, click Manage - Add Servers and I add the other server where I have already installed and activated the License Server so that it is now managed in Server Manager. Don't add the second server to Server Manager before this step. (The wizard didnt work for me if I did) I go back to Remote Desktop Services Overview tab in Server Manager and on the green cross for RD Licensing within Deployment Overview I choose the license server which is now available. Next, on the same screen next to deployment overview I click Tasks - Edit deployment Properties.
On the RD Licensing tab I specify Per User licensing (or Per device if you prefer that) and the license server was already pre-populated in the licence server box. If not try to add it and this time it should not complain that it is not valid. Next, click the collection tab in Remote Desktop Services Overview in Server Manager and follow the wizard to create a collection.
When this is done, check the licensing diagnoser. It now works for me. I should point out I'm pretty sure this is not the 'correct' way to configure RDS in Server 2012 but atleast I got it working. I really miss the RD Session host tool from Server 2008 R2.