• Shortcuts : 'n' next unread feed - 'p' previous unread feed • Styles : 1 2

» Publishers, Monetize your RSS feeds with FeedShow:  More infos  (Show/Hide Ads)


Date: Thursday, 28 Feb 2013 18:34

imageHello everyone, John Behneman here, and in today’s post I wanted to pass along a tip that might come in handy as you prepare for App-V v5. I recently worked with a customer who had multiple corrupt App-V 4.6 SP1 RDS Client installs that were failing to upgrade. When we tried to uninstall the clients that also failed. Fortunately for us, the following procedure allowed us to completely remove the App-V 4.6 SP1 client and then successfully install the current version.

1. After exiting any running App-V packages, remove the App-V related services by running the following commands from an elevated CMD prompt (Run As Administrator):

sc delete sftvsa 
sc delete sftlist 
sc delete sftplay 
sc delete sftfs 
sc delete sftvol

Note that sc delete does not remove running services so you may have to issue the sc stop <serviceName> command before running sc delete <serviceName>.

When complete, reboot the client.

2. Remove the App-V files by running rmdir /s on the install directory (usually c:\program files\microsoft application virtualization client).

Note: If you get an "Access is denied" error when trying to delete .dll and/or .exe files, run Task Manager in an Administrator context, select the Services tab, click Name to sort by task name, then for every "sft*" (App-V) service listed, right-click and click "Stop Service". Then try deleting the install directory again. This problem usually only shows up if you didn’t reboot after step #1.

3. Delete the following directories on the client:

  • %public%\documents\softgrid client
  • %appdata%\softgrid client
  • %localappdata%\softgrid client

4. Reboot the client.

This will normally take care of the problem and you should be able to reinstall at this point. However, if you still can’t get your new client installed, check in the Registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet for any SFT* services (e.g. via 'reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services | findstr /i "\sft"'). These should have been removed by step 1 above followed by a reboot, but if they are still there you can remove them manually.

John Behneman | Senior Support Escalation Engineer | Microsoft CTS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms- identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 27 Feb 2013 16:48

imageLooking for the best resources for your App-V v5 migration or deployment? If so then Microsoft’s very own Steve Thomas has amassed a veritable salad of links and information that I’m sure you'll find invaluable in making your App-V 5.0 rollout a success. Before you embark on an App-V 5.0 deployment or migration, be sure you look to the following resources for assistance in migrating to App-V 5.0:

Must Have App-V 5.0 Migration Resources!

J.C. Hornbeck | Knowledge Engineer | Microsoft CTS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 19 Feb 2013 16:33

KBIf you use System Center Configuration Manager 2007 with App-V then you might want to take a look at this new KB we published. It’s a hotfix that addresses a situation where you may see a memory leak when you use an App-V package that contains icons.

Consider the following scenario:

  • You build a three-tier System Center Configuration Manager 2007 Service Pack 2 (SP2) hierarchy that has a central site, a child primary site, and a secondary site.
  • You add a Microsoft Application Virtualization (App-V) virtual application package to the central site.
  • The App-V package contains icons.
  • You distribute the App-V package to all distribution points (DPs).

In this scenario, memory usage on the child primary site increases based on the size of the icons included in the App-V package. Additionally, if you create another package by using the same App-V source, or by clicking Update Distribution Points on the existing package, more memory is leaked on the child primary site.

For all the details and a download link please see the following:

KB2802399 - Memory leaks when you use an App-V package that contains icons in System Center Configuration Manager 2007 SP2 (http://support.microsoft.com/kb/2802399)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 13 Feb 2013 18:40

imageHello everyone, John Behneman here, and today I wanted to tell you about an interesting App-V issue I ran into the other day and what we did to fix it.

What happened was that the Microsoft Application Virtualization client service failed to start and generated the following error message:

Error 1114
A Dynamic Link Library (DLL) initialization routine failed

We also found the following event in the Application event log:

Log Name: Application
Source: Microsoft-Windows-WMI
Date: <date-time>
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
Description: Event filter with query "select * from __instancecreationevent within 60 where targetinstance isa "win32_service" and targetinstance.name="msmpsvc"" could not be reactivated in namespace "//./root/cimv2" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

When we checked the sftlog.txt file we found this:

[01/29/2013 19:04:48:773 ABCD CRT] {tid=1980}
Initialization of the Application Virtualization file system security failed (status 16D13A0A-0000E016).

I began to suspect a WMI issue but running the Winmgmt /verifyrepository command in an elevated command prompt indicated that the WMI repository is consistent.

We did some more investigation and found that although the WMI repository was consistent it was missing the CIMWIN32.MOF class objects.

To resolve this, we simply ran the following command in an elevated command prompt:

mofcomp %systemroot%\system32\wbem\CIMWIN32.MOF

As a side note, if the result of the Winmgmt /verifyrepository command indicates that the repository is inconsistent, try running the following command:

Winmgmt /salvagerepository

Also note that WMI issues are not the only cause of this particular error. I’ve included a couple other links that might also help below:

John Behneman | Senior Support Escalation Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 06 Feb 2013 16:07

ReplicationLooking to get a head start on virtualizing Microsoft Visual Studio 2012 with App-V? If so then this one’s for you. Microsoft’s own Arnab Biswas just posted a recipe that describes how to sequence Microsoft Visual Studio 2012 for use with Microsoft Application Virtualization (App-V) over in our TechNet forum. The method that he describes is not the only possible method but it’s one we’ve tested and know will work. You can find Arnab’s post here:

How to Sequence Visual Studio 2012 in Microsoft Application Virtualization 4.6 SP2: http://social.technet.microsoft.com/Forums/en-US/prescriptiveguidance/thread/7e93e525-31ed-43fc-8415-88a12766d2c2

Enjoy!

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Monday, 28 Jan 2013 18:08

KBJust a quick heads up on a new Configuration Manager hotfix we released that may affect some of you. There’s an issue in ConfigMgr 2007 SP2 where Hardware Inventory does not inventory Microsoft Application Virtualization (App-V) applications in Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) if the VAppCollector.exe process exceeds the 30-second time-out period. In this situation, no App-V applications are reported during the Hardware Inventory action.

