Announcement

Collapse
No announcement yet.

2003 Printing Solution required.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 2003 Printing Solution required.

    History
    I am designing a Large network and Domain installation for a process control network. In this network we are limited to a windows 2003 infrastructre unitl some of the applications can be redesigned for 2008.
    In a process controll network the way they work is not necisarly the best or most optimal way in an IT infrasructre.

    Situation
    In the PCN thay have plants and in these plants they have a operator. this operator account is used in several locations and is a shared account.
    In the PCN they have engineers who wander around to different plants and do engineering work on that plant them move to other location do work there.

    Requirements
    Operator
    Install a printer for the opertator account on the comuter in specific location that the operator is logging in with.
    So for example:
    The operator logs on at site 1, and he needs to have the printer 1 installed for him.
    If the operator logs on at Site 2 the printer of site 2 needs to be installed. But the printer for site 1 should not be installed as well on the Site 2 computer.
    However the operator account may be logged on with 500 different computers at anyone time in 30+ different locations.

    Engineer
    Engineer again needs the same solution as above but he will also be going from plant to the next plant on the domain and that printer in the other plant needs to install when the engineer logs on.

    restrictions
    Printers are not to be installed by the users
    Printers must not be installed on the local computer by the administrator. all installations need to be automatic when a user logs in
    All other printers that engineer is allowed to be installed should not be installed on the computer unless he is physacaly in the location of the printer.
    All solutions need to be a centralised solution and not a local computer solution.
    No client applications to assist with the installation can be used on the local computers.


    Possibilities
    I would accept a script solution which would install with what subnet the compute is in.
    Using active directory to run a login script or some thing like that.

    Many thanks for any help
    Last edited by Fozzy325; 20th May 2010, 15:03.

  • #2
    Re: 2003 Printing Solution required.

    Sounds like you'll want to use both logon and logoff scripts; logon to add whatever printer, and logoff to remove. A quick Google search for 'printer install scripts' came up with several interesting bits, the first being MS KB articles for cmd line methods and VB script methods to add printers.

    Another Google search for 'printer delete script' comes up with more links. Something in there should work. Deleting any printer instance during a logoff should be simple, but the work is gonna be tough depending on how many different types/models of printer there are, spread out.

    Prob have to read the %computername% variable and define which model drivers to load using 'Select Case' statements.


    Hope this gives you some ideas.
    *RicklesP*
    MSCA (2003/XP), Security+, CCNA

    ** Remember: credit where credit is due, and reputation points as appropriate **

    Comment


    • #3
      Re: 2003 Printing Solution required.

      1- Setup a printer server and install all the printers there
      2- Create OUs and put all the computer objects in there to mimic your physical locations/printing locations
      3- Create a GPO and enable "loopback processing policy " and use a logon script to map to the network printer and link the GPO to the required OU. Script sample here: http://www.computerperformance.co.uk...ter_Method.htm
      4- Repeat step three for linking the GPOs to other OUs
      Caesar's cipher - 3

      ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

      SFX JNRS FC U6 MNGR

      Comment

      Working...
      X