Re: recommended TS license setup
- From: "Blake" <blake.duffey@xxxxxxxxx>
- Date: Thu, 11 Dec 2008 10:59:08 -0500
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_domai
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
.
- Follow-Ups:
- Re: recommended TS license setup
- From: Blake
- Re: recommended TS license setup
- References:
- recommended TS license setup
- From: Blake
- Re: recommended TS license setup
- From: Vera Noest [MVP]
- Re: recommended TS license setup
- From: Blake
- Re: recommended TS license setup
- From: Blake
- Re: recommended TS license setup
- From: Vera Noest [MVP]
- recommended TS license setup
- Prev by Date: Re: recommended TS license setup
- Next by Date: Redundant Terminal Services Gateway Server
- Previous by thread: Re: recommended TS license setup
- Next by thread: Re: recommended TS license setup
- Index(es):
Relevant Pages
|