Hi,

I'm having problems deploying software using the KBOX 1000, for the vast majority of our MI's they're ZIP files, because they have a few items or the MSIEXEC requires public properties, or the MSIEXEC line just doesn't work.

The only success I have is specifying a .bat file and including that in the ZIP, which contains the whole MSIEXEC command, this works.

It's driving me crazy though, as now I have a ZIP file and need to call a vbs file within it.

I'm watching the KBOT Log file and whatever I try fails, sadly the simple "installer.vbs" did not work, it said "System.ComponentModel.Win32Exception: %1 is not a valid Win32 application" so I try to use cscript, but that failed, so I said Run command only, then it tried to run cscript installer.vbs and had file not found.

I tried using $(KACE_DEPENDENCY_DIR) but it didn't rewrite and replace it in the log... ARGH!!! Seriously, do I HAVE to put an installer.bat file in the ZIP file, JUST to call the vbs file? 0 Comments [ + ] Show Comments ## Comments Please log in to comment ### Community Chosen Answer 1 • What are the run parameters / install command in your MI? • Are you using the "configure manually" option?At the top of the MI it will say "The windows client will install this via:" what does that say? • In the log files (kdeploy and klaunch) what is the command line that it interprets it as. • Does your MI (same command as above) run as the SYSTEM user when not using the kbox agent? Answered 01/10/2012 by: GillySpy • Hi All, Im trying to install two different McAfee packages but both are same version with different configuration, one frame pkg for Region1 and another for Region 2, how i can do this MI ? when I create new managed install im able to associate only one file at a time, any idea how can i perform this ? as i need to perform the two installation with different configuration at a time..I have zipped both the frame pkgs, and trying to call as below Managed Install 1: Override Default Installation Full Command Line: FramePkg1.exe FRAMEPKG /INSTALL=AGENT/SILENT Managed Install 2: Override Default Installation Full Command Line: FramePkg2.exe FRAMEPKG /INSTALL=AGENT/SILENT would this work? Please log in to comment Rating comments in this legacy AppDeploy message board thread won't reorder them, so that the conversation will remain readable. ### Answers 0 Hi GillySpy, Oh I've already come across the whole "test running MSI as System account" and ALLUSERS, not that, this is strictly getting the right command line issued by the client. I've tried with and without all the options, "Configure manually", "run command only", had no luck with any of it, I'm just trying to run a .vbs file from within the ZIP file. I did say in my first post, I'd checked the logs and it wasn't doing it right. Some full examples from the KBOT_LOG are: C:\Program Files\KACE\KBOX\downloads\15596\installer.vbs = "System.ComponentModel.Win32Exception: %1 is not a valid Win32 application" C:\Program Files\KACE\KBOX\downloads\15596\cscript installer.vbs = "System.ComponentModel.Win32Exception: The system cannot find the file specified" installer.vbs = "System.ComponentModel.Win32Exception: The system cannot find the file specified" cscript "$(KACE_DEPENDENCY_DIR)\installer.vbs = Doesn't do anything

0
$(KACE_DEPENDENCY_DIR) is only relevant in scripts. An MI should use that location as it's context anyway, but I've recently seen it not. I'm betting this works:  cscript.exe C:\Program Files\KACE\KBOX\downloads\15596\installer.vbs If so please call support and log a bug. You can reference this post. Answered 01/10/2012 by: GillySpy Please log in to comment 0 If you don't select "Run Command Only", then yes you get C:\Program Files\KACE\KBOX\downloads\15596\ problem is you end up with nonsense like: C:\Program Files\KACE\KBOX\downloads\15596\msiexec someprogram.msi C:\Program Files\KACE\KBOX\downloads\15596\cscript installer.vbs When it should be: msiexec C:\Program Files\KACE\KBOX\downloads\15596\someprogram.msi = This never seems to actually happen, unless I do it within a .bat file and call that in the commandline on the MI. cscript C:\Program Files\KACE\KBOX\downloads\15596\installer.vbs To my mind you don't call a vbs from msiexec, only msi's. For a .vbs you should be able to call it like a bat file, or failing that either wscript file.vbs or cscript file.vbs of course both wscript and cscript are located in the system32 dir. Answered 01/10/2012 by: AJStevens Please log in to comment 0 Sorry meant cscript. too many pots today. Since cscript is likely in your system path you don't need the path for that. Answered 01/10/2012 by: GillySpy Please log in to comment 0 No, true, if you say run command only and put in "cscript install.vbs" the problem is it looks for installer.vbs in the system path instead of the current directory. We really need some variable or to split the command line so either two boxes: Commandline Command: cscript Commandline Arguments: installer.vbs KBOX Client then rewrites as: cscript C:\Program Files\KACE\KBOX\downloads\15596\installer.vbs OR we have something like$(KACE_DEPENDENCY_DIR) we can drop into the command line.

