- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's the experience I was hoping for when we started on this journey. We've torn the environment down and stood it up fresh 3 separate times. Each time running into new issues. We've brought in consultants, spent countless hours with vmware support, upgraded, downgraded, whatever they've asked us to do, and each time we run into a showstopper. Keep in mind this is in a very high-end environment. Storage, network, hosts, etc. are all top of the line.
For our business, the persona management portion of this is a showstopper. Our users currently all have their own full clone. My one requirement for moving from full clones to linked clones is that it has to be "seamless". The users cannot know that anything has been changed. So to have random things (even if they might seem insignificant to other companies) regularly breaking isn't acceptable.
With this current issue, every single time a user opens firefox they get a different experience. Sometimes it works, sometimes they just get a white page, sometimes they get an error, sometimes all their plugins stop working. It's because of the location of the firefox profile on the writable volume, and as far as I can tell it's because of this issue being discussed.