Hello,

I'm trying to test a supersedence for an application that originally was deployed via task sequence when the operating system is deployed to the client, without reimaging the client itself. I've conducted the following steps to try and get this to work:

1. Application A was deployed via task sequence and now has a copy, which I'll call Application A2. 

2. In Application B I've setup the supersedence rule with the old deployment type being A2 and the replacement deployment type being Application B, with the uninstall check box enabled as well. I've set the deployment of Application B to a device collection with my test client in. I specified A2 because I'm assuming that the live version A would supersede all clients, regardless of collections specified, and obviously I want to test before the live environment. 

3. In software centre on the test client in available software Application B is listed with the status "past due - will be updated", showing the latest version I want to supersede with. However when trying to install it instantly fails. I've pulled up the log for AppDiscovery.log with cmtrace and found the following line.

"+++ Did not detect app deployment type Adobe_Reader_11.0.10_01 - Microsoft Application Virtualization 5(ScopeId_B88C7C83-8BD7-4E0C-84FB-734DB5AF3194/DeploymentType_ee26ebc6-ec62-4cf2-8341-867e95edc7ae, revision 11) for system. AppDiscovery 19/03/2015 14:12:39 1272 (0x04F8)" "

The package with GUID a9fb1207-84ce-45de-be98-9ef9bbaeb2bd is not installed on this machine yet AppVHandler 19/03/2015 14:12:39 1272 (0x04F8)"

(I didn't want to flood this topic with loads of lines, is there a way to attach logs?)

In the AppEnforce.log I noticed it states this line.

The package with GUID 83ae1846-a3fc-448a-8cec-0848e560d3cc is not installed on this machine yet AppEnforce 19/03/2015 09:32:49 1980 (0x07BC)
The package with GUID a9fb1207-84ce-45de-be98-9ef9bbaeb2bd is not installed on this machine yet AppEnforce 19/03/2015 09:32:49 1980 (0x07BC)

I deployed A2 on its own, after removing Application A which was done by task sequence, and checked the PackageID and it is exactly the same as the one deployed through the task sequence. I re-added the supersedence rule back so that Application B is to supersede the A2 that just installed, and again it has failed to update and asking to retry. 

In CMTRACE two lines have now highlighted:

Cannot uninstall deployment type ScopeId_B88C7C83-8BD7-4E0C-84FB-734DB5AF3194/DeploymentType_4867b86f-060b-4a85-8393-1bea743de20c. All the publish components in this DT are still published by other DTs. This DT will be always detected as long as other DTs are still installed AppEnforce 19/03/2015 14:41:22 4052 (0x0FD4)
CAppV5XHandler::UninstallApp() failed to uninstall the app (DTId = ScopeId_B88C7C83-8BD7-4E0C-84FB-734DB5AF3194/DeploymentType_4867b86f-060b-4a85-8393-1bea743de20c, Revision = 1), error (0x87d0128e). AppEnforce 19/03/2015 14:41:22 4052 (0x0FD4)

Am I setting up supersedence correctly at all? Is it possible to supersede an application that was originally deployed via task sequence, without a reimage and amendment to the task sequence? OR am I missing something ridiculously obvious.

Much appreciated for your time,

Ollie

Ollie,

Untick the uninstall check box and give that a try

Hi Paul,

Thanks for your reply.  I re-ran the scenario with uninstall unchecked and it worked fine. I noticed however that on an uninstall of the latest application that was to supersede, as a scenario for if the latest had an issue of sorts and needed to revert back, an empty shortcut would appear for the previous version. With the Get-AppVClientPackage cmdlet I noticed that no path or cache existed, just the old version number and name. 

For App-V applications is there more that needs to be done to ensure a full uninstall of the old application that is superseded by the newer? Instead of just doing an upgrade on top, as both versions were in the cache on Get-AppVClientPackage.

Many thanks,

Ollie

Cannot uninstall deployment type ScopeId_B88C7C83-8BD7-4E0C-84FB-734DB5AF3194/DeploymentType_4867b86f-060b-4a85-8393-1bea743de20c. All the publish components in this DT are still published by other DTs. This DT will be always detected as long as other DTs are still installed AppEnforce
19/03/2015 14:41:22 4052 (0x0FD4)
CAppV5XHandler::UninstallApp() failed to uninstall the app (DTId = ScopeId_B88C7C83-8BD7-4E0C-84FB-734DB5AF3194/DeploymentType_4867b86f-060b-4a85-8393-1bea743de20c, Revision = 1), error (0x87d0128e).
AppEnforce 19/03/2015 14:41:22
4052 (0x0FD4)

Sorry - Just wanted to bump this post up to see if anyone else was able to comment on my reply to Paul. Is there another measure that needs to be taken to fully uninstall an AppV package to replace with another? In the initial scenario I mentioned the PackageIDs are not the same and I intend to fully remove the older version to replace with a later version. Whenever I select the uninstall checkbox it fails, with the error above.

Many thanks,

Ollie

Me again,

I've managed to find the answer from some more testing. Instead of creating a copy, which in this scenario above was A2, I referenced Application A (original application) as the item to be superseded by Application B. At second guess I assume the ScopeID is different for A2 compared to A, which allowed me to uninstall and supersede which is what I was looking for. 

O

• Marked as answer by Ollie__ 15 hours 34 minutes ago