App-V: How the Sequencer Detects an Existing Package was Created

One of the most consistent recommended practices throughout the history of App-V sequencing is to always sequence on a clean sequencer. Starting with App-V 4.6 SP1, a detector was put in to warn users if they were about to sequence on a machine where a previous package was sequenced.   When the App-V sequencer is…

0

App-V 5: On why the App-V 5 Sequencer *Really* Reboots

Prior to version 5 of App-V, when you sequenced an application that required a reboot, the reboot was simulated in that the sequencer would process the reboot action including the Pending File Operations and the RunOnce registry keys (RunOnce, RunOnceEx, GuiRunOnce, etc.) when monitoring ceased. In most cases, the simulation would be fine and all…

4

App-V 5: On Using Sequencing Templates

Sequencing Templates (.APPVT) files are designed for automating the sequencing of applications. While you can take advantage of some of the benefits of templates with manual, interactive sequencing, be careful making assumptions when sequencing following the importing of a template in the Sequencer GUI. Sequencing Templates are also essential for the upgrading of packages. Remember…

6

App-V: On Virtual Services in App-V 5.0

On the subject of services, it is probably worth mentioning some of the changes with how App-V handles virtual services in V5. First and foremost, you may have noticed there is no separate virtual service agent service running for the V5 client. You have probably also noticed that virtual services are not managed or modified…

4

AppV: On Devirtualization

So, I am hanging out on the Technet Forums one Saturday night and I got inspired by a thread (http://social.technet.microsoft.com/Forums/en-US/9b136314-77be-4568-8bc6-6e2ed865f43e/this-document-could-not-be-opened-it-does-not-appear-to-be-a-crystal-report-document) to write this particular blog post. Yes, before I go any further, I will acknowledge the pathetic revelation of what I like to do on a Saturday night – because there is nothing more wild…

4

Important Information for those still using Softgrid 4.1 and 4.2

If you are currently using Softgrid 4.1 or4.2 clients and/or servers, you need to be aware of the following support milestones: Product Availability Mainstream Supports Ends SoftGrid Application Virtualization 4.1 for Desktops 5/25/2007 7/10/2012 SoftGrid Application Virtualization 4.2 for Desktops 5/25/2007 7/10/2012 SoftGrid Application Virtualization for Terminal Services 4.1 5/25/2007 7/10/2012   As of last…

0

App-V 4.6: Are you using the Latest Version of the Client and Sequencer? You should be.

When many organizations move to Windows 7, they also take on the task of discovering, inventorying, testing, and remediating all of their current applications currently used in production. Often part of that process includes a decision to deliver those applications with App-V. The App-V 4.6 SP1 Sequencer and client offers a streamlined workflow to virtualize,…

0

App-V: Don’t use WMI for querying virtual registries.

It is important to understand that the virtual registry is designed for virtualization of an application’s registry and it facilitates it through the interception of standard Win32 registry APIs. These APIs (i.e. RegOpenKeyEx, RegEnumKeyEx,  RegEnumValue,  RegCreateKeyEx, etc.) I have, from time to time, dealt with alleviating confusion with how to access the virtual registry. I…

0