Silent Install deployment
New to packaging and was directed to appdeploy.com by the microsoft technet forums
I normally install our software silently using the ff command line
/setup.exe /s /f1"C:\SetupFolder\ISSFiles\setup.iss" /config"C:\SetupFolder\ConfigInfo\config.xml" /serial"xxxxxxxxxxxxxxxx"
I was wondering if any one knew how to translate this into a command line instruction for software deployment with SCCM?
I have the .iss files and .xml files in the same folder as the setup.exe. Testing silent install deployment with SCCM and can't seem to figure this out.
Any help is deeply appreciated.
Thanks
I normally install our software silently using the ff command line
/setup.exe /s /f1"C:\SetupFolder\ISSFiles\setup.iss" /config"C:\SetupFolder\ConfigInfo\config.xml" /serial"xxxxxxxxxxxxxxxx"
I was wondering if any one knew how to translate this into a command line instruction for software deployment with SCCM?
I have the .iss files and .xml files in the same folder as the setup.exe. Testing silent install deployment with SCCM and can't seem to figure this out.
Any help is deeply appreciated.
Thanks
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
MSIPackager
13 years ago
Hi EnamT
Personally I'd use a vb or command line script so that you can pick up the current folder to use as part of your command line install... here's a crude example which you should be able to build on to get your package installed, whether its from the DP or cached locally...
There are way better scripters than I on here, they will probably be able to produce something more elegant but this should work for you. Yes Ian, I know there is no error trapping or logging - like I said it's something to build on [;)]
Hope it helps,
Rob.
Personally I'd use a vb or command line script so that you can pick up the current folder to use as part of your command line install... here's a crude example which you should be able to build on to get your package installed, whether its from the DP or cached locally...
Option Explicit
Dim objShell, strScriptPath, strCmd
Set objShell = CreateObject("WScript.Shell")
'Get current script location
strScriptPath = CreateObject("Scripting.FileSystemObject").GetAbsolutePathName(".")
'Install vendor setup package
strCmd = """"&strScriptPath&"\setup.exe"""&" /SILENT"
objShell.Run strCmd, 1, True
Set objShell = NothingThere are way better scripters than I on here, they will probably be able to produce something more elegant but this should work for you. Yes Ian, I know there is no error trapping or logging - like I said it's something to build on [;)]
Hope it helps,
Rob.
Posted by:
EnamT
13 years ago
Thank you so much Rob, I figured it out, very simple really. SCCM was sending the package to a different location and all i had to do was change my command line to reflect that location change (or manually move the copied folder to the right location) to perform the install
Thank you again for taking the time!
Thank you again for taking the time!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.