+ Post New Thread
Results 1 to 9 of 9
Windows Thread, Printer issues on terminal server in Technical; We have Windows 2003 R2 terminal servers apx.30 for our ultra thin client network. The problem is when the user ...
  1. #1
    lsheldon's Avatar
    Join Date
    Feb 2009
    Location
    Bradford
    Posts
    42
    Thank Post
    4
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Printer issues on terminal server

    We have Windows 2003 R2 terminal servers apx.30 for our ultra thin client network.

    The problem is when the user selects a printer it does not allow them to print, unless a administrator origanaly selects the printer on there login
    The administrator can then delete the printer and the user can still addd the printer themselfs.

    Its like something is not letting the user install possibly the printer drivers.

    Does anybody have any ideas.

  2. #2
    lsheldon's Avatar
    Join Date
    Feb 2009
    Location
    Bradford
    Posts
    42
    Thank Post
    4
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    I wondered if thee is anything i should be setting in gpo ?

  3. #3

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    17,095
    Thank Post
    511
    Thanked 2,309 Times in 1,785 Posts
    Blog Entries
    24
    Rep Power
    803
    Not sure about how to get around it in an automated manner, but I have installed all available printers as administrator, so when a user comes along, they can install/uninstall freely.

  4. #4
    lsheldon's Avatar
    Join Date
    Feb 2009
    Location
    Bradford
    Posts
    42
    Thank Post
    4
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    I could i just dont want to do this on 30 servers

  5. #5
    lsheldon's Avatar
    Join Date
    Feb 2009
    Location
    Bradford
    Posts
    42
    Thank Post
    4
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    One of the message is: You do not have sufficent access to your computer to connect the selected printer.

  6. #6

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,582
    Thank Post
    107
    Thanked 761 Times in 592 Posts
    Rep Power
    179
    Just run a script to install all the printers and then delete them again. This is easiest done using a startup script. The page at http://www.edugeek.net/wiki/index.ph...ed_on_Location shows how to add and delete printers.

  7. #7
    User3204's Avatar
    Join Date
    Aug 2006
    Location
    Wirral
    Posts
    769
    Thank Post
    55
    Thanked 66 Times in 62 Posts
    Rep Power
    33
    We have always found that we need to be an adamin level user to install the drivers for the printers, although I always suspected that this is due to a GPO that was on the system/network.

    We found the solution was to install the drivers for all the printers onto all the machines in advance, since we build the machines and then image them, this means we only have to do it once per new image.

  8. #8

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,582
    Thank Post
    107
    Thanked 761 Times in 592 Posts
    Rep Power
    179
    Since you have 30 terminal servers, I would hope that you would have something to manage them. Citrix XenApp has a feature that replicates printer drivers across all the servers in the farm. This is something else to look into.

  9. #9

    Join Date
    Mar 2008
    Location
    Gloucestershire
    Posts
    32
    Thank Post
    2
    Thanked 2 Times in 2 Posts
    Rep Power
    13
    The problem you are facing is because unlike workstations, Terminal Servers (or Citrix Servers) do NOT allow users to download printer drivers, which if you think about it makes sense.

    Generally, on a workstation a user can download drivers as this will only affect just that workstation and only the users that use that workstation. On a Terminal/Citrix server you have multiple users using that same server, therefore if you do download a 'dodgy' print driver, it will affect a whole load of users - not good. There used to be a time, quite a while ago, when servers would frequently blue screen if you added the 'wrong driver'.

    As mentioned previously, you could do the following:
    1)... Allow users to download drivers, via a policy.
    2)... Install all the necessary drivers, as an admin on that server, probably best to do this at build time.
    3)... If they are Citrix servers then replicate them around using the Console, or use the Universal Print Driver.
    4)... If they are simple Windows Terminal Servers, then you'll have to manually go to each and add the driver, or as an admin, simply connect to the printer, which should add the drivers. Alternatively, you could try and script it, if you have loads of printers, but this will mean copying files and exporting/importing registry keys.

    You might also be able to use 'printmig' which might do the trick of getting the drivers across to all servers?

    HTH
    Last edited by e-class; 8th March 2009 at 03:02 PM.

  10. Thanks to e-class from:

    lsheldon (12th March 2009)

SHARE:
+ Post New Thread

Similar Threads

  1. Please help X32 X64 Printer server issues
    By lsheldon in forum Windows Server 2000/2003
    Replies: 0
    Last Post: 3rd March 2009, 10:57 AM
  2. Licensing issues associated with student remote access to terminal servers
    By meastaugh1 in forum Thin Client and Virtual Machines
    Replies: 2
    Last Post: 24th October 2008, 11:56 AM
  3. Terminal Server 2008 NTLMV2 issues!
    By darknova in forum Windows Server 2008
    Replies: 3
    Last Post: 7th April 2008, 12:35 PM
  4. Eliminating Printer "sessions" on W2k3 Terminal Server
    By Behuck in forum Thin Client and Virtual Machines
    Replies: 12
    Last Post: 17th January 2008, 04:18 PM
  5. Printer Issues;
    By MoTa in forum Wireless Networks
    Replies: 8
    Last Post: 14th November 2007, 12:36 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •