I am trying to update the snapvol.cfg file on all writable volumes using a .zip file containing the updated snapvol.cfg.
However, after uploading the file to the manager, the snapvol.cfg files on the wri don't get overwritten.
Is there a logfile that can tell me more about why the update is not applied?
The newly updated snapvol.cfg will apply to new writables created....not currently existing.
Is this changed in previous releases?? For as far as I know the way sjesse is doing this it should work. Create a zip file, add the snapvol.cfg in it and during logon the snapvol.cfg file will be overwritten in the writable. if you add a new one it will also overwrite the older updated zip file you used.
Normallty, if you look at the update writable tab it should say which writables have been updated. Do you see those registrations there?
According to the VMware Docs (Update Writable Volumes ) uploading a .zip file is the correct way to do so. And it should work on all new and existing Writables (according to VMware Support).
"You can upload ZIP files to the Writable Volumes VMDKs and update the volume. The uploaded files become available to the user the next time the user logs in to the desktop."
At the Writables=>Update tab is can see that 4 out of the 51 writables are updated. And i know for sure that those writables are all used frequently.
Does anyone know if the updating process is dependent on the snapvol.cfg configuration?
I see it the same way in AVM when I update my snapvol.cfg however I don't think it is correct. I know it works though cause I usually check couple of random ones and my snapvol.cfg configurations are properly updated on all existing and new writables
Can you please verify if your statement is correct?
We need to update the snapvol.cfg on existing Writables and the way we try to accomplish this is exactly as described in the knowledge base.
The only thing is, that it doesn't work in our case and i need to know how i can troubleshoot the process? I need to know were i can check to see whats going wrong...
If not done so already you can set debug logging on the App Volumes Managers by following KB 2101668.
You can check in System Messages under the Activity tab
Once you save the update writable in the Manager and login to a VM with a test user you can check https://<AVManagerFQDN>/log and see if there is any information on the update.
Also what version of App Volumes is this?
Can you open a case for this issue?