Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2237
  • Last Modified:

Setting Default Printer per User in Terminal Services 2008

I have about 100 users in four states utilizing an application as a remote app on Terminal Services.  My app servers are Windows Server 2008.   Currently each user must pick their printer from printer setup within the application when they first launch it.  If they forget, they print to the default app server printer, usually in the wrong state.  I would like to specify the default printer by user.  If I was using RDP, I could put a vbs file in each users startup folder with something like the following:

Set objNetwork = CreateObject("WScript.Network")
objNetwork.SetDefaultPrinter "NJ-IT DEPT"

Since they are using a remote app, not a remote desktop, I'm not sure how to go about this.  Any help would be appreciated.  Thanks
1 Solution

I would think best would be to use group policy to do this.

I don't have a terminal server to play around with but I found this detailed link, maybe this would assist you.

This might be easier to troubleshoot also than a script.

Kind Regards,

Johan Van Zyl
You can also add a login script to the profiles of all affected users and put it on a network share.

Go to the "Profile" tab of the "User Properties" dialog in the Active Directory (Users and Computers)

(more details:
DwightIVDAuthor Commented:
Thanks for the input.  I'm not sure where to start on group policy since I have so many printer choices, which, if I'm understanding this correctly, would each have to be assigned a group.  The group policy preferences is interesting, but not really practical in my application since I have so many workstations in diverse locations.

The login script seems perfect - but it isn't working.  I can't find the proper path on the DC to place the scripts, so I'm putting them on a network share.  When I tried to run them on the app servers from the share (  \\ivdfs\ts\setprintit.vbs ) I get an open file security warning, which I believe is preventing it from running from the script.

I logged into the app server as admin and added the file server to the intranet, and I can now run the script from the server without getting the dialog, however, if I RDP in through TS using a user account, I still get the dialog.

I've given full permission to everyone on the share.  Can someone help me find the netlogon share (I'm not seeing a domain directory in c:\windows on the DC - which is where I think I need to go to find %SystemRoot%\SYSVOL\sysvol\<domain DNS name>\scripts.

If not I'd also like to know what I'm missing to allow the script to run from the share without triggering the open file security warning.


DwightIVDAuthor Commented:
After examining the registry, I discovered that the netlogon directory was on a different drive.  I Placed the script there and it worked fine.

Thanks for the help
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now