locked
Deploying Rollup2 client update during station build - task sequence RRS feed

  • Question

  • Hi

    I am new to SCCM and I am a little confused, so please bear with me! I have just upgraded SCCM 2012 to Cumulative Rollup 2.   Following the installation it has added a client update package (one for x32 and one for x64)

    A couple of questions:

    1) Is there a way I can automatically include this when I build new stations?

    For example in the task sequence  that I use for our 'Windows 7 x86' deployments.  Under the section 'setup windows and configuration manager' we seem to deploy 'Microsoft Configuration Manager Client Upgrade 5.0 ALL'

    Can I add the update here, so new builds install this update automatically along with the base client?

    2) How can I tell if the update has been installed on a client? 

    3) Why is there a x32 and x64 bit version of the update when there seemsto be only one version of the client out of the box 'Microsoft Configuration Manager Client Upgrade 5.0 ALL'' ?

    Thank you in advance for any help that you can offer.




    Friday, December 21, 2012 10:11 AM

Answers

  • 1. There's no auto include switch to flip but you can easily include the client msp using the PATCH property of msiexec. Basically, you set this property in the client properties of the Setup Windows and ConfigMgr task in you TS. This guidance (for 2007) is still valid: http://blog-en.netvnext.com/2011/11/how-to-install-sccm-client-with.html . This TechNet doc is also pretty comprehensive: http://technet.microsoft.com/en-us/library/jj553405.aspx

    2. You can create a simple query to do this or I'm nearly positive that there is also a built-in report you can use.

    3. There is only one ccmsetup, but there are definitely two different agents, one for 32 bit and one for 64 bot. ccmsetup is just a bootstrapper that downloads the necessary files and licks off the actual install.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by SuperPlay-UK Sunday, December 23, 2012 10:26 AM
    Friday, December 21, 2012 4:09 PM

All replies

  • 1. There's no auto include switch to flip but you can easily include the client msp using the PATCH property of msiexec. Basically, you set this property in the client properties of the Setup Windows and ConfigMgr task in you TS. This guidance (for 2007) is still valid: http://blog-en.netvnext.com/2011/11/how-to-install-sccm-client-with.html . This TechNet doc is also pretty comprehensive: http://technet.microsoft.com/en-us/library/jj553405.aspx

    2. You can create a simple query to do this or I'm nearly positive that there is also a built-in report you can use.

    3. There is only one ccmsetup, but there are definitely two different agents, one for 32 bit and one for 64 bot. ccmsetup is just a bootstrapper that downloads the necessary files and licks off the actual install.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by SuperPlay-UK Sunday, December 23, 2012 10:26 AM
    Friday, December 21, 2012 4:09 PM
  • Hi Jason

    Thank you for the information, very useful :-)

    Sunday, December 23, 2012 10:26 AM