[THIN] Re: autocrated printers stop creating on single client

  • From: Rob Slayden <rslayden@xxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Fri, 25 Jun 2004 13:03:53 -0700

Don't know if this has anything to do with the problem, but at an
integrator-sponsored Citrix workshop yesterday, a Sr. Citrix Sys. Engineer
told the audience that the ICA 8.x client is definitely the client to use
while 7.1 is "buggy." You might give it a try. 
 
rob

  _____  

From: Matthew Shrewsbury [mailto:MShrewsbury@xxxxxxxxxxxxxxx] 
Sent: Friday, June 25, 2004 6: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

 

Other related posts: