Auto Provisioning not running daily
I might be mis-understanding what Auto Provisioning is. So I just want to get it clarified.
We have an Auto Provisioning setup for windows platform for a specific IP range (ie 172.18.1.1-254). The schedule is set to run every day at 10 am. Currently we have 27 succeed, 161 failed and 66 running. The Last Run is from 6 days ago. I several others setup the same way for different IP ranges. Only a few of them have Running provisions. For all of them the Last Run was from 6 days ago.
My questions:
1. Why is there still some IPs marked as running?
2. Why is the Last Run from 6 days ago, when my schedule says to run every day at 10 am.
We have an Auto Provisioning setup for windows platform for a specific IP range (ie 172.18.1.1-254). The schedule is set to run every day at 10 am. Currently we have 27 succeed, 161 failed and 66 running. The Last Run is from 6 days ago. I several others setup the same way for different IP ranges. Only a few of them have Running provisions. For all of them the Last Run was from 6 days ago.
My questions:
1. Why is there still some IPs marked as running?
2. Why is the Last Run from 6 days ago, when my schedule says to run every day at 10 am.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
airwolf
13 years ago
I wish I could give you a concrete answer, but I figure I'll throw my $.02 in since there have been no replies to your inquiry...
I assume that the job isn't re-running every day at 10am due to it not completing from the day prior. How large of a scope do you have defined for the scan? Have you tried rebooting your KBOX (a service could be hung)?
It doesn't seem like the scan is functioning as intended, so I'd suggest putting in a ticket to KACE support. They may need to tether to your KBOX to troubleshoot the problem.
I assume that the job isn't re-running every day at 10am due to it not completing from the day prior. How large of a scope do you have defined for the scan? Have you tried rebooting your KBOX (a service could be hung)?
It doesn't seem like the scan is functioning as intended, so I'd suggest putting in a ticket to KACE support. They may need to tether to your KBOX to troubleshoot the problem.
Posted by:
KevinG
13 years ago
Click on "Settings" -> "KBOX Agent" tab -> " Provisioned Configurations"
Click on the number in the failed column and clink on the IP address on the next page to get detailed information on why they fail.
Post error information.
Click on the number in the failed column and clink on the IP address on the next page to get detailed information on why they fail.
Post error information.
Posted by:
jeremys
13 years ago
Airwolf
Each job is setup for to scan 255 clients (ie 172.20.1.1-254). There is about 3 out of 60 that still have a running process. For all of them they are set to run daily, but from what I can see they have only ran once.
KevinG
I am not questioning why they fail. Most of the fails are expected, as there is no machines assigned to those IPs. What I am questioning is what the auto provisioning is for. I assume it is used to rescan the network to look for new machines and install the kbox agent. Our setup seems to have run once ( and worked), but it does not appear to be periodically re-scanning the network.
The other issue is why some are stuck as running. That means there is no fail or success messages.
I think I will contact KBox support and open a ticket with them. If we find a solution I will try to post it here.
Each job is setup for to scan 255 clients (ie 172.20.1.1-254). There is about 3 out of 60 that still have a running process. For all of them they are set to run daily, but from what I can see they have only ran once.
KevinG
I am not questioning why they fail. Most of the fails are expected, as there is no machines assigned to those IPs. What I am questioning is what the auto provisioning is for. I assume it is used to rescan the network to look for new machines and install the kbox agent. Our setup seems to have run once ( and worked), but it does not appear to be periodically re-scanning the network.
The other issue is why some are stuck as running. That means there is no fail or success messages.
I think I will contact KBox support and open a ticket with them. If we find a solution I will try to post it here.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.