GLADIATOR@MSFT

Adventures in Desktop, Application, and User State Virtualization

Browse by Tags

Related Posts
  • Blog Post: 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...
  • Blog Post: App-V 5: On Environment Variables

    Environment variables are managed on a per-package basis in App-V 5 just as they have with previous versions. During sequencing, the Environment Variable Virtualization Subsystem (say that 10 ten times fast) will capture snapshots of the user and system variable list before and after the monitoring process...
  • Blog Post: AppV 5: Important Considerations and Ramifications for Package Upgrade and VFS Write Mode

    If you are running any version of the App-V 5 client or Sequencer prior to App-V 5.0 Service Pack 2 Hotfix 4 – stop reading. This does not apply to your environment. If you are running HF4 or sooner, you need to have a good understanding of the net effects of toggling VFS Mode on and/or off during...
  • Blog Post: App-V 5: On Sequencing Using Tokenized Paths, PVAD’s, VFS, and VFS Write Mode

    Update 12/5/2014: The PVAD is now considered optional due to changes in App-V 5Service Pack 3. Read more here: http://technet.microsoft.com/en-us/library/dn858700.aspx#BKMK_pvad_hidden When sequencing applications, you often never know how the application was written with regards to what paths...
  • Blog Post: App-V 5: Application Troubleshooting: On the Origins of an Error Message

    Have you ever been testing a virtualized application and it fails with a bizarre application error that is either extremely vague (unknown error) or coupled with some random hex code? Your first reaction usually is “Where’d that error come from?” That is a good reaction to have as it...
  • Blog Post: 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...
  • Blog Post: App-V 5: Capturing Data Source Configuration

    You may have noticed that in previously releases of Softgrid and App-V, it was recommended as a best practice to manually create a dummy (I hate that word – I prefer “artificial”) ODBC data source (DSN) connection on the sequencing prior to sequencing anything that interacts with ADO...
  • Blog Post: On the Art of Troubleshooting App-V Applications

    Lately I have been dealing with the big challenge of teaching something that I have become to know as more of an art than a science. That is, the troubleshooting of virtual applications not functioning correctly in App-V. I have seen many articles that walk through how someone was able to figure out...
  • Blog Post: App-V 4.6SP1: Issue with Sequencing the Dynamics NAV 2009 R2 Client

    There is an issue that currently being investigated by the App-V support team regarding virtualization of the Microsoft Dynamics NAV 2009 R2 client with the new App-V 4.6 SP1 sequencer. It appears the issue is tied to the Classic Client more and not the Role-Tailored client. In addition to the workflow...
  • Blog Post: App-V: Process Exit Codes and why they matter when troubleshooting virtual applications

    In a previous blog post ( http://blogs.technet.com/b/gladiatormsft/archive/2013/04/27/on-the-art-of-troubleshooting-app-v-applications.aspx ) I discussed the “art” of troubleshooting virtual applications and mentioned the fact that there are a lot of custom recipe’s out on the Internet...