Yes, from the unpacked LANDesk source, just run setup.exe with a /s. Or use /? for all possible parameters. Same goes for service packs that need to be installed after the main program.
Thanks for the assistance and answer.
I had a batch file with the command to kick off the installation with a silent switch, but the template keeps failing out at that point. At first we got a bad credentials error, even though the account used for provisioning has access to the core. We tried sharing and mapping the drive in a step prior to pre-establish the access, but it still failed. Then we copied the install folder to our software server share to eliminate permissions, but it still fails. It only gives the external status of 1, and an internal status of -2147479552. The syntax of the batch is below:
@ echo on
\\my server\software\landesk\remote console files\install\setup.exe /s CORE=my core
What I find to be strange, is that even with the echo on and a pause statement to hold the window post-install, it still never shows the command window and any messages of failure. But if I run that batch file locally from the provisioning account, it works fine.
I also tried changing from a batch file, to running the setup.exe directly through LD, and adding the command-line options, and it still failed, same error statuses.
Any ideas or suggestions?
I created a batch file package to install LDMS which I added to one of our templates, but I wrote it like this:
@ echo on
"\\my server\software\landesk\remote console files\install\setup.exe" /s Product=RemoteConsole Language=ENU CORE=my core
So this has been resolved, with some tweaking.
The batch file method Frank suggested did indeed work. The reason the first batch test kept failing was a simple syntax error, a typo in the server name. Amazing what little things can hide so neatly in code, that will bring your command to a halt.
So the final batch file being used and working looks like this, which is similar to Slapp's batch file..
"\\myserver\software\landesk\remote_console\install\setup.exe" /s CORE=MYCORE
So basically the same as Slapp's, but without the extra parameters. I left off the Product and the Language, because by default the language is English, and the product will be the Remote Console. I also wound up copying the install files from the core to my software distribution share.