I updated my App Volume manager and clients on my Parent VM's and i have two parent vm's for composer and instant clones and for whatever reason when i log into my Instant Clone Parent vm my appstack doesn't mount, but it does mount on my Linked Clone Parent.
I reinstalled the AppVolume Agent on the Parent and made sure i could hit the manager and also accepted my vCenter Certificate manually on my App Volume Manager and then my app stack was mounting.
Thanks for the suggestion!
We are having a problem right now with "error code 500" from any client that has the agent. It's not mounting any AppStacks or Writables. We were on version 2.11 and it was working, but after upgrading it now forces SSL by default which is fine but the agent is not able to communicate entirely. The interesting thing is the VM that the agent is running on is showing up in the AppVol console and is connected, and the Writable shows up as "attached" in the console also... but the user does not see it attached from the VM itself.
I currently have a ticket open with VMware and am waiting on a response.
You're too quick, I was going to reply when I saw this a few weeks ago but I saw your updated post. Updating the agent and validating cert is definitely a common issue we have been seeing since the changes on cert validation...
Good catch Daniel