This was originally posted on our Configuration Manager blog here: http://blogs.technet.com/b/configurationmgr/archive/2013/01/28/hotfix-hardware-inventory-action-does-not-inventory-app-v-applications-in-system-center-configuration-manager-2007-sp2.aspx

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Monday, 28 Jan 2013 16:34

eThis isn’t really App-V specific but since this is our short-term temporary home for UE-V content I wanted to post a quick heads up. We just published a new KB article about an issue where Microsoft User Experience Virtualization (UE-V) environments that also have the Citrix EdgeSight client agent installed may see 64-bit applications crash on exit. You’ll also see an Event ID: 1000 logged in the Application log but you can get all the details here:

KB2808222 - 64-Bit UE-V applications crash on exit when Citrix EdgeSight is installed (http://support.microsoft.com/kb/2808222)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 23 Jan 2013 16:07

GrayAndYellowGears5Hi all! This is Vladimir from the App-V team and today I want to show you how to collect App-V 5.0 server ETL traces. These ETL traces can be helpful in certain troubleshooting scenarios and the steps below show you how to collect them from the App-V 5.0 Management, Publishing and Reporting servers.

1. First we need to register what kind of ETL traces we want to collect. There are 7 different ETL streams available and to collect them all in the same trace we can type the following at an elevated command prompt on the App-V 5.0 Management/Publishing/Reporting server:

Logman create trace APPV5 -p Microsoft-AppV-PolicyLibrary -o appv.etl

Logman update trace APPV5 -p Microsoft-AppV-Server-Management        

Logman update trace APPV5 -p Microsoft-AppV-Server-Management-Private

Logman update trace APPV5 -p Microsoft-AppV-Server-Publishing       

Logman update trace APPV5 -p Microsoft-AppV-Server-Publishing-Private

Logman update trace APPV5 -p Microsoft-AppV-Server-Reporting         

Logman update trace APPV5 -p Microsoft-AppV-Server-Reporting-Private 

clip_image001

2. We then need to start the trace by running the following command:

Logman start APPV5

3. Now reproduce the issue.

4. Once the issue is reproduced, we need to stop the trace using this command:

Logman stop APPV5

5. Next we need to find out where the ETL file was created by using this command:

Logman query APPV5| find /I "ETL"

6. Finally, we can convert the ETL file into a TXT file using the following:

Netsh trace convert APPV_<RANDOM>.ETL

An example of this is below:

clip_image002

Note that you can also view more detailed App-V 5.0 server event logs by checking “Show Analytic and Debug Log” in the Event Viewer:

clip_image003

I hope that you found this information useful. See you soon!

Vladimir Petrosyan | Support Escalation Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 22 Jan 2013 17:24

toolsignHere’s an issue we’ve seen a time or two here in support so I thought it would be worth a mention in case any of you happen to run across it. What happens is that Keepass.exe fails to synchronize settings with Microsoft User Experience Virtualization 1.0 (UE-V 1.0) enabled and crashes on launch.  An error similar to the following will be reported in the Application log:

Log Name:      Application
Source:        Application Error
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      Classic
Description:
Faulting application name: KeePass.exe, version: 2.20.1.0, time stamp: 0x506d455e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
Exception code: 0xe0434352
Fault offset: 0x0000000000009e5d
Faulting process id: 0x544
Faulting application start time: 0x01cdef9d0028ee0a
Faulting application path: C:\Program Files (x86)\KeePass2x\KeePass.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 3dff0aaa-5b90-11e2-bb4e-005056c00008
Faulting package full name: %14
Faulting package-relative application ID: %15

A UE-V debug (ETL) trace will show a pattern similar to the following:

03:43:05.689 01-10-2013 11 1348 10232 16 2013-Jan-10 20:43:05.689 - Orchestrator: [10232]: INFO: An updated settings data package was not found to import for settings location template KeePass.
...
03:43:05.689 01-10-2013 2 1348 5540 16 2013-Jan-10 20:43:05.690 - AppAgent: [5540]: SCOPE: <-- SyncSettingsFromCentralStoreToLocalStore() [Settings successfully imported]
03:43:05.689 01-10-2013 2 1348 5540 16 2013-Jan-10 20:43:05.690 - AppAgent: [5540]: INFO: Calling monitored application's main entry point.
03:43:05.767 01-10-2013 102 4636 10872 0 The Agent Driver trapped the start of process WerFault.exe (ID 9752).

This crash occurs because UE-V and Keepass.exe both attempt to load different versions of the .Net runtime into the same process space when the UE-V agent DLL is injected in to the Keepass.exe process.

To resolve this issue, complete the following steps:

1. Open Notepad.exe in an elevated context by right-clicking on a shortcut to Notepad and choosing Run as administrator....

2. Select File\New... and create or edit a file named keepass.exe.config in the same folder as Keepass.exe (C:\Program Files (x86)\KeePass Password Safe 2 by default). Be sure to remove the .txt extension.

3. Copy and paste the following lines into keepass.exe.config.  If the file already exists, change the <startup> tag to <startup useLegacyV2RuntimeActivationPolicy="true">

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
  <supportedRuntime version="v4.0" />
  <supportedRuntime version="v2.0.50727" />
</startup>
<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
   <dependentAssembly>
    <assemblyIdentity name="KeePass"
     publicKeyToken="fed2ed7716aecf5c"
     culture="neutral" />
    <bindingRedirect oldVersion="2.0.9.0-2.20.0.0"
     newVersion="2.20.0.18622" />
   </dependentAssembly>
  </assemblyBinding>
  <enforceFIPSPolicy enabled="false" />
  <loadFromRemoteSources enabled="true" />
</runtime>
</configuration>

4. Save the file and exit Notepad.

5. Re-launch Keepass.exe.

This crash occurs because UE-V and the process that UE-V is trying to inject its monitoring and management DLL in to are both compiled to use the .Net Runtime 2.0.5, but reference different builds of the runtime.  Adding the useLegacyV2RuntimeActivationPolicy tag to the executable’s .config file allows the program to successfully load despite this incompatibility.  This is a relatively rare error that has only been experienced with the KeePass.exe executable, but it is possible that other .Net applications may witness the same behavior.  To diagnose that you are in this state, verify that the process you are investigating is generating Application log event 1000 with the Exception code: 0xe0434352 string in the details of the event.  Edit or add a .config file to the executable referenced in the Faulting application path.

We have a new KB article on this issue here:

2802058 - Keepass crashes and fails to synchronize with UE-V (http://support.microsoft.com/kb/2802058)

Mark Stanfill | Senior Support Escalation Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 16 Jan 2013 19:46

imageHere’s a new KB article we published today. This one describes an error you’ll get when trying to use an App-V Management Console that’s been installed to a drive other than the C drive. If you want to do this you’ll need to add the appropriate permissions for the alternate install location and you can get all the details here:

2800730 - Error granting access to an App-V package: Invalid input was passed (http://support.microsoft.com/kb/2800730)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 15 Jan 2013 21:25

imageHere’s one more App-V KB article we published today. This one discusses and issue where using the Microsoft Application Virtualization (App-V) Management Server website to grant access to a package to an Active Directory group fails. There are a couple different error messages you might get but they all come down to an issue with permissions on the AD containers. You can get all the details here:

2797968 - Error granting access to an App-V package: Invalid input was passed (http://support.microsoft.com/kb/2797968)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 15 Jan 2013 16:53

imageHere’s a new KB we published on an issue in App-V where the sequencer errors out and package creation fails. We’ve seen this a few times and it basically comes down to not having all the latest updates applied to the sequencing computer so the fix is pretty straight forward. You can read the entire article here:

2790852 - The Server App-V sequencing process fails with "The Sequencer could not stop the MSIServer service" (http://support.microsoft.com/kb/2790852)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 08 Jan 2013 22:30

imageHi everyone, Somaning Turwale here.  I recently went through the process of sequencing the Configuration Manager 2012 admin console and thought I’d share what I learned with you here.  

NOTE In my example below I am sequencing the Microsoft System Center 2012 Configuration Manager Admin Console for the 64-bit version of Windows 7 Service Pack 1.

1. Follow the best practices for the Microsoft Application Virtualization Sequencer:

http://technet.microsoft.com/en-us/library/dd351420.aspx

2. Build your clean sequencing system with the 64-bit version of Windows 7 Service Pack 1 and join it to the domain. 

3. Install .NET 4 full version on the Sequencer machine (http://www.microsoft.com/en-us/download/details.aspx?id=17851).

4. Copy the Tools folder from your ConfigMgr 2012 central site server to the sequencing machine and place it in the following path:

C:\Program files\Microsoft Configuration Manager\Tools

NOTE This is used for sequencing ConfigMgr 2012 Version 5.00.7711.0000 and build 7711

5. Install the App-V 4.6 SP1 Sequencer with Hotfix 8 (http://support.microsoft.com/kb/2761558)

6. Launch the Microsoft Application Virtualization Sequencer and select Create New Virtual Application Package.

7. Select the Create Package (Default) option and click Next.  Note that Prepare the Computer for Creating a Virtual Package may give the Warning “Windows Defender is active”.  If so, launch the Services.msc snap-in and stop the Windows Defender service.  After doing so, click Refresh and then click Next.

7. Select the Standard Application (default) option and click Next.

8. On the Select Installer screen, browse to the Tools folder and select ConsoleSetup.exe, then click Next.

9. Name the package ConfigMgr2012Console, leave other options as the defaults and click Next.

10. Once the ConfigMgr installation screen appears, click Install Configuration Manager 2012 and click Next.

11. Type the FQDN of the Central Site server name and click Next.

12. Leave the Destination Folder as the default (e.g. C:\Program Files(x86)\Microsoft Configuration Manager Console\) and click Next.

13. Click Install and wait for the installation to complete, then click Finish.

14. Now the ConfigMgr 2012 console will launch. Verify that everything functions properly and exit from the console.

15. Select the I am finished installing option and click Next.

16. Select the ConfigMgr console and run it. After launching the console close it.  Click Next to review the installation report and click Next when you’re done.

17. Select the Customize option and click Next.

18. If you would like to remove the "Remote Control View" then right-click and remove it.

19. Click Next and then Run All. Once the console launches completely, verify the settings and exit the console.

20. Select the Target OS, click Next and then select Create the Package. The package will be saved as ConfigMgr2012Console.

21. Copy the package to the App-V management content share.

22. Follow the normal procedure to import the package into your App-V Management server.

23. Verify that the console is published to the App-V users.

24. Ensure that the .NET 4 full version is installed on the App-V clients as it is a prerequisite for console.

25. Make sure that the App-V clients have the latest hotfix installed (e.g. 4.6.1.30151).

26. Ensure that you have the required permissions and connectivity to the Site server.

If all steps are followed correctly then the client should be able to launch the Configuration Manager console successfully.

Somaning Turwale | Support Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Thursday, 03 Jan 2013 14:24

written by – Ozge Yavuz, SDE

Introduction

App-V 5.0 “isolates” virtual applications from the operating system and other processes. This is done by hiding the application resources from everything else. One can imagine this as running the virtual application in a bubble that isolates the application from the outside world. Integration, on the other hand, can be thought of as tunnels punching through this bubble, exposing the virtual application capabilities to the native operating system and to the user in a controlled manner. This enables virtual applications to behave as native applications. Think about a shortcut of a virtual application residing on the user’s desktop. This shortcut is outside the virtual bubble and is not isolated since it is on user’s desktop. But this shortcut enables the user to launch the virtual application seamlessly as if it was a native application. This shortcut feature and some others make up the Integration component of App-V. Integration is a collection of subsystems that individually handle one specific integration area. The following is the list of integration subsystems currently available in App-V product:

· Shortcut Subsystem

· FTA Subsystem

· COM Subsystem

· Software Clients Subsystem

· Application Capabilities Subsystem

· URL Protocol Handler Subsystem

· App Path Subsystem

· Virtual Applications Subsystem

Extension Points

An extension point is a single integration unit such as a shortcut of a virtual application. Each integration subsystem can have one or more extension points (EPs). An example would be a virtual package having multiple shortcuts.

Integration Workflows

Integration has two separate work flows:

1. Sequencing: Capturing integration data from the application being sequenced

2. Publishing: Integrating the application to the native operating system during publishing of the package by using the data captured during sequencing

Sequencing

During sequencing of a package, integration subsystems are started after the target application is installed. These subsystems consume the application installation data that the installer lays down (e.g. shortcuts, FTAs, etc.) and then produce extension points (EPs) that end up in the package manifest.

 

 

Sample Package Manifest

 

Publishing

During publishing of an App-V package, Integration reads extension points from the package manifest, dynamic deployment configuration and dynamic user configuration files (if these configuration files are provided). Integration then merges EPs from all these sources and finally integrates these EPs to the native operating system.

 

Important:

Please note that throughout this blog entry, I will refer to publishing of a package as “integrating the package to the computer”. The reasoning behind that is integration of a package can be initiated externally by a publishing operation or internally when the package is already published to the user but not yet integrated. Further details are outside the scope of this article and will be discussed in a future blog entry.

Global vs. User Publishing

During publishing of an EP, App-V will automatically select where in the operating system the EP should be integrated based on how the package is published.

Global publishing

If the package is published globally (sometimes referred as machine publishing), the shortcuts will be created in public locations on the computer and other integration will happen in HKLM locations in the registry.

Examples:

o If a shortcut is to be created on the desktop, the location would be FOLDERID_PublicDesktop (%PUBLIC%\Desktop),

o If an FTA registration is to happen, it would be created under HKLM\Software\Classes

User publishing

This will place shortcuts in user locations and other integration to HKCU registry locations.

Examples:

o If a shortcut is to be created on the desktop, the location would be FOLDERID_Desktop (%USERPROFILE%\Desktop)

o If an FTA registration is to happen, it would be created under HKCU\Software\Classes

Backup, Restore and It’s Ownership

During integration, integration subsystems backup existing data of native applications that would be otherwise overwritten.

For example, if a native application is installed and has the .docx file type association, and a virtual application package with the .docx EP is being integrated, the file type association belonging to the native application is backed up first and then the EP is integrated. Also, when the package gets unpublished, the EP will be de-integrated first and the backed up .docx file type association will be restored.

App-V also tracks which package owns the backed up data and only restores it if the owner package gets de-integrated. This is to allow for two or more virtual application packages publishing the same EP (e.g. the same .docx file type association), the last published package should be the owner and if the first package gets unpublished first, we shouldn’t restore the backed up data so that we don’t overwrite the last package’s extension points.

· If two packages are competing for the same EP, the last package that is integrated takes ownership.

· If the first package gets unpublished, backed up data will NOT be restored since the package is no longer the owner of the backed up data.

· If the second package gets unpublished, backed up data will be restored.

This backup and restore process happens for each extension point, including shortcuts and registry-based subsystems.

Notifying Windows Shell of User Account

App-V client uses a separate process called AppVShNotify.exe during integration of a package to send notifications to the Windows Shell. For example, the Windows Shell requires applications (here, App-V Integration) to notify the Shell when a new shortcut on user’s desktop is created. When the Shell receives this notification, it refreshes the user’s desktop display. The AppVShNotify.exe process runs under the user account. It will be started when the first package for the user is published and will keep running until user logs out.

Dynamic Configuration Files

App-V uses dynamic configuration files to provide customizations to the virtual package since the package itself is not editable. These configuration files can be used to alter behavior of integration subsystems such as adding or editing a new shortcut.

These configuration files can be used to:

· Enable or disable integration subsystems. When a subsystem gets disabled, its EPs will not be integrated

· Provide extra configuration for integration subsystems (see COM subsystem below for an example)

· Replace EPs of subsystems

Important:

When a configuration file includes EPs of a subsystem, these extensions will replace all EPs defined in the package manifest. To edit or remove a single EP (e.g. a shortcut), all the EPs belonging to that subsystem should be copied first from the manifest and the EP in question edited or removed.

There are two types of configuration files:

· Dynamic User Configuration (DUC)

    • Configure the package for an individual user
      • E.g. add a new shortcut specific to the user to whom the package is being published
    • If a Dynamic Deployment Configuration (DDC) exist for the package, DUC replaces “User Configuration” section during integration

· Dynamic Deployment Configuration (DDC)

    • Configure the package for global publishing or user publishingon that machine
      • E.g. add a new shortcut for all users that get the package

o Can have a “User Configuration” section which can be overridden by DUC

The App-V Sequencer generates sample DUC and DDC files for each package to ease creation or modification of these documents. It uses EPs from the package manifest to prepopulate them.

Example Integration Scenarios

Let’s examine the example scenarios below using sample files to understand what happens during publishing. First, let’s introduce sample files:

When package is published to a user

· If no DDC or DUC provided during publishing, Shortcut 1 and Shortcut 2 are integrated

· If DDC is provided, only Shortcut 3 is integrated

· If DUC is provided, only Shortcut 4 is integrated

· If both DDC and DUC are provided, only Shortcut 4 is integrated

When package is published globally

In global publishing a DUC cannot be provided. So the scenarios become simpler

· If no DDC provided during publishing, Shortcut 1 and Shortcut 2 are integrated

· If DDC is provided, only Shortcut 3 is integrated

App-V client PowerShell Cmdlets and Integration

Below are the PowerShell cmdlets that are relevant to integration. See App-V 5.0 Client PowerShell Deep Dive for further details.

Add-AppVClientPackage <path to package> [- DynamicDeploymentConfiguration <path to file>]

o No integration of the extension points from the package is done

o Dynamic Deployment Configuration is optional

Publish-AppVClientPackage [- DynamicUserConfigurationPath <path to file>] [-Global]

o Package gets integrated

o Dynamic User Configuration is optional

o If Dynamic Deployment Configuration was provided to Add-AppvClientPackage, and/or Dynamic User Configuration is provided to Publish-AppvClientPackage, they will be used during integration

Unpublish-AppVClientPackage [-Global]

o Package gets de-integrated

o If Dynamic Deployment Configuration and/or Dynamic User Configuration was provided, they will be used during de-integration

Remove-AppVClientPackage

o If package is published globally: The package gets de-integrated immediately if not de-integrated before (by an Unpublish-App-VClientPackage)

o If package is published for user: The package gets de-integrated immediately if the user is logged on or next time the user logs on

Repair-AppVClientPackage [- Extensions] [-Global]

o If “Extensions” flag is provided, or if “-UserState” not provided, the package gets re-integrated, effectively repairing all extension points

Integration Subsystems

Following are the integration subsystems currently supported by App-V as of 5.0.

Shortcut Subsystem

Shortcuts are one of the main mechanisms by which a user can launch an application. The Shortcuts subsystem captures shortcuts that were created during installation. During publishing of a package, these shortcuts are recreated.

Note: For information about shortcuts, Shell Links on MSDN.

This is the only file-based integration subsystem that exists in App-V 5.0.

Manifest Example:

<Extension Category="App-V.Shortcut"> 

  <Shortcut>

    <File>[{Desktop}]\Shortcut.lnk</File>

    <Target>[{App-VPackageRoot}]\Folder\application.exe</Target>

    <Arguments />

    <WorkingDirectory />

    <ShowCommand>1</ShowCommand>

    <ApplicationId>[{App-VPackageRoot}]\Folder\application.exe</ApplicationId>

  </Shortcut>

</Extension>

FTA Subsystem

This subsystem allows file extensions to be associated with applications.

· FTAs usually associates a file extension to a ProgID

o Ex: .docx => Word.Document.12

· The ProgID for an FTA will usually have a shell command to execute

o Word.Document.12 \ shell \ Open \ command \ <Path to Winword.exe>

Notes:

1. As of App-V 5.0, the only supported shell extensions are:

a. Preview Handler

b. Icon Handler (partially)

2. For more information about FTAs, see File Types and File Associations on MSDN.

This is a registry-based integration subsystem.

Manifest Example

<Extension Category="App-V.FileTypeAssociation">

  <FileTypeAssociation>

    <FileExtension MimeAssociation="true">

      <Name>.abc</Name>

      <ProgId>AbcFile</ProgId>

    </FileExtension>

    <ProgId>

      <Name> AbcFile</Name>

      <Description>Description of the ProgID</Description>

      <EditFlags>65536</EditFlags>

      <ShellCommands>

        <DefaultCommand>Open</DefaultCommand>

        <ShellCommand>

          <ApplicationId>[{App-VPackageRoot}]\Folder\application.exe</ApplicationId>

          <Name>Open</Name>

          <CommandLine>"[{App-VPackageRoot}]\Folder\application.exe" "%1"</CommandLine>

        </ShellCommand>

        <ShellCommand>

          <ApplicationId>[{App-VPackageRoot}]\Folder\application.exe</ApplicationId>

          <Name>Print</Name>

          <CommandLine>"[{App-VPackageRoot}]\Folder\application.exe" /p "%1"</CommandLine>

        </ShellCommand>

      </ShellCommands>

    </ProgId>

  </FileTypeAssociation>

</Extension>

COM Subsystem

App-V has two subsystems to provide support for COM objects in a virtual application package.

· COM integration: Responsible for integration of COM objects, TypeLibs, etc. from the virtual application package to the native operating system. This is an integration subsystem and is covered in this document.

· COM virtualization: Isolation of COM objects when the virtual application is launched. This is a virtualization subsystem and is not covered in this document.

COM Integration

Com integration subsystem is responsible for integrating registration of COM objects from the App-V package. These registrations are captured during sequencing and are integrated during publishing.

Note: For more information about COM, see Component Object Model (COM) and COM Registry Keyson MSDN

This subsystem supports two types of registration:

· Out-of-process COM registration

· In-process COM registration

Note: Virtualization of In-process COM objects are not supported by the App-V 5.0 client and thus it is not guaranteed that such objects will function properly.

COM Modes

COM support in App-V can be configured using dynamic configuration files. These files provide a “COM Mode” setting that alters the behavior of the two COM subsystems (integration and virtualization)

The possible values for the “COM Mode” are:

· Off

· Isolated (default)

· Integrated

o Out-of-process registration (OOP)

o In-process registration (IP)

COM Mode

COM Integration

COM Virtualization

Off

No integration with OS

Off

Isolated

No integration with OS

On – renaming on

Integrated (OOP: N, IP: N)

No integration with OS

On – renaming off

Integrated (OOP: Y, IP: N)

Integrate only OOP

On – renaming off

Integrated (OOP: N, IP: Y)

Integrate only IP

On – renaming off

Integrated (OOP: Y, IP: Y)

Integrate both OOP and IP

On – renaming off

Renaming: Mechanism used by virtualization subsystems to “hide” named objects of the package (such as COM) from native applications by modifying the name of these objects

Sample Dynamic User Configuration

<UserConfiguration ....>

  <Subsystems>

     <COM Mode=“Integrated">

      <IntegratedCOMAttributes OutOfProcessEnabled="true" InProcessEnabled="false" />

    </COM>

</UserConfiguration>

 

Software Clients Subsystem

Allows virtual applications register to the software client list of the native operating system. This in turn allows actual users of the virtual applications to set default programs for certain tasks.

To set the default programs, a user can follow these steps: Control Panel > Default Programs > Set program access and computer defaults

Used for the following types:

· Email (MAPI)

· Instant messenger

· Media player

· Virtual machine for Java

Note: For more information, see How to Register an Internet Browser or Email Client with the Windows Start Menu on MSDN

Manifest Example

 <SoftwareClients Enabled="true">

  <ClientConfiguration EmailEnabled="true" />

  <Extensions>

    <Extension Category="App-V.SoftwareClient">

      <SoftwareClients>

        <EMail MakeDefault="true">

          <Name>Contoso Email</Name>

          <Description>An Email Client</Description>

          <DefaultIcon>[{ProgramFilesX86}]\Folder\application.exe,0</DefaultIcon>

          <InstallationInformation>

            <RegistrationCommands>

              <Reinstall>"[{ProgramFilesX86}]\Folder\reghelper.exe" /SetAsDefaultAppGlobal</Reinstall>

              <HideIcons>"[{ProgramFilesX86}]\Folder\reghelper.exe" /HideShortcuts</HideIcons>

              <ShowIcons>"[{ProgramFilesX86}]\Folder\reghelper.exe" /ShowShortcuts</ShowIcons>

            </RegistrationCommands>

            <IconsVisible>1</IconsVisible>

            <OEMSettings />

          </InstallationInformation>

          <ShellCommands>

            <ApplicationId>[{ProgramFilesX86}]\Folder\application.exe</ApplicationId>

            <Open>"[{ProgramFilesX86}]\Folder\application.exe" -mail</Open>

          </ShellCommands>

          <MAPILibrary>[{ProgramFilesX86}]\Folder\application.exe\mapi.dll</MAPILibrary>

          <MailToProtocol>

            <Description>Email URL</Description>

            <EditFlags>2</EditFlags>

            <DefaultIcon>[{ProgramFilesX86}]\Folder\application.exe,0</DefaultIcon>

            <ShellCommands>

              <ApplicationId>[{ProgramFilesX86}]\Folder\application.exe</ApplicationId>

              <Open>"[{ProgramFilesX86}]\Folder\application.exe" /email "%1"</Open>

            </ShellCommands>

          </MailToProtocol>

        </EMail>

      </SoftwareClients>

    </Extension>

  </Extensions>

</SoftwareClients>

 

Application Capabilities Subsystem

This subsystem exposes the capabilities of virtual applications to the native operating system. Users can use these capabilities to set default programs by: Control Panel > Set Default Programs.

Notes:

1. As of App-V client 5.0 this subsystem is integrated only when package is published globally

2. For more information, see Set Program Access and Computer Defaults (SPAD) on MSDN

URL Protocol Handler Subsystem

This subsystem exposes the URL protocol handing capability (such as “mailto:”) of an application to native operating system

Note: For more information about URL protocol handlers, see Registering an Application to a URI Scheme on MSDN

Manifest Example

<SoftwareClients Enabled="true">

  <ClientConfiguration EmailEnabled="true" />

  <Extensions>

    <Extension Category="App-V.SoftwareClient">

      <SoftwareClients>

        <EMail MakeDefault="true">

          <Name>Contoso Email</Name>

          <Description>An Email Client</Description>

          <DefaultIcon>[{ProgramFilesX86}]\Folder\application.exe,0</DefaultIcon>

          <InstallationInformation>

            <RegistrationCommands>

              <Reinstall>"[{ProgramFilesX86}]\Folder\reghelper.exe" /SetAsDefaultAppGlobal</Reinstall>

              <HideIcons>"[{ProgramFilesX86}]\Folder\reghelper.exe" /HideShortcuts</HideIcons>

              <ShowIcons>"[{ProgramFilesX86}]\Folder\reghelper.exe" /ShowShortcuts</ShowIcons>

            </RegistrationCommands>

            <IconsVisible>1</IconsVisible>

            <OEMSettings />

          </InstallationInformation>

          <ShellCommands>

            <ApplicationId>[{ProgramFilesX86}]\Folder\application.exe</ApplicationId>

            <Open>"[{ProgramFilesX86}]\Folder\application.exe" -mail</Open>

          </ShellCommands>

          <MAPILibrary>[{ProgramFilesX86}]\Folder\application.exe\mapi.dll</MAPILibrary>

          <MailToProtocol>

            <Description>Email URL</Description>

            <EditFlags>2</EditFlags>

            <DefaultIcon>[{ProgramFilesX86}]\Folder\application.exe,0</DefaultIcon>

            <ShellCommands>

              <ApplicationId>[{ProgramFilesX86}]\Folder\application.exe</ApplicationId>

              <Open>"[{ProgramFilesX86}]\Folder\application.exe" /email "%1"</Open>

            </ShellCommands>

          </MailToProtocol>

        </EMail>

      </SoftwareClients>

    </Extension>

  </Extensions>

</SoftwareClients>

App Path Subsystem

This subsystem exposes the App Path registration of a virtual application to the native operating system. Using this registration, the operating system can find the application’s executable. This feature is usually used by an application to avoid modifying the system PATH environment variable.

For example: When this registration is done, the user can start an application by providing the application name. To launch Microsoft Office Word one can:

· Start “Run” dialog

· Type Winword

Note: For more information, see Application Registrationon MSDN

Manifest Example

<Extension Category="AppV.AppPath">

  <AppPath>

    <Name>application.exe</Name>

    <ApplicationPath>[{AppVPackageRoot}]\path\application.exe</ApplicationPath>

    <PATHEnvironmentVariablePrefix>[{AppVPackageRoot}]\path\</PATHEnvironmentVariablePrefix>

    <ApplicationId>[{AppVPackageRoot}]\path\application.exe</ApplicationId>

  </AppPath>

</Extension>

Virtual Applications Subsystem

This subsystem provides a list of applications captured during sequencing. This list is usually consumed by other App-V components. Also, using dynamic configuration files, integration of EPs belonging to a particular application can be disabled. For example, if a package contains two applications, it is possible to disable all EPs belonging to one application, to only allow integration of EPs of the other application.

Manifest Example

<Applications xmlns="http://schemas.microsoft.com/appv/2010/manifest">

  <Application Id="[{AppVPackageRoot}]\Path\Application1.exe">

    <Target>[{AppVPackageRoot}]\Path\Application1.exe</Target>

    <VisualElements>

      <Name>Contoso E-mail Client</Name>

      <Version>1.2.0</Version>

    </VisualElements>

  </Application>

  <Application Id="[{AppVPackageRoot}]\Path\Application2.exe">

    <Target>[{AppVPackageRoot}]\Path\Application2.exe</Target>

    <VisualElements>

      <Name>Contoso News Reader</Name>

      <Version>1.2.1</Version>

    </VisualElements>

  </Application>

</Applications>

 

Author: "Anurag Juneja [MSFT]" Tags: "App-V"
Comments Send by mail Print  Save  Delicious 
Date: Monday, 17 Dec 2012 19:35

imageHere’s a new KB we published on an issue where App-V applications may stop working when the client’s virtual drive is being scanned by AV software. Generally when this happens you’ll see a 000000C3 error in the SFTLOG.TXT. 

2792121 - Virtualized applications fail to launch and generate 00-000000C3 errors in sftlog.txt (http://support.microsoft.com/kb/2792121)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Thursday, 13 Dec 2012 18:33

imageLooking for a way to find packages in Microsoft App-V v5 client connection groups using PowerShell? If so then this KB article is for you:

2780809 - How to use PowerShell to find packages in App-V v5 client connection groups (http://support.microsoft.com/kb/2780809)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 12 Dec 2012 22:26

imageJust a quick heads up on a KB article we just published. When you deploy a virtualized app to an App-V v5 client using ConfigMgr, as part of the process ConfigMgr removes the Publishing Servers from that client. This is by design but it may cause some confusion if you’re not expecting it. 

You can read the entire article here:

2780808 - Publishing Servers are automatically removed from App-V v5 clients (http://support.microsoft.com/kb/2780808)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 12 Dec 2012 22:16

imageHere’s an new KB article we published that is particularly interesting. In the article, it talks about five common App-V scenarios and lists the basics of what clients are supported, a general configuration and even how ConfigMgr may enter the picture. If you’re trying to get a handle on your App-V v5 implementation then this will be a handy guide.

You can read the article here:

2780807 - Five common App-V v5 implementation scenarios (http://support.microsoft.com/kb/2780807)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Wednesday, 12 Dec 2012 17:39

imageHere’s a new KB article that tells you how to fix an issue where removing and then adding the same package version in the Microsoft Application Virtualization console fails and returns error 0x8007012F. This is something you’d probably only see in a test environment but if you happen to run into it at least now you’ll know why it happens and how to fix it.

You can read the entire article here:

2780304 - Adding a package version in Microsoft Application Virtualization returns error 0x8007012F (http://support.microsoft.com/kb/2780304)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Date: Tuesday, 11 Dec 2012 23:21

imageHere’s another new KB article we published. This one tells you how to fix an issue where launching an app virtualized with App-V v5 fails with error 00090001 if the path to the container file is incorrect.

You can read the entire article here:

2783096 - Launching a virtual application fails with error code 0x3E500D05-00090001 (http://support.microsoft.com/kb/2783096)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Author: "J.C. Hornbeck"
Comments Send by mail Print  Save  Delicious 
Next page
» You can also retrieve older items : Read
» © All content and copyrights belong to their respective authors.«
» © FeedShow - Online RSS Feeds Reader