NS7 - Patch Management [Default Update / Maintenance Windows]
I'm sure i'm missing something terribly obvious here...
I'm trying to setup patching in NS7 so that they run at the Default Update time like they did in NS6. However, i've noticed that it doesn't appear to care what the Default Update time is - it downloads and installs any necessary patches every time the configuration updates (every hour).
Now, i've noticed that if i set the global Maintenance Window to a specific time, the patches don't install when the configuration updates. Only problem is that the global Maintenance Window obviously affects everything. So I tried to set the maintenance window within the Default Software Plug-in Policy, and change the global one back to being 24hrs. That put me back at square one (patches installed at the config update again)...so it only seems to look at the global maintenance window.
What am I doing wrong here? I'm assuming I have to set a seperate maintenance window, but i'm not sure exactly what I should be targeting, etc.
Any help is greatly appreciated...
RC
Comments
ok, nevermind i think...
If you set the Default Policy to override Maintenance Windows then it works the way I expected. Still not sure how you apply different global maintenance windows though. If someone has a good explanation let me know.
----------------------------------------------- i'm no stranger to slack, but i'm not a slacker
Further information?
The maintenance window default after the installation is open for 24 hours. I made the mistake of changing this maintenance window to represent "Off Hours" and in turn could not get a generic job or task to run unless it was within the "Off Hours" period of time (9pm to 5am). What I would like some clarification on is the purpose of the maintenance window setting. Is there a reason to have the default maintenance window at 24 hours and then add further maintenance windows that refine the time? Is there a write-up or document that goes a little more in-depth on the topic. I am just wondering what is the purpose of having one all encompassing window for maintenance that is then either overridden or preempted by another.
Thanks,
Mark
Would you like to reply?
Login or Register to post your comment.