If time is the constraint for you then there is no solution as a device CAL gets issued only for a random period of 52-90 days. Once that CAL gets expired the client has to connect to the TS pointing to that license server to get the CAL.But if the machine is an issue, then you can use the 'License server security group policy'. By setting this policy, the terminal servers in the 'Terminal Server Computers' group only can get a license from the license server. For more details on how to set the policy, please check the post.Hope that helps!ThanksSilviaRemote Desktop Services Team Blog: http://blogs.msdn.com/rds.

Nod32 antivirus 3.0.642with unlimited update fix cracked. 2014-10-22T18:52:46-04:00 Daily 1.0 2014-10-22T18:52:46-04:00 Daily 1.0 2014-10-22T18:52:46-04:00 Daily 1.0.

Hi I 've had AdminStudio 9.0a running and undated to 9.5 including service pack 1. All up and running using my activation code from the customer portal. Now I want to change to new hardware. How do I deactivate/recover the licence? I believe the licence agreement says one user per machine per zone. Yes I have just tried to reinstall on a new machine - says the activation code is invalid.

I 've noticed that if I lose my local profile it does not matter as long as I am logged into the zone on that device. So the licence is in the zone and tied to the device. NB I posted on the software Package management but no replies so try here. GERWIL, It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options: - Visit and search the knowledgebase and/or check all the other self support options and support programs available. - You could also try posting your message again. Make sure it is posted in the correct newsgroup. (Be sure to read the forum FAQ about what to expect in the way of responses: If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot. Your Novell Product Support Forums Team http://support.novell.com/forums/. I've got a Windows 2003 Std Terminal Server that's configured to get Per Device CALs from one of my Windows 2008 Ent Domain Controllers.

The Domain Controller is configured as a TS License server, it's activated and I've installed Per Device CALs on it. Despite this, the TS event log on the Windows 2008 DC TS Licensing Server gives me an Event 22 Warning saying:The Terminal Services license server MY2008DC does not have any Terminal Services client access licenses (TS CALs) installed and registered with the Microsoft Clearinghouse for product Windows Server 2003 - Terminal Server Per Device CAL Token. Therefore, the Terminal Services license server cannot issue TS CALs of the type Windows Server 2003 - Terminal Server Per Device CAL Token to the terminal server ip number. To resolve this problem, install additional TS CALs as required.I do show a Windows Server 2003 - Terminal Server Per Device CAL Token license in my TS Licensing Manager with 250 total, 154 available and 46 issued.

Why would this event be coming up?Orange County District Attorney. Hello,Since a couple of weeks I notice that our TS Per Device CALs are being licensed to our Terminal Servers (W2K3 R2 Standard) itself. As a result, all of my 225 TS CALs are issued now. The strange thing is that for every Terminal Server we have (6) a number of TS CALs are issued.I really do not have a clue how this can happen. Does someone have a idea how to solve this problem? Of course I can buy some more TS Per Device CALs, but I don't think that a Terminal Server itself should occupy TS CALs.Peter.

HiI have already 180 TS Device CALs installed, and all of them is in use(available 0). Now I have purchased 70 additional TS Device CALs, so the total will be 250. When I installed the new licenses I did a mistake, I typed in 250 when I probably should have typed in 70. The problem is that now I got 250+180 licenses, my question is then: How do I remove the 180 licenses, so that the total will be 250 and not 250+180= 430.This is the status from Terminal Server Licensing console:Windows server 2003 - TS Per Device CAL Type: Volume License 250 Available: 249 Issued:1Windows server 2003 - TS Per Device CAL Type: Volume License 180 Available: 0 Issued:180 (this is what I need to remove/ uninstall)any suggestions? Ok, a little background. I have a terminal server on a Server 2008 Enterprise server. I have to setup a new TS for a new company we are starting up, and I need to take 25 cals from our current TS to the new server.

The old TS will continue to run for all of our RDP clients that connect. It seems all the info I can find requires one to deactivate the old server. We are simply adding another domain controller and TS on our vmware system and need to move 25 cals to that new TS. Is this possible?Computer Systems Specialist. Hi, You need to De-activate the old license server,On the ‘License Server Deactivation’ page, you will be provided with the same clearinghouse phone number and the License Server ID of your old server. Make a note of this License Server ID as you need to provide this to Microsoft Clearinghouse.

Call Microsoft Clearinghouse at the number you have noted and give them the product ID of the new license server which you want to activate and of the old license server which you want to deactivate. Once you have given them this information, Microsoft Clearinghouse will provide you with the confirmation code. Enter this code into the License Server Deactivation Wizard when prompted.And activate the new one from scratch. Best regards, ClarencePlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hi Luigi, You should be fine moving from one domain to another. Regardless I recommend you gather the original licensing paperwork, authorization number, license number, agreement number, emails, etc., as appropriate for the type of licensing program you purchased them through.

If for whatever reason you need to reinstall the RDS CALs you will be fine if you have the license documentation. After moving the server you should test by connecting to the server via Remote Desktop and then verify that there are no warnings/errors related to licensing in the server's log. You may also want to create a RDS Per User CAL Usage report in RD Licensing Manager, export it to.csv, and then examine it in Notepad. You should see in the file where the server has issued licenses to users in the new domain.

Hi guys I want to deploy an application through sccm 2012 r2 with a license key in the command line. So far no problem, with the paramater ISX_SERIALNUMBER=XXX I can handle that. So command line looks like: msiexec /i XY.msi ISX_SERIALNUMBER=XXX But here's the problem. That license key changes very often, usually a key can just be used for 2-3 installation. After that I get a new key which I have to use (we have no volume licensing.

Do not ask.). I tried to create a machine variable (device - properties - variables) with the license key. But I didn't manage to get the variable in the command line correctly. I tried ISX_SERIALNUMBER=%variable% but it didn't work. Dictionary Expresii Francez Roman Pdf there. I realised that those variables just can be used with a TS. But I really don't want to use a TS for software deployments.

