Right now we're using SCCM2007 and I'm evaluating LANDesk to see if it's a viable replacement. We're looking for something that can work with both Macintosh and Windows clients - which SCCM obviously cannot do.
Anyway... Right now, under SCCM, one of the packages I'm deploying consists of a batch file that installs a pile of .MSI's with patches.
It looks something like this:
MSIEXEC.EXE /i %~dp0something.msi /norestart /update %~dp0someupdate.msp; %~dp0someotherupdate.msp /qn
MSIEXEC.EXE /i %~dp0somethingelse.msi /norestart /update %~dp0someupdate.msp; %~dp0someotherupdate.msp /qn
MSIEXEC.EXE /i %~dp0yetanother.msi /norestart /update %~dp0someupdate.msp; %~dp0someotherupdate.msp /qn
XCOPY.EXE %~dp0JustForTheFunOfIt\stuff.inf C:\ToMakeThingsDifficult\stuff.inf /y
So, obviously, I can create a Batch File distribution package. I can point it at that batch file, and I can add a bunch of additional files.
But how does it all work? SCCM will download all those files into a single location, and I can use %~dp0 to call files from that location. Does LANDesk do something similar?
If not - is there a way to make this process work nicely with LANDesk? Or will I need to completely re-invent/re-script/re-package this particular bit of software?