Win2k terminal services in a Win2k3 native mode AD

Discussion in 'Active Directory' started by Clarky, Jan 26, 2006.

  1. Clarky

    Clarky Guest

    Hello everyone!

    Were about to migrate from an NT4 network to a Win2k3 AD. We have a number
    of Win2k TS servers running in application mode and the devices connecting to
    them are Win2k pro desktops. We also have a number of Exchange 5.5 servers.

    I suggested moving the WIN2k TS servers into the AD domain in mixed mode and
    migrating the Exchange 5.5 servers to Win2k3, then increasing the functional
    level to native mode once the migration was complete.

    I've been told that the AD domain has to be in native mode for TS to work
    correctly (something to do with the licence server). Is this person talking
    rubbish?? If this is true, are we not not going to be able to migrate the
    Exchande 5.5 to Exchange 2k3 once the AD is in native mode?
    Clarky, Jan 26, 2006
    1. Advertisements

  2. It would appear that they are talking rubbish. Native mode applies only to
    the DCs that can be used. The following KB discusses upgrading a TS box and
    doesn't mention needing to be in native mode - only that there are benefits
    as soon as you do:
    Paul Williams [MVP], Jan 26, 2006
    1. Advertisements

  3. Clarky

    Cary Shultz Guest


    I might jump in for a second. I think that Paul has this well in hand,

    First off, as Paul stated, Mixed Mode vs. Native Mode specifically refers to
    the type of Domain Controllers that you can have in the environment. In
    Mixed Mode you can have both WIN2000 Domain Controllers as well as WINNT 4.0
    Backup Domain Controllers. However, once you go to Native Mode (and this is
    a one shot deal) you can not longer have any WINNT 4.0 Backup Domain
    Controllers....only WIN2000 Domain Controllers will work. Actually, there
    are a couple of other things that Native Mode allows. Here is an article
    that explains this:

    In WIN2003 there are three Domain Modes: WIN2000 Mixed, WIN2000 Native and
    WIN2003. Please note also that there are two Forest Modes: WIN2000 and

    Please check out the requirements for WIN2000 Terminal Server vs. WIN2003
    Terminal Server. Of key interest is that in WIN2000 Terminal Server the
    WIN2000 Pro and WIN XP Pro clients have a free license to access the TS.
    That means that there is no additional expenditure involved. However, this
    is not the case in WIN2003 Terminal Server. All clients must have a
    license. So, this would mean some more money needs to be spent. Now, I
    have not done much with WIN2003 so please verify that this is still true. I
    know that it was last time I checked (about eight months ago....). Please
    forgive me if this has changed and I am giving you incorrect information.

    I think that what the person was trying to say is that the TSLS requirements
    are a bit different in WIN2003 from WIN2000. Here is a link that might help
    (or maybe confuse even more):
    Cary Shultz, Jan 29, 2006
  4. Clarky

    Cary Shultz Guest

    Er, should have mentioned that in WIN2003 Terminal Server you know have the
    choice as to per User or per Computer. In WIN2000 this choice did not
    Cary Shultz, Jan 29, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.