Blog Post: App-V error 0x00000000 after SCCM integration

I've just gone through integrating SCCM and App-V (post to follow!) and suddenly all the packages stop working with the following error.

So to give a bit of background, on this client, App-V in full infrastructure mode was fine. In order to test SCCM and App-V integration I installed the SCCM client on the desktop and SCCM streamed applications to it without issue.

I then decided to roll back to infrastructure mode (demo's et all) and bingo, the above error pops up.

So....

When you install the SCCM client, the App-V client assumes that from now on, all streaming will be carried out by SCCM and takes a back seat - in effect the SCCM client takes control of the App-V client.

The following registry settings are changed

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface

Before SCCM client install
LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>"
DDELaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>

With the SCCM client installed:  
LaunchCommand "C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"
DDELaunchCommand "C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"

Change this back and it works - i've yet to see if it reverts and I don't want to have to remove the SCCM client.

Michelle Behennah Julie Benz Saira Mohan Brittny Gastineau