RepairCBDChain.exe
A Utility called RepairCBDChain.exe available for download from the following link
http://support.citrix.com/article/CTX104631
However i have not had any success with this utility repairing the problem.
Client registry Key
Also a registry key can be added on the Client end to get the ICA client to check the state of the clipboard on a regular basis and try and repair it if neccessary (ICA client 10 or newer)
to this add the following key on your client
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\WFClient, add the following value:
CbChainInterval=
Full Details on http://support.citrix.com/article/CTX112434
I have added the registry key to my workstation now and will have to wait and see if it improves the copy and paste reliability.
SessionViewSize
There is also some discussions about the sessionpage memory pool filling up and preventing copy and paste working (and also causing session freezes)
see http://support.microsoft.com/kb/840342
I know it has been quite sometime since you were addressing this, but do you recall ever coming across a solution? I'm testing with the article reference now.
ReplyDeleteNo, I have still not resolved this issue. We still get the copy and paste problem randomly occuring in the environment. We have also seen the copy and Paste problem causing Lotus Notes to hang. Notes goes into a loop with Process Monitor showing the clipboard as the culprint. We have to kill the notes session and log the user off the server. Next logon all works ok again.
ReplyDeleteWe had a call from a user on a copy and paste issue on their Thin Client. The user was trying to PRINTSCREEN in 1 application to another and this failed. Because of limited resource on thin clients we suggested to try ALT+PRINTSCREEN to only copy the active window. This worked.
ReplyDeleteUPDATE: Running the RepairCBDChain.exe inside my Citrix Session did fix the problem on my recent session.
ReplyDeleteI had run the RepairCBDChain.exe on my PC first but that did not fix it. Then ran it within citrix session and it was fixed. I now need to test if it the combination of both that fixes it or if its only required within the TS session.
So waiting for my next failure.