Virtualization

Hi,

I have had MS support for 40 to 50 houres, and not get any explanation why, but we have talk about WMI timing issue..

So this hot fix can maybe help.
http://support.microsoft.com/kb/2532192

I can see the same issue in SCCM 2012 Beta 2, here we have also seen that the icon get wrong graphics, and when you deploy an new App-V application to that box the icon flips like a jackpot machine, and you get new graphics for your icon.

In SCCM 2007 we have seen an other issue. Lets say you create an App-V package with the q:\app1.r01 and you deploy this package with CM07. Then you want to add some more to the original package and do an upgrade in CM07 this package often get stucked at the client. Then we have to clean the Windows box from the original package and then redeploy the upgraded package. Then it works fine. But it take much time to logon and clean old crap from the App-V client.

I think it is a general cleanup problem with the App-V client.

/SaiTech

If you delete the advertisement in SCCM it doesn't mean the app is uninstalled automatically. To remove the app from the App-V client there are several commands...

Clear

The clear task can be performed to remove the shortcuts and file type associations for an application. None of the PKG files are removed during this administrative operation. This process could be done if a user is experiencing problems with file type associations and you need to remove all of the FTAs created by App-V.

Unload/Delete
The Unload or Delete operation will delete all of the PKG files except the per user UsrVol_sftfs_v1.pkg file. This will retain any user changes if the package is then loaded or published again to the client. This process also deletes the package from the client cache. The difference between the two functions is the unload operation does not delete the shortcuts and file type associations created for the application in the package
The exact commands can be found here: http://technet.microsoft.com/en-us/library/cc817090.aspx

If you delete the advertisement in SCCM it doesn't mean the app is uninstalled automatically

Are you sure ? It does here, if I go into the App-V client on a workstation the package has removed itself from the list but sometimes the shortcuts and their folders remain.

Actually, you're right. It's supposed to remove the apps. I was under the impression it didn't because for the one customer I used the App-V/SCCM combination, I always had shortcut junk in my start menu too.

Anyways, I've made some calls. Turns out there's several possibilities:

- App-V client has a slight delay in removing the apps sometimes. So it could just take a while before they're really gone.
- Besides the delay from the App-V client, it's also possible the Start Menu is displaying things that aren't there anymore. Somehow the Start Menu seems to have a delay of it's own.

A reboot might help in speeding up the updatint process of the above two.

- 3rd option is a bit tricky. Apparently it's also possible that the shortcuts have been stored in the roaming profile (if you use this). If that's the case, you'll have to remove it from the roaming profile manually. This can occur in situations where 1 user is logged on to more than 1 machine and the app is removed during that time (but the clients never recieve this at the same time with SCCM and next that happens is some hocus pocus profile sync issues??). If you're having this issue on a test account that you use a lot it might be more likely that this is the problem....

Thanks, I'll look into it a bit more. All our shortcuts get sent to ProgramData so nothing will be roaming (in theory [;)] )

Hey Jon, We've also found that deleting the Advertisement often leaves shortcuts/folders in the start menu. We've written a script that can remove these. Seems like the App-V/SCCM integration isn't as smooth as we're led to believe.

Cheers, Mike

Wierd, that should not be the case using defaults. I'll have to take a quick poke into a live environment to double check but I believe you set that behavior in the advertisement.

My bad, it is set at the package level.


Almost would be more useful at the advertisement level.

Thanks for that kkaminsk, just checked the package and it has that ticked.
The package is actually removing so that side of things is kicking in ok, its just the shortcuts that remain, which then cause errors and grief when users click on them.
Michael - Thanks for that, scripts are an option but ideally I'd like to find a cleaner way or work out why they still remain sometimes.

Anyway, I've got access now to a PC displaying these symptons so I'll take a closer look and report back anything useful.....

So are you saying that the package is remove from the app-v client console but the shortcuts are still in the user profile?

Jon, Just curious. Are you advertising to machines or users?

Kevin, in our case yes, the app is removed from the console, but the icons remain in the start menu. This isn't always consisted either.

Michael I'm curious about how you are advertising as well. Is it to users or marchines where this is failing at your site.

We're only advertising to users.

Damn, I was hoping it was the opposite. I'll see if I can repro that.

We're advertising to machines. Shortcuts always go to C:\ProgramData\Microsoft\Windows\Custom Folder

I gave up in the end trying to find out why they weren't always going, the actual uninstalls of this particualr piece of software took place in mid-August so the logs have long since been overwritten etc. I would estimate that on about 60 machines that had the package orginially and then had it uninstalled about 20% still had the shortcuts.

To be fair, at the time we were doing an awful lot of install and uninstalls of software via SCCM and App-V so I'm prepared to give it the benefit of the doubt for now [:)]

Just a FYI that I haven't broke this yet. I've done some fairly standard provisioning proceedures by leaving the Group and Virtual package in SCCM and just removing the users from the group. I plan to get more creative where I delete the advertisement and package outright and see what happens.

I'm wondering if my lab is too small (not enough clients to see an intermittent failure) or if it is something unique I'm not properly reproducing. Just for fun I've tried outright deleting the advertisement and package but the client still knows that the application is gone and removes the shortcuts. Definitely a weird one.

Hi,

I have also this problem with App-V/SCCM, any news in the issue.

/SaiTech

I can't reproduce but if you send me your execmgr.log and virtapp.log on the client I'll look at it. PM me and we'll arrange a way to do it.

Thanks KKaminsk.
So it is "you", I reading your book now "The Client Book about Microsoft App-V"

I will look for the logs

/SaiTech

Yep its me, I hope you like the book!

Has anyone found a solution to this problem?

We ask our package team to remove any shortcuts in the APPV package.
We create our own shortcuts and let them copy at login for the user, the only bad thing about this is that an user can see the shortcut but the app is not available on the pc yet.

Thanks for the info and instructions!

How about this issue? We've got the same issue. Advertisements are on usergroups. App-V + SCCM 2007 R3 combi. And I've installed the latest App-V Client hotfix package. (441796).

When deleting a advertisement --> Shortcuts remain in startmenu
When disabling a advertisement --> Shortcuts remain in startmenu

Is it worth opening another ticket with Microsoft?

Double post

"Is it worth opening another ticket with Microsoft?"

Well I dont think so, and It looks like this issue is gone in SCCM 2012. I think it is better to plan for SCCM 2012...

/SaiTech

Thanks, i also come across such a problem.

Similar situation here and still no real solution ...

Have you used uninstalling using MSI. In your SCCM uninstall program write the MSI uninstallation command. Use this advertisement to remove the app-v installed. It removes the shortcuts too. The only thing i observed with this is , app-v always removes the first level folder of the shortcuts and leaves empty if other parent folders exist.\

Hope this helps...