Even if you use Add/Remove programs to remove the ICA client, there are still bits left over in the registry (pretty easy to find the "Citrix" keys" and nuke those), and also in the Documents and Settings\<user name>\Application Data folder. Again, it's easy to spot the Citrix stuff in that directory and wipe it out. Then try re-installing your ICA client and see if that doesn't fix things up. That might be less pain that blowing away the entire profile and having to set up email, etc., all over again. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Matthew Shrewsbury Sent: Friday, June 18, 2004 2:48 PM To: thin@xxxxxxxxxxxxx Subject: Spam:[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