![]() How to check if the correct package version is installed? The location of the OSD is known and it is possible to read the cached OSD. It is not possible to check the GUID of the cached OSD because this is randomly generated. ![]() Finally the shortcut is not being displayed in the start menu. So I changed the name of the “DescriptionURL” to “DescriptionURL.old”. But to my surprise the shortcut is still available. This way RES Workspace Manager should be able to find the location and publish the shortcut in the start menu. So for testing I changed the value of the “DescriptionURL” to OSD.old. In Procmon it is clearly visible that the executable “Pfwsmgr.exe” from RES Workspace Manager is checking the locations in the registry. The value of the string is the location of the cached OSD. In this registry tree App-V package information can be found and also the string “DescriptionURL”. This is created by importing the App-V package on the machine. Under “HKLM\Software\Microsoft\Softgrid\4.5\Client\Applications” there is a key with the shortcut name and version combined. Like Raymon described to me RES Workspace Manager checks the registry for the installed App-V packages. To exactly know what happens when the “Workspace” is refreshed I used Procmon to monitor the actions. Raymon Rahiembaks has provide me with some information about how RES Workspace Manager handles the shortcuts. So I started investigating how RES Workspace Manager detect if an App-V package is installed or not. The “production” App-V package was only deployed on the machine but I saw both shortcuts. What the heck! I always thought when an App-V package is not deployed on the machine the shortcut will not be displayed. The shortcuts from the original “production” and the new version were published in the start menu. The user can now use the latest App-V package and work happily ever after.ĭuring testing I discovered a strange behavior how RES Workspace Manager handles the shortcuts while the original “production” version was still deployed on the machine. When the SCCM has completed the deployment and the workspace manager is refreshed the old shortcuts will disappear and the new are published. When the update process is started by SCCM the new App-V package version will be deployed on the machine. The shortcut’s of this version are published in the start menu and is behaving as normal. Users are having the old App-V package deployed on there systems. "Folder Vendor Name" - "Folder Application Name" - "Shortcut" The shortcuts are published in the following folder structure. Both versions are linked to the same AD security group. Because I updated the package I create double shortcuts based on the original “production” package and the new updated package. Users have to be a member of the application group to receive the correct shortcut. The shortcuts are published with RES Workspace Manager. The update part is covered by SCCM and has been tested successfully. Therefore I created an update script which updates an App-V package with SCCM. Because the shortcuts are the same the two packages cannot be deployed both to the same machine. SCCM is used to deploy the App-V packages. The package name is changed to a higher build “vendor-app-version-lang-release-build”. The shortcut location, name and version are the same because the executable’s where not modified and only some parameters where changed. Workspace Manager: RES Workspace Manager 2011 SR4 with Fix Pack 6 (9.5.4.6)ĭeployment: Microsoft Configuration Manager 2007 R2Īn App-V package has been upgraded with an application fix and not an update. Workspace Manager: RES Workspace Manager 2011 SR2 with Fix Pack 5 (9.5.2.5) Virtualazation Client: Microsoft App-V 4. Then I will explain the issue I encountered. ![]() I will first summarize the software and versions which are used for the deployment. During an update of an App-V package I discovered a bug in RES Workspace Manager.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |