Terminal server application mode newbie

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Good morning,

I've used TS for remote administration for a while, but am now getting ready
to employ it as an application server. We are primarily a novell shop, but
have a windows 2000 domain, which is expanding. We're currently not using
GPO to manage desktop configuration. All this being said, here's the
situation:

We've installed sql 2000 on one w2k server and ts on another. Both have been
joined to our w2k domain. We will be adding a dc to this remote location,
which is a story for another forum. In trying to figure out how to secure
the server that users will login in to, I found in the user properties an
Environment tab which allows for starting a program when connecting to ts.
It seems like a nobrainer to use that versus creating a ts profile or
creating a group policy and using loopback processing.

I'm looking for others experiences on how they have implemented a terminal
server application. I know there's no ONE way to do this or a BEST way,
other than what would be best for our situation.

Thanks in advance!

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

I would definitively use Group Policies to configure your terminal
server connections.
Gives you much more control, and the advantages become still
bigger when you add a second TS in the future.

You already seem to master most of the principles of GPO, but here
are some links that might be helpfull.

You'll definitively want this hotfix, adds new functionality to
W2K GPOs:
843261 - You cannot use Group Policy settings to configure
Terminal Services roaming user profiles on a Windows 2000-based
Terminal server
http://support.microsoft.com/?kbid=843261

315675 - HOW TO: Keep Domain Group Policies from Applying to
Administrator Accounts and Selected Users in Windows 2000
http://support.microsoft.com/?kbid=315675

278295 - How to Lock Down a Windows 2000 Terminal Services Session
http://support.microsoft.com/?kbid=278295

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"C Hall" <someone@novell.com> wrote on 10 dec 2004 in
microsoft.public.windowsnt.terminalserver.misc:

> Good morning,
>
> I've used TS for remote administration for a while, but am now
> getting ready to employ it as an application server. We are
> primarily a novell shop, but have a windows 2000 domain, which
> is expanding. We're currently not using GPO to manage desktop
> configuration. All this being said, here's the situation:
>
> We've installed sql 2000 on one w2k server and ts on another.
> Both have been joined to our w2k domain. We will be adding a dc
> to this remote location, which is a story for another forum. In
> trying to figure out how to secure the server that users will
> login in to, I found in the user properties an Environment tab
> which allows for starting a program when connecting to ts. It
> seems like a nobrainer to use that versus creating a ts profile
> or creating a group policy and using loopback processing.
>
> I'm looking for others experiences on how they have implemented
> a terminal server application. I know there's no ONE way to do
> this or a BEST way, other than what would be best for our
> situation.
>
> Thanks in advance!

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Vera,
Thanks for the post. Is there a particular reason you wouldn't use "Start
the following program at logon:" in the user properties?

Chris
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns95BCACFD63A4Averanoesthemutforsse@207.46.248.16...
> I would definitively use Group Policies to configure your terminal
> server connections.
> Gives you much more control, and the advantages become still
> bigger when you add a second TS in the future.
>
> You already seem to master most of the principles of GPO, but here
> are some links that might be helpfull.
>
> You'll definitively want this hotfix, adds new functionality to
> W2K GPOs:
> 843261 - You cannot use Group Policy settings to configure
> Terminal Services roaming user profiles on a Windows 2000-based
> Terminal server
> http://support.microsoft.com/?kbid=843261
>
> 315675 - HOW TO: Keep Domain Group Policies from Applying to
> Administrator Accounts and Selected Users in Windows 2000
> http://support.microsoft.com/?kbid=315675
>
> 278295 - How to Lock Down a Windows 2000 Terminal Services Session
> http://support.microsoft.com/?kbid=278295
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "C Hall" <someone@novell.com> wrote on 10 dec 2004 in
> microsoft.public.windowsnt.terminalserver.misc:
>
> > Good morning,
> >
> > I've used TS for remote administration for a while, but am now
> > getting ready to employ it as an application server. We are
> > primarily a novell shop, but have a windows 2000 domain, which
> > is expanding. We're currently not using GPO to manage desktop
> > configuration. All this being said, here's the situation:
> >
> > We've installed sql 2000 on one w2k server and ts on another.
> > Both have been joined to our w2k domain. We will be adding a dc
> > to this remote location, which is a story for another forum. In
> > trying to figure out how to secure the server that users will
> > login in to, I found in the user properties an Environment tab
> > which allows for starting a program when connecting to ts. It
> > seems like a nobrainer to use that versus creating a ts profile
> > or creating a group policy and using loopback processing.
> >
> > I'm looking for others experiences on how they have implemented
> > a terminal server application. I know there's no ONE way to do
> > this or a BEST way, other than what would be best for our
> > situation.
> >
> > Thanks in advance!

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

No, if providing the users with one single application is what you
want, you can use this setting.
Make sure that the session really logs off when the application is
closed. Sometimes there remain other processes in the session,
preventing it from logging of and leaving the user with a blank
desktop without any means to end it gracefully.

I would still use a GPO to do this (create a
"single_application_users" GPO), not the Environment tab, but
that's mostly a question of taste.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"Chris Hall" <someone@microsoft.com> wrote on 13 dec 2004 in
microsoft.public.windowsnt.terminalserver.misc:

