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.