We are using Windows, Linux and Mac clients.
Now that the licensing part seems to be working just fine, it’s time to test out different clients. Five (per device) licenses are currently checked out Everything seemed ok! (Fig 3 has the details).Ĭhecking that a client gets a (permanent) license can be done from the license server/RD Licensing Manager (Fig 4).įig 4.
#How to setup remote desktop server 2012 r2 install
If you are interested in the difference between per user and per device licenses, read for example.Ĭhecking that the licensing is working can be done from RD Licensing Diagnoser (I didn’t install RD Licensing Manager, it is already installed on another (license) server). Oh well, the steps are still quite similar, but I skipped to the next step in the guide. I couldn’t point to an existing license server in this step.
In the guide it says “Click the RD licensing icon and either add the server as your license server or point it to your existing license server on the network by entering the server name or IP then click the forward arrow”. The procedure for adding the license server was a bit different from the one in the above guide though. I won’t go into the licensing system here, I just say that we’ll be using per machine licenses and that the licenses will be issued from an existing license server in our domain. Our University has some licenses so no problem. A RDS Server requires licenses either per device or per user (Remote Desktop CALs). Installed the RDS Server role (Fig 1) following a guide from (my own knowledge was a bit rusty 🙂 ).Please restart the computer to refresh the Local Policy C:\Program Files (x86)\LocalGPO>cscript f /path:c:\Users\xxx\Downloads\gpo\.I replaced “Call ChkOSVersion” with “ ‘ Call ChkOSVersion” (that is, commented out the whole check).I edited the script and commented out the line which checks for OS version (in f). The script checks for OS version so it can’t continue if wrong OS is detected. The tool wasn’t updated for Windows Server 2012 R2, only for Windows Server 2012.
0 kommentar(er)
