[THIN] Re: autocrated printers stop creating on single client
- From: "Robert K Coffman Jr - Info From Data Corporation" <bcoffman@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 18 Jun 2004 16:31:53 -0400
I get this on occasion too, but to fix it I remove the local driver
(PDMANAGER to get all of it out of there) and re-add it... I haven't tried
zapping the profile on the workstation.
- Bob Coffman
-----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!
Other related posts:
