Managed Install Timing
I created a managed install with the following settings:
Enabled: Checked
Managed Action: Execute anytime (next available)
Limit Deployment to Labels:-None-
Limit Deployment to Listed Machines: there is one listed
Deploy Order: 1
Max Attempts: 3
Deployment Window: 0 - 24
Allow Snooze: Unchecked
There are no pre or post install messages
How long should I wait before assuming that the managed install is just not going to run? I have forced an inventory check on the computer and restarted it, but the Status is still listed as "Not Installed". I think that I'm being patient enough and I've waited almost two hours, but is that not long enough?
Thanks for any input.
--
Chuck Steel
Enabled: Checked
Managed Action: Execute anytime (next available)
Limit Deployment to Labels:-None-
Limit Deployment to Listed Machines: there is one listed
Deploy Order: 1
Max Attempts: 3
Deployment Window: 0 - 24
Allow Snooze: Unchecked
There are no pre or post install messages
How long should I wait before assuming that the managed install is just not going to run? I have forced an inventory check on the computer and restarted it, but the Status is still listed as "Not Installed". I think that I'm being patient enough and I've waited almost two hours, but is that not long enough?
Thanks for any input.
--
Chuck Steel
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
ms01ak
13 years ago
Hi Chuck,
It should start as soon as the agent checks back in. Did the machine actually sync back in with the server (check the last sync) on the Inventory Computers. Also is the software for that Operating System or is it the wrong version of the software (check that the os is checked under the software inventory, otherwise kace will not install the software because it think it isn't supported. Lastly, check the log files on the computer itself it should tell you what's going on.
Cheers,
Mike
It should start as soon as the agent checks back in. Did the machine actually sync back in with the server (check the last sync) on the Inventory Computers. Also is the software for that Operating System or is it the wrong version of the software (check that the os is checked under the software inventory, otherwise kace will not install the software because it think it isn't supported. Lastly, check the log files on the computer itself it should tell you what's going on.
Cheers,
Mike
Posted by:
nshah
13 years ago
also check under Inventory > the computer in question
click the computer to see the details and under activities you should see a "to install list"
if what you are pushing isn't listed there then what ms01ak said are the places to check.
click the computer to see the details and under activities you should see a "to install list"
if what you are pushing isn't listed there then what ms01ak said are the places to check.
Posted by:
GillySpy
13 years ago
If an MI has failed 3 times then it will stop trying. You should see it in the failed list. You need to resave the MI to try again. See this faq for a bunch of things to check:
http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=821&artlang=en
http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=821&artlang=en
Posted by:
afzal
13 years ago
Here are some basic but important considerations and questions while deploying anything using KACE Kbox.
1. What package you are trying to install.
2. Have you manually installed that software on a machine and then uploaded the installer on the same software inventory item.
3. Have you tested the install parameters from the command prompt, if these are working form command prompt then they should work using Kbox. for silent installation of MSI based package 'Orca.msi' command line will look like [ msiexec.exe /i Orca.msi /qn]
4. Blank spaces in parameters may also cause problems in some cases.
5. Try using Pre and post install message to see what messages did you get.
6. Please note that on first inventory update kbox will install the package and on 2nd inventory update it will report it to Kbox. so force the invetory twice once before and one after the installation .
Regards,
1. What package you are trying to install.
2. Have you manually installed that software on a machine and then uploaded the installer on the same software inventory item.
3. Have you tested the install parameters from the command prompt, if these are working form command prompt then they should work using Kbox. for silent installation of MSI based package 'Orca.msi' command line will look like [ msiexec.exe /i Orca.msi /qn]
4. Blank spaces in parameters may also cause problems in some cases.
5. Try using Pre and post install message to see what messages did you get.
6. Please note that on first inventory update kbox will install the package and on 2nd inventory update it will report it to Kbox. so force the invetory twice once before and one after the installation .
Regards,
Posted by:
steelc
13 years ago
Thanks for the replies. It has now installed on one computer, not the other test machine still hasn't tried to install it. I guess I just need to be more patient.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.