Invalid App-V junction points after second login

Question

Hi all,

We are testing FSLogix Profile Containers in Windows 10 environment on (persistent) desktops. We are using App-V for user based application distribution. After first logon with FSLogix, all App-V packages are published and working well. But only after second login, the App-V junction points have become invalid.

To get them work again, we have to run the appv-repair for all (published) packages and connection groups. Or unpublish all connection groups and apps, and republish. After this once action, the junction points seem not become invalid anymore in next logon sessions

We want to migrate to FSLogix in one logon session. Does anyone experience the same issue? Any idea how to prevent this behaviour?

Answer 1

Hello,

Which versions of App-V and FSLogix are these?

Regards

Answer 2

App-V 5.2 Windows 10 1803 and FSLogix Apps 2.9.7117

Answer 3

Hello Peter,

Thanks for the update. There are some known compatibility issues between FSLogix and App-V 4..6, but since you are using the latest version of App-V and FSLogix running on a supported version of Windows, you will probably need to open an FSLogix support ticket to be able to share you full logs to troubleshoot this issue further. Please see the instructions at:

How to open an FSLogix Support Request

- Micah Adamson

Answer 4

Hi Peter

Same issue here with FSLogix 2.9.7205.27375 and App-V 5.2.

After first Login when new vhdx was created, the junction points are correct ([C:\ProgramData\App-V\productid\versionid]). After second login junction points becomes invalid ([\??\C:\Users\username\productid\versionid\]).

Were you able to resolve the issue or are u still using a Workaround (repair or republish)?

regards

Answer 5

Hi,

The support team could not reproduce this issue.

I solved it by adding 'AppData\Local\Microsoft\AppV\Client' as an exclusion to the redirections.xml.

Unfortunately I ran into another App-V issue related to FSLogix: error 0x9B501B2A-0x2. Although it appears with just one user (a new employee), I stopped testing FSLogix for a while. In our situation it is still not stable enough.

Regards

Answer 6

another workaround is available @ chawn.com by modifying the app-v refresh scheduled task to run 5-10 secs after logon instead of at logon (they won't let me post the full URL here)