Control Windows 2003 Terminal Server and RDC with Windows 2000 GPO

Posted on 2006-05-08
Last Modified: 2010-04-13
I have a Windows 2000 AD deployment, and I have one Member Server running Windows 2003 R2 that is also a Terminal Server.

I only run one proprietary application in the Terminal Server, but I need to run 5 difference INI settings files depending on which remote branch the users are connecting from.  Terminal Server Remote Desktop Client allows me to "start the following program when I connect," but I want to be able to enforce this using AD-based GPO

The problem I have is that Win2k AD GPO for Terminal Services does not show this functionality.  The Windows 2003 GPO settings for Terminal Server have the function that I require.  I know I could use the LOCAL GPO settings directly on the Terminal Server, but I do not then have the ability to change the .INI argument depending on WHERE they are connecting from.  I need to be able to enforce a user connecting to TS to run a specific application with a changing argument (depending on which branch they are connecting from).  

Branch A would run an EXE that passed "filename.exe -branch_a.ini"
Branch B would run the same EXE but with the argument as "filename.exe -branch_b.ini"
Branch C would run "filename.exe -branch_c.ini"

So, if I could just get the Windows 2000 AD GPO to give me all of the options presented in a Windows 2003 GPO, I would be laughing.

Having said all of that... How can I get the Windows 2003 GPO "Terminal Services" settings for the Remote Desktop Client to be configurable from within the Windows 2000 AD&U Policy Templates?

My clients are a mix of Win2kPro and WinXP Pro, but all of the Win2kPro clients will have the updated RDC client installed, and as such they should be fine receiving GPO settings for which program to run.
Question by:Hayzeus
    LVL 48

    Accepted Solution

    Hi Hayzeus,

    laugh away my friend, you can import 2003 ADM files into 2000
    LVL 28

    Assisted Solution

    Info: when using current ADM templates on Windows 2000 you can run into this error when starting gpedit:

    "The following entry in the [strings] section is too long and has been truncated" error message when you try to modify or to view GPOs in Windows Server 2003, Windows XP Professional, or Windows 2000

    See here for solution:

    Author Comment

    Thank you both very much.  I split some points out as I did run into the issue raised by Mpfister.

    You're both Grade A in my books :)

    LVL 28

    Expert Comment

    :) thanks for the points
    LVL 48

    Expert Comment

    thankyou :)

    Featured Post

    Enabling OSINT in Activity Based Intelligence

    Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

    Join & Write a Comment

    NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
    Outlook Free & Paid Tools
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    20 Experts available now in Live!

    Get 1:1 Help Now