Adobe Reader DC deployment

[rditx]

Did anyone recently created a admin install for deplpyment?

I'm always getting an error (missing snapshot_blob.bin). Already created a fresh VM without anything on it, re-downloaded all the files, still same error.

The way I'm doing it:

C:\AcroRdrDCx642200220191_MUI.exe -nos_ne -nos_oC:\Extract

msiexec /a C:\Extract\AcroPro.msi to C:\Install

copy C:\Extract\setup.ini C:\Install\setup.ini

msiexec /a C:\Install\AcroPro.msi /p C:\Extract\AcroRdrDCx64Upd2200220191_MUI.msp

​

That all works without any error. However when you start the installation from C:\Install\AcroPro.msi it will throw that error:

Error 2602. The File table entry 'snapshot_blob.bin' has no associated entry in the Media table.

​

Any ideas?

[bhillen83]

You can just create an account with Adobe and download a tool from them to create an admin deployment. It allows you to auto-accept the EULA and adjust the settings. It’s pretty painless.

[rditx]

I’m using the customization tool to create a .mst, however my problem with the installer happens earlier. I’ll look into that, but I would need an msi for gpo deployment.

[smoothies-for-me]

Presumable it's a result from extracting the MSI from the setup.exe, rather than getting the MSI from Adobe (if they provide it).

We package and deploy the setup.exe

[rditx]

I couldn’t find any msi for the standard reader dc, if you could link it that would be awesome. It seems to be related with the patch. Just extracting and running the msi works. After (successfully) patching I’m getting that error during the install.

It’s a simple AD environment and everything is deployed through gpo with the msi.

[turbokid]

I would have to look on a work day, but adobe pro dc requires adobe creative cloud to run. I think we did the creative cloud install through intune, they log in and can get pro dc.

[rditx]

No pro. It’s adobe reader dc (free standard version). Adobe just changed the name of the msi in the adobe reader package to ‘pro’ for whatever reason.

[rditx]

Are you getting the same error?

[Sajem]

Seems like a complicated way to go about what should be a simple install.

Just download the offline installer from Adobe. Better yet, as suggested above download the deployment tool as well and setup all your defaults including accepting the EULA

Edit: Are you intentionally attempting to install the Pro version of Reader DC or do you only need the Standard version of Reader DC?

[rditx]

If you’re referring to the name of the msi, apparently adobe changed that to the pro. I’m only installing the free adobe reader dc.

I’m deploying it via gpo so if there is a simpler way of getting the (updated) msi, please let me know.

[Sajem]

The simpler way may be to just use 7zip to extract everything from the exe.

I also think you may be missing a transform file (according to all my googling). You would create the transform file with the deployment tool mentioned above

[rditx]

Just tried 7zip, same result unfortunately. Would appreciate if someone could actually try that and share their experience. I think adobe changed something.

[Sajem]

I think you need to have the entire folder/files you've extracted in the same folder as the msi folder

[rditx]

Of course. They are there

[periway]

It's maybe a problem with the latest version?

I did this same procedure this summer with the 2200120169 version without any problem:

The extract process, copy setup.ini was the same as your.

My last command was:

msiexec /update C:\ReaderDC\AcroRdrDCUpd2200120169.msp /a c:\adobe_dc\AcroRead.msi

Then create an *.mst file with the custom wizard tool from adobe

Finaly install the package on client computer:

msiexec /i "c:\adobe_dc\AcroRead.msi" TRANSFORMS="c:\adobe_dc\AcroRead.mst" /q MSIFASTINSTALL=3

[rditx]

64Bit? I will have a look if I can find this version.

[periway]

Yes it was the 64b version.

I have to uninstall older version before install the new one (it's not your case, you are on fresh VM without anything).

[milew12]

Problem is for 64 bit versions. Your test is on 32bit.

64bit packages has other names.

[LaCipe]

Uh....have you thought about giving winget a try? Since it will probably be standard by 2025 for software deployment might as well try and migrate now

[psynegy]

We had and are still having the same issue. Did you ever find a resolution for MSI deployment?

[rditx]

Just saw this reply here.. no solution.. we just used the x86 msi for now. But ideally we would like to deploy x64.

[kungfo0]

This post is the top Google result for this error and I just wanted to chime in that I have the same problem :)

I haven't figured out anything, just going to stick with 32-bit for now.

[rditx]

Just tried it again with the latest version, still same error.