Acrobat update keeps looking for AcroPro.msi on a network location
Ok so here is my issue: I'm trying to push out an update to Adobe Acrobat (11.0.16) in SCCM. It pushes out fine, but the issue is that during the installation the update wants to look at AcroPro.msi which is stored on a network drive (R:/) and fails if it can't find it. This may be due to how our customized installation of Acrobat was initially set up, although that was a while ago and I don't really remember how we customized it. Our users reboot their machines when they leave and we push stuff out at night so the fact that no user is logged in (or even if a local admin is logged in) the update won't install because it does not have the network drive (R:/) mapped.
So my question is why is it looking at this location (I saw someone on the net that it might be checking for licence info) and how can I get around this? Is there a way to edit the .msp update from adobe to tell it not to check for...whatever? (I tried opening it in InstEd which I use to edit .msi files but it won't open). Or is there some parameter in Adobe that is pointing to a licence or something else this is looking for? Any help is much appreciated!!!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
7 years ago
Your intial installation will have been done from the location on the R:\ drive. Simple to fix:
- copy the original MSI to a local location (not %TEMP%, %WINDIR%\TEMP or similar!). I use either SCCM's cache folder (if SCCM is used) or a branch from 'C:\ProgramData\Package Cache'
- edit the SourceList entry in the registry to point at that location
The WI engine will then search for the MSI in the order of the entries in 'SourceList'
Now, naturally, Microsoft don't make it easy to get to SourceList. First, you need the ProductCode from the MSI. Then you need to perform (what's bizarrely named) a Darwinian transformation on the ProductCode. I posted a QAD script here (well, originally on AppDeploy but it should still be here...) that does a two-way transformation for you. You end up with what I call a munged GUID. Microsoft calls it a compressed GUID. Yeah, "compressed" as in "lost the curly brackets and 4 hyphens". Jeez...
Anyway, then you need to browse to HKEY_CLASSES_ROOT\Installer\Products\[munged ProductCode]\SourceList\Net. Here's where you add your new location. You can edit the numeric sequence so that the local folder comes first, if you like.
- copy the original MSI to a local location (not %TEMP%, %WINDIR%\TEMP or similar!). I use either SCCM's cache folder (if SCCM is used) or a branch from 'C:\ProgramData\Package Cache'
- edit the SourceList entry in the registry to point at that location
The WI engine will then search for the MSI in the order of the entries in 'SourceList'
Now, naturally, Microsoft don't make it easy to get to SourceList. First, you need the ProductCode from the MSI. Then you need to perform (what's bizarrely named) a Darwinian transformation on the ProductCode. I posted a QAD script here (well, originally on AppDeploy but it should still be here...) that does a two-way transformation for you. You end up with what I call a munged GUID. Microsoft calls it a compressed GUID. Yeah, "compressed" as in "lost the curly brackets and 4 hyphens". Jeez...
Anyway, then you need to browse to HKEY_CLASSES_ROOT\Installer\Products\[munged ProductCode]\SourceList\Net. Here's where you add your new location. You can edit the numeric sequence so that the local folder comes first, if you like.
Comments:
-
Thanks for the info! Unfortunately it still doesn't work, it can see the .msi locally, but gets an error saying it can't find the data.cab file (which obviously still resides on network drive R:/) - winterelegy 7 years ago
Posted by:
anonymous_9363
7 years ago
>still resides on the network drive
Ummm....[quizzical look...] Can you think of a really quick way that that situation might be resolved?
Ummm....[quizzical look...] Can you think of a really quick way that that situation might be resolved?
Posted by:
JasonEgg
7 years ago
Did you use the Adobe Customization Wizard? I've had a lot of success with that tool: http://supportdownloads.adobe.com/thankyou.jsp?ftpID=5515&fileID=5526