After that I thought I'll try to get the variable with powershell and it worked. But just with an Administrator account who has access to the server. If i run the script in system context while deploying, it fails. Does anyone have another way to deploy Software with a Licence Key as a computer variable?

Or any other way to specify a specific Licence key for a specific computer? Thanks in advance p.s. I know I could entering it manually. But that's not an option at this time. I have a two host VMware ESX 5 environment. I had a vSphere virtual machine which managed these two hosts (it was hosted on one of the hosts). The storage device for the hosts has failed.

I have restored the device and created a new vSphere VM. The two ESX hosts also have the vSphere licence key associated with them. I have added the vSphere Essentials Licence key I had for this purpose on the vSphere machine. When I try to add the ESX hosts to this vSphere VM I get an error. A general system error has occurred: Timed waiting for vpxa to start. I have checked for snapshots, and there are none in the environment, so it cant be that, On the licence screen, it shows the evaluation licence and the VMware vSphere 5 Essentials licence (unlimited cores per CPU) Assigned 0 CPUs, capacity 6 CPUs, expires never. Anybody got any ideas what I am doing wrong?

Many thanks Paul. Hi, sorry for the long title, but I've checked previous discussions but I've not found a specific response to my situation. I've two farm of TS Servers host that works with Citrix; the old one are 2003 SP1 TServers and the new one are 2008 R2 TS servers. The first group of TS 2003 server discover TSL server in a Enterprise scope, the second group of 2008 TS Server found the 2008 TSL installed as Domain scope by GPO definition. The terminal client PCs that are used to connect to Citrix applications - on boths farm - are the same.

TS 2003 host servers are in the same AD site as in the same domain of the TS 2008 r2 Host Servers. In this context happens that: if I was connect to a Citrix application that works on 2008 TS Host the client received a TS CAL licence from 2008 TLS (as right ), but after that if I connect to a old citrix application that require 2003 TS hosts I continue to use the 2008 cal licence ( temporary or permanent ) without make use of the 2003 CALs on the windows TLS ( that are two DCs). I can check by TSTts.exe on the client, as taking a look at licence server manager the licence list that are in use. I sholud expect that - even the client show a right licence ( 2008 RDS TS licence allow 2003 TS ) just cause it's a 2003 TS host and the CAL type is not a A02-5.00 a new request could be tried to get a CAL licence from the 2003 TSL or at last do this when the license must be renewed. In that way I could preserve some 2008 TS licence that I need for 2008 TS, but I 've not found a solution.

So my question is if the only possibility to handle this situation is to transfer the 2003 TS device CAL to the 2008 R2 TLS. For that I need to make a phone call and do some work. Butif there are nosolutions and no costI will do. Thanks for your advise or best practice, Onorato. Hi, As far my knowledge, you can use highest version of server CAL for lower server version (i.e.

You can use server 2008 R2 CAL for server 2003) but as in your case, we need to migrate the server 2003 CAL to higher version i.e. Server 2008 R2. Its better practice and advice if you can migrate your existing RDS CAL on server 2008 R2 and make 2008 R2 as RD licensing server and then you do not need to point to different server. As RD Licensing Server 2008 R2 can handle all RDS CAL and licensing. More information: 1. Migrating a Windows Server 2003 TS License Server 2.

Coexistence 2003 and 2008 TS Servers (Licensing) Hope it helps! Thanks, Dharmesh. Hi We have a windows 2008 R2 environment with a server running remote desktop services. We want to add a server with the remote desktop gateway to allow staff to access the remote desktop server from home.

Today we are using licence mode per device. But with the remote desktop gateway I want to use licens mode per user.

Is it possible to use mixed licence mode? And can I control so that users connecting direct (internal LAN) are using per device licens and users connecting through remote desktop gateway are using per user license? Thanks in advance /Birger. Hi, A RD Session Host server can only contact a single (set) of RD License servers. Unfortuantly there is no way to have the RD Session Host decide to hand out device or user CALs based on a condition.

If you really want the seperation, the only option would be to setup two (sets of) RD Session Hosts. One for internal connections that hands out devices licenses from a RD License Serverthat holds device licensesand one for external connections that hands out licenses from a different RD License Server that hold User CALs. Of course setting up the RD Gateway to only allow external connections to the 1st RD Session Host. Or, purchase user cals for all users and stop using device CALs if you decide to publish RDS over the internet.

Kind regards, Freek Berson The Microsoft Platform Twitter Linked-in Wortell company website. We have a Windows 2008 R2 Terminal Server licensing Server in ourenvironment.

When checking the issued CALs in Remote desktop Licensing manager, i seeWindows 2000 Server - Built-in TS Per Device CALs. Ibelieve these are CALs which are issued by the Windows 2000 terminal Server itself to the Device or client. My question is: 1. Is there a way to find out which Terminal Server is issuing the CALs or can we revoke the licenses? Can we stop Issuing Windows 2000 Server TS CALs?

Help in this regards is muchappreciated Thank You. Hi, Once the Windows 2000 terminal servers are removed, if you want to get rid of the issued CALs in the RD Licensing database then you may rebuild the licensing database. This will clear out everything including your installed RDS CALs so you need to have your licensing authorization numbers, agreement numbers, etc. Ready to allow you to re-install your RDS CALs.

To rebuild open RD Licensing Manager (licmgr.exe), right-click on the server name and choose Manage RDS CALs, follow the wizard,select to rebuild the database,choose the databasehas becomecorrupted reason, etc. Will the per user licenses I purchase for the 2003 TS be usable and transferable to the 2008 box? The same users will be using the TS.

The license server will reside directly on the TS box along with the TS app. Noel To be more specific, If you mean to installTS2003 CALs in the 08 licencse server, it is ok and you need to call the Microsoft Clearinghouse to deactivate the TS2003 and install the appropriate CALs in 08 license server for serving 03 TS. For information about how to call the Clearinghouse, see: If you mean to use the TS2003 CALs for serving TS 2008, it is not useable.You need to buy the 2008 r2 TS CALs for serving 08 or 08r2 TS/RDS. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites to find contact information in their locations.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This is 2008 Server Standard (Not R2), SP2. The TS Licensing Manageer shows 25 Installed TS Per Device CALs.

