[mdt] Deploying SMART Product Drivers 12.13

[interslice]

Hi,

 

How are we deploying SMART Product Drivers 12.13?

 

I have downloaded the installer from the SMART website and used the Install Manager to create an XML file, however, the installer ignores the "--adminfile [xml_File]" switch (installer doesn't launch) - I have tried:

Running the installer from the deployment share with the applicable switches

--and--

Writing a script to copy the installer and config file to c:\temp before executing:

"c:\temp\smartdrivers.exe /qb --adminfile config.xml"

"c:\temp\smartdrivers.exe /qb --adminfile c:\temp\config.xml"

"c:\temp\smartdrivers.exe /qb --adminfile .\config.xml"

 

 

I have tried without specifying "/qb" too!

 

I have tried extracting the contents of the *.exe file to get an *.msi, however, there is no *.msi file in here...

 

There used to be an *.msi file for product driver installation - is this no longer the case?

 

Thanks!

Edited September 26, 2019 by interslice

[interslice]

Interestingly, smartdrivers.exe /qb INSTALL_BOARD=1 INSTALL_INK=0 works - I will try this with the rest of my options set...

 

I would definitely prefer an *.msi to the above though - a transform keeps things simpler than a mess of parameters!

[crc-ict]

Don't install 12.13!

 

We've been having a horrible issue with Smart Ink crashing and causing all sorts of issues, and SMART support told me that there is a bug in 12.13 and to use 12.11 for now.

 

Of course, if you don't use SMART Ink, there is no issue.

[interslice]

Interestingly, smartdrivers.exe /qb INSTALL_BOARD=1 INSTALL_INK=0 works - I will try this with the rest of my options set...

 

I would definitely prefer an *.msi to the above though - a transform keeps things simpler than a mess of parameters!

 

Spoke too soon! The INSTALL_INK=0 is ignored - SMART Ink was installed anyway!

[interslice]

Don't install 12.13!

 

We've been having a horrible issue with Smart Ink crashing and causing all sorts of issues, and SMART support told me that there is a bug in 12.13 and to use 12.11 for now.

 

Of course, if you don't use SMART Ink, there is no issue.

 

Thanks for that - we are trying to install 12.13 without Ink and SPU (as these aren't used); but having difficulty with the installer recognising the parameters passed to it (or an adminfile created using the SMART Install Manager). Do you know if it is possible to get/create a *.msi file for the drivers?

[crc-ict]

I tried and failed to get the MSI

[interslice]

I tried and failed to get the MSI

 

That's unfortunate - I will raise a case with SMART support and see if they can assist (though I'm doubtful!)

 

Thanks for your confirmation!

[sted]

iirc the config file creator only works with the msi AND you don't want the xml file it creates an mst file you use the xml file is for the config program itself so you can reload a config and edit it later. (iirc you need to publish it in the software to create an mst)

[interslice]

iirc the config file creator only works with the msi AND you don't want the xml file it creates an mst file you use the xml file is for the config program itself so you can reload a config and edit it later. (iirc you need to publish it in the software to create an mst)

 

The option to publish only creates an XML for the product drivers installer. With the SLS installer, a transform file is created as expected.

[georgeescott]

When running the SMART .exe installer normally, as it installs it’ll extract the .msi’s to folders in: C:\ProgramData\Downloaded Installations\ that you can use to install the drivers