UUPDUMP Iso creation -- Pended operations ???

Impact to Package Life Cycle
Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (unpublished) virtual application packages, it's recommended you update the base image to reflect these changes. To understand why review the following section:

App-V 5.0 SP2 introduced the concept of pending states. In the past,

If an administrator changed entitlements or created a new version of a package (upgraded) and during a publishing/refresh that package was in-use, the unpublish or publish operation, respectively, would fail.

Now, if a package is in use, the operation will be pended. The unpublish and publish-pend operations will be processed on service restart or if another publish or unpublish command is issued. In the latter case, if the virtual application is in-use otherwise, the virtual application will remain in a pending state. For globally published packages, a restart (or service restart) often needed.

In a non-persistent environment, it's unlikely these pended operations will be processed. The pended operations, for example tasks are captured under HKEY_CURRENT_USER \ Software \ Microsoft \ AppV \ Client \ PendingTasks. Although this location is persisted by the UPM solution, if it isn't applied to the environment prior to a sign in, it will not be processed.

Click to expand...

Performance Guidance for Application Virtualization - Microsoft Desktop Optimization Pack

Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.

learn.microsoft.com

iko22 said:

According to Microsoft, an operation will be pended if the package is in use:



Source:

Performance Guidance for Application Virtualization - Microsoft Desktop Optimization Pack

Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.

learn.microsoft.com

Click to expand...