[Teams 2.0 Recipe]

https://www.stephenwagner.com/2023/10/07/deploy-install-new-teams-vdi/

 

[Printing to redirected LPT ports no longer works like expected from VDA version 2203 and above]

Problem solved. 

 

Disabling the policy "Virtual channel allow list" did the trick

 

“Starting with Citrix Virtual Apps and Desktops 7 2109, virtual channel allow lists are enabled by default.” – from https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/policies/reference/ica-policy-settings/virtual-channel-allow-list-policy-settings.html

[Printing to redirected LPT ports no longer works like expected from VDA version 2203 and above]

Hi Robert,

 

I've installed the CU3 version but the problem is still there.

 

Thanks,

René

 

 

 

[Printing to redirected LPT ports no longer works like expected from VDA version 2203 and above]

Hi Robert,

 

Thanks, I'm going to install it.

 

 

 

[Printing to redirected LPT ports no longer works like expected from VDA version 2203 and above]

Hello Citrix engineers.

 

We have a strange problem and I hope that some can help us.

 

We use within a server VDI (VDA 2012) desktop a program in production that prints to a redirected lpt1 port on the client. We use the LPT and COM redirection that is applied via Citrix policies.

 

When we use VDA version 2203 or higher, that no longer works. If we print from the program, no print job is placed in the queue, but if we first give a print to lpt1 command via the command line    “dir > lpt1” inside the VDI it’s printed and then we can also print from the program.

 

Printing to a redirected LPT port works fine with the VDA versions 2012 (now live) and subsequent current releases up to 2112. From 2203 LTSR and above, printing to a redirected LPT port no longer works except when we issue the cli command “dir > lpt1” first.

 

Can you help us figure out this strange issue? Citrix support is also looking into it, but after several months now they haven’t found a solution yet.

 

The environment.

Windows 2019 server VDI (VDA 2012), non-persistent, vSphere and MCS images are created with Citrix Applayering

 

Kind regards,

René

[MS Teams for VDI Recipe?]

Just follow the Citrix Teams VDI instructions https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html. Prerequisite layers are not needed!

 

 

[Cannot upgrade and delete layers anymore]

Hi Rob,

I've opened a support case.

 

Thanks

René

[Cannot upgrade and delete layers anymore]

Hello,

 

We have a several problems with our ELM. 

1.  I cannot delete any app layer or layer version and get the following error message: "One or more of the selected layer versions are being modified and cannot be removed."

2. I cannot upgrade the ELM to a newer version and get the following message: Cannot upgrade, tasks are in progress.

Rebooting the device won't help. 

We are using version 21.4.0.1066

 

Thanks

 

René

[Keyboard shortcuts not working in HDX optimized Teams]

Hello,

An update from Citrix support.

I have checked on this issue with our product team and they have informed us that Citrix is currently working with Microsoft team to fix this issue as issue is on Microsoft end. Once the issue is fixed it will be updated in the following articles/docs. https://support.citrix.com/article/CTX253754 https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html.

Regards,

Rene

[Keyboard shortcuts not working in HDX optimized Teams]

Hello we have the following issue.

 

Users working with HDX optimized MS Teams in a virtual desktop (VDI) cannot use the keyboard shortcuts with this program. All shortcuts starting with CTRL and function keys e.g. F1 are not working. Shortcuts starting with ALT are working OK. Other programs installed on the same VDI are working OK e.g. CTRL F (Find) is working in Adobe reader.

When we make a direct console connection to the VDI the keyboard shortcuts are working OK. We have tried also different versions of the Workspace client.

 

Does anyone experience the same issue?

Regards.

Rene

[Cannot finalize app layers after upgrade from 2003 to 2009. “a Microsoft NGen operation is needed”]

Thanks Raymond and Pennyad,

 

Creating a new version of the OS layer and using ngen eqi 3 instead of ngen update before finalize was the solution.

 

Thanks

René 

[Cannot finalize app layers after upgrade from 2003 to 2009. “a Microsoft NGen operation is needed”]

Thanks Raymond, I will run the update to 2009 again (next week) and I will add a new version of the OS layer and from that version I will create a new app layer. I will let you know if this solves the problem

 

 

 

[Cannot finalize app layers after upgrade from 2003 to 2009. “a Microsoft NGen operation is needed”]

Cannot finalize app layers after upgrade from 2003 to 2009.

When I choose Finalize it comes up with “a Microsoft NGen operation is needed”. It doesn’t matter if I run ngen update several times and I’ve tried it also with the force switch. The registry keys HKLM\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\NGenService\Roots\WorkPending and HKLM\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727\NGenService\Roots\WorkPending both have the value 0

When I create a new layer and open the LayerIntegrity.txt file the message “a Microsoft NGen operation is needed”. Is already there while there isn’t any application installed yet.

 

I’ve restored the ELM to the version before the upgrade every thing works fine again and the is no message in the LayerIntegrity.txt file only “”

 

Thanks

René

["Waiting for the Compositing Engine machine to be ready"]

When we try to create a new platform layer and we use the offload composing option the operation to create the VM timeout after 20 minutes waiting.

 

"Waiting for the Compositing Engine machine to be ready" and after 20 minutes "The Compositing Engine failed to initialize after '00:20:00'."

 

Thanks,

René

 

 

[Machine Hangs at "please wait for the citrix layering service"]

Hi,

 

We have the same problem with or without fslogix and av installed.