RDS published apps stops working after installing XenApp VDA

[Eduardo Aguirre]

Good Morning,

 

We are doing some tests to migrate RDS publish apps to Citrix.

 

Yesterday we install the VDA on a RDS server; after that connections to remote apps (RDS) stopped working.

 

I added the required user group to the "Direct Access Users" security group on the server, but that is only letting us login to the server using the entire desktop. We can´t launch an app the way we used to do it.

 

Additional to that, I also enable the following Citrix policies:

• Desktop Launches (enabled)
• Launching of non-published programs during client connections (Enabled)

I don´t know if I need to add any other permission. We even try making the users administrators of the server, but it also didn't work either.

 

As an additional note, every time a user connect we get a message 9009 on the event viewer saying that "The Desktop Window Manager has exited with code (0xd00002fe)"

 

 

 

Thanks in advanced for you help.

[Jack Tu]

Maybe you could try the solution mentioned in the KB https://support.citrix.com/article/CTX200082.

 

Regards

Jack Tu :)

[Eduardo Aguirre]

Hi Jack,

 

That would not apply for us, because what we are trying to do is keep users connecting to the server using RDS as we migrate them to ICA.

 

In our case what is not working is RDP RemoteApp publishing, ICA App publishing works fine.

 

Thanks

[Thorsten Ellmers1709153287]

​Hi Eduardo

 

check if the following reg keys are in place.

Citrix Support told me, they are not needed anymore since some version around 7.9 or 7.11. but in my case, without the keys published app starts but is not visible, only in studio!!

Also in case you use intel moonshot cartridges with VDA 7.13, not working, looks like a bug in combination with Intel.

 

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs\   "REG_SZ" =  c:\progra~2\citrix\system32\mfaphook64.dll

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs\   "REG_SZ" =  c:\progra~2\citrix\system32\mfaphook.dll

 

 

​greets

​Thorsten

 

 

[James Yount]

Did you ever get this resolved?  I am also having  an issue. The RDP file launches, but I get an error "The initial application you are trying to open is currently unavailable" Policy is set to allow listed and unlisted programs. As this is our backup for when there is a WAN outage, we have to have this working. It only works on the XenApp 6.5 servers that have not been updated to XenApp 7.15.

 

I also did the following as you did:

I added the required user group to the "Direct Access Users" security group on the server, but that is only letting us login to the server using the entire desktop. We can´t launch an app the way we used to do it.

 

Additional to that, I also enable the following Citrix policies:

Desktop Launches (enabled)

Launching of non-published programs during client connections (Enabled)

[Adam Bowers]

On 9/25/2018 at 2:49 PM, James Yount said:

Did you ever get this resolved?  I am also having  an issue. The RDP file launches, but I get an error "The initial application you are trying to open is currently unavailable" Policy is set to allow listed and unlisted programs. As this is our backup for when there is a WAN outage, we have to have this working. It only works on the XenApp 6.5 servers that have not been updated to XenApp 7.15.

 

I also did the following as you did:

I added the required user group to the "Direct Access Users" security group on the server, but that is only letting us login to the server using the entire desktop. We can´t launch an app the way we used to do it.

 

Additional to that, I also enable the following Citrix policies:

Desktop Launches (enabled)

Launching of non-published programs during client connections (Enabled)

 

Hello ASEAdmin, I am having the same exact issue with 7.15 were you able to get the RemoteApp connections working again? Thanks

[Eduardo Aguirre]

Hello abowers164

 

In our case we had some issues with the OS, we end up re-installing the OS. I know is not the easiest way, but I solved our issue for good.

 

Regards

Eduardo Aguirre