GLADIATOR@MSFT

Adventures in Desktop, Application, and User State Virtualization

Browse by Tags

Tagged Content List
  • Blog Post: App-V: Current Recommended Practices for using App-V with Azure RemoteApp

    In recent blogs posts, I’ve been discussing the topics of how to leverage App-V for software delivery and management to custom Azure RemoteApp images joined to a hybrid collection. I’ve discussed what is supported and demonstrated a few walk-throughs regarding image setup and targeting. While...
  • Blog Post: App-V: On Targeting Azure RemoteApp Images with the App-V Management & Publishing Server

    There are two types of Collections with Azure RemoteApp: A Cloud Collection and a Hybrid Collection. App-V requires that the client must exist on domain-joined machines in order to be supported. Azure RemoteApp Custom Images can be part of a Hybrid RemoteApp collection where the images are joined to...
  • Blog Post: App-V: More on App-V with Azure RemoteApp

    Last April, we gave a little bit of information on the limited us of App-V applications with Azure RemoteApp ( http://blogs.technet.com/b/gladiatormsft/archive/2015/04/29/app-v-on-app-v-applications-hosted-in-azure-remoteapp.aspx .) This piqued the curiosity of many and over the past several months,...
  • Blog Post: Anatomy of an Outlier Bug: The Issue of the Failed App-V Report Upload

    When software malfunctions, product support teams attempt to narrow the issue down to user error, configuration, or code. If the software attempts to perform a function where a specific result is expected and the actual results are different, we classify that as a bug. Of course, there is great debate...
  • Blog Post: App-V 5.x Client Publishing Server Address

    Hi all, I've had the pleasure of working with the Gladiator for the past 5 years and now I have the opportunity to provide some great information about App-V 5.x to the world. What we have been seeing out in the field is that there seems to be some confusion on how to view the App-V 5.x Publishing...
  • Blog Post: App-V 5: Further into COM and Dynamic Virtualization

    It has been addressed to me by the MVP community that more clarification is needed with regards to the architecture of how App-V 5 implements COM and how that may now differ as a result of the changes in Service Pack 2. The differences are simplified to the difference between the standard COM virtualization...
  • Blog Post: App-V 5: On the PackageSourceRoot

    One way App-V client administrators are able to centrally control and override content streaming locations has been through a client-based content-path override. In App-V 5, this is called the PackageSourceRoot configuration item. The PackageSourceRoot configuration item is used to override the Package...
  • Blog Post: App-V 5: On the Catalog and Catalog Caching

    The App-V 5 catalog is the client collection of package information and package group (Connection Groups) information organized by GUID containing downloaded package manifests and dynamic configuration. The metadata stored in the catalog governs the overall behavior of the application with regards to...
  • Blog Post: App-V 5: On Package Entitlement and Publishing

    Before you ever want to begin testing client publishing, you want to ensure that your entitlements (assignments of packages and package configurations to groups) are properly set and the publishing metadata document is properly updated with the package, configuration, and entitled groups. You could otherwise...
  • Blog Post: App-V 5 and Citrix Integration Resources

    Whether it is integration with XenApp, XenDesktop, PVS, or UPM, App-V 5 is the recommended application virtualization and streaming model for Citrix Session and VDI environments. I work with a lot of customers who leverage App-V in this capacity and they have been asking me to maintain a “living...
  • Blog Post: App-V 4 Application Troubleshooting: Breaking Down Virtualization Issues Pt. II

    App-V 4.5 and 4.6 virtualize at the user mode layer. One of the most identifying factors of seeing that a thread stack is that of a virtualized application is the presence of the SFTLDR.DLL file. This is what is injected into every process a virtual application...( read more )
  • 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 the (now sometimes) Immutable Package Cache Location

    When you add/configure and publish a package in App-V, the primary file assets and source registry hives are stored in the package cache location. It defaults to %PROGRAMDATA%\App-V. The package cache will store packages in a <PACKAGE_GUID>\<VERSION_GUID> directory structure for each package...
  • Blog Post: App-V 4 Application Troubleshooting: Breaking Down Virtualization Issues Pt. I

    If you are working with an application that has been virtualized with App-V 4.x and that application is not functioning as expected, one of the first steps in troubleshooting should always be to try to determine if the issue is related to sequencing or...( read more )
  • Blog Post: App-V 5: Application Troubleshooting: “Fly-by-Night” Error Messages

    To continue the discussion of application troubleshooting, I wanted to provide some clarification on a certain type of application failure. In a blog post a while back ( http://blogs.technet.com/b/gladiatormsft/archive/2013/05/15/app-v-process-exit-codes-and-why-they-matter-when-troubleshooting-virtual...
  • Blog Post: App-V 5: On App-V Nomenclature

    As you may have figured out by now, App-V 5 has components that are referred to by multiple names depending on context. In some cases, App-V 5 basically takes the synonym concept to interesting levels. This can be misleading if misinterpreted. This can lead ISV’s and IT Pros down the wrong path...
  • Blog Post: App-V 5: Installing to the PVAD: Don’t do it . . . Yes . . . I said it.

    If you have ever dealt with me directly as a customer, attended one of my presentations, or even simply stomached one of my diatribes in a casual, technical conversation, you have no doubt heard about one of my pet peeves (no, not “Tips –n- Tricks” – we’ll visit that another...
  • Blog Post: App-V 5: Revisiting Registry Staging

    Last year, I wrote a blog post on registry staging in App-V and how it can affect initial publishing times – particularly on VDI ( http://blogs.technet.com/b/gladiatormsft/archive/2013/09/25/app-v-on-registry-staging-and-how-it-can-affect-vdi-environments.aspx ) and many people wrote me to tell...
  • Blog Post: Chatting All Things Dash V with Richard C on RunAs Radio!

    Last week, Chris Jackson appeared on RunAs Radio talking about about the benefits of Windows XP Migration (Yes, we still have customers who have not made the jump to a modern OS.) You can view the recording here: ( http://www.runasradio.com/default.aspx?showNum=374 ) It is an honor to be following...
  • Blog Post: App-V 5: Be Careful Toggling Shared Content Store Mode

    One of my colleagues in support let me know of an important note for those upgrading to App-V 5.0 Service Pack 2 Hotfix 4. It appears that the value for Shared Content Store (registry value SharedContentStoreMode in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Streaming or the same option using...
  • Blog Post: App-V 5: The Case of the Failed Connection Group Descriptor (or . . . Another Reason not to Use Notepad for XML File Creation)

    Have you ever noticed that when you go to save a newly created file in Notepad, the default encoding is ANSI? And this matters to App-V how you ask? Normally this may not matter to you but I should inform you that this actually is important – especially if you are a purist and insist on...
  • Blog Post: App-V 5: On Virtual Fonts

    App-V has many virtualization subsystems that make up how App-V isolates itself from other applications. Often I, and others have discussed virtual COM, virtual kernel objects, virtual services, etc. when discussing App-V in depth. Until now, one virtual subsystem that has not been discussed much in...
  • Blog Post: App-V 5: On Roaming Exclusions

    When you use App-V with roaming profiles or a service or product that may roam integration settings of virtual applications, it was historically assumed by App-V that once a package’s extension points are laid down (or integrated,) roaming user profiles will carry it alongside the user’s...
  • 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: On Dynamic Configuration

    When you create a package using the App-V sequencer, everything that you will need for the package will be self-contained inside the .APPV package file. In addition to the file and registry assets, the APPV file also maintains XML metadata that governs the operating system integration configuration and...
Page 1 of 2 (29 items) 12