BUT every couple of days (anywhere from 1 to 4 days) I see this in the event log one or more times: Log Name: System Source: Microsoft-Windows-TerminalServices-Licensing Date: 9/17/2010 10:39:58 AM Event ID: 22 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: IPPD2008 Description: The Terminal Services license server IPPD2008 does not have any Terminal Services client access licenses (TS CALs) installed and registered with the Microsoft Clearinghouse for product Windows Server 2008 - Terminal Server Per Device CAL Token. Therefore, the Terminal Services license server cannot issue TS CALs of the type Windows Server 2008 - Terminal Server Per Device CAL Token to the terminal server IPPD2008.

To resolve this problem, install additional TS CALs as required. Is there a problem here? Thanks, Debbie. Na terminlovm server Windows 2008 se mi objevila chyba Terminal Server License Server/Remote Desktop License Server Only Issuing Temporary Licenses and Event ID 17 Logged - postupoval jsem podle deaktivace a reaktivace se nepodařila. Takže jsem stopnul licenčn službu, přejmenoval c: windows system32 lserver a licenčn službu odnistaloval, restartoval a znovu nainstaloval. Pak jsem znova aktivoval a přidal ts device caly. Terminlov licenčn server je na tmže serveru jako terminlov server a je to jedin Windows2008 server (nen řadič AD).

V AD je tento server ve skupině Terminal Server License Servers. Diagnostika licenc je vpořdku, hls 100 instalovanch ts device cal. Pokud na stanici smažu mslicensing klč v registry, licence je vystavena.

Přesto mm v logu na serveru hlky: Na licenčnm serveru Terminlov služby server3 nejsou nainstalovny a registrovny ve službě Microsoft Clearinghouse ždn licence pro klientsk přstup k Terminlov službě (TS CAL) pro produkt Windows Server 2008 token licence pro klientsk přstup vzan na zařzen terminlovho serveru. Proto nemůže licenčn server Terminlov služby vydat terminlovmu serveru server3 licence TS CAL typu Windows Server 2008 token licence pro klientsk přstup vzan na zařzen terminlovho serveru. Tento problm vyřete instalac dalch licenc TS CAL podle potřeby. Tute kde je zakopan pes? Hello all, I took over the role of managing the TS licensing server which I did not setup and have little information in it. I logged on to the server which is a Windows 2008 R2. I checked the TS licensing Manager and the license has been activated for Windows 2008 TS per device and TS per user.

It shows servers with with certs issued on and expires on. Why does it only issue an 120 days license?

Does it force the server to get another license after 120days? Also, the windows 2003 shows as temporary.

How do I activate it? I right clikc and select install license and I have many choices for the license program. How I check how the Windows 2008 was installed and how do I go about installing the license on windows 2003? Can I used my MSDN? Hi, About how to activate or install the license,pls refer to Deploying Remote Desktop Licensing Step-by-Step Guide:As for whether your license has benen installed,pls open your RD licensing Manager,it will show the license program, total licenses number,expiry date and so on.You can also generate report for the detail.If you haveinstalledCALs,the expiry date is usually showed as Never. You can also contact the MS resellerfor presale license detail.

