During an update of an App-V package I discovered a bug in RES Workspace Manager. I will first summarize the software and versions which are used for the deployment. Then I will explain the issue I encountered.
Operating System: Windows 7
Virtualazation Client: Microsoft App-V 220.127.116.113
Workspace Manager: RES Workspace Manager 2011 SR2 with Fix Pack 5 (18.104.22.168)
And also tested with
Workspace Manager: RES Workspace Manager 2011 SR4 with Fix Pack 6 (22.214.171.124)
Deployment: Microsoft Configuration Manager 2007 R2
Having a healthy application virtualization infrastructure platform involves configuring the App-V client with the appropriate settings. Today there are two main ways of configuring the client, either during the initial client installation process or afterwards.
Benefit of configuring the client during installation is that the client is fully operational in the shortest amount of time and can be used directly after the installation. Configuration can be done through one of the many command line parameters. If command line configuration is not preferred, settings can also be captured in a Microsoft Transform file (MST) and applied to the original installation.
I was searching for a quick way to restore to a default installation. After a search I found “Differencing Disk”. Here is some information about differencing disk from Microsoft TechNet.
A differencing disk is a virtual hard disk you use to isolate changes to a virtual hard disk or the guest operating system by storing them in a separate file. A differencing disk is similar to the Undo Disks feature because both offer a way to isolate changes in case you want to reverse them. However, Undo Disks is associated with a virtual machine and all disks assigned to it, while a differencing disk is associated only with one disk. In addition, Undo Disks is intended to be a shorter-term method of isolating changes.