{"id":6496,"date":"2014-01-22T16:00:49","date_gmt":"2014-01-22T15:00:49","guid":{"rendered":"https:\/\/ingmarverheij.com\/?p=6496"},"modified":"2014-01-24T11:45:24","modified_gmt":"2014-01-24T10:45:24","slug":"microsoft-app-v-dynamic-configurations-res-workspace-manager","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/microsoft-app-v-dynamic-configurations-res-workspace-manager\/","title":{"rendered":"Microsoft App-V: Dynamic Configurations or RES Workspace Manager?"},"content":{"rendered":"

\"\"When you\u2019re using Microsoft App-V 5 to distribute your \u201cvirtual\u201d applications it can be cumbersome to apply settings afterwards<\/strong>. With native installed applications you have to ability to update files, registry settings or apply permissions<\/a> (since App-V 5 always applies default permissions).<\/p>\n

Within a virtual application these settings needs to be applied within<\/strong> the virtual environment<\/strong> (often referred to as \u201cthe bubble<\/strong>\u201d). Up to App-V 4.x you had the ability to add custom actions in the OSD<\/strong> file, starting App-V 5 this is replaced with Dynamic Configurations<\/strong>.<\/p>\n

While Dynamic Configurations are more powerful<\/strong> and flexible<\/strong> then the static OSD files I couldn\u2019t resist to show you how RES Workspace Manager<\/a> can simplify this.<\/p>\n

<\/p>\n

Dynamic Configurations<\/h1>\n

Let\u2019s start with diving a bit deeper in the Dynamic Configurations. Basically what\u2019s changed from App-V 4 to App-V 5 is that the information that previously was stored in the OSD file (shortcuts \/ FTA\u2019s and optionally scripts) are now stored in the main package with an .appv extension. Inside the .appv package a manifest xml file resides containing information that was previously in the OSD file.<\/p>\n

Dynamic Configuration files are XML files can be applied to all environments (the Default Configuration) or a certain group of users \/ computers (a user configuration). Dynamic Configuration files are created automatically when an package is created with the App-V Sequencer: <packagename>_UserConfig.xml<\/em> and <packagename>_DeploymentConfig.xml<\/em>.<\/p>\n

 <\/p>\n

Before you consider using Dynamic Configurations there are some things you should know:<\/p>\n