To install and activate your license server,youneed to call the clearinghouse to finish the installation. Regards, Clarence Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi I need to clarify this scenario: I have a PC which is used to access a hosted system, using TS (2003 flavour, per-device CALs). So my PC has obtained a CAL token from that server (in somone else's domain), and is happily connecting and working. About half my pc's are in this state. I now set up my own terminal server system, with per-device cals. And I connect to it from my pc.

My understanding is that my pc will not request a licence token from my own terminal server, because a token is a token is a token, and it's got one already, and can use it to connect legally to any number of terminal servers, irrespective of who, or what domain, issued the original CAL. That certainly seems to be the case, because there's no temp or perm licence showing up as issued to my pc in my TS Licensing Manager.So. I really only need enough CALs to cover the half of my pcs that are never used to connect to the hosted system? Hi all,We have a Mac connecting to our Citrix servers using the Citrix client receiver. Our TS licensing is done per device. On Windows machines, the device license can be found in the registry under the MSLICENSING key.

However, I can't seem to find such a licence on the Mac.Searching on the web, the following locations are mentioned, neither of which I can find on the Mac I'm using:MacHD/Users/Shared/Microsoft/RDC Crucial Server InformationMacHD/Users/Username/Library/Preferences/Citrix_ICA_Client/Citrix_IDDoes anyone know of any other locations the TS license could be stored on a Mac running OSX?Thanks,Simon. Hi, We are hoping to migrate our Windows 2003 terminal servers to a Windows 2008 farm but are running into a brick wall.

As soon as the grace period expires on a TS 2008 server and you have the TS server set in per-device licensing mode (as most people would want for a Sun Ray environment) the sessions will not connect. UTTSC reports no errors, but is disconneced by the server. Rdesktop is also disconnected but at least gives the error 'Internal Licensing Error'. The first connection is always successful from a specific Sun Ray client (where the TS license server gets a temporary device CAL from the TS license server which is issued to the client).

On the second connection the Sun Ray client is expected to provide the temporary CAL certificate to the TS server for checking against the TS license database. This is what appears to be broken.

This issue is not reproducable from Windows or MacOSX clients. Hopefully this is a simple config problem on the Sun Ray server. Can anyone help? Hi, is there an easy Way to List all Issues Licenses on a TS-Licensing Server together with the Issuing Data and (if possible) a unique Device ID as a csv-List? My Problem is, that there are multiple License-Packages installed (- multiple Lists) and some Clients have also been renamed in the meantime.The Licensing MMC doesn't allow me to export a List (like AD-Management does) and I have no Idea how to extract Tables from TLSLic.edb to obtail the Informations directly. The Generate per User CAL - VB Script doesn't work for Device-CAL Licensing it seems.

My AIM is to generate a List with the Client Stations in AD, TS-Licensing and the Antivirus-Management and compare them. I already have the two other Lists. Does anybody have an Idea about this? Hi TP [] Thanks fior your reply, I have already checked that, License server security group and Prevent license upgrade are not configured, I read this two articles: By default, when the Per Device licensing mode is used, after a client logs and authenticates to a terminal server for the first time, and after the terminal server locates a license server, the terminal server issues the client a temporary license. After a client logs on and authenticates to a terminal server for the second time, if the license server is activated and at least one Per Device CAL is installed on the license server and not yet issued, the terminal server issues the client a permanent, Per Device CAL.

(my license server is well activated, client logs and authenticates more than Two times and Per Device Cal are available in the license server!!! Hi I have a problem with a smal terminal server setup. It's based on a Windows 2008 TS and that licensing server is installed on the server itself. 14 thin clients are connected to the server and we have 20 per device licenses. But I experience that some of the thin clients can't log in to the server.

In the Application log I get an event 1004: Event Type: Error Event Source: TermService Event ID: 1004 Description: The terminal server cannot issue a client license. In TS Licensing manager I have 20 installed per device cal's. 0 = available and 9 issued. I would be happy is someone could help me solve this problem. Hi, It appears your licensing database is corrupt. Based on what you have written you should have available Per Device TS CALs since only 9 have been issued.

To resolve this I recommend you rebuild the database. For Server 2008 R2 you may do this through the Manage RDS CALs wizard within RD Licensing Manager. For Server 2008 (non-R2) you may do this by Deactivating the server using the Advanced menu in TS Licensing Manager, uninstalling the TS Licensing Role Service, re-installing TS Licensing, Activating, and then Installing your TS CALs. IMPORTANT: Before rebuilding make sure you have your licensing paperwork including any authorization numbers, license number, retail keys, etc. This will be needed to reinstall your TS CALs, and if necessary you may needto provide this information tothe Clearinghouse if you have problems reinstalling your CALs. HOW TO: Locate a Phone Number for the Microsoft Clearinghouse -TP.

Hi All I have server 2008r2 and have setup remote desktop. I have been on the rd licenceing manger and i have a green dot on the server and it states that it activated. Discovery scope is domian configeration ok. I pres the plus sign on server1 and it expands to windows 2008 servicer _ Builtin ts per divce CALs. On right click i have 3 options refresh, install licences and help.

When i press install licences i get the welcome screen to install licences wizard. When i click next it contacts the clearinghouse then comes up with the licence page to install the licence. I am now given 8 options licence pack, open licence, select licence, enterprise, campus, school agreement, service provider, and other agreement. When i put the disk code it come back with licence code not reconised ensure you have entered the rcorrect licence code any ideas would be very helpfull. Many thanks Richard C. You may click Start--Run and enter the following command to show the Tooltip in the notification area with the days remaining in grace period: tlsbln 2. No TS CALs are included with windows.

You must purchase them separately. TS CALs for 2000 Server TS do not give you the ability to connect to a 2003 TS, however, they would give you the ability to connect to a 2000 Server TS if you needed to. TS CALs are now called RDS CALs, and are available as Per Device or Per User. If you have more physical machines that user will use to connect to your server than you have users, then I recommend you purchase Per User RDS CALs. For example, often people will connect from a PC at the office, their laptop, and their home PC.

Under Per User licensing only 1 RDS CAL would be required, under Per Device licensing 3 RDS CALs would be required. So in this example Per User licensing makes the most sense.

Below is the part# and a sample reseller for a Per User RDS CAL Microsoft Windows Remote Desktop Services 2008 R2 - Per User CAL Part# 6VC-01164 After purchasing RDS CALs they will need to be downgraded for 2003. If you have any trouble installing them on your TS Licensing server you may contact the Microsoft Clearinghouse for assistance.

Have your license agreement numbers ready. In Terminal Services Configuration (tscc.msc) you will need to set the licensing mode to match the type of RDS CALs you purchased and Specify the name of your TS Licensing server.

For example, if you purchase and install Per User RDS CALs make sure you set the mode to Per User. Your TSLicensing server can be on the same server if you wish since it uses very little resources. I have an issue with TS Licensing, we are looking to change from per device to per user licensing Scenario TS Licesning Server shows 200 per device licenses and 400 per user licenses We have new external users with a one way trust, therefore the device names are not known by the internal TS licensing server All our TS Servers are set to per device licensing My questions are as follows (Please Note fairly new to TS licensing and appologise if these questions sound stupid) 1.

As the TS Licesning Server already shows per user licensing, am I safe to assume the user licenses are installed and no further config on the License server is required 2. I have read that changing the Terminal Servers to per user mode allows both the Per device and per user licenses to be assigned is this correct, or does the per user setting restrict it to per user licensing as the name suggests 3. When converting a TS to per user mode it can only be done once ie there is no going back if we find issues? Dear All, We have installed a MS 2008 Server with SP1 on a Sun VM and an AD on a separate VM.

The licensing server is running on the terminal server. We are connecting some HP thin clients which work with no issues whatsoever and 2 netbooks which we connect via RDP with a third party tool similar to Citrix. One of the directors also connects with the same third party tool from a different laptop from home. When we originally set things up, everything was working fine, however about a month later we started having issues with the netbooks connecting to the TS. We bought a series of TS CAL's per device and per user (some were provided with our partnership pack) and installed them. The licensing server is configured to a per device setting.

When I go to the terminal services configuration tool, I am presented with two errors: The Terminal Services Configuration tool is running with local account credentials. Licensing Diagnosis will not be able to discover domain or forest license servers automatically and the Total Number of TS client access licenses Available value may be inaccurate. The terminal server is in Per Device licensing mode, but license server 10.0.0.3 does not have any Windows Server 2008 Per Device TS CALs available.

Img src = http://farm5.static.flickr.com/41670_38a6fbc7cd.jpg. Hi, Thanx for the info, after I changed the licensing to User based all users were able to connect, not sure which licenses are used though. Restarted the licensing service and then went into Licensing Manager to check the amount of licenses. Nothing has changed.

Also tried to contact the clearing house which is somewhere in the UAE. However, the numbers have changed and the numbers provided are not answered. However for now things are working.

Would be very interested to find out more about the way the licensing works though. Any info woould be very welcome. Thanx again D. I have 4 Terminal Servers that are 2003 servers. The License server is a 2008 R2 SP1(license server only). I am reciving event ID 21 for 3 of the 2003 TS. CALS are showing available on the 2008 server.

The 2008 License server has 3 licenses pack Per Device CALs installed. 1 - 30 Per Device CAL pack with 30 Used, 1 - 150 Per Device Pack with 42 Used, 1 - 50 Per device pack with 0 Used. I have reactivated the License server, followed instuctions on how to delete the MSLicensing key from the registry, ensued that all 2003 TS have the correct licensing configuration asPer Device Can anyone tell me why I am getting this error and how to correct it? As per the article: 1.

Check the type of TSCALs installed on the license server - Per Device (all licenses packs are per device) 1 - Server 2003 30 Per Device CAL pack with 30 Used, 1 - Server 2003 150 Per Device CAL - 55 Used 1 - Server 2003 50 Per Device CAL 0 Used 2. Check the licensing mode on the terminal server All 3 2003 Terminal Servers are configured with the licensing mode Per Device. They are also sets to a specified license server - which is the 2008 license server. - We do not use group policy to licensing configuration. Install TS CALS onto the license server.

I do not believe this is necessary as there are CALS still available. Verify All the terminal servers are 2003 OS they do not have the License Diagnosis tool in the Terminal Servers Configuration. (only the license server is a 2008 R2 server.) I have not been notified that any users have not been able to login to any of the 2003 Terminal Servers.

Therefore, I think the license server is working as it should - and I can see the CALs issued field increase from day to day. If this is a bug in the 2008 r2 system I can live with that. I just need it confirmed so that I can document it on my end. If it is not a flaw then I would greatly like to get this error resolved as it would be one less warningto sift through in the daily log check. Windows Server 2008 R2 Vorrei tirare su le remote app ed il ts web access ma non mi e' chiaro che tipologia di licenza (user o device) conviene utilizzare. Mentre le cal per utente sono facili da capire (immagino che vengano conteggiate le sessioni in base all'autenticazione), per device come funzionano? Da cosa il server determina quali postazioni stanno utilizzando il servizio?

E per chi si collega attraverso il Web Access? Come funziona, per esempio, se uno si collega da un internet point. Scusate le domande ma e' Natale e sono alle prime armi!:-) Auguri a tutti!! Hi Neill, In addition to TP's suggestion, you can also revoke Client Access Licenses (CALs) manually. Please refer to the following article for detail: Wilson Jia TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided AS IS with no warranties, and confers no rights.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hi, normally it is all about following the EULA. So say if you have something in the license manager, but dont have license for - as long as you do not use it actually I think its oK.

MFST probably is different opinion:) Never the less. If you messed up your license Manager, please proceed as follow: 1) Stop Terminal Services Licensing Server SERVICE (make sure the License Manager is closed!) 2) Go to your system drive, into C: Windows System32 lserver 3) Rename the TLSLic.edb file to OLD_TLSlic.ebd 4) Start the License SERVICE 5) Now when you go to the License Manager you will see that there are no licenses except the 2000 one. (that means the licenses are RESET. 6) Call Microsoft Clearinghouse: your sins and make sure that they delete the unnecessary licenses underyour account Another way of duing it Done. PubForum.net Founder, The Bible of Remote Desktop Services! Love Microsoft its people to bits!

