Windows NT Re: TS admin mode

  • Thread starter Thread starter Nick_Shmakov
  • Start date Start date
N

Nick_Shmakov

Vera, I really need your help.

I have the Teminal Server running on Remote Administration Mode. Is buying
one CAL only one way to switch this mode to the application mode? Does
Application mode make any difference for the customer who uses the Terminal
Server as a Application server at his network? The root of the problem is the
VPN Cisco Client which is perfectly working at the console connection, but
requires a few additional steps when running on the Terminal session...

Any help would be highly appreciated...

Nick
nshmakov@screamsavers.com.au

"Vera Noest [MVP]" wrote:

> Remote admin mode gives you a maximum of 2 normal + 1 console
> connection simultaneously.
> If you need more simultanuous connections, then you have to install
> Terminal Services (= switch to Application mode), install a TS
> Licensing Server and buy TS CALs for every user or every client
> which is used to connect to the server.
>
> It is beyond me why you would need more than 2 + 1 concurrent
> administrative connections, just for maintenance!
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> "S K Thilakan" <skthilak@gmail.com> wrote on 23 apr 2007:
>
> > Hi all,
> >
> > I need to have 8 admin mode TS connection to a windows 2003 R2
> > server. do I need to have additional licenses for this in the
> > server? how do I configure for around 8 users at a time access
> > this server in admin mode connection.(not application mode
> > connections)
> >
> > Thanks
> > Thilak.
>
 
I don't think that I understand the problem, Nick.
To answer your question: yes, you could install Terminal Services
(implied: in Application Server mode) and buy just a single TS CAL.
That would give you just a single TS connection (+ 1 console
connection), so one connection *less* than you have now.
I'm assuming that you run 2003 on the server, is that correct?

By installing Terminal Services, you change the internal tuning of
the server. It will now be tuned to give priority to foreground
processes (= users running applications on the servers desktop).
That means that the performance of other functions (SQL server,
file and print server, etc) can suffer.
You also have to uninstall all applications before installing
Terminal Services, and re-install them again after TS.

I don't understand where the VPN client comes into the picture.
Currently, you connect to the server with a remote session and then
run the VPN client in the session, is that correct?
What problems does that create?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

<Nick_Shmakov@discussions.microsoft.com> wrote on 15 jul 2007 in
microsoft.public.windows.terminal_services:

> Vera, I really need your help.
>
> I have the Teminal Server running on Remote Administration Mode.
> Is buying one CAL only one way to switch this mode to the
> application mode? Does Application mode make any difference for
> the customer who uses the Terminal Server as a Application
> server at his network? The root of the problem is the VPN Cisco
> Client which is perfectly working at the console connection, but
> requires a few additional steps when running on the Terminal
> session...
>
> Any help would be highly appreciated...
>
> Nick
> nshmakov@screamsavers.com.au
 
Thank you, Vera

I've found some information on your website already. However, I'd like to
get to the understanding of how it works and would be pleased if you can help
me with that.

The Terminal Server /the server that is acting as the Terminal Server is
running on SBS 2003 Standard that I've bought separately. It's now the member
of the domain X. As far as I understood, I cannot install proper Terminal
Server on the SBS, can I?

I installed the Terminal Server Licensing Service on the machine that acts
as the Terminal Server (SBS). I've activated it and now I'm waiting for your
advice whether I still need to buy the terminal server License (Per-User) in
order to switch TS from Remote Administration to the Application mode or
leave it as it is.

CISCO VPN

The customer uses RDC to connect to a TS to run his accountant software.
Then he runs Cisco VPN client in the TS session to get reports from/to the
taxation office. VPN Client should run as the background service and bring up
the connection when the software requests it to do so. It works this way only
when you phisically login to the console of the server. When you do that over
the RDC you have to manually open up the VPN Client in order to complete the
reports transferring. Another words, the service doesn't start over the RDC,
but it showes as "started" if you have a look at the Services at the
management console. Sounds a bit knotty, but if didn't I would already have
an answer :))

So, I don't know whether switching TS to the application mode would make any
difference particular in the way the services work or I have to leave it as
it is and don't bother at all.

Sorry for the messy questions. I hope I"ve explained them well.

Looking forward to hearing from you.

Nick


"Vera Noest [MVP]" wrote:

