I spent alot of time figuring out on my own how, what and when to install the many components required to install Food Processor 10.
I hope you readers will apreciate.
This was deployed with SCCM 2007. It`s actually 4 deployment packages and they must be in a specific order which i`ve listed here.
Step 1 - Install SQL Server Express 2005
Please note that i still have an issue with step 1. I`m able to run it with a command prompt but when i put this command line in SCCM 2007, it doesn`t seem to find the ini file. (work in progress)
Command line
setup.exe /qn /Settings "yourINIfilename.ini"
This is my ini file:
[Options]
USERNAME=UdeM
COMPANYNAME=UdeM
INSTALLSQLDIR=
INSTALLSQLSHAREDDIR=
INSTALLSQLDATADIR=
ADDLOCAL=SQL_Engine,SQL_Data_Files,Client_Components,Connectivity
INSTANCENAME=ESHA
SQLBROWSERACCOUNT=AUTORITE NT\SYSTÈME
SQLBROWSERPASSWORD=
SQLACCOUNT=AUTORITE NT\SYSTÈME
SQLPASSWORD=
AGTACCOUNT=AUTORITE NT\SYSTÈME
AGTPASSWORD=
ASACCOUNT=AUTORITE NT\SYSTÈME
ASPASSWORD=
RSACCOUNT=AUTORITE NT\SYSTÈME
RSPASSWORD=
SQLACCOUNT=SYSTÈME
SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
AGTAUTOSTART=0
SECURITYMODE=SQL
SAPWD=Fpro2011
;SQLCOLLATION=
;ASCOLLATION=
DISABLENETWORKPROTOCOLS=0
ENABLERANU=1
ADDUSERASADMIN=1
-----------------------------------------------------
Step 2 - Install SQL Server Management Objects Collections 9
Command Line : msiexec.exe /q ALLUSERS=2 /m MSIDAUXP /i "SQLServer2005_XMO_x64.msi"
Step 3 - Install Nova PDF Printer (64bit in my case)
Command Line
"ISSetupPrerequisites\NovaPDF v6 printer driver - 64-\novapk.exe" /verysilent /suppressmsgboxes /nocancel /norestart /lang="fr" /languages="fr"
Step 4 - Install Esha Food Processor 10.10 (lattest version at time of documentation)
Command Line
setup.exe /v"/qb! CUSTOMERNUM=##### PRODUCTKEY=####-####-####-####-####"
Note
Had to modify the setup.ini to `rem` out the following lines:
;PreReq1=novaPDF v6 printer driver - 64 bit.prq
;PreReq3=novaPDF v6 printer driver.prq
For some reason, setup won`t run even when the NovaPDF is installed on the previous step so this disables the verification.
Deployed succesfully with SCCM 2012. The software will only run succesfully when logged in with the Administrator account. The only thing left to do afterwards (for me) was to add "domain users" to the database acces list. Then anybody that logs into the system will be able to run the application.
View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.