locked
Question on APP-V with SCCM RRS feed

  • Question

  • * What is the procedure to do an active upgrade with SCCM?

    * How do we remove virtual applications in SCCM? Does it reflect in the APP-V client when it is removed?


    J.Caleb Kirubakaran
    Tuesday, April 7, 2009 6:21 AM

Answers

  • Hi J.Caleb,

    Did you check the document Virtual Application Management with Microsoft Application Virtualization 4.5 and System Center Configuration Manager 2007 R2? 
    I think it explains your questions pretty much in the sections:
    - Upgrade a Previously Deployed Virtual Application
    - Delete a Virtual Application from All Members of a Collection or a Specific Client

    It can be downloaded here: http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/App-V_and_ConfigMgr_Whitepaper_Final.docx

    If you have any additional (detailed) questions please let me know.

    Regards,

    Ment van der Plas
    Tuesday, April 7, 2009 6:55 AM
    Answerer

All replies

  • Hi J.Caleb,

    Did you check the document Virtual Application Management with Microsoft Application Virtualization 4.5 and System Center Configuration Manager 2007 R2? 
    I think it explains your questions pretty much in the sections:
    - Upgrade a Previously Deployed Virtual Application
    - Delete a Virtual Application from All Members of a Collection or a Specific Client

    It can be downloaded here: http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/App-V_and_ConfigMgr_Whitepaper_Final.docx

    If you have any additional (detailed) questions please let me know.

    Regards,

    Ment van der Plas
    Tuesday, April 7, 2009 6:55 AM
    Answerer
  • Hello

    There is also additional documentation available using the following URL.

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

    Thanks,


    Dan Bernhardt [MSFT]
    Tuesday, April 21, 2009 2:02 PM
    Answerer
  • Went through the document suggested but could you tell me whether anyone has had success performing an active upgrade for a virtual application with SCCM+APP-V client. Coexistance upgrade of virtual application works fine with SCCM.

    Is it a functionality lost with the Integration of SCCM R2. Or do we have a workaround to get this to work??


    J.Caleb Kirubakaran
    Monday, April 27, 2009 12:34 PM
  • Are you running SCCM with or without R2 then? Or are you refering to a behaviour that worked on SCCM "without" but does not work with R2 any longer?

    The reason for asking is that there _could_ be significant differences between both SCCM versions with regards to App-V (however, on the other hand both versions could be treated the same if desired)


    Falko
    Tuesday, April 28, 2009 1:35 PM
    Moderator
  • Are you running SCCM with or without R2 then? Or are you refering to a behaviour that worked on SCCM "without" but does not work with R2 any longer?

    The reason for asking is that there _could_ be significant differences between both SCCM versions with regards to App-V (however, on the other hand both versions could be treated the same if desired)


    Falko
    Tuesday, April 28, 2009 1:36 PM
    Moderator
  • Are you running SCCM with or without R2 then? Or are you refering to a behaviour that worked on SCCM "without" but does not work with R2 any longer?

    The reason for asking is that there _could_ be significant differences between both SCCM versions with regards to App-V (however, on the other hand both versions could be treated the same if desired)


    Falko
    Tuesday, April 28, 2009 1:36 PM
    Moderator
  • Im using Microsoft SCCM 2007 R2 (4.00.6221.1000) its an evaluation version. Would that make a difference?
     

    J.Caleb Kirubakaran
    Tuesday, April 28, 2009 3:13 PM
  • To give you a better idea about the issue... I have sequenced winzip 3.1 and then opeend for upgrade and sequenced winzip 3.3. I want to do an active upgrade with these packages..

    Iam able to do the active upgrade with the APP-V Server and client model. 

    But Iam tryin to do the active upgrade with the integration of SCCMR2. Is active upgrade possible???

    I get the following error while doing so

    Configuration Manager - Program Failed. 
    The package could not be registered with the application virtualization management client.

    Please find the VirtualApp.log details attached below.

    OverrideURL is set as [http://SCCMTEST.NIBR.WIPRO.COM:80/SMS_DP_SMSPKGE$/VirtualAppStreaming/NIB0005E/{E328B53B-BDC6-47B1-A02F-95EA67049F65}/NIB0005E.sft] VAppLaunchManager 28.04.2009 19:28:15 824 (0x0338)
    Successfully updated OverrideURL [http://SCCMTEST.NIBR.WIPRO.COM:80/SMS_DP_SMSPKGE$/VirtualAppStreaming/NIB0005E/{E328B53B-BDC6-47B1-A02F-95EA67049F65}/] for SG Package Guid [{C1592596-7D0C-4798-A292-F47F5AD9643E}]. VAppLaunchManager 28.04.2009 19:28:15 824 (0x0338)
    Registering the virtual application package [NIB0005E] with the AppVirtMgmt client. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Searching for file using pattern: [\\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\*manifest.xml] VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Found file \\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\WinRar_3.30_L_EN_01_manifest.xml. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Searching for file using pattern: [\\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\*.SFT] VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Found file \\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\NIB0005E.sft. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Loading package properties from the manifest file: \\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\WinRar_3.30_L_EN_01_manifest.xml. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Checking for changes to key package properties. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    The version guid for the package has not changed. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    The SCCM package id for the package has not changed. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    The delivery method for the package content has not changed. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    The key properties for the package have not changed. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    The current state for package guid [{C1592596-7D0C-4798-A292-F47F5AD9643E}] is Failure. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    The package name is WinRar_3.30_L_EN_01. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Retrieving the AppVirtMgmt client install path from SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Checking if the file C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM exists. VAppRegistration 28.04.2009 19:38:54 2860 (0x0B2C)
    Opened the root\microsoft\appvirt\client WMI namespace. VAppQuery 28.04.2009 19:38:54 2860 (0x0B2C)
    BuildWMIObjectPath completed successfully.  Path = Package.PackageGUID="C1592596-7D0C-4798-A292-F47F5AD9643E". VAppQuery 28.04.2009 19:38:54 2860 (0x0B2C)
    Found the package object Package.PackageGUID="C1592596-7D0C-4798-A292-F47F5AD9643E". VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    The virtual package {C1592596-7D0C-4798-A292-F47F5AD9643E} is not in use. VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    CVAppQuery::PackageInUse() completed successfully. VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    CVAppPackageInfo::WriteToRegistry() succeeded. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    Registering the launch tool VappLauncher.exe for virtual app shortcuts. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    The launch tool VappLauncher.exe is already registered for the OSD file open command. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    The launch tool VappLauncher.exe is already registered for the Launch command. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    The DDE launch tool VappLauncher.exe is already registered for the Launch command. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    Successfully registered the VappLauncher.exe launch utility with the AppVirtMgmt client. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    Retrieving the AppVirtMgmt client install path from SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    Checking if the file C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM exists. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    Opened the root\microsoft\appvirt\client WMI namespace. VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    BuildWMIObjectPath completed successfully.  Path = Package.PackageGUID="13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096". VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    Found the package object Package.PackageGUID="13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096". VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    The virtual package {13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096} is not in use. VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    CVAppQuery::PackageInUse() completed successfully. VAppQuery 28.04.2009 19:38:55 2860 (0x0B2C)
    Attempting to remove Package [{13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096}] which was not registered via SCCM Software distribution. VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    Executing command line: "C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" DELETE PACKAGE:{13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096} /GLOBAL VAppRegistration 28.04.2009 19:38:55 2860 (0x0B2C)
    The command completed with exit code 0. VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    Removed Package [{13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096}] which was not registered via SCCM Software distribution. VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    The AppVirtMgmt client is configured for use with SCCM. VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    ADD PACKAGE command line = ["C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" ADD PACKAGE:"WinRar_3.30_L_EN_01" /MANIFEST "\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\WinRar_3.30_L_EN_01_manifest.xml" /OverrideUrl "FILE://\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\NIB0005E.sft"] VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    Executing command line: "C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" ADD PACKAGE:"WinRar_3.30_L_EN_01" /MANIFEST "\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\WinRar_3.30_L_EN_01_manifest.xml" /OverrideUrl "FILE://\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\NIB0005E.sft" VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    The command completed with exit code 6156. VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    CVAppRegistration::RunAddPkgCommand failed. (0x80009101) VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    Succeeded loading resource DLL 'C:\WINDOWS\system32\CCM\1033\swd_res.dll' VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    Raising event:
    [SMS_CodePage(850), SMS_LocaleID(2055)]
    instance of CLIMSG_VIRTUALAPP_ERROR_PACKAGEADD_FAILURE
    {
     AdvertisementId = "NIB2004F";
     ClientID = "GUID:6E81D768-9347-46BB-90B9-FF6F9648701D";
     DateTime = "20090428140856.911000+000";
     ErrorCode = "0x0000180C";
     ErrorMessage = "The command failed with error 0x0000180C.";
     MachineName = "ARRCLIENT3";
     PackageID = "NIB0005E";
     ProcessID = 560;
     SiteCode = "NIB";
     ThreadID = 2860;
     VirtualAppPackageGUID = "{C1592596-7D0C-4798-A292-F47F5AD9643E}";
     VirtualAppPackageName = "WinRar_3.30_L_EN_01";
    };
     VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    Raised ADD PACKAGE Registration Failure event for Ad: NIB2004F, PackageID: NIB0005E, Name: WinRar_3.30_L_EN_01, PackageGUID: {C1592596-7D0C-4798-A292-F47F5AD9643E} VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    CVAppRegistration::ExecuteAdd failed for the virtual application package. (0x80009101) VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    CVAppPackageInfo::WriteToRegistry() succeeded. VAppRegistration 28.04.2009 19:38:56 2860 (0x0B2C)
    Registering the virtual application package [NIB0005E] with the AppVirtMgmt client. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Searching for file using pattern: [\\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\*manifest.xml] VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Found file \\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\WinRar_3.30_L_EN_01_manifest.xml. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Searching for file using pattern: [\\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\*.SFT] VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Found file \\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\NIB0005E.sft. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Loading package properties from the manifest file: \\SCCMTEST.NIBR.WIPRO.COM\SMSPKGE$\NIB0005E\WinRar_3.30_L_EN_01_manifest.xml. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Checking for changes to key package properties. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    The version guid for the package has not changed. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    The SCCM package id for the package has not changed. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    The delivery method for the package content has not changed. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    The key properties for the package have not changed. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    The current state for package guid [{C1592596-7D0C-4798-A292-F47F5AD9643E}] is Failure. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    The package name is WinRar_3.30_L_EN_01. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Retrieving the AppVirtMgmt client install path from SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Checking if the file C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM exists. VAppRegistration 28.04.2009 20:08:50 4056 (0x0FD8)
    Opened the root\microsoft\appvirt\client WMI namespace. VAppQuery 28.04.2009 20:08:50 4056 (0x0FD8)
    BuildWMIObjectPath completed successfully.  Path = Package.PackageGUID="C1592596-7D0C-4798-A292-F47F5AD9643E". VAppQuery 28.04.2009 20:08:50 4056 (0x0FD8)
    Found the package object Package.PackageGUID="C1592596-7D0C-4798-A292-F47F5AD9643E". VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    The virtual package {C1592596-7D0C-4798-A292-F47F5AD9643E} is not in use. VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    CVAppQuery::PackageInUse() completed successfully. VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    CVAppPackageInfo::WriteToRegistry() succeeded. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    Registering the launch tool VappLauncher.exe for virtual app shortcuts. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    The launch tool VappLauncher.exe is already registered for the OSD file open command. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    The launch tool VappLauncher.exe is already registered for the Launch command. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    The DDE launch tool VappLauncher.exe is already registered for the Launch command. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    Successfully registered the VappLauncher.exe launch utility with the AppVirtMgmt client. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    Retrieving the AppVirtMgmt client install path from SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    Checking if the file C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM exists. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    Opened the root\microsoft\appvirt\client WMI namespace. VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    BuildWMIObjectPath completed successfully.  Path = Package.PackageGUID="13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096". VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    Found the package object Package.PackageGUID="13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096". VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    The virtual package {13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096} is not in use. VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    CVAppQuery::PackageInUse() completed successfully. VAppQuery 28.04.2009 20:08:51 4056 (0x0FD8)
    Attempting to remove Package [{13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096}] which was not registered via SCCM Software distribution. VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    Executing command line: "C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" DELETE PACKAGE:{13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096} /GLOBAL VAppRegistration 28.04.2009 20:08:51 4056 (0x0FD8)
    The command completed with exit code 0. VAppRegistration 28.04.2009 20:08:52 4056 (0x0FD8)
    Removed Package [{13C82CAB-E3DD-4DC5-8D1D-076E1F6D2096}] which was not registered via SCCM Software distribution. VAppRegistration 28.04.2009 20:08:52 4056 (0x0FD8)
    The AppVirtMgmt client is configured for use with SCCM. VAppRegistration 28.04.2009 20:08:52 4056 (0x0FD8)
    ADD PACKAGE command line = ["C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" ADD PACKAGE:"WinRar_3.30_L_EN_01" /MANIFEST "\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\WinRar_3.30_L_EN_01_manifest.xml" /OverrideUrl "FILE://\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\NIB0005E.sft"] VAppRegistration 28.04.2009 20:08:52 4056 (0x0FD8)
    Executing command line: "C:\Program Files\Microsoft Application Virtualization Client\SFTMIME.COM" ADD PACKAGE:"WinRar_3.30_L_EN_01" /MANIFEST "\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\WinRar_3.30_L_EN_01_manifest.xml" /OverrideUrl "FILE://\\\\SCCMTEST.NIBR.WIPRO.COM\\SMSPKGE$\\NIB0005E\\NIB0005E.sft" VAppRegistration 28.04.2009 20:08:52 4056 (0x0FD8)
    The command completed with exit code 6156. VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)
    CVAppRegistration::RunAddPkgCommand failed. (0x80009101) VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)
    Succeeded loading resource DLL 'C:\WINDOWS\system32\CCM\1033\swd_res.dll' VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)
    Raising event:
    [SMS_CodePage(850), SMS_LocaleID(2055)]
    instance of CLIMSG_VIRTUALAPP_ERROR_PACKAGEADD_FAILURE
    {
     AdvertisementId = "NIB2004F";
     ClientID = "GUID:6E81D768-9347-46BB-90B9-FF6F9648701D";
     DateTime = "20090428143853.058000+000";
     ErrorCode = "0x0000180C";
     ErrorMessage = "The command failed with error 0x0000180C.";
     MachineName = "ARRCLIENT3";
     PackageID = "NIB0005E";
     ProcessID = 560;
     SiteCode = "NIB";
     ThreadID = 4056;
     VirtualAppPackageGUID = "{C1592596-7D0C-4798-A292-F47F5AD9643E}";
     VirtualAppPackageName = "WinRar_3.30_L_EN_01";
    };
     VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)
    Raised ADD PACKAGE Registration Failure event for Ad: NIB2004F, PackageID: NIB0005E, Name: WinRar_3.30_L_EN_01, PackageGUID: {C1592596-7D0C-4798-A292-F47F5AD9643E} VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)
    CVAppRegistration::ExecuteAdd failed for the virtual application package. (0x80009101) VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)
    CVAppPackageInfo::WriteToRegistry() succeeded. VAppRegistration 28.04.2009 20:08:53 4056 (0x0FD8)

    Sorry for the big post....

    J.Caleb Kirubakaran
    Tuesday, April 28, 2009 3:22 PM
  • Hello,

    And what steps did you do to proceed with the upgrade with SCCM?

    /Znack
    Tuesday, April 28, 2009 4:21 PM
  • Followed the steps mentioned below to upgrade the package.

    * Right-click the virtual application package and then click Update Package.
    * Specify the network location of the updated Manifest XML file that you created when you upgraded the sequenced application.
    * Type the name,Version, Manufacturer, Language, and an optional Comment
    * Checked "update all associated distribution points with a new package source version"
    * Checked "re-run advertisements withe existing mandatory assignments"
    * Next-->close.

    Correct me if Iam wrong.


    J.Caleb Kirubakaran
    Wednesday, April 29, 2009 4:37 AM
  • Hello,

    Here are the steps copy-and-pasted from the SCCM R2 / APP-v integration whitepaper;

    Upgrade a Previously Deployed Virtual Application

    ·         Virtual application packages that have been deployed with Configuration Manager can easily be upgraded to include service packs, software updates, etc.

    ·         To deploy multiple versions of the same application to different collections, it is necessary to create separate sequenced application packages (one for each version) and import them into Configuration Manager to create separate Configuration Manager virtual application packages with different Configuration Manager package IDs.  This can be done using the Save As feature in the Sequencer program.

    ·         When a virtual application package is updated, Configuration Manager evaluates the data source for the package and makes the necessary file updates to the advertised application.

    ·         The updated package must be advertised again to Configuration Manager Clients and/or users in order for the users to use the updated applications in the package. Virtual application packages that have been deployed with Configuration Manager can be updated by using the Virtual Application Package Update Wizard or by editing the package source directory. Users must exit and restart the virtual application for the updated version to be available.

    More general information regarding this, but written in a more detailed description is here (same info)
    http://msmvps.com/blogs/daniel/archive/2009/04/16/configuration-manager-2007-r2-with-app-v-integration-clarification.aspx

    Wednesday, April 29, 2009 4:51 AM
  • I am getting exaclty the same issue.

    I have also noticed that it takes a number of hours before attempting to update and then I get the same "CVAppRegistration::RunAddPkgCommand failed (0x80009101)"error.

    did you ever figure this out? I have seen this update functionality working on a video http://www.youtube.com/watch?v=AVE6TsaLb6I

    but I can't replicate this at all!

    Wednesday, April 21, 2010 2:58 PM
  • Hello,

    See this page for the error-code;

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

    I would investigate the app-v log files to determine what happend.

    /Znack

    Wednesday, April 21, 2010 6:39 PM
  • Hi J.Caleb,

    I know that this is an old thread, bu I'm wondering if you ever discovered a solution to this 0x80009101 error when attempting to update a virtual package via SCCM? 

    Cheers, Mike

    Wednesday, October 27, 2010 2:38 PM
  • Hello,

    See this blog-post;

    http://www.viridisit.se/eng/blog/?p=921 


    /Znack
    • Proposed as answer by znack Wednesday, April 20, 2011 1:21 PM
    Monday, April 11, 2011 12:42 PM
  • How did you install the App-V client?  Did you use a command line or did you run the install wizard?  Where any variables used in your paths?

    Wednesday, March 28, 2012 3:39 AM