+ Post New Thread
Results 1 to 11 of 11
Windows Thread, "Per Room Printing" in Technical; Dear All, I am trying to implement a system in the school where by computers only have access to the ...
  1. #1

    Join Date
    Oct 2005
    Location
    Wakefield, UK
    Posts
    51
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    "Per Room Printing"

    Dear All,

    I am trying to implement a system in the school where by computers only have access to the printer which is in the same room as them..

    To acheive this task, i have found a couple of simple .vbs scripts (see the bottom of this post im sure a lot of you have seen these before)

    How can i implement these on a per room basis? In my active directory I have containers set up for each room, I have tried adding the scripts under computer configuration --> startup and shutdown scripts and also under user configuration logon and logoff scripts but they dont seem to work.

    If i copy these scripts into a test students home folder and run them manually they work fine, so the rights are set up ok.

    Is there a better way that I should be doing this?

    Please help, this would really earn me some much needed brownie points (there is a governers meeting on whether to make me Network Manager on March 14th)!!!!




    My Scripts

    Adding A Printer

    ' Example VBScript to map a printer on a server
    ' Guy Thomas February 2004.
    ' ******************************
    Option Explicit
    Dim netPrinter, UNCpath
    UNCpath = "\\server1\PRLaserjet"
    Set netPrinter = CreateObject("WScript.Network")
    netPrinter.AddWindowsPrinterConnection UNCpath
    WScript.Quit
    ' End of example VBScript

    Removing A Printer

    ' Example VBScript to remove a Printer
    ' Guy Thomas February 2004.
    ' ******************************
    Option Explicit
    Dim DelPrint, UNCpath
    UNCpath = "\\server1\PRLaserjet"
    Set DelPrint = WScript.CreateObject("WScript.Network")
    DelPrint.RemovePrinterConnection UNCpath, true, true
    WScript.Quit

    ' End of Example Script to remove printer

  2. #2
    Quackers's Avatar
    Join Date
    Jan 2006
    Posts
    1,402
    Thank Post
    43
    Thanked 153 Times in 128 Posts
    Rep Power
    55

    Re: "Per Room Printing"

    What i do is create a package to install that script on the local machine, push it out via Active directory/Group Policy Software installs. Then for all users have them run the script on logon. When our students logon group policy runs c:\local\printers.vbs.

    They get the correct printers.vbs depending on which organisational container they are in.

  3. #3
    ChrisH's Avatar
    Join Date
    Jun 2005
    Location
    East Lancs
    Posts
    4,993
    Thank Post
    120
    Thanked 286 Times in 263 Posts
    Rep Power
    107

    Re: "Per Room Printing"

    There are examples of such scripts in the scripts section. They basically see what the name of the machine is and set the printer up accordingly. You must have a good naming structure in place for this.
    Printers are added per user rather than machine so they wont wont work in a start up script. It it however handy to have one in the startup script to get the new drivers on the machine if there are any as it will install as system. If you dont do this then you may have trouble when locked down users are tryign to connect to a new printer.

  4. #4
    Guest

    Re: "Per Room Printing"

    To use your room OUs to set logon / logoff scripts you will need to enable loopback processing.

    Enable the following:

    Computer Configuration\Administrative Templates\System\Group Policy\loopback processing mode

    And select Merge as the mode.

    Restart the workstation.

    Job done.

  5. #5

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,812
    Thank Post
    110
    Thanked 585 Times in 506 Posts
    Blog Entries
    1
    Rep Power
    224

    Re: "Per Room Printing"

    Yes, I use Ric's (heavily modified) printer script in the way ChrisH mentions above. Only difficulty I have is with WiFi Laptops. Its sometimes difficult to predict where they are.

    Perhaps I can query which AP they are connected to somehow?

  6. #6

    Join Date
    Oct 2005
    Location
    Wakefield, UK
    Posts
    51
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Re: "Per Room Printing"

    Quote Originally Posted by SYSMAN_MK
    To use your room OUs to set logon / logoff scripts you will need to enable loopback processing.

    Enable the following:

    Computer Configuration\Administrative Templates\System\Group Policy\loopback processing mode

    And select Merge as the mode.

    Restart the workstation.

    Job done.
    This sounds great, i've just tried enabling the loopback processing on one of the containers, but the scripts don't seem to be applying at the moment.

    I would really like this solution to work, as it would be best suited to our setup

  7. #7
    alan-d's Avatar
    Join Date
    Aug 2005
    Location
    Sutton Coldfield
    Posts
    2,421
    Thank Post
    360
    Thanked 258 Times in 189 Posts
    Rep Power
    76

    Re: "Per Room Printing"

    Quote Originally Posted by Geoff
    Only difficulty I have is with WiFi Laptops. Its sometimes difficult to predict where they are.

    Perhaps I can query which AP they are connected to somehow?
    If you do find a way let me know I tried some time ago using the IP address and/or mac address of the Airstation but couldn't get it to work, but then again I'm rubbish when it comes to scripts

  8. #8

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,812
    Thank Post
    110
    Thanked 585 Times in 506 Posts
    Blog Entries
    1
    Rep Power
    224

    Re: "Per Room Printing"

    It looks possible, but there's precious little information on the MSNdis_80211_*.Blah WMI classes. I guess I'll have to download the WPSSDK from MS. Bah!

  9. #9

    Join Date
    Jan 2006
    Posts
    143
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Re: "Per Room Printing"

    We have developed an approach which uses a shutdown script for the individual machines. We've found it works well for more ad hoc groupings which don't fit into our existing OU structure.

    Using Group Policy, we apply a shutdown script to machines (less likely to be cancelled by eager students) - this checks the security groups of the machine, and if they are of format CanPrintInsertPrinterName , looks in the Group's Description field which contains the relvant Printer share name.

    This then adds the specified printers to the machine in the system context which means that they are available for all users.

    In this way, we can easily manage printer additions to machines - it's simply a matter of plonking them in the right Security Groups.

    Our previous method was to use a little AddPrinter.cmd script (which used rundll32) on shutdown which we applied via Group Policy to our Machine OUs, passing the relevant printer(s) as required.

    Cheers

    Alison

  10. #10
    marco84's Avatar
    Join Date
    Jul 2005
    Location
    Manchester
    Posts
    146
    Thank Post
    4
    Thanked 5 Times in 4 Posts
    Rep Power
    19

    Re: "Per Room Printing"

    The way we do the printing on a per room basis is also using Ric's script. . . .
    http://www.edugeek.net/index.php?nam...ewtopic&t=1076

    Its set as the logon script for pupils through AD, with a few extra lines of code added to map drives.
    Or if you have a .bat logon script you can amend that to run the .vbs script as part of its logon tasks.

  11. #11
    tarquel's Avatar
    Join Date
    Jun 2005
    Location
    Powys, Mid-Wales, UK
    Posts
    1,740
    Thank Post
    13
    Thanked 45 Times in 35 Posts
    Rep Power
    29

    Re: "Per Room Printing"

    I do it with a kixtart script - during user logon.

    Current there is one script for everyone and it is smart enough to know which room and user is logging on, to know which printer to setup for that user. Its pretty quick and works well.

    It does depend on machine names naturally but the user aspect is usually read from which usergroup they belong to i.e. photocopier is only mapped to staff members

    Regards
    Nath

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 31
    Last Post: 30th June 2008, 10:03 AM
  2. Replies: 7
    Last Post: 19th June 2007, 08:34 AM
  3. Replies: 6
    Last Post: 28th September 2006, 07:06 PM
  4. Replies: 2
    Last Post: 13th June 2006, 09:22 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
  •