Distributed install bat file
Answer Summary:
murbot | 03/21/2012 I figured it out. The first batch file that calls the others uses xcopy to copy the install files from the developers server instead of using the local copy they already gave me. After repointing that command line, it works great...on XP. On Windows 7, I don't even see RunKbot running. I do have all Windows 7 versions selected on the software page. Any idea why it run for XP, but no Windows 7? This is Kace issue I'm sure, not with the install files themselves. Thanks
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1
I figured it out. The first batch file that calls the others uses xcopy to copy the install files from the developers server instead of using the local copy they already gave me. After repointing that command line, it works great...on XP.
On Windows 7, I don't even see RunKbot running. I do have all Windows 7 versions selected on the software page.

Any idea why it run for XP, but no Windows 7? This is Kace issue I'm sure, not with the install files themselves.

Thanks
Answered 03/21/2012 by: murbot
Tenth Degree Black Belt

Please log in to comment

Answers

0
kace managed install
Answered 03/21/2012 by: murbot
Tenth Degree Black Belt

Please log in to comment
0
What is it you are wanting to install?
Answered 03/21/2012 by: WGM_Jeff
Fourth Degree Black Belt

  • Sorry. My browser's been flaky and I posted a few senseless questions today.
    The app is an in house app designed by people in a different institute who I can't speak with. It's got 7 batch files that call one after another, then they call 1 of 2 possible MSI's and register a few handfuls of dlls. I could pack it or part of it into AutoIT, then use Kace to push that exe, but I'd like to just use the existing batch file if possible.

    Doing the install manually would mean running 1 batch file in the top level folder and then it automates the rest through completion.

    I need to know if and how best I can add it as a managed install and add it as a new Software Library item. I zipped the top level folder retaining the structure and added that zip as a mng'd install to Kace, added a new Software Library item and pushed to my account. It runs, but all it does is mkdir the first directory which is the first command line in the first batch file. That directory is empty though and it should have about 20MB's of files. It does unpack to the C:\Docs&settings\All users\Dell\Kace\downloads\xxx directory. So it's starting, but not doing the rest. KDeploy, KLaunch and RunKbot stay up and I have force reboot the machine. I'm testing on a 32 bit XP Sp3 physical Dell box.

    I know this is a disjointed question, but any help or tips are appreciated.

    Thanks,
    -Steve
Please log in to comment
0
A few thoughts on the Win7 install:

Does everything work properly if it's run locally (i.e. manually starting the initial batch file)?

If yes, what account is being used - the currently logged in user, an admin account (domain or local) or a system account?

Are any of the batch files writing to any of Win7's protected folders (Programdata, Program Files, Users, Windows)? I'm deploying vbscripts that were trying to write to the Windows folder (with UAC enabled) and had to change to a different target folder to get them working.


John
Answered 03/25/2012 by: jverbosk
Red Belt

Please log in to comment
0
Have you tried adjusting the path in the initial batch file to reflect the path that is present when the files are copied to the machine during the managed install? This could be the reason it never goes anywhere, if there's a path error.

John
Answered 03/26/2012 by: jverbosk
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity