?
Solved

change the WI interface fom Dynamic Client Name configuration

Posted on 2006-06-19
3
Medium Priority
?
937 Views
Last Modified: 2008-02-01
How would I change the WI not to use Dynamic Client name configuration? We would require the following script to work . Thye script works but in the dev$ dir the %clientname% is being generating dynamically.

@ echo off
REM Check for HBOWEM32.ini
if not exist \\bks-gps001\dev$\%CLIENTNAME% mkdir \\bks-gps001\dev$\%CLIENTNAME%
if not exist \\bks-gps001\dev$\%CLIENTNAME%\HBOWEM32.ini xcopy c:\Windows\HBOWEM32.ini \\bks-gps001\dev$\%CLIENTNAME% /i
xcopy \\bks-gps001\dev$\%CLIENTNAME%\HBOWEM32.ini \\bks-gps001\TermServerProfile$\%username%\Windows /i /Y
0
Comment
Question by:cogit
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 19

Expert Comment

by:BLipman
ID: 16936228
Instead of using %clientname% can you just use 'client'?  Client is a citrix variable and it may return the real client name

if not exist \\bks-gps001\dev$\client mkdir \\bks-gps001\dev$\client

etc...
0
 

Author Comment

by:cogit
ID: 16936557
that will just make a directory called client.

I did the following and it worked

How to Return the ClientName when Connecting through Web Interface 4.0

Document ID: CTX107112


What are tjhe implitcations of doing the following above:
0
 
LVL 19

Accepted Solution

by:
BLipman earned 2000 total points
ID: 16937487
"the Web Interface server, which cannot detect the device name, continues to use a randomly generated client name when sending workspace control requests to the farm. Therefore, the disconnect and logoff requests will cease to function, because the server farm will not contain any sessions that use the random generated client name" (from a link in the above KB article).  

Sounds like you will break Workspace Control which is responsible for disconnecting and reconnecting sessions in your Web Interface.  You might be able to ease this issue by setting a short disconnect timeout (like 1 minute).  This way, if users fail to reconnect to a broken session the old one will go away shortly.  Do you have concurrent application limits in place?  That might cause some inconvenience.  
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

#Citrix #XenDesktop #POC #Proof-of-concept
Citrix XenDesktop 7.6 Citrix Policies Audio
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
Suggested Courses

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question