> I don't think that I understand the problem, Nick.
> To answer your question: yes, you could install Terminal Services
> (implied: in Application Server mode) and buy just a single TS CAL.
> That would give you just a single TS connection (+ 1 console
> connection), so one connection *less* than you have now.
> I'm assuming that you run 2003 on the server, is that correct?
>
> By installing Terminal Services, you change the internal tuning of
> the server. It will now be tuned to give priority to foreground
> processes (= users running applications on the servers desktop).
> That means that the performance of other functions (SQL server,
> file and print server, etc) can suffer.
> You also have to uninstall all applications before installing
> Terminal Services, and re-install them again after TS.
>
> I don't understand where the VPN client comes into the picture.
> Currently, you connect to the server with a remote session and then
> run the VPN client in the session, is that correct?
> What problems does that create?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> <Nick_Shmakov@discussions.microsoft.com> wrote on 15 jul 2007 in
> microsoft.public.windows.terminal_services:
>
> > Vera, I really need your help.
> >
> > I have the Teminal Server running on Remote Administration Mode.
> > Is buying one CAL only one way to switch this mode to the
> > application mode? Does Application mode make any difference for
> > the customer who uses the Terminal Server as a Application
> > server at his network? The root of the problem is the VPN Cisco
> > Client which is perfectly working at the console connection, but
> > requires a few additional steps when running on the Terminal
> > session...
> >
> > Any help would be highly appreciated...
> >
> > Nick
> > nshmakov@screamsavers.com.au
>
 
So the only server you have on the network is an SBS 2003 server,
correct? Btw, it can't be a member server on your network, a SBS
server is always a DC.
If so, then you cannot install Terminal Services on it, that isn't
supported on SBS2003, just because an SBS server always is a DC. So
at the moment, you do not have a Terminal Server at all (TS implies
in Application Server mode), you just have a DC which you can
connect to with Remote Desktop for Administration.
Installing a TS Licensing Server and buying TS CALs is unnecessary,
since you will not be able to switch the SBS2003 server into a
Terminal Server.

If I've misunderstood your post and you *do* have a separate
Windows 2003 server as a member server in your SBS2003 domain, then
you can install Terminal Services on it, and then this TS can use
the TS Licensing Service on your SBS server. If that's the case,
yes, you need to buy TS CALs and install them on the TS Licensing
Server and make sure that the licensing mode of your TS (on the
Windows 2003 server) equals the type of TS CALs that you buy (Per
User or Per Device).

But if that changes the way in which your VPN client works, I don't
know. At the minimum, you would have to uninstall the VPN client
before installing Terminal Services and re-install VPN again
afterwards, while the server is in install mode. It's possible that
that would solve the problem, but I've never used a VPN client
within a TS session.

_________________________________________________________
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?Tmlja19TaG1ha292?=
<NickShmakov@discussions.microsoft.com> wrote on 16 jul 2007 in
microsoft.public.windows.terminal_services:

> Thank you, Vera
>
> I've found some information on your website already. However,
> I'd like to get to the understanding of how it works and would
> be pleased if you can help me with that.
>
> The Terminal Server /the server that is acting as the Terminal
> Server is running on SBS 2003 Standard that I've bought
> separately. It's now the member of the domain X. As far as I
> understood, I cannot install proper Terminal Server on the SBS,
> can I?
>
> I installed the Terminal Server Licensing Service on the machine
> that acts as the Terminal Server (SBS). I've activated it and
> now I'm waiting for your advice whether I still need to buy the
> terminal server License (Per-User) in order to switch TS from
> Remote Administration to the Application mode or leave it as it
> is.
>
> CISCO VPN
>
> The customer uses RDC to connect to a TS to run his accountant
> software. Then he runs Cisco VPN client in the TS session to get
> reports from/to the taxation office. VPN Client should run as
> the background service and bring up the connection when the
> software requests it to do so. It works this way only when you
> phisically login to the console of the server. When you do that
> over the RDC you have to manually open up the VPN Client in
> order to complete the reports transferring. Another words, the
> service doesn't start over the RDC, but it showes as "started"
> if you have a look at the Services at the management console.
> Sounds a bit knotty, but if didn't I would already have an
> answer :))
>
> So, I don't know whether switching TS to the application mode
> would make any difference particular in the way the services
> work or I have to leave it as it is and don't bother at all.
>
> Sorry for the messy questions. I hope I"ve explained them well.
>
> Looking forward to hearing from you.
>
> Nick
>
>
> "Vera Noest [MVP]" wrote:
>
>> I don't think that I understand the problem, Nick.
>> To answer your question: yes, you could install Terminal
>> Services (implied: in Application Server mode) and buy just a
>> single TS CAL. That would give you just a single TS connection
>> (+ 1 console connection), so one connection *less* than you
>> have now. I'm assuming that you run 2003 on the server, is that
>> correct?
>>
>> By installing Terminal Services, you change the internal tuning
>> of the server. It will now be tuned to give priority to
>> foreground processes (= users running applications on the
>> servers desktop). That means that the performance of other
>> functions (SQL server, file and print server, etc) can suffer.
>> You also have to uninstall all applications before installing
>> Terminal Services, and re-install them again after TS.
>>
>> I don't understand where the VPN client comes into the picture.
>> Currently, you connect to the server with a remote session and
>> then run the VPN client in the session, is that correct?
>> What problems does that create?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> <Nick_Shmakov@discussions.microsoft.com> wrote on 15 jul 2007
>> in microsoft.public.windows.terminal_services:
>>
>> > Vera, I really need your help.
>> >
>> > I have the Teminal Server running on Remote Administration
>> > Mode. Is buying one CAL only one way to switch this mode to
>> > the application mode? Does Application mode make any
>> > difference for the customer who uses the Terminal Server as a
>> > Application server at his network? The root of the problem is
>> > the VPN Cisco Client which is perfectly working at the
>> > console connection, but requires a few additional steps when
>> > running on the Terminal session...
>> >
>> > Any help would be highly appreciated...
>> >
>> > Nick
>> > nshmakov@screamsavers.com.au
 
