[THIN] Re: autocrated printers stop creating on single client
- From: "Mack, Rick" <RMack@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Sat, 26 Jun 2004 12:10:09 +1000
Hi,
Printcfg should be your primary debugging tool.
If you can manually add a client printer using printcfg, then we're
looking at a client setup issue, so basically cmstart etc isn't doing
it's job. If printcfg fails, then you're looking at something a bit more
basic, possibly a printer alias issue of IMA issue.
Worst case scenario, if printcfg works, is to use that as an interim
workaround.
I've found on a number of occasions that cached printer settings in the
user's profile can cause problems where a user uses the same client
machine at work and remotely (different printers), so the solution may
be as simple as a logoff script to strip out cached printer settings.
Regards,
Rick
Ulrich Mack
Volante Systems
18 Heussler Terrace, Milton 4064
Queensland, Australia
tel +61 7 32467704
rmack@xxxxxxxxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Robert K Coffman Jr - Info From Data Corporation
Sent: Friday, 25 June 2004 11:53 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on single client
I've mentioned this before, but just for the purposes of the thread,
I'll say it again. This happens to me about once a week or so, and the
last step you mentioned is how I fix it (remove/readd the local client
printer.)
I'm absolutely at a loss as to why this occurs. I've compared the
registry and the files, and neither change after the printer is
removed/readded!
My environment:
NT 4 TSE / Citrix XPe
- Bob Coffman
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Matthew Shrewsbury
Sent: Friday, June 25, 2004 9:46 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on single
client
Once again the autocreated printers stopped working for one of
our top Execs (no pressure of course). I took these steps to resolve the
issue.
1) Logged in as administrator on the Windows 2000 SP4
client...autocreated printers worked.
2) Logged in as myself and again autocreated printers worked.
3) Restart PC, logged into PC as user and autocreated printers
don't show up with in Citrix.
1) De-installed the ICA client, and cleaned the registry and
profile of all ica entrys...reboot.
2) Installed PN 7.1....reboot
3) Test with user logged into PC, no autocreated printers.
1) Delete local network printers from Windows 2000 workstation,
reconnect network printers...still no autocreated printers.
2) Run PDManager delete all local printers...all but the
"default" printer delete. Default printer (HP LJ 5500DN) won't delete.
3) Reboot PC, log in as user and PDManager is able to delete
default printer.
4) Reboot one more time for the fun of it....
5) Reconnect network printers, log into Citrix and autocreated
printers WORK!!!!
This is the 4th person I have had this happen with now. Very
annoying when it just stops working for no apartment reason. My plan as
I have always found with Citrix is to move away from autocreated
printers as they just aren't rock solid. At the moment I am writing a
logon script to map printers by group.
Anyone have any more thoughts on this problem? I have had this
occur on Windows 2000 SP3 and SP4.
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA
Network Administrator
-----Original Message-----
From: Matthew Shrewsbury
Sent: Friday, June 18, 2004 5:05 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on single
client
Thanks for all the tips!! I will try a complete clean out of ICA
client, then maybe the printer using PDManager. Anyone know if there
will be a Windows XP friendly version of PD Manager?
Again thanks for all your help:-)
Matthew
-----Original Message-----
From: Steve Raffensberger [mailto:sraffens1@xxxxxxxxxxx]
Sent: Friday, June 18, 2004 4:37 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on single
client
Matthew,
If it's feasible, I'd do periodic backups of folks profile
directories within their C: drives. Then, when one goes bad, you can do
two things. 1. Capture both the old (hopefully good) and new (bad)
profiles to a shared drive for analysis. 2. Restore the old (hopefully
good) profile over the new one. This should be quicker than recreating
it.
Raff
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Matthew Shrewsbury
Sent: Friday, June 18, 2004 3:48 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on
single client
Very correct and in a load balanced farm that is a must
as far as I am concerned. However in our case we don't load balance and
each server has a different set of applications...so the benefits would
be minor. In the future when we switch to load balancing I do plan to
use roaming profiles.
However my problem is not on the server at all. The
problem is on the workstation (Windows 2000) that is running the ICA
client. When the problem occurs and the auto created printers stop
creating I find the only fast fix is to blow away the workstation
profile. I have tried reinstalling the client and it made no difference.
Upgraded clients and that didn't do anything. I think it must be a file
corruption or registry setting that gets corrupted but what actually
causes the problem I have no idea.....
Thanks for your help!
-----Original Message-----
From: Bergman, Bryan L. [mailto:Bryan.Bergman@xxxxxxx]
Sent: Friday, June 18, 2004 3:23 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on
single client
Not confused at all. Whenever you have multiple Citrix
servers, it is considered "best practices" to use roaming profiles.
Even if the user sits at the same workstation at all times and does not
"roam" around to other workstations. When a user accesses an
application deployed via Citrix, that application can be coming from
server A or server B. Lets say that on Monday, the application comes
from server A and on Tuesday it comes from server B. Though it was only
1 user from the same workstation, there are 2 profiles - 1 on server A
and 1 on server B. Those profiles can be different. I.E Changing a
default printer on Monday and not seeing the change on Tuesday. Why,
because his profile was changed on server A and not on server B. Hence
the need for roaming profiles.
_____
From: Matthew Shrewsbury
[mailto:MShrewsbury@xxxxxxxxxxxxxxx]
Sent: Friday, June 18, 2004 3:10 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on
single client
Currently we only have two servers XPS (so no load
balancing). I think you might be confusing the Citrix profiles with the
client profiles. I am talking about the fat Windows 2000 WS client
profiles that is used for accessing the Citrix servers. Roaming profiles
really wouldn't be of much use here as our users don't roam.
Thanks for your input:-)
-----Original Message-----
From: Bergman, Bryan L. [mailto:Bryan.Bergman@xxxxxxx]
Sent: Friday, June 18, 2004 2:56 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: autocrated printers stop creating on
single client
How many Citrix servers do you have? You said that you
delete their profile on the Win2K PC they are working. Have you thought
about utilizing roaming profiles?
_____
From: Matthew Shrewsbury
[mailto:MShrewsbury@xxxxxxxxxxxxxxx]
Sent: Friday, June 18, 2004 2:56 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] autocrated printers stop creating on
single client
I have now noticed at least 3 cases over the last 2
months of a user on Windows 2000 running Citrix Program Neighborhood
(version 6.x and 7.1) find that their auto created printers stop being
created.
The only way I can find to get them to start working
again is to delete there profile on the Windows 2000 PC they are working
on. Once it is recreated and I re-setup all there settings it works
fine.
Does anyone have an idea what causes this? It is
something in there profile but what? If I know what it was I could fix
that instead of recreating the whole profile every time.
Thanks for any suggestions!!
Matthew Shrewsbury,
Network Administrator
#####################################################################################
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this email has been
sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this email is prohibited. If you have received it in
error please notify the sender immediately by reply email and destroy all
copies of this email and any attachments. All liability for direct and
indirect loss arising from this email and any attachments is hereby disclaimed
to the extent permitted by law.
#####################################################################################
********************************************************
This weeks sponsor Emergent Online Thinssentials Utilities
Using the latest software, hardware, networking technologies, proven technical
expertise, proprietary software and best practices, EOL provides
custom-tailored solutions for each client?s mission and specific goals.
http://www.go-eol.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
