Question: When trying to run the App-V 5.1 or App-V 5.0 SP3 created MSI in the client machine, it fails with the error code 0300000102. How to resolve this.
Corresponding Event log:
Solution: Try running the CMD as Administrator and from here run the MSI file.This will resolve the issue. The MSI requires Admin privileges to run in the client machine.
Ok, now this works but what might be the reason? This comes into everyone's mind. Let me explain further.
Opened the App-V 5.1 sequenced MSI package and first checked in the Launch Condition table using ORCA. I see that there is a Privileged condition. I removed it by creating a Transforms file for the MSI. Tried Installing again and even this time it failed.
Analyzed further by opening the MSI template file for App-V 5.0 SP2. The msi will be located in C:\Program Files\Microsoft Application Virtualization\Sequencer\en-US
I see that the Custom Action PublishPackage32 and PublishPackage64 has Type to run in deferred execution in system context (3073)
Now opened the MSI template file for App-V 5.1 and see that those Custom Action PublishPackage32 and PublishPackage64 has Type to run in deferred execution (1025)
Ok now I have found a reason. It's time to test it. I created a Transforms file for the App-V 5.1 generated MSI package (Testpackage.msi) and changed the type for PublishPackage32 and PublishPackage64 to run in deferred execution in system context.
Tried installing the MSI with the created Transforms file (MST). Viola!! it works fine without the need for CMD as admin.
The same applies for RemovePackage32 and RemovePackage64 custom action also. This method works great for App-V 5.0 SP3 generated MSI also.
NOTE:
I heard from Dan Gough that he has created a Transforms file (MST) which would automate this case and resolves the need for Run as Admin. In addition to that he has also added support to include the deployment config.xml file too when installing. Hopefully he will be releasing it officially by this month. Once he releases it, I will be updating this blog with his Link to download the MST file.
Corresponding Event log:
Solution: Try running the CMD as Administrator and from here run the MSI file.This will resolve the issue. The MSI requires Admin privileges to run in the client machine.
Ok, now this works but what might be the reason? This comes into everyone's mind. Let me explain further.
Opened the App-V 5.1 sequenced MSI package and first checked in the Launch Condition table using ORCA. I see that there is a Privileged condition. I removed it by creating a Transforms file for the MSI. Tried Installing again and even this time it failed.
Analyzed further by opening the MSI template file for App-V 5.0 SP2. The msi will be located in C:\Program Files\Microsoft Application Virtualization\Sequencer\en-US
I see that the Custom Action PublishPackage32 and PublishPackage64 has Type to run in deferred execution in system context (3073)
Now opened the MSI template file for App-V 5.1 and see that those Custom Action PublishPackage32 and PublishPackage64 has Type to run in deferred execution (1025)
Ok now I have found a reason. It's time to test it. I created a Transforms file for the App-V 5.1 generated MSI package (Testpackage.msi) and changed the type for PublishPackage32 and PublishPackage64 to run in deferred execution in system context.
Tried installing the MSI with the created Transforms file (MST). Viola!! it works fine without the need for CMD as admin.
The same applies for RemovePackage32 and RemovePackage64 custom action also. This method works great for App-V 5.0 SP3 generated MSI also.
NOTE:
I heard from Dan Gough that he has created a Transforms file (MST) which would automate this case and resolves the need for Run as Admin. In addition to that he has also added support to include the deployment config.xml file too when installing. Hopefully he will be releasing it officially by this month. Once he releases it, I will be updating this blog with his Link to download the MST file.
No comments:
Post a Comment