Good morning,

We are using KACE to rollout Bomgar and symantec endpoint protection to our store systems.

Store devices have a deployment window of 2AM to 4AM for both Bomgar and SEP however this deployment doesn't appear to be happening, I started rolling KACE agent to a number of store devices on Tuesday night with most of the sites installed by Wednesday afternoon so I was expecting that the Bomgar and SEP installs would have taken place this morning between 2 and 4AM however this doesn't appear to have happened.

The MI jobs are based on a machine smart tag that checks to see if Bomgar/SEP is already installed, if not, then the MI job should run against that client.

I am also still deploying agents to other stores over night (we have around 700 stores, approx 4000 devices to install the client to so are doing it slowly) using the provision tool, could this have stopped the MI jobs from running?

0 Comments   [ - ] Hide Comments


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.
Answer this question or Comment on this question for clarity


Top reasons I see failures on MI's:
Ensure that the OS you are deploying to was marked as supported in your software inventory record; make sure your managed action is set apropriately (user logged on, execute anytime, etc); make sure the installer package runs correctly outside of K1000 with the same command line switches. Make sure you test the MI in EXACTLY the scenario you intend to deploy in - meaning don't change the switches or the managed action after testing and expect it will perform the same. It should but I have 20+ stories about when it doesn't and it was a baaaad day.

Also, note that deploy window translates loosly to "start the install on systems that check in during this time"; it will not halt in progress installs at the close of the window, and machines checking in outside the window will not start. Chances are with 4000 devices not all of them check in in a 2 hour window- that'd murder your K1000. Open the window wider, and/or wait a few days.

Neither of these products has much if any impact that I'm aware of (unless SEP wants a reboot), so you may be able to push them out more aggressively?
Answered 09/15/2011 by: cblake
Red Belt

Please log in to comment
2am is the default maintenance window on the kbox. Depending upon how long that takes your window could be much shorter. You can change the maintenance window.

Some ideas:
  • To optimize network bandwidth and speed up each task -- you could distribute the installer files during the day -- using file sync as an example (c:\bomgar.msi). Then the MI could just contain the command for the local installer and not copy any files
  • You could setup the install as an offline script that runs between 2a and 4a. Unlike inventory, an offline script does not require a task on the kbox so many many more boxes can run it at the same time. Just make sure you put some time checking in your script.
Answered 09/15/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
We rolled out Bomgar to a number of machines that were critical and had no issue, we just let the MI install at any time.
Answered 09/16/2011 by: ms01ak
Tenth Degree Black Belt

Please log in to comment
ms01ak -- that means that your install would basically happen on next check-in which is an option. But this customer wants to optimize the rollout in a narrow window of 2 hours. Most check-in windows are more than 2 hours long to start with.

But maybe if you guys swapped command lines or has a sense of the deployment time per machine that might help one another?
Answered 09/16/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
Thanks for the advice guys, changed the window from 2AM-4AM to 1AM-7AM and installs went ahead.

Issue with Bomgar is more that the vast majority of devices I am installing it on are point of sale tills, having the "detecting proxy settings" dialogue window appear during taking an order would be disruptive to store sale operations hence why the window.
Answered 09/16/2011 by: nbs
Orange Belt

Please log in to comment