Scripting with KACE
We have created a script that should:
1. Set a Trusted site
2. Check if Windows Installer 3.1 is installed, if not launch a program to install it
3. Check if .Net 2.0 is installed, if not launch a program to install it
4. Check if .NET 3.5 is installed if not launch a program to install .Net 2.0 .Net 3.0 and .Net 3.5
5. Check if C++2005 Redistributable SP1 is installed, if not launch a program to install it
6. Check if C++2008 Redistributable is installed, if not launch a program to install it
7. Run a batch file to add .NET 1 and 2 to Local Intranet and Trusted zones.
We have to run it several times to get everything installed. For some reason it would only install parts of the script at each time. For exampe it installs .Net 2.0 and 3.0 and C++ 2005 at one run and .Net 3.5 and C++2008 at the next run.
What can we do to make all of the steps finish at one script run?
Also even though we assign .Net to run silently it still brings up several windows: "Another instance of setup is running.
1. Set a Trusted site
2. Check if Windows Installer 3.1 is installed, if not launch a program to install it
3. Check if .Net 2.0 is installed, if not launch a program to install it
4. Check if .NET 3.5 is installed if not launch a program to install .Net 2.0 .Net 3.0 and .Net 3.5
5. Check if C++2005 Redistributable SP1 is installed, if not launch a program to install it
6. Check if C++2008 Redistributable is installed, if not launch a program to install it
7. Run a batch file to add .NET 1 and 2 to Local Intranet and Trusted zones.
We have to run it several times to get everything installed. For some reason it would only install parts of the script at each time. For exampe it installs .Net 2.0 and 3.0 and C++ 2005 at one run and .Net 3.5 and C++2008 at the next run.
What can we do to make all of the steps finish at one script run?
Also even though we assign .Net to run silently it still brings up several windows: "Another instance of setup is running.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
airwolf
13 years ago
The installs are probably overlapping, so the first one needed is running while the others trigger.
Try adding "start /wait" to the front of a command to launch a program. This will force the command line to wait until that installer is finished.
Try adding "start /wait" to the front of a command to launch a program. This will force the command line to wait until that installer is finished.
Posted by:
MarshallU
13 years ago
We are using this command. here is an example of the command line:
START /WAIT $(KACE_DEPENDENCY_DIR)\NetFx20SP1_x86.exe /q /norestart
Is there an error?
START /WAIT $(KACE_DEPENDENCY_DIR)\NetFx20SP1_x86.exe /q /norestart
Is there an error?
Posted by:
cblake
13 years ago
Are you using the checkbox for wait for startup?
Why not do these in Managed installs? That behavior is built into MI's to check for presence and install.
Why not do these in Managed installs? That behavior is built into MI's to check for presence and install.
Posted by:
zookdj
13 years ago
Your suggestion to use an MI would be a good one if it worked consistently and reliably. I've been moving some of my MI deployments to scripts instead, which is more effective for some applications (OpenOffice.org being one example.)
MarshellU: perhaps you may need to try using MIs to install the software and then setup your script to verify that everything is installed correctly when it sets the trusted sites and configures the IE zones.
MarshellU: perhaps you may need to try using MIs to install the software and then setup your script to verify that everything is installed correctly when it sets the trusted sites and configures the IE zones.
Posted by:
rmeyer
13 years ago
some of the installers will start the installation, then the exe file will close and an MSI will finish the installation, that sound like it is the problem
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.