Hi, I did a search for this and found nothing, so I am sorry if I am repeating a question already answered. Actually this has two parts; 1. I would like to reassign TS CALs (Per Device) as during testing, we used some machines that will never be used again, and need to assign them to new machines, permanently. Licensing Server, when I click on Terminal Server Licensing, it states there is no TS Licensing Server, but when I click on connect and type the name of the server in, it connects to the TSLS and shows the licenses and seems to be working fine, as it's giving out the license, and we can TS in.

Any help would be greatly appreciated! Thanks in advance! Since the question is a license issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there. You can also visit the following site for more information and support on licensing issues: Lakhani Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker -------------------------------------------------------------------------------- This posting is provided AS IS with no warranties, and confers no rights. -------------------------------------------------------------------------------- My Blog Team Blog @Twitter Facebook Author: SQL Server 2012 AlwaysOn - Paperback, Kindle.

Hi, Thanks for your question. As far as I know, in order to install office on RDS server, we need a Microsoft Office volume license key.

Since I am not an expert on this specialty, I would recommend that you contact Microsoft Volume Licensing Service Center for detailed information. In addition, share some documents on install Office on Terminal server. Hope it helps.

Plan to deploy Office 2010 in a Remote Desktop Services environment How to enable Office Professional Plus 2010 to run on a terminal server Licensing Office on Remote Desktop Services Best Regards, AidenAiden Cao TechNet Community Support. Hello,There is no possibility to migrate your 2003 licenses.You need to install TS 2008 licenses on a 2008 TS license server.More info: Windows Server® 2008 provides a license management system for Terminal Services known as Terminal Services Licensing (TS Licensing).

