Question : Registry settings for RemoteApp in Terminal Server Profile - Windows 2008 r2

I have an enterprise application, TP, that is deployed to users via RemoteApp on a Win 2008 R2 server.

The application saves a connection string and some favourite setting in the Registry of the RDP user. When I run Regedt32, I can see a folder with the application name that contains these values HKEY_CURRENT_USER\Software\TP\CXL

Most of the time, this work properly. However, sometimes, the application loses the connection string and values in the favourite. When this happens, I checked the Registry and found that under registry folder TP, another folder PXL is created.


under HKEY_CURRENT_USER\Software\TP\
                                                                       CXL\
                                                                       PXL\

This PXL folder has the same registry settings but null values. The application seems to be reading this folder.

If I delete the PXL folder, the application's connection string etc works normally again.

Is there anything on RemoteApp that triggers this behaviour? How can I ensure that the additional registry folder is not created?

Answer : Registry settings for RemoteApp in Terminal Server Profile - Windows 2008 r2

I would say this is a problem with your application, not your RDP server. Your best bet would be to figure out why the application is doing that and then fix the root cause.

If you want to investigate workarounds you could try copying the contents from the CXL folder to the PXL folder and see if that works, and if that helps maybe you can write a script to make sure those values are correct, but really those are not good solutions and I would only consider those if no other solution can be found.