> Vera,
> Thanks for the post. Is there a particular reason you wouldn't
> use "Start the following program at logon:" in the user
> properties?
>
> Chris
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns95BCACFD63A4Averanoesthemutforsse@207.46.248.16...
>> I would definitively use Group Policies to configure your
>> terminal server connections.
>> Gives you much more control, and the advantages become still
>> bigger when you add a second TS in the future.
>>
>> You already seem to master most of the principles of GPO, but
>> here are some links that might be helpfull.
>>
>> You'll definitively want this hotfix, adds new functionality to
>> W2K GPOs:
>> 843261 - You cannot use Group Policy settings to configure
>> Terminal Services roaming user profiles on a Windows 2000-based
>> Terminal server
>> http://support.microsoft.com/?kbid=843261
>>
>> 315675 - HOW TO: Keep Domain Group Policies from Applying to
>> Administrator Accounts and Selected Users in Windows 2000
>> http://support.microsoft.com/?kbid=315675
>>
>> 278295 - How to Lock Down a Windows 2000 Terminal Services
>> Session http://support.microsoft.com/?kbid=278295
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "C Hall" <someone@novell.com> wrote on 10 dec 2004 in
>> microsoft.public.windowsnt.terminalserver.misc:
>>
>> > Good morning,
>> >
>> > I've used TS for remote administration for a while, but am
>> > now getting ready to employ it as an application server. We
>> > are primarily a novell shop, but have a windows 2000 domain,
>> > which is expanding. We're currently not using GPO to manage
>> > desktop configuration. All this being said, here's the
>> > situation:
>> >
>> > We've installed sql 2000 on one w2k server and ts on another.
>> > Both have been joined to our w2k domain. We will be adding a
>> > dc to this remote location, which is a story for another
>> > forum. In trying to figure out how to secure the server that
>> > users will login in to, I found in the user properties an
>> > Environment tab which allows for starting a program when
>> > connecting to ts. It seems like a nobrainer to use that
>> > versus creating a ts profile or creating a group policy and
>> > using loopback processing.
>> >
>> > I'm looking for others experiences on how they have
>> > implemented a terminal server application. I know there's no
>> > ONE way to do this or a BEST way, other than what would be
>> > best for our situation.
>> >
>> > Thanks in advance!

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Thanks again!
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns95BEED9FE548Bveranoesthemutforsse@207.46.248.16...
> No, if providing the users with one single application is what you
> want, you can use this setting.
> Make sure that the session really logs off when the application is
> closed. Sometimes there remain other processes in the session,
> preventing it from logging of and leaving the user with a blank
> desktop without any means to end it gracefully.
>
> I would still use a GPO to do this (create a
> "single_application_users" GPO), not the Environment tab, but
> that's mostly a question of taste.
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "Chris Hall" <someone@microsoft.com> wrote on 13 dec 2004 in
> microsoft.public.windowsnt.terminalserver.misc:
>
> > Vera,
> > Thanks for the post. Is there a particular reason you wouldn't
> > use "Start the following program at logon:" in the user
> > properties?
> >
> > Chris
> > "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> > in message
> > news:Xns95BCACFD63A4Averanoesthemutforsse@207.46.248.16...
> >> I would definitively use Group Policies to configure your
> >> terminal server connections.
> >> Gives you much more control, and the advantages become still
> >> bigger when you add a second TS in the future.
> >>
> >> You already seem to master most of the principles of GPO, but
> >> here are some links that might be helpfull.
> >>
> >> You'll definitively want this hotfix, adds new functionality to
> >> W2K GPOs:
> >> 843261 - You cannot use Group Policy settings to configure
> >> Terminal Services roaming user profiles on a Windows 2000-based
> >> Terminal server
> >> http://support.microsoft.com/?kbid=843261
> >>
> >> 315675 - HOW TO: Keep Domain Group Policies from Applying to
> >> Administrator Accounts and Selected Users in Windows 2000
> >> http://support.microsoft.com/?kbid=315675
> >>
> >> 278295 - How to Lock Down a Windows 2000 Terminal Services
> >> Session http://support.microsoft.com/?kbid=278295
> >>
> >> --
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> http://hem.fyristorg.com/vera/IT
> >> --- please respond in newsgroup, NOT by private email ---
> >>
> >> "C Hall" <someone@novell.com> wrote on 10 dec 2004 in
> >> microsoft.public.windowsnt.terminalserver.misc:
> >>
> >> > Good morning,
> >> >
> >> > I've used TS for remote administration for a while, but am
> >> > now getting ready to employ it as an application server. We
> >> > are primarily a novell shop, but have a windows 2000 domain,
> >> > which is expanding. We're currently not using GPO to manage
> >> > desktop configuration. All this being said, here's the
> >> > situation:
> >> >
> >> > We've installed sql 2000 on one w2k server and ts on another.
> >> > Both have been joined to our w2k domain. We will be adding a
> >> > dc to this remote location, which is a story for another
> >> > forum. In trying to figure out how to secure the server that
> >> > users will login in to, I found in the user properties an
> >> > Environment tab which allows for starting a program when
> >> > connecting to ts. It seems like a nobrainer to use that
> >> > versus creating a ts profile or creating a group policy and
> >> > using loopback processing.
> >> >
> >> > I'm looking for others experiences on how they have
> >> > implemented a terminal server application. I know there's no
> >> > ONE way to do this or a BEST way, other than what would be
> >> > best for our situation.
> >> >
> >> > Thanks in advance!