This system allows terminal servers to obtain and manage Terminal Services client access licenses (TS CALs) for devices and users that are connecting to a terminal server. TS Licensing supports terminal servers that run Windows Server 2008 as well as terminal servers running Windows Server 2003 or Windows® 2000 Server. (step-by-step licensing TS: http://technet2.microsoft.com/windowsserver2008/en/library/4b4dd54a-46df-4b18-813f-2424cbc865031033.mspx?mfr=true)http://www.microsoft.com/windowsserver2008/en/us/licensing-terminal.aspxgr,Kurt. You look at the complete picture, not just what the TS or TS license server sees. The key thing is the number of users (humans) or end devices (PCs/Macs/thinclients/etc.) that are viewing/interacting with your TS.If this is a paid service you are providing, then most likely you need to be under Services Provider Licensing Agreement (SPLA). In this case you would license your TS users on a per subscriber basismonthly. The license agreements for OEM/Retail/Volume licenses do notgrant rights forsoftware as a service/rental/paid hostingor similar cases.Thanks.-TP.

Mm 2 dotazy: 1) je možn někde nastavit, ze kterch zařzen je možn se připojit k TS? Pokud m uživatel povolen přstup na TS - je členem Remote Desktop Users, potom se k TS může přihlsit z libovoln stanice. Jelikož mm licencovn per device začn se objevovat, že se uživatel přihls ze stanice, ze kter by neměl (kde aplikaci může spustit po sti a nemus použt TS) a tm pdem se zabere dal licence TS. To je naprosto nevyhovujc. Kdyby lo alespoň ručně vydat ty per device licences danm zařzenm.

2) Jak zabrnit sežrn licence, pokud se k TS připojm přes RDP jako administrator? To myslm v licenčnch podmnkch je, že tm pdem nepotřebuji licenci k připojen, přesto mi to licenci zabere a přiřad ji počtači ze kterho se připojuji. To je tak naprosto neždouc. Hi i need help with this. Im installing a brand new SERVER with 2003 SERVER R2 STANDARD with SP2 using VOLUME LICENCE. We bought 10 DEVICE CALS to connect the 10 WIN XP clients on the LAN (domain) The question is. When i was installing the server (at installation process) its asked me about CALS per SERVER or DEVICE/USER On SERVER CALS option it asked me on how many CALS i want to active, but we have DEVICE CALS (not SERVER) Cause the CALS we bought are DEVICE CALS, i chose the DEVICE/USER option, but in that option it dont allow me to set how many CALS is have.

How i must do to configure the 10 DEVICE CALS we bought? Or i dont need to set that number?

Can anyone give me some light at this point? I must clarify that i dont talking about TS CALS (the CALS that we bought are NORMAL DEVICE CALS, just lo log on the DOMAIN) Thx in advance. Hi, yes this is very confusing at the beginning:) So, when you choose during installation Per Seat (user or device) licensing mode, you have to only store your invoice for purchased CALs. That's all:) When you select Per Server licensing during installation, then you need to specify how many CALs do you have. When max concurrent limit would be reached, the next client won't be able to connect to server. In case you chose User/Device licensing mode, you don't have to do anything more:) Just only store the invoice for purchased CALs to prove during audit that you have appropriate amount of them. You can only purchase RDS CALS - TS Cals are a thing of the past.

When you purchase RDS CALS you've the option of licensing in one of two modes (from When Per Device licensing mode is used, and a client computer or device connects to an RDSession Host server for the first time, the client computer or device is issued a temporary license by default. When a client computer or device connects to an RDSession Host server for the second time, if the license server is activated and enough RDSPer Device CALs are available, the license server issues the client computer or device a permanent, RDSPer Device CAL. An RDSPer User CAL gives one user the right to access an RDSession Host server from an unlimited number of client computers or devices. You can therefore purchase per device RDS CALS - however, consider the environment and usage. If you've a small amount of devices shared by a lot of users - per device is sensible. If you've a lot of users each using a wide range of device - then per user CALs would be better. It is possible to track usage using the Remote Desktop Licensing Manager.-------------------------------------- Andrew Wood Sunderland, UK.

Hi everyone, I have a question regarding RDS licensing. I am looking into a solution that requires 100 servers to connect through to a RDS (TS) farm. Each one of those 100 servers will have around 30 users. My question is, if i use the per device licensing model, would I be correct in thinking only 100 device licenses are required or would each user need a seperate CAL to connect? It is unclear as to whether per device is deemed to mean 1 device = 1 user concurrently or whether 1 device = multiple concurrent users.

Many Thanks for your assistance. In that use case I would strongly recommend you talk to a Microsoft Licensing expert. In essence you are trying to circumvent the requirements, but from my understanding if you have 300 devices connecting (even indirectly) to access the service, you need 300 device CALs to stay compliant. Also from a technical standpoint, I'd recommend that you strongly test any such scenario. My experiencing in general is that linux rdp clients are not updated often and are not up-to-date enough to be able to handle things like redirections and security that 2008 r2 has and will be in action if the server is a member of a farm. Dear all, I can give the customer 400 RDS CAL Per Device license software and Windows Server 2008 R2 Ent 64 -bit is copyrighted. The network consists of a Server HP DL380 G6 as Remote Management Licensing Manager, 3 hosts Server DL580 G5 32 GB Ram 4 Cpu as TS Server, each server management ThinClient each floor of the Center.

Thinclient configuration using HP T5740 operating system using Microsoft Windows Embedded Standard 2009 and the number thinclient only 300 machines. The duplicated issue is appear on the remote Licensing Manager and Thinclient s can not remote on TS Server because do not enough RDS CAL Per Device license. Here is picture Thank for your helps. Hi, I used to deploy Terminal Services on Windows Server 2003 operating system and run Windows CE on thin machine, and it works stable. Existing systems based on last network infrastructure and network diagram, Present, i just upgrade hardware and operating system Windows Server 2008 R2. Hello, We have windows server 2003 R2 and also we have TS per device cal a total of 5 licenses and we are looking to add five more licenses.