Now everythings is right on spot :)
Thank you so much. I've found a lots of your comments on the net regarding
TS and they've been very helpfull. I've been a bit confused cos none of the
courses that I've passed do far mention about SBS roles at all.. I would
presume perhaps I've missed something .

No, unfortunatelly, all we have is two licenses for SBS 2003, not Windows
Server 2003 Server. So I'll probably end up with setting up the dedicated PC
under WinXP that customer can access using Remote Workplace then. if there is
no other use for the second DC for just one user. Yet. It's going to be
another four users in the next few months but it doesn't make a huge
difference though.

Thanks again,

Nick

"Vera Noest [MVP]" wrote:

> So the only server you have on the network is an SBS 2003 server,
> correct? Btw, it can't be a member server on your network, a SBS
> server is always a DC.
> If so, then you cannot install Terminal Services on it, that isn't
> supported on SBS2003, just because an SBS server always is a DC. So
> at the moment, you do not have a Terminal Server at all (TS implies
> in Application Server mode), you just have a DC which you can
> connect to with Remote Desktop for Administration.
> Installing a TS Licensing Server and buying TS CALs is unnecessary,
> since you will not be able to switch the SBS2003 server into a
> Terminal Server.
>
> If I've misunderstood your post and you *do* have a separate
> Windows 2003 server as a member server in your SBS2003 domain, then
> you can install Terminal Services on it, and then this TS can use
> the TS Licensing Service on your SBS server. If that's the case,
> yes, you need to buy TS CALs and install them on the TS Licensing
> Server and make sure that the licensing mode of your TS (on the
> Windows 2003 server) equals the type of TS CALs that you buy (Per
> User or Per Device).
>
> But if that changes the way in which your VPN client works, I don't
> know. At the minimum, you would have to uninstall the VPN client
> before installing Terminal Services and re-install VPN again
> afterwards, while the server is in install mode. It's possible that
> that would solve the problem, but I've never used a VPN client
> within a TS session.
>
> _________________________________________________________
> 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?Tmlja19TaG1ha292?=
> <NickShmakov@discussions.microsoft.com> wrote on 16 jul 2007 in
> microsoft.public.windows.terminal_services:
>
> > Thank you, Vera
> >
> > I've found some information on your website already. However,
> > I'd like to get to the understanding of how it works and would
> > be pleased if you can help me with that.
> >
> > The Terminal Server /the server that is acting as the Terminal
> > Server is running on SBS 2003 Standard that I've bought
> > separately. It's now the member of the domain X. As far as I
> > understood, I cannot install proper Terminal Server on the SBS,
> > can I?
> >
> > I installed the Terminal Server Licensing Service on the machine
> > that acts as the Terminal Server (SBS). I've activated it and
> > now I'm waiting for your advice whether I still need to buy the
> > terminal server License (Per-User) in order to switch TS from
> > Remote Administration to the Application mode or leave it as it
> > is.
> >
> > CISCO VPN
> >
> > The customer uses RDC to connect to a TS to run his accountant
> > software. Then he runs Cisco VPN client in the TS session to get
> > reports from/to the taxation office. VPN Client should run as
> > the background service and bring up the connection when the
> > software requests it to do so. It works this way only when you
> > phisically login to the console of the server. When you do that
> > over the RDC you have to manually open up the VPN Client in
> > order to complete the reports transferring. Another words, the
> > service doesn't start over the RDC, but it showes as "started"
> > if you have a look at the Services at the management console.
> > Sounds a bit knotty, but if didn't I would already have an
> > answer :))
> >
> > So, I don't know whether switching TS to the application mode
> > would make any difference particular in the way the services
> > work or I have to leave it as it is and don't bother at all.
> >
> > Sorry for the messy questions. I hope I"ve explained them well.
> >
> > Looking forward to hearing from you.
> >
> > Nick
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> I don't think that I understand the problem, Nick.
> >> To answer your question: yes, you could install Terminal
> >> Services (implied: in Application Server mode) and buy just a
> >> single TS CAL. That would give you just a single TS connection
> >> (+ 1 console connection), so one connection *less* than you
> >> have now. I'm assuming that you run 2003 on the server, is that
> >> correct?
> >>
> >> By installing Terminal Services, you change the internal tuning
> >> of the server. It will now be tuned to give priority to
> >> foreground processes (= users running applications on the
> >> servers desktop). That means that the performance of other
> >> functions (SQL server, file and print server, etc) can suffer.
> >> You also have to uninstall all applications before installing
> >> Terminal Services, and re-install them again after TS.
> >>
> >> I don't understand where the VPN client comes into the picture.
> >> Currently, you connect to the server with a remote session and
> >> then run the VPN client in the session, is that correct?
> >> What problems does that create?
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> <Nick_Shmakov@discussions.microsoft.com> wrote on 15 jul 2007
> >> in microsoft.public.windows.terminal_services:
> >>
> >> > Vera, I really need your help.
> >> >
> >> > I have the Teminal Server running on Remote Administration
> >> > Mode. Is buying one CAL only one way to switch this mode to
> >> > the application mode? Does Application mode make any
> >> > difference for the customer who uses the Terminal Server as a
> >> > Application server at his network? The root of the problem is
> >> > the VPN Cisco Client which is perfectly working at the
> >> > console connection, but requires a few additional steps when
> >> > running on the Terminal session...
> >> >
> >> > Any help would be highly appreciated...
> >> >
> >> > Nick
> >> > nshmakov@screamsavers.com.au
>
 
