RDM as Citrix Published app has black screen when selecting session

Hello,

Could you please try the following solution that was helpful for other customers?

With the tool Winspector we could find out what the RDM application ID is and which you had to use.
Then you need to add a class name of RDM in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CITRIX\wfshell\TWI



You can also find the detailed information on the following web page.
http://techgenix.com/seamless-application-explained/

Let me know if this solution helps to resolve your issue too!

Best regards,

Hi,

I found the ClassName of RDM in my case (which is a cryptical name: WindowsForms10.Window.8.app.0.2b89eaa_r14_ad1 :)), but not sure what flags could be usefull for me.
Tried with flag 0x80, but no result.

Any suggestions?

What version of Citrix Receiver\Workspace are you using? Does this issue occur using Workspace for HTML5?

Never used HTML5 receiver.
I have version 19.11.0.50 of the Workspace app. But also a collegue with version 19.9.0.21 has the same experience.

Use the HTML5 client a lot to isolate the issue, I suspect it will work and the issue is with the the seamless application. Is the end device single screen or multi-screen display? If multi does it work normally in single screen display.

I have HTML5 client not available at the moment, so need to appy that for testing.
I used multi-screen, but also single screen has the same issue.

HTML5 will probably resolve the issue but the experience changes since the app is locked in the browser.

I haven't started looking at Win2019. Don't have any other suggestions. Good luck.

Hi
We have the same issue
arno02 have you found a solution?

Hello,

This issue seems to be on Citrix and Microsoft side. From many articles I have read online, it seems that the computer must have the latest GPU drivers installed, the Windows desktop zoom must set at 100%, or it could be a single Microsoft KB that needs to be installed. Here are few articles but not sure if they are relevant in your situation.
https://gridforums.nvidia.com/default/topic/2056/xenapp/published-application-black-window/
https://support.citrix.com/article/CTX218217
https://support.citrix.com/article/CTX225819
https://support.citrix.com/article/CTX235681

Best regards,

Hello,

As an additional information, please check if your Citrix VDI version is at least 7.18 or above according to the following article.
https://devolutions.atlassian.net/servicedesk/customer/portal/1/article/709459992

Best regards,

Hi Érica,

Many thanks. I can confirm this works. The black square which is visible in the original post is gone when opening a session.

If you apply the fix. Please make sure the the Window ID is in fact WindowsForms10.Window.0.app.0.<version> as WindowHistory for ex. shows
WindowsForms10.Window.8.app.<version> for the main window. The seamless flag option to set is 0x1000 as outlined in the article, which can conveniently be done using the CAXTool or manually in the registry https://support.citrix.com/article/CTX222592


Option Explanation:


FORCE MENU WINDOW TO HAVE OWNER
Value: 0x1000
Explanation: Specifies that Menu Windows will always be re-created on the ICA client with an owner window.

See the attached screenshot for the required CAXTool configuration.

Regards

Hello,

Thank you for your feedback @christoph and glad that you have successfully get rid of the black boxes.

Best regards,

Thanks Christoph, changing the 8 to a 0 in the windowsID did the trick.
Now the black square also disappeared in our environment.

Unfortunately this is not working for us. We have both the issues listed. and the seamlessflags are not working as intended.

Hello,

Which version of the Citrix server and Citrix receiver are installed on the server?

Regards,

Hello David, We are citrix CSP. so we keep it very up to date.


I was also surprised with the seamlesstags x01000 as they are "only" supported as global flags, and not application flags.

We are running server 2019 VDA 1909.1 workspaceapp 1911

Hi,

What makes you think those are global only? Both Citrixs' own CAXTool as well as Citrix article https://support.citrix.com/article/CTX219996 list them as per application (window) flags.

Regards

I was looking at https://support.citrix.com/article/CTX101644 and in the documentation, looking at "per application" seamlessflags.

But in any case, regardless. the flags, are not solving our issue.

I am setting it with a machine gpo, during boot.

Alright, i just checked, and the ClassID differs, depending on what VDA i am logging on to.

on vda1 and 4 = WindowsForms10.Window.8.app.0.db0535_r13_ad1
on vda3 and 2 = WindowsForms10.Window.8.app.0.14ca613_r13_ad1

Hi,

Base on arno02 comments "changing the 8 to a 0 in the windowsID did the trick."

Could you try to change the Windows.8.app by Windows.0.app ?

Regards,

yes, my seamleaasflags are for

on vda1 and 4 = WindowsForms10.Window.0.app.0.db0535_r13_ad1
on vda3 and 2 = WindowsForms10.Window.0.app.0.14ca613_r13_ad1

already (i had already read that post :)

I don't know with this regkey how it doesn't work.

Is your Citrix Receiver on your local computer is updated? If so, which version I will try to test with the same setup.

Regards,

workspaceapp 1911

right, so I don't have the problem today, but other colleagues did. We compared, and was alike.

i then tested, and opened the app, on the same server, with 2 different users. and the ClassID was different..

windowsforms10.Window.8.app.0.1bb715_r15_ad1 and windowsforms10.Window.8.app.0.1bb715_r15_ad1

Please note, my application flags was:

WindowsForms10.Window.0.app.0.db0535_r13_ad1
WindowsForms10.Window.0.app.0.14ca613_r13_ad1

from earlier testing, but this is totally different.

I will be trying out the "method" flag to resolve this classid name randoming.

HI,

Thanks for the follow-up, please let me know the result.

Regards,

Currently my reg settings is:

SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\WindowsForms10.Window.0.app\

ClassName WindowsForms10.Window.0.app REG_SZ
Type 1000 REG_DWORD
Method 1 REG_DWORD

I have no errors from users. But this is defacto a global application specific flag for alle WindowsForms10 applications. Since the suffix is randomized based on username etc.

Thank for this information it is very useful, I will add it to our help topic.

Regards,