cscript $(KACE_DEPENDENCY_DIR)\installer.vbs which gets rewrote as: cscript C:\Program Files\KACE\KBOX\downloads\15596\installer.vbs Answered 01/11/2012 by: AJStevens Please log in to comment 0 In previous version it would use the current directory for support files. A variable would help but it should just work in the current context IMO. If you are able, I recommend opening a support ticket or make a uservoice request for any idea. Answered 01/11/2012 by: GillySpy Please log in to comment 1 Within a batch file (.cmd or .bat), you can refer to the "current" directory, the directory the batch file itself is in, as %~dp0, which ends in a \. Here's an example: in a batch file in the$(KACE_DEPENDENCY_DIR) folder, I could run a .vbs from that same directory with this command:
cscript //nologo //b //time:300 %~dp0somescript.vbs

This technique assumes that command extensions are enabled, which they are by default. For more information, I recommend this site:
http://ss64.com/nt/syntax-args.html

90% of the errors when using this technique result from typos in all those punctuation characters: %~dp0 Sande

0
snissen, see the last line of my original post.

I think it's a bit rediculous that for every MI we need a .bat file to be called to initiate the process, unless it's a VERY simple msiexec command (msiexec /i whatever.msi), anything else you need a bat file for.

0
I think snissen was offering a today solution not necessarily a long-term one (+1) I am very interested in making the product better in the future and giving solutions that work today whenever possible.

FYI, I just tested 5.3.47657 with configure manually with a zip file and this command line:
 ultravnc_1.0.8.2_x64_setup.exe /verysilent /loadinf=ultravnc.inf

And it worked fine. Also did some tests with msi's, etc. all fine. BTW, here is what I detected as actually running:
 UltraVNC_1.0.8.2_x64_Setup.exe "C:\ProgramData\Dell\KACE\downloads\4508\ultravnc_1.0.8.2_x64_setup.exe" /verysilent /loadinf=ultravnc.inf
ultravnc_1.0.8.2_x64_setup.tmp "C:\Windows\TEMP\is-PG5CT.tmp\ultravnc_1.0.8.2_x64_setup.tmp" /SL5="\$9B1D10,1708378,346112,C:\ProgramData\Dell\KACE\downloads\4508\ultravnc_1.0.8.2_x64_setup.exe" /verysilent /loadinf=ultravnc.inf

You may want to open a support ticket AJStevens.

0
Yes, I know, but I did say at the end of my first post, did I really have to use a BAT file, meaning I knew that workaround.

GillySpy, your examples don't reflect the problem, what if the /loadinf= argument required a full path, what would you do?

Calling .bat or .exe is fine, providing the parameters you pass to it are simple, or accept a relative path (basically no path), even MSI's if they're simple. If either of those become more complicated, or you need to call a .vbs it won't work.

Hmm.. we had a Dell guy here update our K1000, but I notice our clients are 5.1.38724, not 5.3.47657 (which I presume is the client agent version you're referring to? As it says our K1000 is up to date at 5.2.38773)

0
GillySpy, your examples don't reflect the problem, what if the /loadinf= argument required a full path, what would you do?
I provided an example very similar to your situation where I am using a zip file. If I required a full path to a file that wasn't in my zip then I would provide that path. E.g.
 ultravnc_1.0.8.2_x64_setup.exe /verysilent /loadinf=c:\path\to\file\ultravnc.inf

If my zip had folder structure then
 ultravnc_1.0.8.2_x64_setup.exe /verysilent /loadinf=.\relative\path\to\file\ultravnc.inf

Since you have a big upgrade ahead be sure to read release notes and test your software, etc against a 5.3 agent test bed

I have used the above with success on 5.1 agent as well.

0
Thanks GillySpy, I'll give ".\relative\path\to\file" a try and see if that works.

I'll mention it to the higher ups and our dell guy.

Is 5.3 ok now? I've seen a lot of problem posts about it on here...

Oh... looks like our K1000 is "dead" again... *sigh*, guess they didn't fix it... well, I say "dead", it just seems like it's web server dies, since we can still ping it, and I can still read the DB remotely.