Preparing Autodesk InventorView 2017 deployment

[Anonymous]

Hi to all,

I'm preparing deployment for Autodesk InventorView 2017 and I wonder if you could help me to solve several issues I faced.
1. Install sp1 + hotfix 1.1 during the deployment.
I tried different approaches, using PATCHES param in setup.ini file or by creating new section in setup.ini file and adding it to the sequence. Both cases are not working

2. Remove Uninstall tool shortcut.
This shortcut exists both in main InventorView.msi file and in InventorViewLP.msi file. For the main msi it can be easily removed by editing mst file which applied during deployment. But for LP msi I can't push it to use my mst file, I tried CONFIG_TRANSFORM, TRANSFORMS in LP section and unfortunately without success. The only working solution is to remove this shortcut directly in LP msi, but I don't really want to use this dirty approach

I'll appreciate any help:)

[m_latz]

You can also try to pass parameters for PATCH or TRANSFORMS through the "EXE_PARAM".

In another post the user had a problem, that the "PATCHES" parameter does not work in his deployment.ini file.

So we used EXE_PARAM to pass parameter to:

Sample from other post:

EXE_PATH=%platform%\C3D\C3D.msi
EXE_PARAM= PATCH="C:\Autodesk\DeployCivil2017\Img\x64\C3D\SP1.1.msp"

regards

Markus

[Anonymous]

I'm not sure that this approach is suitable for SP1 because patch should be applied after langpack and applied to main MSI. But I tried this method to apply TRANSFORMS 

[INVENTORVIEW_en-US]
LOG=%tmp%\InventoViewr2017_en-usInstall.log
ACTION=INSTALL

#============================= InventorView Language Pack =============================
[INVENTORVIEW_LANGPACK]
PRODUCT_NAME=Autodesk Inventor View 2017 Language Pack
EXE_PATH=%platform%\%lang%\inventorview\InventorViewLP.msi

EXE_PARAM=TRANSFORMS="%platform%\%lang%\inventorview\inventorViewLP.mst"
ADMIN_INSTALL=YES

And unfortunately this approach also doesn't help. I checked log file property TRANSFORMS was not specified during installation

[m_latz]

1st a patch (.msp) is applied to a msi file. And it doesn't matter (in general) in which order other msi packages are installed.

Important is only the order in which different patches are applied to a .msi file.

And if you pass parameters through the EXE_PARAMS you can't use variables from the setup.exe program. This couldn't resolved (what I know).

regards

Markus

[Anonymous · Accepted solution]

Ok. I just want to share working solution for my first question about implementing Service pack and Hot fix in existing deployment.

1. I created two new sections in ini:

#============================= InventorView Service Pack 1 =============================
[INVENTORVIEW_SP1]
PRODUCT_NAME=Autodesk Inventor View 2017 SP1
EXE_PATH=Patch\InventorView2017_SP1_x64.msp
LOG=%tmp%\InventoViewr2017_sp1Install.log
ACTION=INSTALL

#============================= InventorView Hot Fix 1.1 =============================
[INVENTORVIEW_HF11]
PRODUCT_NAME=Autodesk Inventor View 2017 HotFix 1.1
EXE_PATH=HotFix\IVV21101_x64.msp
LOG=%tmp%\InventoViewr2017_HF11Install.log
ACTION=INSTALL

2. and added new line to the main section:

[INVENTORVIEW]
PLATFORM=NATIVE
PRODUCT_NAME=Autodesk® Inventor® View 2017
PREREQUISITE=
POSTREQUISITE=INVENTORVIEW_SP1;INVENTORVIEW_HF11
EXE_PATH=%platform%\inventorView\inventorView.msi
LOG=%tmp%\InventoViewr2017Install.log
ROLLBACKABLE=YES

.......

And I have to say that I didn't find a way to extract msp from hotfix.exe and I've just got it from Windows Installer cache "C:\Windows\Installer\"

Regarding the applying mst to LP msi I still without success.