RE: Terminal Server tokens
Vera,
Thank you very much for your prompt reply. As I installed Windows Server,
Terminal Services were already installed as I saw the Terminal Server License
Server, Terminal Server Manager, and the last TS option were all under the
Administrative Programs. So I was just going to install all of the
applications through Add/Remove Programs as I did in my previous
installations of TS.
This server is not going to be in our domain. I am creating a new domain
strictly for this server and a member server, thus why I am making this a DC.
I've maxed out this server's hardware requirements based on the number of
users accessing this machine. It is solely for one of our clients (about 20
users from the same company) and not for my company's use, and it will be
behind a firewall in a data center that we have hired as a co-location
service.
Also, thank you for the advice. I have set up Terminal Servers in the past,
so I do know of the pitfalls that you speak of.
I have always ordered CALs as I know that temporary CALs (or tokens) are
used for (i think) 120 days after the License Server has been activated.
What my problem is since this is used as a hosted service, all of my
licensing is from the Microsoft SPLA licensing agreement. So I cannot mix
license types on this server, they all have to be SPLA (monthly subscription
based). My question is who to contact at Microsoft to get a number of CALs
that I can activate without having to pay ahead of time since I am paying for
the connections on a monthly subscription.
Again, thank you for you prompt response. I truly appreciate all of the
information.
Stewart
"Vera Noest [MVP]" wrote:
> A couple of comments:
>
> * yes, you can install your applications before installing the TS
> Licensing service. But you MUST install Terminal Services before you
> install your applications.
>
> * do NOT make the Terminal Server a DC! A Terminal Server is a multi-
> user workstation. You don't want to have a lot of users on the most
> important server in your domain. It will also have a negative impact
> on performance and make it very difficult to lock down the server.
>
> * test your setup thoroughly before taking it into production! Be
> sure to test all functionality with a normal user account. TS
> configuration is not a trivial job, and once you have live users on
> the system, it's much more difficult to change things.
>
> * CALs and (license) tokens are sometimes used as synonyms
>
> * The Application Services Agreement (ASA) allows Terminal Services
> Client Access licenses (CALs) and licenses for other Microsoft
> products to be allocated on a per-subscriber basis, instead of on a
> per-seat basis. Agreements are available either from your local
> Microsoft account manager or from the following Microsoft Certified
> Partner Members Only Web site:
>
> http://members.microsoft.com/certpartner/partnering/CertifiedPartnerP
> rogram/ASPPartners/LicensingProgram/
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?c2hhcnR6?= <shartz@discussions.microsoft.com> wrote on
> 29 okt 2007 in microsoft.public.windows.terminal_services:
>
> > I need to also say that I was told this by my Software Products
> > reseller. I know that TS License Server offeres temporary
> > tokens for a limited amount of time until CALs are installed.
> > We are using this TS for our clients and therefore the need for
> > SPLA licensing. So my main question is how can I configure the
> > tokens to remain permanent rather than temporary so that it does
> > not affect our client connections to this server.
> >
> > "shartz" wrote:
> >
> >> I have never used the SPLA licensing agreement and I was told
> >> that I have to get Terminal Server tokens rather than
> >> purchasing Terminal Server CALs because the SPLA licensing will
> >> be charging me a monthly usage for the Terminal Server
> >> connections. Has anyone ever heard of this (the tokens)? Does
> >> anyone have any contact information that I can follow up on?
> >> Also, I was wondering if I could install my applications before
> >> I activate the server as a license server. Right now, I have
> >> the server as part of a workgroup and was planning on
> >> activating the server once I get the server to our datacenter
> >> (out of our environment). Should I wait until the server is
> >> in the datacenter or can I activate the server before making it
> >> a DC in our datacenter.
> >>
> >> Thanks in advance for any assistance.
>