Activated Licence Pack but not issuing licenses

I setup Terminal Services and Terminal Services Licensing both on the same
Windows 2003 box. I activated the license over the phone and then also
installed a 100-pack Termianl Serer Per User CAL's.

When I go into Terminal Services Licensing, it shows the server as
activated. It displays the default licensing - Existing Windows 2000 Server
Terminal Services CAL Token (per device), Type is built-in, Total/Available
is Unlimited and Issued is always 0 no matter how many users are connected.

It also shows my added licenses - Windows Server 2003 Terminal Services Per
User CAL Token. For this 100-pack, it displays Type as Volume License, Total
as 100, Available as 100, but then Issued as Not Applicable. I have users
connecting to the server all day long and it never displays that any licenses
are issued. Should I be seeing the issued number change?

I still have about 30 days before my 120-day trial period ends but I want to
make sure that the licensing server will continue to work after the trial
period expires.

Also note that in Terminal Services Configuration I have the license type
set to Per User and I have the License Server Discovery Method set to the
local host.

This is normal behavior. Per User licenses are unmanaged, and
as such will not be issued. That is why you see Issued as Not
Applicable.

Thanks.

-TP

cwaugh wrote:
> I setup Terminal Services and Terminal Services Licensing both on the
> same Windows 2003 box. I activated the license over the phone and
> then also installed a 100-pack Termianl Serer Per User CAL's.
>
> When I go into Terminal Services Licensing, it shows the server as
> activated. It displays the default licensing - Existing Windows 2000
> Server Terminal Services CAL Token (per device), Type is built-in,
> Total/Available is Unlimited and Issued is always 0 no matter how
> many users are connected.
>
> It also shows my added licenses - Windows Server 2003 Terminal
> Services Per User CAL Token. For this 100-pack, it displays Type as
> Volume License, Total as 100, Available as 100, but then Issued as
> Not Applicable. I have users connecting to the server all day long
> and it never displays that any licenses are issued. Should I be
> seeing the issued number change?
>
> I still have about 30 days before my 120-day trial period ends but I
> want to make sure that the licensing server will continue to work
> after the trial period expires.
>
> Also note that in Terminal Services Configuration I have the license
> type set to Per User and I have the License Server Discovery Method
> set to the local host.

Thanks for confirming



"TP" wrote:

> This is normal behavior. Per User licenses are unmanaged, and
> as such will not be issued. That is why you see Issued as Not
> Applicable.
>
> Thanks.
>
> -TP
>
> cwaugh wrote:
> > I setup Terminal Services and Terminal Services Licensing both on the
> > same Windows 2003 box. I activated the license over the phone and
> > then also installed a 100-pack Termianl Serer Per User CAL's.
> >
> > When I go into Terminal Services Licensing, it shows the server as
> > activated. It displays the default licensing - Existing Windows 2000
> > Server Terminal Services CAL Token (per device), Type is built-in,
> > Total/Available is Unlimited and Issued is always 0 no matter how
> > many users are connected.
> >
> > It also shows my added licenses - Windows Server 2003 Terminal
> > Services Per User CAL Token. For this 100-pack, it displays Type as
> > Volume License, Total as 100, Available as 100, but then Issued as
> > Not Applicable. I have users connecting to the server all day long
> > and it never displays that any licenses are issued. Should I be
> > seeing the issued number change?
> >
> > I still have about 30 days before my 120-day trial period ends but I
> > want to make sure that the licensing server will continue to work
> > after the trial period expires.
> >
> > Also note that in Terminal Services Configuration I have the license
> > type set to Per User and I have the License Server Discovery Method
> > set to the local host.
>