myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


Software Update Deployments and Maintenance Windows

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Software Update Deployments and Maintenance Windows Page: [1]
Login
Message << Older Topic   Newer Topic >>
Software Update Deployments and Maintenance Windows - 8/28/2008 11:34:28 AM   
rpowell319

 

Posts: 8
Score: 0
Joined: 8/28/2008
Status: offline 		Hello,

Having a little problem with update deployments and maintenance windows.  What I am trying to do is have a single deployment to a collection and its sub-collections.  I have defined a seperate sub-collection for domain controllers and a the main collection contains all servers (including the domain controllers.  The domain controllers collections have a maintenance window set for 11:00pm - 1:00am.  The main collection has a maintenance window of 1:30am to 4:00am.  The domain controllers successfully recieve and deploy their updates.  The main collection does not.  the deployment enforcement states report for for the main collection says "waiting for next maintenance window" and none of the patches deploy.

I know for a fact that the window of 2.5 hours is large enough to deploy most if not all patches as most of the patches have a standard 20 minute duration and according to the sccm docs the way it is supposed to work is it will deploy the patches with the smallest duration first and evaluate each patch in sequence according to its duration (not the cummulative duration of all required patches).

So that is the problem.  Also willing to entertain other methods of doing the same thing.  Essentially we want to make sure that some servers (DC's) get patches deployed and rebooted prior to other servers (domain member servers). 

Thanks for any advice.

Russ
Post #: 1
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 11:54:12 AM   
tzegarrundo

 

Posts: 5
Score: 0
Joined: 8/28/2008
Status: offline 		Russ do the servers in the main collection see the maintenance windows and have you verified this by looking at the servicewindowmanager.log? Are there any errors in the servicewindowmanager.log file or the updatesdeployment.log file on the clients? What you describe should work just fine and other than excluding the DC's from the main collection and just having them in the sub collection is the only thing I would consider changing. Also are these maintenance windows re-occurring or one shot windows?

(in reply to rpowell319)
Post #: 2
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 12:04:57 PM   
rpowell319

 

Posts: 8
Score: 0
Joined: 8/28/2008
Status: offline 		Hi,

Yes they do see the maintenance window.  I have included the relevant portion of the servicewindowmanager.log from one of the servers:

<![LOG[A Timer Event has occurred]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:960">
<![LOG[    Sending Message SERVICEWINDOWEVENT:START event]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:304">
<![LOG[    The Service Window={C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} has started at 8/27/2008 1:30:00 AM]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:967">
<![LOG[Checking Service Windows to find Next Event.....]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:983">
<![LOG[    Next Event Time is at 8/27/2008 4:00:00 AM. Service Window with ID:{C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C}. Starttime?:0]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:903">
<![LOG[    Scheduling the Timer Task]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1769">
<![LOG[    Scheduled the timer to fire on 8/27/2008 4:00:00 AM]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1782">
<![LOG[]LOG]!><time="01:30:02.253+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1785">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:1, Type:3]LOG]!><time="01:30:02.300+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1804">
<![LOG[No Service Windows exist for this type. Will check if the program can run in the All Programs window...]LOG]!><time="01:30:02.300+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1263">
<![LOG[        Biggest Active Service Window has ID = {C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} having Starttime=8/27/2008 1:30:00 AM]LOG]!><time="01:30:02.300+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1099">
<![LOG[            Duration is 0 days, 02 hours, 30 mins, 00 secs]LOG]!><time="01:30:02.300+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1100">
<![LOG[ActiveServiceWindow has 8998 seconds left]LOG]!><time="01:30:02.300+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1017">
<![LOG[Program can run! Setting *canProgramRun to TRUE]LOG]!><time="01:30:02.300+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="2144" file="servicewindowhandler.cpp:1018">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:1, Type:4]LOG]!><time="01:30:02.362+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7328" file="servicewindowhandler.cpp:1804">
<![LOG[No Service Windows exist for this type. Will check if the program can run in the All Programs window...]LOG]!><time="01:30:02.362+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7328" file="servicewindowhandler.cpp:1263">
<![LOG[        Biggest Active Service Window has ID = {C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} having Starttime=8/27/2008 1:30:00 AM]LOG]!><time="01:30:02.362+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7328" file="servicewindowhandler.cpp:1099">
<![LOG[            Duration is 0 days, 02 hours, 30 mins, 00 secs]LOG]!><time="01:30:02.362+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7328" file="servicewindowhandler.cpp:1100">
<![LOG[ActiveServiceWindow has 8998 seconds left]LOG]!><time="01:30:02.362+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7328" file="servicewindowhandler.cpp:1017">
<![LOG[Program can run! Setting *canProgramRun to TRUE]LOG]!><time="01:30:02.362+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7328" file="servicewindowhandler.cpp:1018">
<![LOG[]LOG]!><time="04:00:05.830+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:959">
<![LOG[A Timer Event has occurred]LOG]!><time="04:00:05.830+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:960">
<![LOG[    Sending Message SERVICEWINDOWEVENT:END event]LOG]!><time="04:00:05.830+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:326">
<![LOG[        This is a one shot Service Window that has already finished.]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:934">
<![LOG[    The Service Window={C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} has ended at 8/27/2008 4:00:00 AM]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:977">
<![LOG[Checking Service Windows to find Next Event.....]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:983">
<![LOG[    Next Event Time is at 9/24/2008 1:30:00 AM. Service Window with ID:{E8621FE0-D2A6-44A5-8C0C-29D4740B924F}. Starttime?:1]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:903">
<![LOG[    Scheduling the Timer Task]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:1769">
<![LOG[    Scheduled the timer to fire on 9/24/2008 1:30:00 AM]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:1782">
<![LOG[]LOG]!><time="04:00:05.845+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="5668" file="servicewindowhandler.cpp:1785">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:1800, Type:4]LOG]!><time="23:02:17.809+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1804">
<![LOG[No Service Windows exist for this type. Will check if the program can run in the All Programs window...]LOG]!><time="23:02:17.840+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1263">
<![LOG[        Biggest Active Service Window for Type=1 not found]LOG]!><time="23:02:17.840+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1095">
<![LOG[Program cannot Run! Setting *canProgramRun to FALSE]LOG]!><time="23:02:17.840+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1271">
<![LOG[WillProgramRun called with: Runtime:1800, Type:4]LOG]!><time="23:02:19.340+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1828">
<![LOG[No Service Windows of this type exist.]LOG]!><time="23:02:19.340+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1414">
<![LOG[There exists an All Programs window for this duration. The Program will run eventually.]LOG]!><time="23:02:19.340+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1424">
<![LOG[]LOG]!><time="23:02:19.340+300" date="08-27-2008" component="ServiceWindowManager" context="" type="1" thread="7740" file="servicewindowhandler.cpp:1425">

And here is the Updatesdeployment.log
<![LOG[No current service window available to run updates assignment with time required = 1800]LOG]!><time="23:02:17.840+300" date="08-27-2008" component="UpdatesDeploymentAgent" context="" type="1" thread="7740" file="deploymentutils.cpp:664">
<![LOG[No service window available to run updates assignment]LOG]!><time="23:02:19.340+300" date="08-27-2008" component="UpdatesDeploymentAgent" context="" type="2" thread="7740" file="updatesmanager.cpp:2784">
<![LOG[This assignment ({E091F40C-1704-42B6-8407-AF28B9C7CCF4}) will be retried once the service window is available.]LOG]!><time="23:02:19.340+300" date="08-27-2008" component="UpdatesDeploymentAgent" context="" type="1" thread="7740" file="updatesassignment.cpp:1336">
<![LOG[No pending install assignment]LOG]!><time="23:02:19.371+300" date="08-27-2008" component="UpdatesDeploymentAgent" context="" type="1" thread="7852" file="assignmentsmanager.cpp:1125">
<![LOG[No other installations in pipeline. No reboot required.]LOG]!><time="23:02:19.371+300" date="08-27-2008" component="UpdatesDeploymentAgent" context="" type="1" thread="7852" file="updatesmanager.cpp:3155">
<![LOG[OnPolicyModify for assignment ({E091F40C-1704-42B6-8407-AF28B9C7CCF4})... ]LOG]!><time="02:27:54.063+300" date="08-28-2008" component="UpdatesDeploymentAgent" context="" type="1" thread="7544" file="updatesassignment.cpp:1537">
 
It appears by looking at the update deployments log, that it never re-attempts the deployment at the 1:30am window.  A lot of this log information is greek to me and I am not sure what it is trying to tell me.  If you could interpret that might help.

Thanks
Russ


(in reply to tzegarrundo)
Post #: 3
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 1:18:30 PM   
tzegarrundo

 

Posts: 5
Score: 0
Joined: 8/28/2008
Status: offline 		Russ it's much easier to look at the log files using trace32.exe (it's in the sms tool kit) but here is a more readable text below.

From what you have above the client DOES see the service window on the morning of 8/27 @ 1:30am and then it also states that the next service windows will not start until 9/24 @ 1:30am.

The updates deployment log from above only has the entries that start on the night of 8/27 @ 11:02pm and that log states that there is no service window available which corresponds to the servicewindow log that says the next service window will not start until a month later on 9/24 @ 1:30am.

I'd like to see the updates deployment log for the time entry of the early morning of 8/27 @ 1:30am to see why the client did not install the updates at that time.

If you created the deployment after 1:30am on 8/27 then that would explain why it is now waiting until 9/24 @ 1:30am to install the updates, basically the 8/27 1:30am window has already passed before the client recieved the policy for the updates deployment.

Tony


A Timer Event has occurred 8/27/2008 1:30:02 AM 2144 
   Sending Message SERVICEWINDOWEVENT:START event 8/27/2008 1:30:02 AM 2144 (0x0860)
   The Service Window={C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} has started at 8/27/2008 1:30:00 AM 8/27/2008 1:30:02 AM 2144

Checking Service Windows to find Next Event..... 8/27/2008 1:30:02 AM 2144 (0x0860)
   Next Event Time is at 8/27/2008 4:00:00 AM. Service Window with ID:{C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C}. Starttime?:0 8/27/2008 1:30:02 AM 2144 (0x0860)
   Scheduling the Timer Task 8/27/2008 1:30:02 AM 2144 (0x0860)
   Scheduled the timer to fire on 8/27/2008 4:00:00 AM 8/27/2008 1:30:02 AM 2144 (0x0860)
8/27/2008 1:30:02 AM 2144 (0x0860)

OnIsServiceWindowAvailable called with: Runtime:1, Type:3 8/27/2008 1:30:02 AM 2144 (0x0860)
No Service Windows exist for this type. Will check if the program can run in the All Programs window... 8/27/2008 1:30:02 AM 2144 (0x0860)

       Biggest Active Service Window has ID = {C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} having Starttime=8/27/2008 1:30:00 AM 8/27/2008 1:30:02 AM 2144 (0x0860)
           Duration is 0 days, 02 hours, 30 mins, 00 secs 8/27/2008 1:30:02 AM 2144 (0x0860)
ActiveServiceWindow has 8998 seconds left 8/27/2008 1:30:02 AM 2144 (0x0860)
Program can run! Setting *canProgramRun to TRUE 8/27/2008 1:30:02 AM 2144 (0x0860)
OnIsServiceWindowAvailable called with: Runtime:1, Type:4 8/27/2008 1:30:02 AM 7328 (0x1CA0)
No Service Windows exist for this type. Will check if the program can run in the All Programs window... 8/27/2008 1:30:02 AM 7328 (0x1CA0)
       Biggest Active Service Window has ID = {C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} having Starttime=8/27/2008 1:30:00 AM 8/27/2008 1:30:02 AM 7328 (0x1CA0)
           Duration is 0 days, 02 hours, 30 mins, 00 secs 8/27/2008 1:30:02 AM 7328 (0x1CA0)
ActiveServiceWindow has 8998 seconds left 8/27/2008 1:30:02 AM 7328 (0x1CA0)
Program can run! Setting *canProgramRun to TRUE 8/27/2008 1:30:02 AM 7328 (0x1CA0)
8/27/2008 4:00:05 AM 5668 (0x1624)

A Timer Event has occurred 8/27/2008 4:00:05 AM 5668 (0x1624)
   Sending Message SERVICEWINDOWEVENT:END event 8/27/2008 4:00:05 AM 5668 (0x1624)
       This is a one shot Service Window that has already finished. 8/27/2008 4:00:05 AM 5668 (0x1624)
   The Service Window={C8B1FA44-B5EE-43A1-AD0C-084DD485BD9C} has ended at 8/27/2008 4:00:00 AM 8/27/2008 4:00:05 AM 5668 (0x1624)
Checking Service Windows to find Next Event..... 8/27/2008 4:00:05 AM 5668 (0x1624)
   Next Event Time is at 9/24/2008 1:30:00 AM. Service Window with ID:{E8621FE0-D2A6-44A5-8C0C-29D4740B924F}. Starttime?:1 8/27/2008 4:00:05 AM 5668 (0x1624)
   Scheduling the Timer Task 8/27/2008 4:00:05 AM 5668 (0x1624)
   Scheduled the timer to fire on 9/24/2008 1:30:00 AM 8/27/2008 4:00:05 AM 5668 (0x1624)
8/27/2008 4:00:05 AM 5668 (0x1624)
OnIsServiceWindowAvailable called with: Runtime:1800, Type:4 8/27/2008 11:02:17 PM 7740 (0x1E3C)
No Service Windows exist for this type. Will check if the program can run in the All Programs window... 8/27/2008 11:02:17 PM 7740 (0x1E3C)
       Biggest Active Service Window for Type=1 not found 8/27/2008 11:02:17 PM 7740 (0x1E3C)
Program cannot Run! Setting *canProgramRun to FALSE 8/27/2008 11:02:17 PM 7740 (0x1E3C)
WillProgramRun called with: Runtime:1800, Type:4 8/27/2008 11:02:19 PM 7740 (0x1E3C)
No Service Windows of this type exist. 8/27/2008 11:02:19 PM 7740 (0x1E3C)
There exists an All Programs window for this duration. The Program will run eventually. 8/27/2008 11:02:19 PM 7740 (0x1E3C)
8/27/2008 11:02:19 PM 7740 (0x1E3C)

And here is the Updatesdeployment.log

<![LOG[No current service window available to run updates assignment with time required = 1800]LOG]!><time="23:02:17.840+300" date="08-27-2008" component="UpdatesDeploymentAgent" context="" type="1" thread="7740" file="deploymentutils.cpp:664">  1/1/1601 12:00:00 AM 13480744 (0xCDB328)
No service window available to run updates assignment 8/27/2008 11:02:19 PM 7740 (0x1E3C)
This assignment ({E091F40C-1704-42B6-8407-AF28B9C7CCF4}) will be retried once the service window is available. 8/27/2008 11:02:19 PM 7740 (0x1E3C)
No pending install assignment 8/27/2008 11:02:19 PM 7852 (0x1EAC)
No other installations in pipeline. No reboot required. 8/27/2008 11:02:19 PM 7852 (0x1EAC)
OnPolicyModify for assignment ({E091F40C-1704-42B6-8407-AF28B9C7CCF4})...  8/28/2008 2:27:54 AM 7544 (0x1D78)


(in reply to rpowell319)
Post #: 4
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 2:14:22 PM   
rpowell319

 

Posts: 8
Score: 0
Joined: 8/28/2008
Status: offline 		Tony,

The entries that I sent you from the updatesdeployment.log were the last in the log.  There are no further entries after that.

There is only a single deployment that started at 11:00pm to a top level collection and all subcollections.  So the single deployment applies to both sets of machines, but they have different maintenance windows defined. 

As far as the maintenance windows go, currently each collection has two maintenance windows defined.  A single window with no reoccurance for 08/27/08 and a second reoccuring monthly window that starts on 09/24/08.  Obviously the times frames are different for the dc collection and the regular servers collection.

do you think I need to create a seperate patch deployment for the regular servers that has an enforcement time of 1:30am?

Thanks again for your help.

Russ

(in reply to tzegarrundo)
Post #: 5
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 2:51:49 PM   
tzegarrundo

 

Posts: 5
Score: 0
Joined: 8/28/2008
Status: offline 		Russ so the single maintenance window with no reoccurance, starts on 8/27/2008 @ 1:30am correct? So what is the start time/date of your deployment? 11pm on what day? If it starts at 11pm on 8/27/2008 there in lies your problem.

trying to determine if the clients did not get the deployment notification until after 8/27/2008 @ 1:30am if they did then they missed the one shot maintenance window and now they will wait until 9/24/2008 @ 1:30am before applying updates.

Otherwise everything looks to be setup properly to do what you want to accomplish, I think we just have the timing off.

(in reply to rpowell319)
Post #: 6
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 3:40:33 PM   
rpowell319

 

Posts: 8
Score: 0
Joined: 8/28/2008
Status: offline
Tony,

Have a single deployment with a deadline at 08/26/08 11:00pm.  That deployment encompasses both the domain controllers collection and the "all others including dc's collectionothers including dc's collection".

The maintenance window for the domain controllers collection is from 08/26/08 11:00pm to 08/27/08 1:00am
The maintenance window for the "all others including dc's collection" is from 08/27/08 1:30am to 08/27/08 4:00am

So it appears that the enforcement for the deployment happens at 11:00pm.  the domain controllers apply their patches just fine because the window and the enforcement time coincide.  The "all others including dc's collection" evaluates deployment at 11:00pm and finds that the maintenance window is not available.  And apparently it never reevaluates the the deployment when the maintenance window becomes available at 1:30am (because it was a one time shot window?).

So, if I create another deployment that has an enforcement time of 1:30am for the "all others including dc's collection" then will it work properly?  If that is what I need to do, thats fine, just didn't think that was how it worked.

Russ

(in reply to tzegarrundo)
Post #: 7
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 3:59:59 PM   
tzegarrundo

 

Posts: 5
Score: 0
Joined: 8/28/2008
Status: offline 		Russ you shouldn't have to creat another the deployment I do all my deployments basically the same way as you. Couple of things are going on since we don't have the logs for 8/27 1:30am timeframe.

The start time for the deployment maybe set after the 1:30am -4am time frame. The start time is different from the deadline date, look at the schedule tab in the deployment. If the start time is as soon as possible it then becomes the time you created the deployment. also check the software updates client agent properties there you can set the scan and re-evaluation schedules to coincide with your maintaince windows.

(in reply to rpowell319)
Post #: 8
RE: Software Update Deployments and Maintenance Windows - 8/28/2008 5:19:48 PM   
rpowell319

 

Posts: 8
Score: 0
Joined: 8/28/2008
Status: offline 		Tony

The start time for the deployment was set for 1 week prior to the manditory enforcement, so that is not it.

I did look at the software updates client agent properties.  They are set to the defaults of once per day and re-evaluation at every 7 days.  To effectively address the problem I am seeing, would have to be able to set these to an every couple of hours type schedule, but the schedule does not allow for anything less then days.  So that won't work either.

Think we are going to try the brute force method of creating an additional deployment that kicks off at 1:30am for a certain collection group and see if that works for us.  Have another patch deployment going out tonight, so we will see if that works.  Will let you know tomorrow.

Thanks again for all your help.
Russ

(in reply to tzegarrundo)
Post #: 9
Page:   [1]
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Software Update Deployments and Maintenance Windows Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts



  
Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.250