Rsasjol

Hi, First, thanks for the feedback. Next, releases : Appvolumes : App Volumes 4, version 2212.2 (4.9.2.18) VSAN : Based on ESXi 7.0 Update 3o

Hi, I have 2 AppVolumes servers, running as a pair, configured to use a VSAN as datastore storage. Since a few days, we encounter problems with them. In short, they're often unable to provide appvolumes to our non-persistent sessions, and user get a "timeout" panel on session. First action was a simple reboot for one of the two. When reboot is complete, I look in the System Messages panel. There, I have this kind of message for many of my apppackages : "Unable to extract app launch data for package AppPackage <#819 AppV_CiscoUCCXEditor_2024-10-28 {4f548231-1c2d-4140-a9bf-7e699d53b361}> with exclusive lock" As it says "Exclusive lock", I've tried to shutdown both of my appvol managers, and just start one of them..... With exactly the same messages. Should I worry about something more intricate ?

Hi, I'm actually trying to package the "new" Microsoft Teams with this procedure : https://kb.omnissa.com/s/article/6000003 Everything runs smoothly with my 2212.2 Appvolume infrastructure, until I try to upload files to the appvolumes managers. Selecting the VMDK to upload is OK, I see files appear in my datastore, except that there is no metadata file generated. JSON and VMDK ok, but not the METADATA file. Consequently, I don't have any application of package refering to my VMDKs. I've tried several approaches, but until now I always end with this exact same result. Is there any minimum requirements for Appvolumes' infrastructure in order to support this new Teams release ? Any other ideas are appreciated ;-) Thanks.