[THIN] Re: Network Printing

We use a slightly modified flex profile setup so printers are always created at 
login and dropped at logout.

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of M
Sent: 27 September 2007 22:06
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Network Printing


This has been a very interesting thread.
Ive been toying with this for a bit myself. 
 
Do your users have roaming profiles or mandatory (or Hybrid) ?
Are you siloing servers or have load managed groups ?
What happens if your users roam from one site to another site ... do the users 
get multiple printers stored in their profiles ?
 
 
 

----- Original Message ----- 
From: Anthony Green <mailto:agreen@xxxxxxx>  
To: thin@xxxxxxxxxxxxx 
Sent: Thursday, September 27, 2007 9:49 PM
Subject: [THIN] Re: Network Printing


That sounds very similar to my app!  Only there's no limits and I can map 
printers based on any scenario (machine, user, group). I'm also planning a few 
other criteria for mapping the printers.

 

I've also put an export function in there as well, and soon to have an import 
function, so print mappings can be saved and imported whenever you like.  Handy 
if you have a load of printer mappings that you want to keep.  It can also do a 
cleanup of printer mappings to remove any legacy mappings that have been there 
since god only knows when.

 

Thanks for the offer with the code I should be ok for now, I really like the 
idea of having an approved driver list in the app somewhere though.  Got me 
thinking J

 

Thanks,

Ant.

 

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of 
Angus Macdonald
Sent: 27 September 2007 09:00
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Network Printing

 

We use something similar for mapping NT queues. Here are the basics:

 

An MSSQL database holds a table containing client (machine) names and up to 5 
NT print queue paths in \\server\share <file:///\\server\share>  format. A tiny 
client app runs from the login script, connects to the database and retrieves 
all the queues associated with the client name. Early versions then ran 
con2prt.exe to make the connections but the latest version hooks into 
printui.dll. This hooking allows the client to retrieve the neccessary driver 
name and decide if it's already installed or not - we don't want drivers 
installing automatically and have specifically banned some. Once the driver is 
confirmed as present and safe, another call to printui.dll maps the queue. The 
management UI (what there is of it) is built into our in-house developed 
helpdesk system.

 

There are a few other bells and whistles but it's pretty simple and I can lend 
you the Delphi source code if it would be useful.

Angus

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of 
Anthony Green
Sent: 26 September 2007 23:32
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Network Printing

I'm looking for a bit of advice with an app I'm developing.  I got the idea 
from the hateful way network printers are assigned to users in Citrix 
(policies).

 

Basically, it's a printing app that will map printers for users based on their 
name, group membership, computername.

 

This is all managed from a single console, with a command line tool that does 
the mapping of printers at login time.

 

What features would be the most desireable?...like mapping printers based on 
client IP / IP range?... or deleting any existing printers before mapping new 
ones?

 

Thanks,

Ant.

 

PS           Anyone using anything similar?


Gallai'r e-bost yma gynnwys gwybodaeth gyfrinachol a/neu ddeunydd hawlfraint.  
Os ydych chi'n meddwl eich bod wedi derbyn yr e-bost yma drwy gamgymeriad rydym 
yn ymddiheuro am hyn; peidiwch os gwelwch yn dda â datgelu, anfon ymlaen, 
printio, copïo na dosbarthu gwybodaeth yn yr e-bost yma na gweithredu mewn 
unrhyw fodd drwy ddibynnu ar ei gynnwys: gwaherddir gwneud hynny'n gyfan gwbl a 
gallai fod yn anghyfreithlon. Rhowch wybod i'r anfonwr fod y neges yma wedi 
mynd ar goll cyn ei dileu.
 
Mae unrhyw safbwynt neu farn a gyflwynir yn eiddo i'r awdur ac nid ydynt o 
anghenraid yn cynrychioli safbwynt neu farn Ymddiriedolaeth GIG Gogledd 
Orllewin Cymru.

Gallai cynnwys yr e-bost yma gael ei ddatgelu i'r cyhoedd o dan Gôd Bod yn 
Agored y GIG neu Ddeddf Rhyddid Gwybodaeth 2000.  Nid oes modd gwarantu 
cyfrinachedd y neges ac unrhyw ateb. 

Bydd y neges yma ac unrhyw ffeiliau cysylltiedig wedi cael eu gwirio gan 
feddalwedd canfod firws cyn eu trosglwyddo.  Ond rhaid i'r sawl sy'n derbyn 
wirio rhag firws ei hun cyn agor unrhyw ymgysylltiad.  Nid yw'r Ymddiriedolaeth 
yn derbyn unrhyw gyfrifoldeb am unrhyw golled neu niwed a allai gael ei achosi 
gan firws meddalwedd.


This e-mail may contain confidential information and/or copyright material.  If 
you believe that you have received this e-mail in error please accept our 
apologies; please do not disclose, forward, print, copy or distribute 
information in this e-mail or take any action in reliance on its contents: to 
do so is strictly prohibited and may be unlawful.  Please inform the sender 
that this message has gone astray before deleting it.

Any views or opinions presented are to be understood as those of the author and 
do not necessarily represent those of the North West Wales NHS Trust.

The contents of this e-mail may be subject to public disclosure under the NHS 
Code of Openness or the Freedom of Information Act 2000.  The confidentiality 
of the message and any reply cannot be guaranteed.

This message and any attached files will have been checked with virus detection 
software before transmission.  However, recipients must carry out their own 
virus checks before opening any attachment.  The Trust accepts no liability for 
any loss or damage, which may be caused by software viruses.

Other related posts: