I never tested it, but I would think that using the flag the article
mentions would save the printers in your profile and therefore speed up
printer connection creation at next logon (since the printer info is
already in your profile). Maybe you can do some testing with this?
However, my original comment still applies then, beeing that you need to
find a way to get rid off printers that do not exist anymore or have
been renamed
Since the whole printer creation is not dynamic anymore all printer info
is retained in the user profile and you'll need other means to purge
that info from the user profiles if needed
This can be done through registry hacks (be it scripted or otherwise)
If you use network printers the keys that you need would be
HKCU\Printers\Connections\,,<printserver>,<printer>
See this example from my AppSense config xml file:
DeleteRegKey Hive = "HKEY_CURRENT_USER" Key =
"Printers\Connections\,,GUIPS001,NP01052"
Ben
------------------------------
Msg: #2 in digest
Date: Thu, 9 Apr 2009 07:43:34 -0700 (PDT)
From: Jeff Bolton <beatbox99@yahoo.ca>
Subject: [THIN] Re: Help with Auto-Created Printers
I did read through those and a few others that I found this morning....
Following the steps I found in another article, I tried publishing the
desktop and connecting as a regular user to see if I could manually add
a printer...Oddly enough, there were all there and the correct defalut
printer was selected.
Looks like my problem might simply be impatience....
I have the applications set to launch without waiting for the printers
to be created to speed up launch time. Of course, I was checking the
print options from Word immediately after launching the app. What I
thought was a little odd was that the list of printers available and the
default one selected were different almost every time I launched it both
via the web interface and the PNAgent.
I just did another round of testing via different access methods,
waiting for a minute or two before checking the print options in word
and surprise, surprise, not only are all the printers listed that should
be, but the correct default was selected as well. I also tried changing
the option to wait for the printers to be created before the app
launches and it took almost a full minute before Word launched; however,
all the printers, including the correct default were there.
In the case of our corporate office, we have about 40 printers scattered
throughout the building hosted on two print servers which would explain
the long delay in waiting for all of them to be created. That long of a
delay would be unacceptable to my users. Would changing the registry
key to prevent the deletion of the network printers after a session ends
reduce this delay in launching apps? Is it something worth changing to
satisfy impatient users (like me) or am I better off leaving it entirely
dynamic and just instructing the odd users or two who might be impatient
to simply wait a couple of minutes?
Cheers
Jeff
------
Scanned for Malware and Spam by Open Line Smart E-mail Filter
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://www.freelists.org/list/thin
Follow ThinList on Twitter
http://twitter.com/thinlist
Thin List discussion is now available in blog format at:
http://thinmaillist.blogspot.com
Thinlist MOBILE Feed
http://thinlist.net/mobile
************************************************
No comments:
Post a Comment