You're welcome, Nick, I'm glad if I have been able to clarify your
possibilities.
BTW, there is a separate newsgroup for SBS questions that you might
find useful:

microsoft.public.windows.server.sbs
_________________________________________________________
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?Tmlja19TaG1ha292?=
<NickShmakov@discussions.microsoft.com> wrote on 16 jul 2007 in
microsoft.public.windows.terminal_services:

> Now everythings is right on spot :)
> Thank you so much. I've found a lots of your comments on the net
> regarding TS and they've been very helpfull. I've been a bit
> confused cos none of the courses that I've passed do far mention
> about SBS roles at all.. I would presume perhaps I've missed
> something .
>
> No, unfortunatelly, all we have is two licenses for SBS 2003,
> not Windows
> Server 2003 Server. So I'll probably end up with setting up the
> dedicated PC under WinXP that customer can access using Remote
> Workplace then. if there is no other use for the second DC for
> just one user. Yet. It's going to be another four users in the
> next few months but it doesn't make a huge difference though.
>
> Thanks again,
>
> Nick
>
> "Vera Noest [MVP]" wrote:
>
>> So the only server you have on the network is an SBS 2003
>> server, correct? Btw, it can't be a member server on your
>> network, a SBS server is always a DC.
>> If so, then you cannot install Terminal Services on it, that
>> isn't supported on SBS2003, just because an SBS server always
>> is a DC. So at the moment, you do not have a Terminal Server at
>> all (TS implies in Application Server mode), you just have a DC
>> which you can connect to with Remote Desktop for
>> Administration. Installing a TS Licensing Server and buying TS
>> CALs is unnecessary, since you will not be able to switch the
>> SBS2003 server into a Terminal Server.
>>
>> If I've misunderstood your post and you *do* have a separate
>> Windows 2003 server as a member server in your SBS2003 domain,
>> then you can install Terminal Services on it, and then this TS
>> can use the TS Licensing Service on your SBS server. If that's
>> the case, yes, you need to buy TS CALs and install them on the
>> TS Licensing Server and make sure that the licensing mode of
>> your TS (on the Windows 2003 server) equals the type of TS CALs
>> that you buy (Per User or Per Device).
>>
>> But if that changes the way in which your VPN client works, I
>> don't know. At the minimum, you would have to uninstall the VPN
>> client before installing Terminal Services and re-install VPN
>> again afterwards, while the server is in install mode. It's
>> possible that that would solve the problem, but I've never used
>> a VPN client within a TS session.
>>
>> _________________________________________________________
>> 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?Tmlja19TaG1ha292?=
>> <NickShmakov@discussions.microsoft.com> wrote on 16 jul 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Thank you, Vera
>> >
>> > I've found some information on your website already. However,
>> > I'd like to get to the understanding of how it works and
>> > would be pleased if you can help me with that.
>> >
>> > The Terminal Server /the server that is acting as the
>> > Terminal Server is running on SBS 2003 Standard that I've
>> > bought separately. It's now the member of the domain X. As
>> > far as I understood, I cannot install proper Terminal Server
>> > on the SBS, can I?
>> >
>> > I installed the Terminal Server Licensing Service on the
>> > machine that acts as the Terminal Server (SBS). I've
>> > activated it and now I'm waiting for your advice whether I
>> > still need to buy the terminal server License (Per-User) in
>> > order to switch TS from Remote Administration to the
>> > Application mode or leave it as it is.
>> >
>> > CISCO VPN
>> >
>> > The customer uses RDC to connect to a TS to run his
>> > accountant software. Then he runs Cisco VPN client in the TS
>> > session to get reports from/to the taxation office. VPN
>> > Client should run as the background service and bring up the
>> > connection when the software requests it to do so. It works
>> > this way only when you phisically login to the console of the
>> > server. When you do that over the RDC you have to manually
>> > open up the VPN Client in order to complete the reports
>> > transferring. Another words, the service doesn't start over
>> > the RDC, but it showes as "started" if you have a look at the
>> > Services at the management console. Sounds a bit knotty, but
>> > if didn't I would already have an answer :))
>> >
>> > So, I don't know whether switching TS to the application mode
>> > would make any difference particular in the way the services
>> > work or I have to leave it as it is and don't bother at all.
>> >
>> > Sorry for the messy questions. I hope I"ve explained them
>> > well.
>> >
>> > Looking forward to hearing from you.
>> >
>> > Nick
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> I don't think that I understand the problem, Nick.
>> >> To answer your question: yes, you could install Terminal
>> >> Services (implied: in Application Server mode) and buy just
>> >> a single TS CAL. That would give you just a single TS
>> >> connection (+ 1 console connection), so one connection
>> >> *less* than you have now. I'm assuming that you run 2003 on
>> >> the server, is that correct?
>> >>
>> >> By installing Terminal Services, you change the internal
>> >> tuning of the server. It will now be tuned to give priority
>> >> to foreground processes (= users running applications on the
>> >> servers desktop). That means that the performance of other
>> >> functions (SQL server, file and print server, etc) can
>> >> suffer. You also have to uninstall all applications before
>> >> installing Terminal Services, and re-install them again
>> >> after TS.
>> >>
>> >> I don't understand where the VPN client comes into the
>> >> picture. Currently, you connect to the server with a remote
>> >> session and then run the VPN client in the session, is that
>> >> correct? What problems does that create?
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> <Nick_Shmakov@discussions.microsoft.com> wrote on 15 jul
>> >> 2007 in microsoft.public.windows.terminal_services:
>> >>
>> >> > Vera, I really need your help.
>> >> >
>> >> > I have the Teminal Server running on Remote Administration
>> >> > Mode. Is buying one CAL only one way to switch this mode
>> >> > to the application mode? Does Application mode make any
>> >> > difference for the customer who uses the Terminal Server
>> >> > as a Application server at his network? The root of the
>> >> > problem is the VPN Cisco Client which is perfectly working
>> >> > at the console connection, but requires a few additional
>> >> > steps when running on the Terminal session...
>> >> >
>> >> > Any help would be highly appreciated...
>> >> >
>> >> > Nick
>> >> > nshmakov@screamsavers.com.au
 
Back
Top