I just got done reviewing the following post:
This is what I thought might fix my issue but I wanted to clarify the differences before I shell out the money for the script editor.
My scenario is this:
We have a windows 2003 server environment with one Windows 2003 terminal server. We run Navision financials and just went through a rather painful poorly planned upgrade so we are sorting out the kinks. We were forced to install Navision on the terminal server to run as a remote application when someone logs in because research wasn't done on whether or not the new version would run in our Windows 2000 environment. So the deal is each person has a printer on their local machine and when each user is in terminal server running the program they need access to this share, which unless it is installed on the terminal server under their login, is not available.
Currently the AD contains an OU with the remote users accessing Terminal server listed in there, inside this OU is a VB script that auto launches the application and disallows any other functionality of the terminal server resources. This makes it rather inconvenient to add the shared printer after the fact because i have to go in and remove them from the OU, put them back in the main AD directory, login as each of the users and map their local printer. This normally would be no big deal had this upgrade been tested and planned properly because I could have done it over the weekend without causing issues to work flow, but that is not the case.
So I am wondering is it worth it to build a script for each of these users and map their printers that way or should I just remove them from the OU, login and map, put them back in the OU and go from there. We are only talking about maybe 12 users who need this to happen.
Thanks everyone for the great advice.