Permissions compatible with pre-Windows2000 servers

Discussion in 'Microsoft Windows 2000 Upgrade' started by Guest, Jul 1, 2005.

  1. Guest

    Guest Guest

    We just migrated an NT4 domain (15 servers/200 clients) to Win2003 AD. It
    went smoothly except for one dialogue box that spooked us into choosing

    "Permissions compatible with pre-Windows2000 servers".
    "Select this option if you run server programs on pre-
    Windows2000 servers or on Windows2000 Servers that are
    members of pre-Windows2000 domains."

    Our SQL7 servers (e.g. "server programs") run on NT4 member servers; as a
    result, with SQL being critical to our business, we chickened out and kept
    the pre-Win2000 perms and also decided to avoid raising the Windows domain
    functional level to native mode.

    I realize that pre-Win2000 compatible perms refers to allowing the Everyone
    group into the Pre-Windows 2000 Compatible Access group; I always thought
    this mattered mainly for NT RAS servers but taking this dialogue literally, I
    don't want something with SQL7 running on NT member servers to break and then
    have only myself to blame for not having heeded this message. In case anyone
    suggests that only DCs are involved with going native, I would say "yes, I
    think this too" but when Microsoft presents such a message, I'd better have
    some valid justification for not taking it very literally.

    We want to strengthen the perms and then go native for a variety of good
    reasons but does Microsoft mean that SQL7 might be broken if we use it on NT4
    member servers in an AD domain? It is literally an "application" running on
    NT4 which is a "pre-Windows2000 server". This MS statement seems to suggest
    I should first upgrade the OS on which SQL7 runs from NT to 2000/2003 before
    proceeding with any more domain work; we intend to upgrade SQL to 2000 or
    2005 (we already purchased the licensing for this) but this will have to be
    an implementation for another time.

    Is there any danger in going with the post WinNT perms and then shifting the
    domain to native mode or are we being overly cautious? I am sure we are
    being too cautious but would someone please tell me why? We would also
    appreciate hearing of anyone who runs SQL7/NT4 servers under a Win2000 or
    Win2003 AD without the compatibility permissions and possibly in a native
    mode domain.

    Please forgive the length of my post and I thank you in advance.
     
    Guest, Jul 1, 2005
    #1
    1. Advertisements

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. E. Bach

    Warning! Windows2000 SP4 "feature" disallows SBS/sp3 connections!!

    E. Bach, Jul 28, 2003, in forum: Microsoft Windows 2000 Upgrade
    Replies:
    0
    Views:
    465
    E. Bach
    Jul 28, 2003
  2. Slavas

    Can't upgrade from Windows ME to Windows2000

    Slavas, Sep 12, 2003, in forum: Microsoft Windows 2000 Upgrade
    Replies:
    5
    Views:
    149
    Slavas
    Sep 13, 2003
  3. Sekhar

    Unattend installation of Windows2000 professional

    Sekhar, Feb 6, 2004, in forum: Microsoft Windows 2000 Upgrade
    Replies:
    1
    Views:
    222
  4. bbok

    Windows2000 can not support OVER 128GB IDE HDD?

    bbok, Aug 8, 2004, in forum: Microsoft Windows 2000 Upgrade
    Replies:
    1
    Views:
    321
    Guest
    Aug 12, 2004
  5. Mr. Martinez

    How to install windows XP pro on a existing windows2000 pro

    Mr. Martinez, Aug 18, 2004, in forum: Microsoft Windows 2000 Upgrade
    Replies:
    1
    Views:
    250
    Dave Patrick
    Aug 18, 2004
Loading...

Share This Page