The task sequence doesn’t have any implicit knowledge of what updates need to 
be installed. The Install Software Updates task sequence item will either 
install: 1) Mandatory (Required) Software Updates, or 2) All “available” (and 
“required”) Software Updates that are targeted to the device.

 

If you want to install only specific updates, then you’ll need to use some 
custom automation to achieve that.

 

Cheers,

Trevor Sullivan

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Iacaruso, Mike
Sent: Wednesday, March 19, 2014 11:31 AM
To: [email protected]
Subject: RE: [mssms] RE: SCCM 2012 task sequence for software updates

 

I see how the TS would work now.  The next question is how does the TS know 
which updates to install?  I don’t see a way of applying the required monthly 
software update group to the TS.

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of [email protected] 
<mailto:[email protected]> 
Sent: Wednesday, March 19, 2014 11:43 AM
To: [email protected] <mailto:[email protected]> 
Subject: Re: [mssms] RE: SCCM 2012 task sequence for software updates

 

I don’t see why a TS wouldn’t work.  I only see 3 steps… seems pretty 
straightforward, actually…

 

Step 1:  posh or vb or even a cmd line of sc stop <servicename>

I’d maybe script it tho; so that you build into the script to watch/monitor 
that the service is really stopped; so that it exits with an error code if not 
stopped (and therefore the TS fails) or exits with a 0 if the service is 
stopped.

Step 2: the install software updates 

Step 3: Reboot 

 

Note that if a server doesn’t actually install any software updates it would 
reboot regardless.  Not sure if that’s ok or not.  I’d call it a necessary evil 
to keeping the TS simple --that it *might* happen that no updates are 
installed, but a reboot happens anyway.

 

 

 

 

From: Mark Mears <mailto:[email protected]> 
Sent: ‎Wednesday‎, ‎March‎ ‎19‎, ‎2014 ‎10‎:‎01‎ ‎AM
To: [email protected] <mailto:[email protected]> 

 

You could probably get it to work using a custom task sequence and doing some 
scripting in those places where necessary.

 


Thanks, 


 

Mark Mears

 <mailto:[email protected]%0d> [email protected]

Phone: (757) 945-2651

 

 <http://www.cireson.com/> 


 <http://twitter.com/teamcireson>   Check out our System Center App Store: 
www.cireson.com/app-store <http://www.cireson.com/app-store> 

“Self Service Portal Unleashed!” Webinar | Watch it here. 
<https://vimeo.com/87792187> 

 


  _____  

 

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of Iacaruso, Mike
Sent: Wednesday, March 19, 2014 9:56 AM
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] RE: SCCM 2012 task sequence for software updates

 

We do not have Orchestrator setup in our environment.  In looking at the task 
sequence wizard I don’t think creating a new custom task sequence  does what I 
need and I don’t need to install an image.  Am I looking at this the wrong way?

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of Mark Mears
Sent: Wednesday, March 19, 2014 10:46 AM
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] RE: SCCM 2012 task sequence for software updates

 

You might want to utilize calling an Orchestrator runbook activity in your task 
sequence and let Orchestrator do all of the heavy lifting.

 


Thanks, 


 

Mark Mears

 <mailto:[email protected]%0d> [email protected]

Phone: (757) 945-2651

 

 <http://www.cireson.com/> 


 <http://twitter.com/teamcireson>   Check out our System Center App Store: 
www.cireson.com/app-store <http://www.cireson.com/app-store> 

“Self Service Portal Unleashed!” Webinar | Watch it here. 
<https://vimeo.com/87792187> 

 


  _____  

 

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of Iacaruso, Mike
Sent: Wednesday, March 19, 2014 9:25 AM
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] SCCM 2012 task sequence for software updates

 

I have several servers that require special attention when it comes to software 
update deployments.  Theses servers needs to have a service stopped before 
updates are installed and then force a reboot once the updates are completed.  
I was thinking of creating a task sequence that can be used to stop the 
service, run the updates package and then reboot.  Is this possible?

 

Mike Iacaruso

Enterprise Desktop Engineer

Office of Technology Services

Towson University

410-704-3965

 <mailto:[email protected]> [email protected]

 

 

 

 

 

 

 

 




<<image001.png>>

<<image002.jpg>>

Reply via email to