[THIN] Re: WI 4 causing issues with random long printer names
- From: "Matthew Shrewsbury" <MShrewsbury@xxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 15:00:03 -0500
Ok I tested it and it did work. The problem is the domain name plus user
name is even longer. Anyway to just set the user name instead of domain
and user name?
Thanks!
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Evan Mann
Sent: Monday, November 14, 2005 2:20 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: WI 4 causing issues with random long printer names
I don't know what they did on the site you linked. If you look at what
I posted, it's an extremely basic code change. I only use Win32 and IE,
so I cannot comment for sure, but I can't see why that simple code
change would have these requirements. I didn't need to add the FQDN of
the WI added to the trusted zones on any computer either.
Note that in the link you provided they have a custom clientdetect.js,
the thing I posted uses the default one. My guess is the
clientdetect.js modification that made is why it's Win32/IE only.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Matthew Shrewsbury
Sent: Monday, November 14, 2005 2:18 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: WI 4 causing issues with random long printer names
Does this have any limitations that you know of? On
http://www.citrix4ge.de/wim/wimcl.htm they said there version only works
with Win32 and IE. Do you know if this version has those types of
limitations?
Thanks!
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Matthew Shrewsbury
Sent: Monday, November 14, 2005 1:41 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: WI 4 causing issues with random long printer names
Thank you very much for the quick response! I'll give it a try and
report back.
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Evan Mann
Sent: Monday, November 14, 2005 1:33 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: WI 4 causing issues with random long printer names
Modify session.cs as follows:
Session.cs info:
Here is the original Code
Change these lines to decide how the client name is chosen:
// Get the client name to use (create a new one, if necessary)
String clientName =
(String)deviceState.get(COOKIE_LOGIN_CLIENT_NAME);
if (!MPSClientNames.isValidUniqueName(clientName)) {
if( config.getWorkspaceControlConfiguration().getEnabled() ) {
clientName = MPSClientNames.generateUnique();
deviceState.put(COOKIE_LOGIN_CLIENT_NAME, clientName); //
Remember for future sessions
} else {
// Use the old client name format when Workspace Control is
disabled for
// compatibility (MPS/U and MF1.8 need the old format to do
roaming
// reconnection).
clientName = MPSClientNames.fromAccessToken( accessToken );
}
}
For example, replacing the lines above with this should always use the
client name derived from the username:
// Always determine the client name from the user's identity
String clientName = MPSClientNames.fromAccessToken( accessToken );
---
This works on WI4. I've been doing it for months. This maintains
workspace control. Credit goes to another poster.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Matthew Shrewsbury
Sent: Monday, November 14, 2005 1:32 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] WI 4 causing issues with random long printer names
I just upgraded to WI 4 and PS4. Now anyone who logs into the WI has a
client name of "WI_Random 17 letter". The good news is the auto created
printers have a better format "PrinterName on Server (WI_LongClientName)
in session x". So normally the users can at least see the printer name
which is all they really need to know.
My problem is one application that has very nasty printing requires that
the printer now be reselected inside of application before it will
print. I believe this is caused by the fact that the printer name is
dynamic each time the user logs on.
1) Is there anyway to shorten the long WI_XXXXXXXXXXXXXXXXX client name?
2) Anyway to set the auto created printers so they will be the same name
when logging on from the same client (E.G. not dynamic printer naming)?
3) Is the reason for the dynamic names session reliability, if so and I
turn it off will to switch back to normal client names?
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
Other related posts:
