Over the last few months, I’ve been deep diving into some of the stranger issues that appear when you mix Omnissa Horizon Instant Clones, Hybrid Join with EntraID and App Volumes. Even after fixing the original PRT instability (see my previous post “The Hybrid Join Incident: Recovering the Lost PRT”), the story wasn’t over yet. In this new post, I cover: Why PRTs still fail after the basics are correct How Wait for Hybrid Join radically changes login reliability by using Login VSI How App Volumes packaging can get polluted by failed Hybrid Join attempts If you're running Hybrid Join in a non-persistent Horizon environment or planning to do so, this is one you’ll want to read. linkedin: https://www.linkedin.com/posts/edwin-de-bruin_the-hybrid-join-cascade-when-the-prt-challenge-activity-7401313812181590016-o9qz? Directlink: https://www.debruinonline.net/post/the-hybrid-join-cascade-when-the-prt-challenge-still-isn-t-done