So, we got WinrmtdsktpsrvcsCAL2012 SNGL OLP NL DvcCAL from CDW and we were told that this is a new format and we need to download the iso file and install. However we are touch confused if this is the real deal as when we right click on the windows server 2003 -TS per device CAL there is an option to install licenses: So, the question is are we in the right direction in installing more licences or this is not? If no, please advice us the right course of action. Thanks, GSajja. Hi, for RDS/TS questions, the dedicated RDS/TS forum may be most useful: For information on installing/configuring RDS/TS Licensing, these links may be useful: Don (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions.

Ok, here is the scoop. I have a (Server A) Windows 2003 TS License server configured on a disconnected network. This server was configured with 500 per device Windows 2003 TS CALs. I have installed a new (Server B) Server 2008 TS License server on the same disconnected network.

I called the clearing house and installed 300 2008 CALs and 150 2003 CALs. I called the Clearing house and deactivated Server A. When I deactivate this server, do the 500 license get added back into my total number of available CALs on Microsoft's side? Do I have to turn them in or something? Or does deactivating the server make those 500 now available again for another system if I needed it? Or does this process even matter?

If it only for audit purposes? Hi Kevin, the idea of Licensng is to follow the EULA. So in case, ifyou are not using those 500 CAL's you can indeed keepthem until the day you will need them again. And because you indeed called Microsoft Clearinghouse they will have a note next time you call that they can re-issue the 500 CAL's from the server you diactivated. You can of course upgrade those CAL's to for example 2008 RDS licenses if you have software assurance - double check it with your Local MS representative though. Audit matters for following the EULA in case someone frm BSA will make a visit to your company. Virtualization Conference “PubForum 2011 Dublin”, The Bible of Remote Desktop Services!, Microsoft Virtualization Solutions Day Dublin!

Pessoal como possobloquear/negarum PC especifico, que no membrodo meudomniocontoso.coma acessar meuTS 3389: 7777? Neste caso ousuriopegou os dados ex: (IP 200.216.) de um PC da minha rede e digitou na seu note particular e esta usando meu TS do seu PC de casa, lan house etc. Porque estejsabe o IP de WAN do TS e a porta que eu utilizo fazendo o redirect. Existe algum jeito de eu no engolir esta afronta, j que qualquer usurio/PC do mundo usa meu TS se: Ousuriosouber o IP de WAN A porta E sua conta estiver ativa no AD (logico) OBS: Meu TS libera licenas per device, no posso fazer uma regra no ISA aceitando apenas o IP xxx.xxx.xxx.x j que outros usurios usam modens 3G Claro, Vivo e TIM para acessarem este TS. S complementando eu acho que tem como voc liberar o Acesso TS s para quem tem certificado instalado, ou seja, s acessa que esta com o certificado Digital instalado na maquina. Assim os usurio no conseguiro acessar de qualquer maquina. Da uma olhada nesses Links.

- MCP, MCSA, MCTS-ISA,VISTA. Bonjour, Je dispose d'une version Windows 2008 Datacenter R2 et j'ai activ les services des Bureaux distance pour pouvoir me connecter en RDP sur mon serveur. Aprs avoir fonctionn pendant 120 jours correctement le serveur m'indique qu'il ne dispose pas de licences: La session distante a t deconnectee car aucun serveur de licence n'est disponible pour fournir une licence.

Contacter votre administrateur J'ai activ le gestionnaire de licences Terminal Server et au moment d'installer les licences il me demande un code d'activation. Je n'en possde pas car je souhaite simplement activer les connexions TS permettant l'administration comme j'ai pu le lire ci -dessous Quelle est la diffrence entre une licence CAL Windows Server et une licence CAL Terminal Services (TS)? Une licence CAL Windows Server est ncessaire lorsquun utilisateur ou un poste de travail souhaite utiliser ou accder, directement ou non, au logiciel serveur Windows Server 2008. En outre, si lutilisateur ou le poste de travail utilise ou accde aux services Terminal Services de Windows Server, une licence CAL TS est aussi ncessaire. Seule exception cette rgle: jusqu deux utilisateurs ou deux postes de travail peuvent accder au logiciel serveur des fins dadministration uniquement, sans ncessiter de CAL Windows Server ni de CAL TS.

Comment dois je procder pour activer ces connexions administratives? Merci de vos rponses. I currently run Windows 2000 TS server with 300 per device licenses. I am planning to slowly phase in Windows 2008 RD servers to replace the old 2000 servers. I would like to set the 2008 licensing server to use per user mode with the new licensing which will mix my licensing with 300 per device (win 2000) and 200 per user (win 2008 and under).

I know 2000 will not accept per user licensing. Will this model cause any issues that my stop users from being able to logon or get a valid license to connect on ether set of servers? Hello, If your plan is to create a new RDS farm or standalone RDS and move users by groups which means you will have both solutions running in // then installing a RDS Licensing server with Per User RDSCALwith the RDS solution configured to use that licence server.

In my opinion everything will go fine. Per User or Per device is something, as far as i know,that is enforced by the TS not the client. So the client can logon on both solutions. In this kind of migration the user profil cannot be kept because w2k and w2k8 are non compatible.so you will need to create a new profile repository for hosting w2k8 profiles.

Hope this will help. Let me know Angelo. Hi, You do not need to install Per User or Per Device CAL. The only thing you require is the EULA ( End User License Agreement ) which confirms the number of licenses purchased. In Windows 2000 and Windows Server 2003, we have the license logging service. However, because of original design constraints and evolving license terms and conditions, LLS cannot provide an accurate view of the total number of CALs that are purchased as compared to the total number of CALs that are used on a single server or across the enterprise.

As a result, this service is disabled by default on Windows Server 2003 and is completely removed on Windows Server 2008 and Windows server 2008 R2. Description of the License Logging Service in Windows Server Operating Systems Technology changes life. I have an existing Windows 2003 TS Licensing server.

This is used to deploy per device CALs to 1000 devices. I plan to install a 2008 R2 RDS Licensing server and install our 750 Per User RDS CAL's to the new 2008 R2 RDS server as well as migrate the 1000 Per Device CALs to the new 2008 RDS Licensing Server so I have a singe licensing server. The existing 2003 TS servers are configured to use the existing 2003 TS Licensing server by registry key and therefore I will need to manually update them and point them to use the new 2008 R2 RDS Licensing server once the TS CAL's have been migrated across. What happens to the existing 2003 TS Servers when I deactivate the 2003 TS Licensing server? Will everything will continue to work as usual but I have 120 days to update the registry key on the existing 2003 TS servers to use the new 2008 R2 RDS licensing server? Hi, Thanks for your post in Windows Server Forum. After referring your post, I can understand that you need to deactivate the current Server 2003 TS Licensing Server and migrate to new Server 2008 R2 RDS Licensing Server.

The migration of a license server requires three stages. - First, you must activate the new license server. - Next, you need to deactivate the old server. - Lastly, you need to move all the licenses from the old server to the new server. After Terminal Server Licensing is installed, the server becomes a license server and you are asked whether you want to activate the license server. Activating the license server is highly recommended.

Terminal Server running on Windows Server 2003 operates for 120 days before it must discover an activated license server. Note: If you do not activate the license server within 120 days, Terminal Server will no longer operate. Refer below links for more understanding for migration and activation of TS Licensing Server. Migrating your Terminal Server License Server 2. RDS: The license server must be activated before you can install RDS CALs onto the license server 3. Remote Desktop Licensing website 4. You need to call Microsoft Clearing house, for confirmation code.

Terminal Server Licensing and Internet Communication Might This Helps! Hello, We have windows server 2003 R2 and also we have TS per device cal a total of 5 licenses and we are looking to add five more licenses. So, we got WinrmtdsktpsrvcsCAL2012 SNGL OLP NL DvcCAL from CDW and we were told that this is a new format and we need to download the iso file and install. However we are touch confused if this is the real deal as when we right click on the windows server 2003 -TS per device CAL there is an option to install licenses: So, the question is are we in the right direction in installing more licences or this is not? If no, please advice us the right course of action. Thanks, GSajja. Installed RDS Licensing Server on Windows Server 2008 R2 Datacenter VM.

RDS license server activated. Per Device CALS for both 2003 TS and 2008 RDS installed. AllCitrix Presentation Server 4.5 on Windows 2003 R2 x64 SP2 changed to use this license server and confirmed that they are also requesting Per Device CALs - as they always have. All servers found the licensing server anda popupbox declared itas a valid Windows 2003 TS licensing server, when updated. The RDS server does not show any licenses being issued, but does have this error in the event log repeatedly: Log Name: System Source: Microsoft-Windows-TerminalServices-Licensing Date: 9/3/2010 9:04:04 AM Event ID: 21 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: TS0.scdl.local Description: The Remote Desktop license server TS0 does not have any remaining permanent Remote Desktop Services client access licenses (RDS CALs) of the type Windows Server 2003 - TS Per Device CAL. As a result, the Remote Desktop license server cannot issue RDS CALs of the type Windows Server 2003 - TS Per Device CAL to the Remote Desktop Session Host server 10.34.10.22. To resolve this problem, verify that the Remote Desktop licensing mode configured on the RD Session Host server matches the type of RDS CALs installed on the Remote Desktop license server.

If required, purchase and install additional RDS CALs as needed for this Remote Desktop license server. The error is still being recorded on all Citrix farm servers.

As of today the number of issued licenses is 22. My concern in the beginning was that it wasn't issuing any licenses.

TS licenses expire after roughly 90 days and our experience is that there are some expirations/renewals occurring every day. When this wasn't happening for 3 or 4 days after setting up the new RDS license server, I thought that I had missed something. By the way, the new license server is a virtualmachine using Windows Server 2008 R2 Datacenter. I still think that 22 issued licenses is too few for having gone 3 weeks now, but it does seem to be issuing licenses. I was going to wait the full 90 days and see if all TS licenses are renewed. Hi i have installed ESX server, and on another machine installed infrastructure server plus licence server, i have add the licence file that i got from Vmware. When i go to licence manager in the console it says i have 10 available.

BUT, when i connect an ESX server (v3), i get the message that i don't have enough licences. I have generated several other licence files, but get the same error. Then, have generated several other licence files, ONE 'Licence per host' and one 'licence Server'.

On the ESX Server (2 server for the moment), i put one licence per host with a file licence, and in the console Virtual Center, i put another licence hosted by the licence server (it's another file); IT'S WORK PROPERLY. This configuration is good?, Any problems? Thanks for reply. If you hace a license server, you don't have to put any files on your hosts. There is one step I forgot the first time I configured licensing, and it took me some time to figure it out: 1. On your Virtual Center console, select one of the ESX hosts. Click on the Configuration[/b] tab 3.

Under Software[/b], click on '[i]Licensed Features[/i]' 4. On the right-hand panel, make sure youe ESX hosts has the licenses you want properly assigned. If not, click on 'Edit.' [/i] and add/remove licenses and add-ons as required. Hi (I'm french, sorry for my poor english), I work in a company. We have a client (windows server 2003) with 29 CAL TS 2003 by device.

Yesterday thay had a formation, and some people come to use their terminal server acces. They got a acess licence acces, which could be used for 90 days. But now there is no longer licence available, and some employees of this companay can no longer connect, beacase there is no more licence available.

But some of the licnce are no longer needed, but I didn't success in removing them from the terminal server licence manager 2003. Is it possible to remove an access from a machin to have a new licence free for people to be able to connect nox?

I hope you understand my english, thanks a lot for th help! Tengo un W2003server que es servidor de TS y de licencias; Hemos estado con licencias temporalesy ayer agrege algunas permanentes. ElTerminal Server Licensingdice: Existing Windows 2000 Server -TS Sevices CAL Tolken (per device);Built-in;Unlimited;Unlimited;0 Windows Server 2003 -TS Per user CAL;Open;10;10;0.

Nos conectamos desde XP al servidor y en ningun momento cambia las licencias 2003 Per user de 0 a 1. Pruebo con tsctst.exe en el PC y me dice: The client does not have a license Esto esta correcto?