1/24/2018 0 Comments Activate Terminal Services Licensing Server Windows 2003: Software Free DownloadHi All, I've got 2 boxes setup.one W2K 3 server as my domain controller (SBS actually) and another W2k3 as a terminal server. I installed my TS box as the Terminal Server License Server as well, however, I would like to verify that I've got my TS licensing setup correctly or instruction on how to setup my licensing before the '120 days' is up if I have it wrong. When I open Terminal Server Licensing on the TS, I get a dialog box staing that 'No Terminal Server license server is available in the current domain or workgroup.' ![]() It goes on to say how to connect to another license server. If I click OK and then right click on 'All Servers' > Connect > enter the name of the TS I'm currently on, the right hand pane shows 2 items: 1) 'Existing Windows 2000 Server.' And 2) 'Windows Server 2003 - Terminal Server per User CAL Token'. The 2nd line for W2K3 type as 'Open', total as '31' and available as '31' (I purchased 31 licenses for users). I'm confident that I've got it wrong, but need some direction to get it right. Thanks, Terry. Since you didn't install the TS license server on the DC, you need to tell the terminal server explicitly which license server to use; assuming you have SP1 on your TS, you can do that easily in the Terminal Services Configuration MMC in Administrative Tools. If for whatever reason you don't have SP1 yet, check here: How to Override the License Server Discovery Process in Windows Server 2003 Terminal Services Then make sure you've set your terminal server to request Per User licenses; default is 'Per Device'; you can do that in the TS Configuration MMC as well. Have a look here: The Function of Terminal Server CALs in Windows Server 2003 And maybe of interest: The Ultimate Guide to Windows 2003 Terminal Server Licensing. It's usually better to have it on the DC. It just so happens every now and then that you have to rebuild a terminal server, and in that case, it's easier if you don't have to reinstall the licensing (and call the Microsoft Clearinghosue) as well. Makes it easier to add more terminal servers as well, because you don't have to think about setting the license server manually (even though it's a lot easier since SP1). Anyway, you can still transfer the licensing; you'll just have to install and activate the license server on the DC, then, when installing the licenses again, call the Microsoft Clearinghouse (numbers will be listed) and have them reissue the licenses. It's the only way to transfer/reinstall licenses, but they're quite used to that, so it's usually not a big deal; just have the licensing infomation at hand. ![]() ![]() ![]() Mar 29, 2017. Click the Installation Method tab, click Automatic connection (recommended) in the Installation method list, and then click OK. On the Action menu, click Install Licenses. Follow the steps in the Terminal Server Client Licensing Wizard to install your TS CALs. This template assesses the status and overall performance of a Remote Desktop Services Licensing (Microsoft Terminal Licensing Server). This template uses Windows System Event Log, Windows Service, and PowerShell monitors. This template works on Windows 2003, 2008, 2008 R2, 2012, 2012 R2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |