locked
App-V Application won't remove shortcuts from all programs during cleanup RRS feed

  • Question

  • We are streaming an application via SCCM to Windows Xp Clients.   The problem is when I remove the computer from the collection it exits with 0 on the clean up but it wont remove the start menu shortcuts.  I have verifyied I have the checked the box to remove the package when not adversisted.  Any help would be apprecitaded..

    Here is the results of the log file.

    We are streaming an application via SCCM to Windows Xp Clients.   The problem is when I remove the computer from the collection it exits with 0 on the clean up but it won't remove the start menu shortcuts.  I have verified I have the checked the box to remove the package when not advertised.  Any help would be appreciated..

    Here is the results of the log file.


    Policy deleted for advertisement ASC20047 package SCM00081 program [Virtual application]      7/21/2009 11:01:27 AM  288 (0x0120)

    Evaluating deleted virtual application policy for delete action [PackageID=SCM00081, AdvertisementID=ASC20047]                7/21/2009 11:01:27 AM  288 (0x0120)

    Creating virtual app Delete Policy for Package ID = [SCM00081], Advertisement ID = [ASC20047]                7/21/2009 11:01:27 AM         288 (0x0120)

    CExecutionRequest::Service Windows Manager has allowed us to run.  7/21/2009 11:01:27 AM  288 (0x0120)

    Executing program {12C356EA-5C6B-4B49-B9CE-1DEB15670839} /DeletePkg in Admin context     7/21/2009 11:01:27 AM  288 (0x0120)

    Execution Request for package SCM00081 program [Virtual application]:Cleanup state change from NotExist to NotifyExecution               7/21/2009 11:01:27 AM  288 (0x0120)

    Execution Manager timer has been fired.             7/21/2009 11:01:27 AM  3904 (0x0F40)

    Executing program as a virtual application registration.   7/21/2009 11:01:27 AM  288 (0x0120)

    SCCM package version number : 6.          7/21/2009 11:01:27 AM  288 (0x0120)

    CVirtualAppExecution::ExecuteProgram succeeded.       7/21/2009 11:01:31 AM  288 (0x0120)

    Script for  Package:SCM00081, Program: [Virtual application]:Cleanup succeeded with exit code 0             7/21/2009 11:01:31 AM         288 (0x0120)

    Execution is complete for program [Virtual application]:Cleanup. The exit code is 0, the execution status is Success                7/21/2009 11:01:31 AM  2784 (0x0AE0)

    Could not find the policy in WMI for package SCM00081 program [Virtual application]:Cleanup   7/21/2009 11:01:31 AM  2784 (0x0AE0)

     


    • Edited by JBCMD4 Tuesday, July 21, 2009 8:02 PM
    Tuesday, July 21, 2009 7:40 PM

Answers

  • Weird.. I deleted it off of the DP, re-advertised it to the machine, and then removed it.. This time it worked.. Weird ____.. I'm not sold on this APP-V stuff seems like the old MSI app packaging is still the way to go..


    Thank you all for your help..

    • Proposed as answer by znack Wednesday, July 29, 2009 3:11 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 3:25 PM
    Wednesday, July 29, 2009 2:11 PM

All replies

  • Hello,

    Is it still available within the app-v client management console?

    /Znack
    Monday, July 27, 2009 7:47 PM
  • We are using SCCM to deploy and manage it.
    Tuesday, July 28, 2009 12:33 PM
  • Hello,

    Yeah, I didn't question that in any manner......
    What applications are available within the app-v _CLIENT_ management console?

    /Znack
    Tuesday, July 28, 2009 12:35 PM
  • We are not using the App-v Client management console because we useing SCCM to manage it.   The application is still available in SCCM but I have removed everyone from the collection but it doesn't remove the application form the computer.

    Thank you for your help
    Tuesday, July 28, 2009 12:38 PM
  • Hello,

    A default client installation should still make the Client Management Console available, on the client. This should be able to be accessed regardless of what components are used in the background.

    Can you confirm that the App-v Client Management console is not possible to be accessed directly via the Administrative Tools or the snap-in available in the installation directory on the client, even though you are using SCCM to MANAGE the client.

    /Znack

    Tuesday, July 28, 2009 12:49 PM
  • JBCMD4,

    A few things.

    [PerUser  "Your question is per computer, but I want to include per user for others finding this thread"]

    An important question here will be how it became distributed to the computer to begin with.  Deployment of a virtual applciation via SCCM can be per user or per computer.  Often, attempts to distribute per user are deployed on a per computer basis.  I find that if you really want per-user, when creating assignments, you should not assign to a group of users, but to individual users or you end up with a per-computer deployment (/GLOBAL) that occurs as soon as one user in that group logs into the computer.  I don't know that this would cause your issue but suspect that it becomes really hard for the computer to "know" when all users have had the app removed.

    Second, it is important to ensure durring virtual application advertisement creation that the checkbox for deleting the application if the advertisement is removed is set (but you probably know that already).
    [/PerUser]

    Znack is correct that while you might not normally use the CMC, it will be there on the client (under administrative tools) any time the client is installed.  The CMC is your cleanup tool which is the equivalent of "Add Remove Programs".  Even with natively installed apps via SCCM, sometimes you have to perform some cleanup.  For Virtual Applications, use the Client Management Console.

    Similarly, troubleshooting will require looking at App-V stuff.  The SCCM client log you posted shows no issue, so the next step is to look at the App-V client log.  This appears as a .log file in the folder the App-V client is installed into, plus the windows event log (application).  Check that out.

    tim
    Tuesday, July 28, 2009 1:08 PM
    Moderator
  • Thank you.. There is nothing in the windows event logs but this is from the VirtualApp.log from within the SCCM Log folder.

    Failed to get the application object [Application.Name="BMC Remedy User 7.5.0.2",Version=""] from WMI.  Error (0x80041002) 7/28/2009 8:08:57 AM 2880 (0x0B40)
    GetSoftGridPackageID() failed for virtual application ["BMC Remedy User 7.5.0.2"]. (0x80041002) 7/28/2009 8:08:57 AM 2880 (0x0B40)
    CVAppQuery::GetPackageData() failed for virtual application ["BMC Remedy User 7.5.0.2"]. (0x80041002) 7/28/2009 8:08:57 AM 2880 (0x0B40)
    Failed to call spVAppQuery->GetPackageData, return code = 0x80041002. 7/28/2009 8:08:57 AM 2880 (0x0B40)

    Of course this is what I got when I clicked on the Icon to launch it but I would assume I would get something like this because of its half uninstalled state.  I checked the CMC and the application is not showing up in the application list. O.. I also verified that the check box is checked to uninstall the application when its no longer advertised.  Please let me know if you can think of something else..

     

    Thank you.

     

    Tuesday, July 28, 2009 1:35 PM
  • Hello,

    From the Client Management Console check the path of the log-file for APP-V (should be in %ALLUSERSPROFILE% as default in a non-upgrade scenario).

    Review it and see if you can locate anything related to the removal
    Check VirtualApp.log  again, see if any related messages to the removal of the package is shown, for a list of errors messages see the white-paper;
    http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/App-V_and_ConfigMgr_Whitepaper_Final.docx

    In regards to troubleshoot there is also a section in the whitepaper explaining where log-files are located, howto interpret the error messages and where to look for possible solutions.

    The sequencing whitepaper contains more information for dissecting the app-v logs;
    http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/App-45_Sequencing_Guide_Final.docx

    /Znack
    Tuesday, July 28, 2009 2:00 PM
  • It has been deployed per computer not per user.

    Thanks.

    Tuesday, July 28, 2009 6:16 PM
  • The message you posted indicated that the version string for the application was empty.  This is unusual.  Please check the application (perhaps notepad.exe on the OSD from the original source?) and see if indeed the version string was empty.  In either case this might be a clue.

    If is very strange that the CMC says that the app is gone and yet you still see icons.  Oh, is roaming profiles in use?

    tim
    Wednesday, July 29, 2009 3:16 AM
    Moderator
  • Hello,

    Tim, since its a per computer deployment, the roaming profile shouldn't be an issue - because everything is setup within the %ALLUSERSPROFILE% right?

    JBCMD4, where are the icons-placed? %ALLUSERSPROFILE% or %USERPROFILE%?

    /Znack
    Wednesday, July 29, 2009 5:07 AM
  • Weird.. I deleted it off of the DP, re-advertised it to the machine, and then removed it.. This time it worked.. Weird ____.. I'm not sold on this APP-V stuff seems like the old MSI app packaging is still the way to go..


    Thank you all for your help..

    • Proposed as answer by znack Wednesday, July 29, 2009 3:11 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 3:25 PM
    Wednesday, July 29, 2009 2:11 PM