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?
