[THIN] Re: New Guy

  • From: "Jamie Pepper" <JPEPPER@xxxxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 11 May 2007 14:49:51 -0500

Thanks Neil. This really points me in the right direction. I found
something that does location-based printing in our environment. 
Jamie

>>> "Braebaum, Neil" <Neil.Braebaum@xxxxxxxxxxxxxxxxx> 5/11/2007 9:17
AM >>>
I think this is one of the main problems in the approach that most take
when doing some conditional / logic based grouping or mapping of users
to printers - it's based on some arbitrary - ie group-based security.

Which is just peachy, if your users never roam...

A few years back, when I was first involved in implementing Active
Directory (back when Windows 2000 was the new thing) I designed and
implemented a rationale that did away with that old school, NT-based
groups and printers. I mapped printers based on the workstation somebody
was sat at.

This involved creating an OU structure for printers in AD, that matched
the physical locations of printers. Then I used the location field for
the computer object, to store the name of the printer location OU. Then
I wrote an adsi / vbscript login script that when logging in, checked
the location field for the PC, zipped to that OU, and mapped the
printers that were in that OU.

So it didn't matter where somebody sat (so long as the information in
the location field was correct for the PC) - the printers were
appropriate for the physical location of the PC. And that can work for
thin client sessions, too - because you can always use %CLIENTNAME% to
establish the PC where the session is running.

As an appendix to that, I also wrote a management GUI for the PC
builders / maintainers, to be able to create / move PC objects, so they
were always in the correct OU, and set the location field to the correct
OU for the printers (and also add group memberships for the computer
object (and in very selective cases, remove group memberships) for
application deployment purposes).

Thinking back to when I first implemented thin clients (in 98 and 99) I
did a similar, yet remarkably more simplistic thing for location based
printing - I made sure the device name and the printer share name were
the same (remote locations). The login script then used part of the
mnemonic in the clientname of the thin client to decide on what print
server to use, and then simply mapped a printer of the same name as the
client.

So you see printer mapping can easily be done based on location, and
doesn't need to be based around that old idea of using groups of users.

Neil

> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On

> Behalf Of Jamie Pepper
> Sent: 11 May 2007 14:44
> To: thin@xxxxxxxxxxxxx 
> Subject: [THIN] Re: New Guy
> 
> 
> Thanks Jim. I did think of this. The only thing of it is our 
> security is based on groups. We have a high school group. All 
> members of the group move from lab to lab with in the same 
> building. In the past with a fat client we controlled this by 
> only installing the printer for the lab on the specific lab 
> workstations. With the thinstation the printing has shifted 
> from the workstation to the server. I guess my dilemma is the 
> HS group. I even thought about a script that disables the ip 
> port in the registry. This still would not work with a large 
> group that migrate from lab to lab. 
> 
> Thanks for the help. 
> 
> 
> >>> "Jim Kenzig ThinHelp.com" <jkenzig@xxxxxxxxx> 5/11/2007 
> 8:01 AM >>>
> 
>  You can just set security on the network printers themselves 
> via the security tab in the printers properties applet on the 
> server. This will prevent users whom you don't want to access 
> it using it. 
> Jim
> 
> 
>  
> On 5/10/07, Jamie Pepper <JPEPPER@xxxxxxxxxxxxxxxxxxx> wrote: 
> HI,
> 
> I just started using Citrix and a thin client solution in our 
> labs. I work for a small school district. I have deployed 
> thinstation in two labs. So fare it works great. One problem 
> I have is restricting access to printers. I am using Citrix 
> Presentation 4.5 with Term services on W2K3. On the one 
> server for both labs I have two printers installed. This 
> gives the students the ability to choose either printer. This 
> is not a good idea in a Middle School High School setting. Is 
> there a way to limit printing on the thinstation to only one 
> ip based printer? The only options seems to be sharing LPT1 or USB. 
> 
> Any ideas would be greatly appreciated. 



*****************************************************************************

This email and its attachments are confidential and are intended for
the above named recipient only. If this has come to you in error, please
notify the sender immediately and delete this email from your system.
You must take no action based on this, nor must you copy or disclose it
or any part of its contents to any person or organisation. Statements
and opinions contained in this email may not necessarily represent those
of Littlewoods Shop Direct Group Limited or its subsidiaries. Please
note that email communications may be monitored. The registered office
of Littlewoods Shop Direct Group Limited is 1st Floor, Skyways House,
Speke Road, Speke, Liverpool, L70 1AB, registered number 5059352

*****************************************************************************




This message has been scanned for viruses by BlackSpider MailControl -
www.blackspider.com 
SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com ( http://www.f1u.com/
)
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin 
************************************************

Other related posts: