Re: Terminal services incompatibilities,

From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 10/06/04 

Date: Wed, 06 Oct 2004 13:09:14 -0700

First of all: it is not recommended to install TS in Application
mode on an SQL server! This is bound to give you both security and
performance problems. When you make the switch to Application
mode, the system is tuned very differently and SQL performance
will drop.
Also: you will have to give your users the right to logon locally
on this server, and they will be running all kinds of applications
there, surfing the Internet, downloading viruses, etc. Do you
really want them to do that on your SQL server?
A Terminal Server is a multi-user workstation, and should not have
any other server role.

The warning you received should be taken seriously. It is
certainly true for every application that you want your users to
run within a ts session: such applications must be uninstalled,
then you make the switch to TS in Application mode, and then you
install the applications again, *while the TS is in install mode*.
This last point is the critical point, it is needed to give
applications multi-user capabilities.

You *might* be lucky with your other applications, those that
should not be used by normal users, like backup software and other
management tools. But no guarantees. It's always best to choose
the correct TS mode very early during the installation of your
server.

252330 - Toggling Terminal Services to Application Server Mode May
Cause Programs Not to Work
http://support.microsoft.com/?kbid=252330

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

"Spencer Thomas" <spencer@catalystnet.com> wrote on 06 okt 2004 in
microsoft.public.windows.terminal_services:

> I recently attempted to switch the "mode" of one of my
> clients Windows 2000 Servers to "Application mode" for
> Terminal Services (versus Administration mode) and got a
> nasty warning about applications possibly not
> working/needing to be reinstalled once I made the change.
> Normally I would ignore such warnings, but this warning
> literally listed every application installed on the server
> (SQL Server 2000, Goldmine, Macola, pretty much everything
> listed in add/remove programs). What is the nature of this
> message? Should I heed it's warning? Will I be able
> to "undo" the switch to application mode if it does in
> fact wreck every application on the machine? I was told by
> our Microsoft Rep at Dell that this was no big deal, but
> reinstalling every application on the server would
> certainly be a huge headache. I have only done this switch
> under 2003 Server, never under 2000. Any suggestions?
>
> Spencer

Relevant Pages

  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)
  • Terminal Services Basics
    ... Looking at Terminal Services on Windows Server 2003/Citrix ... Presentation Server 4.5 for the first time. ... other applications. ... install Windows Server 2003 SP2 ...
    (microsoft.public.windows.terminal_services)
Quantcast