When Microsoft release App-V 4.6 Sp1, which was all about the new sequencer, they also quietly put out an updated client. You don’t need the updated client to use SP1 sequenced packages, but it is an option. Supposedly the client was mostly about rolling up hotfixes, but we know that there must be changes to support the upcoming SCCM 2012 release (now in beta).
Today I discovered another small change in the SP1 client. It is a relatively benign change that is behind the scenes in the Windows registry, but it happened to affect one of the tools in my AppV_DeployNPublish toolset. I didn’t notice it right away because you have to install the SP1 client as a clean install (rather than an upgrade) to notice. The change affected my command management replacement tool, which caused it to not show file type associations, and this post is to announce the new release of my tools to address this issue.
“Wait a minute”, I hear you say. “What command management console replacement tool”? Perhaps replacement is too stong of word, but this tool organizes the virtual application information into a more usable form – by package instead of application. By package, it shows DSC dependencies, shortcuts, and file associations. This allows you to delete an entire package from the client in one step, rather than have to hunt down all the application names in the package.
Information on these free tools and the download found at:
