Skip to main content

Unattended update not possible for Acronis B&R 10 Agent from build 11345 -> 11639

Thread needs solution

Hi

I can not update my Acronis B&R 10 Agent via an unattended installation. I already recreated the mst files, but that didn't help.

Used the following command to update the Acronis B&R Agent from version 11345 to 11639:
msiexec /i AcronisAgentWindows.msi TRANSFORMS=AcronisAgentWindows.mst REINSTALL=ALL REINSTALLMODE=vomus /qb

There is no visible error. (of course) It's only visible because of the old version number (11345).
A new installation with: msiexec /i AcronisAgentWindows.msi TRANSFORM=AcronisAgentWindows.mst /qb is working, just no update.
msi logs see attachment...

The unattended installation of Acronis B&R Standalone Management Console works without any trouble too.
This error is reproduceable on several notebooks. (Fujitsu Esprimo Mobile D9510, Fujitsu T900, Fujitsu S710)
A manual update with the delivered installer works fine. It's just about the unattended installation.

About the test system:
Fujitsu Esprimo Mobile 9510D
Windows 7 Professional 32 Bit / UAC is on

Already installed:
Acronis B&R Agent 10 11345 (German)
Acronis B&R Standalone Management Console 10 11345 (German)
Office 2007 + SP2
Adobe Reader 8.3
All Microsoft Updates
Adobe Flash Player
FreePDF 4.02
Ghostscript 8.54

Thats it.

Hope you can find a soloution with these informations.

Thanks

Stefan

0 Users found this helpful

Hello Stefan,

Thank you for posting. I will definitely help you with this.

In order to perform unattended installation in build 11639, please use the following tip:

In earlier builds, such as Build 11345, to update you would use the REINSTALL=ALL REINSTALLMODE=vomus paramater. In Build 11639, you now use the ADDLOCAL=ALL above. If you have set up scripts with this paramater, please edit your script.

You can check this Knowledge Base article for additional information.

If you are still having issues related to this, please submit a support request with an AcronisInfo report, a new msi log and the command that you used, we will be able to resolve this.

Please let me know if you have additional questions.

Thank you.