Re: recommended TS license setup

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

No, I don't think it's possible.
You need either the appropriate trusts, or multiple Licensing
Servers, or Per Device licenses and anonymous connections enabled.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Blake" <blake.duffey@xxxxxxxxx> wrote on 12 dec 2008 in
microsoft.public.windows.terminal_services:

So is there ANY way to host a single TS server and provide
licenses for machines on different domains as well as stand
alone? Is Per Device CALs the way to go, as you mentioned?

I am in the process of creating a number of VMs which might
serve as TS servers - some on my domain, some on the corporate
domain, some standalone. I'd like to put my License Server on a
single machine and serve the farm as needed.

Sigh...


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:Xns9B71E7089A275veranoesthemutforsse@xxxxxxxxxxxxxxxx
This is not a supported scenario with Per User TS CALs, because
the LS cannot modify the user accounts. It would work with Per
Device TS CALs.
I'm not sure if "not supported" means that it won't work, or if
it only means that you will not be able to use the Per User
license usage tracking utility (and produce a lot of errors in
the eventlog).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Blake" <blake.duffey@xxxxxxxxx> wrote on 11 dec 2008 in
microsoft.public.windows.terminal_services:

I'm going to move my TS CALs to a license server on a
standalone machine

Thanks
Blake

"Blake" <blake.duffey@xxxxxxxxx> wrote in message
news:euyonl6WJHA.5760@xxxxxxxxxxxxxxxxxxxxxxx
That's what I was afraid of - the corporate people aren't
going to allow a two-way trust, and I see errors which I
think are caused by the TS License trying to write to the
corporate AD). (to answer your question the users are in the
corporate AD and the TS boxes are in the ad.nicc domain, but
there is only a one-way trust)

If I fall back to installing the TS license server on a
stand-alone system, will this scenario then work? Can
license server installed on a standalone box issue per user
TS CALs to machine in other domains and/or other standalone
systems?

Thanks Vera,
Blake

"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns9B71A7F62581Fveranoesthemutforsse@xxxxxxxxxxxxxxxx
So the users are in the corporate domain, and the Terminal
Server are in the ad.nicc domain, correct? And ad.nicc
trusts the corporate domain.
I think that you need a two-way trust:

The LS can only issue licenses to Terminal Servers in the
same or trusted domains (which would mean the LS must be in
ad.nicc), but the domain which hosts the user accounts must
trust the domain which the LS is in, otherwise the LS can't
write the Per User license to the user account properties in
the corporate domain.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Blake" <blake.duffey@xxxxxxxxx> wrote on 10 dec 2008 in
microsoft.public.windows.terminal_services:

I am not comfortable reducing my security profile as
suggested to make a stand alone license server function.



Let's suppose we ignore any standalone machines.

Most of my machines are members of the ad.nicc domain.
There is a one-way trust between ad.nicc and the corporate
domain so users can use their corporate credentials to log
into my machines..

Users need to be able to log into ad.nicc machines using
their corporate ID. My CALs are Per User.

Where should I install my TS license server? The ad.nicc
domain or the corporate domain?

Blake



"Blake" <blake.duffey@xxxxxxxxx> wrote in message
news:uIlTYYwWJHA.5764@xxxxxxxxxxxxxxxxxxxxxxx
I had already found your great site Vera. :)

I guess my question is - can I issue *Per User CALs* from
a standalone TS License server to machines in other
domains?

Blake

"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns9B70D8AA3D5D0veranoesthemutforsse@xxxxxxxxxxxxxxxx
Check this:

Can I use a single TS Licensing Server to issue TS CALs
to Terminal Servers in multiple untrusted domains and
workgroups?
http://ts.veranoest.net/ts_faq_licensing.htm#LS_untrusted_
do mai ns

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Blake" <blake.duffey@xxxxxxxxx> wrote on 10 dec 2008 in
microsoft.public.windows.terminal_services:

Most of my machines are members of the ad.nicc domain.
There is a one-way trust between ad.nicc and the
corporate domain so users can use their corporate
credentials to log into my machines.

Some of my machines are standalone.

Users need to be able to log into ad.nicc machines using
their corporate ID, and users need to be able to log
into the standalone machines using local credentials.
My CALs are Per User.

Where should I install my TS license server? The
ad.nicc domain? The corporate domain? Stand alone?

Thanks
Blake
.

Relevant Pages

  • Re: recommended TS license setup
    ... I'd like to put my License Server on a single machine and serve the farm as ... to allow a two-way trust, and I see errors which I think are ... Let's suppose we ignore any standalone machines. ...
    (microsoft.public.windows.terminal_services)
  • Re: RH to Debian migration
    ... > Workstation, so they setup one RHN account, added all 10 machines and then ... I don't know about the Enterprise Workstation license, ... On your DHCP server configure it to ...
    (Debian-User)
  • Re: recommended TS license setup
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... I'd like to put my License Server on a ... going to allow a two-way trust, and I see errors which I ... Let's suppose we ignore any standalone machines. ...
    (microsoft.public.windows.terminal_services)
  • Re: License for a member server
    ... Make sure that the SBS 2003 server is the Licensing Computer. ... click License Site Settings. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: How to add a user with very limited rights
    ... The Windows Server 2003 External Connector license is an optional ... An EC license is not applicable to Web Edition or Windows Small Business ... For more information about External Connector License, ...
    (microsoft.public.windows.server.sbs)