major scripting issue in habitat

[ccalverley]

for some reason, every single habitat schedule is pushing mid day
habitat app manage maintenance fires at 5:30 pm on 8000 machines at once
habitat posh maintenance fires at 1:45 pm on 8000 machines at once
habitat printestatus maintenance fires at, 1:39 pm on 8000 machines at once
all this needs to be fired outside business hours you are destroying bandwidth and killing the entire system.
please help resolve this.

[ccalverley]

oh and the kicker, it's not run on a group, it's individually scheduled on each and every machine, meaning between 1 and 6 pm my scheduled scripts table is > 24000 items long.

[ccalverley]

ok here is how you fix this
1. you need habitat groups
2. add the computers that have this enabled to the group
3. schedule the script to run on the group starting at 2 am and set it up to distribute the script over 14 hours on online computers only!
please

[Cubert]

I will start looking into group management for Habitat so we can allow you to use groups to preform the backend automation.

[ccalverley]

thank you,
in the mean time, is there anything i can do to reschedule some of these tasks?

[Cubert]

You can turn off the automation for those services inside the Automated Services tool.

Capture.PNG (115.08 KiB) Viewed 3433 times

Select the services you wish to stop and disable them.




Create the group needed to manage the maintenance scans and set it up as desired to run at least once a day but twice will keep data and alerts more current.

Next create a new script and call it Habitat Maintenance Runner or something like that to identify that this script will be the proxy to Habitat Maintenance and service scan functions.

You want to first set the variable needed for script function you are calling.

Capture11.PNG (7.82 KiB) Viewed 3433 times

Then call the script with a script run command. It should pass the variable to Habitat script and it will go off and do it's thing.

Capture1.PNG (41.11 KiB) Viewed 3433 times

Now configure your group to execute the new Proxy script which can run several maintenance tasks before exiting.

Keep in mind this is a work around and will not provide all the functionality that the automation preforms but is will get you the probe data and such from the agents.

Things you will be missing with automation will mainly be around database cleanup and log data.


You can find what variables you need to set by viewing the Habitat scripts in question to see what variables are allowed and if multiple variables are needed.