The county updates a tax-appraisal application once inside an App Volumes package. What happens for entitled assessor desktops?
Select an answer to reveal the explanation.
Short Explanation
One package is the master cookbook. Update the recipe once and every entitled assessor kitchen gets the new dish the next time the volume attaches. That is how App Volumes avoids a gold-image sprawl party.
Full Explanation
When the county updates a tax-appraisal application once inside an App Volumes package, every entitled assessor desktop receives the updated application on the next attach without rebuilding each gold image. That shared-package model is a primary operational benefit of App Volumes for municipal application lifecycle on floating or instant-clone assessor fleets. It is incorrect that each gold image must be recaptured overnight because App Volumes cannot share a package—sharing one updated package is the point of the product. Workspace ONE UEM pushing an APK to assessor phones does not sync a Windows App Volumes application onto Horizon desktops. Connection Server republishing the entire instant-clone pool as a new template is unnecessary for an App Volumes package content update. Exam caveat: clients pick up the new package version according to attach and refresh timing in your design; schedule a brief assessor change window even though gold images stay untouched, and do not confuse package update with pool recompose. Operational check: update the package once in App Volumes Manager, have an assessor log off and on or otherwise reattach per procedure, confirm the new application version on the desktop, verify no gold-image recapture job ran for that change, and note the attach time in the change record.