App Layering - Changes to Scheduled Tasks do not show up on the layered image

Making changes to an existing scheduled task will not be reflected on the published image. Adding a version to the layer shows the old values and not the changes...

VDAs are not registering using a published image - Use GPO/GPP/Restricted Groups to add the proper accounts and services

VDAs are not appearing as registered, in Studio, no matter what is done to the image or the configuration of the VDA in the Platform Layer...

CVE-2018-11045

Pivotal Operations Manager, versions 2.1 prior to 2.1.6 and 2.0 prior to 2.0.15 and 1.12 prior to 1.12.22, contains a static Linux Random Number Generator LRNG seed file embedded in the appliance image. An attacker with knowledge of the exact version and IaaS of a running OpsManager could get the...

App Layering: Published image to PVS prompts user to restart computer

Customer publishes an image to PVS. When the machine boots up, it prompts for a restart with a box like this: "You must restart your computer to apply these changes." This is telling you that a new device has been detected and the driver has been installed, but Windows must restart to properly...

The list of Windows Updates is usually wrong in app/platform layers and published images/desktops

The Windows Update history is correct only in the layer where the updates were actually installed. So you can only rely on the displayed list of Windows Updates when you are editing the OS layer, because Windows Updates must always be installed in the OS Layer. Similarly, you can only rely on the...

App Layering/Unidesk: Published Image or Packaging Machine Blue Screens with Code STOP 0x75640007

Published image or Unidesk desktop or Packaging Machineblue-screens with code 0x75640007...