Robert Maijen

Home Tech Articles Microsoft SCCM 2007 R2 SCCM 2007 R2: Update Installation During OS Deployment Fails
Login Consultants released two new freeware tools to support Microsoft Application Virtualization 4.5.  App-V 4.5 Client Diagnostic and Configuration tool (ACDC). App-V 4.5 Add-on ADM v1.0 is an add-on for the Microsoft Administrative Template (adm) of App-V 4.5. Go here for more info and download

SCCM 2007 R2: Update Installation During OS Deployment Fails
Written by Administrator   
Tuesday, 04 August 2009 07:48

In some scenarios you want to have SCCM 2007 R2 deploy software updates during OS deployment. I have found that if you have a standard deployment of SCCM 2007 R2 that the deployment of selected and deployed updates fail. The log files will show that the part of the task sequence deploying the updates have timed-out.

 

To be able to deploy and OS you will have to create a task sequence. When creating a task sequence default there will be a step in which you will be asked if you want to install updates. When the task sequence is completed updates will be tried to be installed on the targeted system. What I have found that whenever the task sequence is run it might fail on installing these updates as result of a time out on finding any updates available for the system. Eventually an article on the MS Support Forums led me to the solution as. A

As explained in the article the default client installation, during OS deployment, is unable to find a distribution point from which to search and evaluate updates. So the following steps have to be taken:

 

  • Add a Server Locator Point to your SCCM installation
  • In the OS deployment task sequence, during the step of installing the SCCM client, add the following parameters for the client installation:
    • SMSSLP=<site server>
    • SMSMP=<site server>

 

After adding these parameters the client system is able to find the SCCM distribution point and can query for updates. As you will have created a deployment package for the SCCM Client you might also want to add these parameters in the package.

Read the forum article here

 

Robert

Comments

avatar Mike
0
 
 
I was informaed that an IP subnet also needed to be defined in some cases if you are doing a build and capture and the machine is not joined to the domain. Are you finding that to be the case or are the above settings enough?
Monday 15 February 2010, 02:54
Post Reply
Name *
Email (For verification & Replies)
Code   
ChronoComments by Joomla Professional Solutions
Submit Comment
Cancel
avatar Admin
0
 
 
I always define the boundaries including one for the IP subnet. This is I believe a best practice
Monday 15 February 2010, 22:53
Post Reply
Name *
Email (For verification & Replies)
Code   
ChronoComments by Joomla Professional Solutions
Submit Comment
Cancel
avatar Taye Olaniyi
0
 
 
The parameters SMSSLP and SMSMP are automatically added whenever you use client push installation from the SCCM site server, you will only need to add these parameter if you are carrying a stand-alone installation of the SCCM client. So it depends on how you decide to install the client.
Saturday 20 March 2010, 21:21
Post Reply
Name *
Email (For verification & Replies)
Code   
ChronoComments by Joomla Professional Solutions
Submit Comment
Cancel
Name *
Email (For verification & Replies)
Code