Re: terminal services on domain controller

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

In fact you can go for that, but carefull ntfs permissions and user rights
configuration is required. Also it depends on kind of applications you need
to run. If users are going to use only one application during their
sessions, when you can configure Environment tab in AD users & computers to
start that app automatically. This way is much better than giving full
desktop access for users.

We run such configurations for small customers without problems. But you
probably know that this configuration is not recomended by Microsoft.

Hope this helps. :-)).

Rimantas




"Tom Wern" <TomWern@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:43B53313-ABEF-4DF0-80D1-458EB0889E80@xxxxxxxxxxxxxxxx
> You confirmed the second part of my question - I need second server if I
> use
> SBS2003 (didn't need it with 2000 I think).
>
> However, my main question is with Windows standard edition Server 2003
> running as a domain controller and terminal server what are the
> considerations? I want to do this because it is a very small environment
> and
> justifying another server box and OS would not make sense.
>
> "R.Vilkas" wrote:
>
>> You can't run Win2003SBS in application mode. You need separate server in
>> SBS environment, but you can use SBS CAL's as terminal server CAL's.
>>
>> Rimantas
>>
>> "Tom" <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:DF3A6638-33B5-4586-ACCE-4FA5F933580E@xxxxxxxxxxxxxxxx
>> > Are there any other considerations other than security in running
>> > terminal
>> > services on a Windows 2003 domain controller?
>> >
>> > This is for a small environment and to install a second server and OS
>> > just
>> > for 4-5 terminal services sessions would seem to be overkill? I wish I
>> > could
>> > run terminal services on a SBS 2003 box, but it is not possible is it?
>> >
>> > Comments/suggestions, please.
>> >
>> > Thank you.
>> >
>> >
>>
>>
>>


.

Relevant Pages

  • Re: Server Configuration Help
    ... Domain machines should always use only the domain internal DNS server and NO externals like the ISP's, this should be configured as a FORWARDER ... I'm not really looking to upgrade from the SBS ... configuration, but ideally to start from scratch with the setup (or ... a working production environment. ...
    (microsoft.public.windows.server.setup)
  • missing tabs under local user properties on WTS 2003!
    ... We installed and configured WTS 2003 in an intranet environment for running ... RDP properties on "Environment tab" under "Terminal Services Configuration" ... The tabs at the beginning are "General, Member Of, Profile, Environment ... Can it be related with "Terminal Server licensing" because we have installed ...
    (microsoft.public.windows.terminal_services)
  • Re: VBD
    ... > Please review the environment configuration required on the windows 2000 ... > configuration before the file would work on that environment as well. ... > will need to recreate the proper environment on the new server. ... >> pls. help me find the solution to my problem, i want to use windows server ...
    (microsoft.public.windows.server.sbs)
  • Re: The current topology is not supported. (HELP)
    ... I am not sure I understand your comment about the all-in-one environment. ... >> Small Server Environment ... > configuration on a single-cpu machine three months ago, ... > installation on the VMWare instance reports "Topology not supported". ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Patch management on TS
    ... have some sort of test environment even if it's only a VM environment. ... VMWare GSX is free, MS Virtual Server ... Microsoft MVP - Terminal Server ... Test the updates in a lab environment, or one server in your terminal ...
    (microsoft.public.windows.terminal_services)