[THIN] Re: : Is there an easy way to change the ws name setting in the Citrix key?

  • From: "Jim Kenzig http://thethin.net" <jimkenz@xxxxxxxxxxxxxx>
  • To: <citrixse@xxxxxxxxxxxxxxx>
  • Date: Wed, 9 Oct 2002 18:14:37 -0400

Well it seems it is a bigger issue than I thought...
Deleting the key works fine IF you give users access to PN.  The next time
you open PN the key is recreated.
1. We use a desktop ICA file or Nfuse to launch our apps...therefore our
users never see or do not have access to PN.
(I know NFuse uses the web client...but the ICA file uses the full client,
therein lies the problem)

2. When you delete the key using a reg file it deletes all subcomponents of
the key. Then when you rerun PN it tries to             recreate it and
instead it starts a new installation of the client.  Deleting the key and
then restoring with a Reg file that does not have the client variable and
THEN opening PN is the only way to do it and is the only way around it. Very

3. A blank entry will cause even more havoc as it will be the first in the
list and everyone will be printing to that                  machine.

4. Once this value is set...if it is set wrong, subsequent opening of PN
does not fix it...you still have the problem and your user can't print.

Best solution so far...connect to each registry and do it manually. How we
got 200 machines out before noticing this is beyond me.

John Vorchak sent me an exe to put in a script that will read the machine
name and replace this entry that I am going to test tommorow.  I'll keep you
all posted.  I BET I am not the only one with this problem.

Jim Kenzig

-----Original Message-----
From: bennykronz [mailto:bennykronz@xxxxxxxxx]
Sent: Wednesday, October 09, 2002 4:42 PM
To: citrixse@xxxxxxxxxxxxxxx
Subject: [Citrix South Technical] Re: FW: Is there an easy way to change
the ws name setting in the Citrix key?


I confirmed this here as well.  We have deployed a lot of new
workstations with the 6.2.986 client and these new clients do not
have this issue.  However, my machine is running the 6.3.1050 client
and it is reading the name from the registry key you referenced.
Glad you brought this up before we started deploying 6.3......

As to how to fix it, I am not sure.  I will play with it and see if I
can figure something out.


--- In citrixse@xxxx, Jim Kenzig <jimkenz@xxxx> wrote:
> Hi Folks,
> Here is my dilemma.  We cloned all of our workstations with the
> client preinstalled.
> Well we started putting the new machines out and have learned that
> clients connect the computername is coming up the same for all of
them. Thus
> when they print it is anybodies guess as to where the print job
will go. The
> name is not coming from the wfcname.ini, rather it is coming from
the Citrix
> registry key below.
> Windows Registry Editor Version 5.00
> "DeskTopLink"="\\Documents and Settings\\All
> Program Neighborhood.lnk2"
> "ClientName"="computername"
> I tried creating a reg file and setting the clientname to the
> %computername%  to see if I could change it via a logon script but
this does
> not work.
> This must be something new with the newer client versions (or with
> W2K)because we have not had this problem with cloning before when
we were on
> NT4.

This weeks sponsor 99Point9.com
99Point9 helps solve your unresolved technical
server-based questions, issues and incidents.

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.


Other related posts: