SCCM 2012 R2 SP1 CU1 Client Install (Push, Package,OSD,Login Script)

Hi Everyone,

I have been reading all the posts about client installation in different scenarios.  Just looking to make sure still valid. I just upgraded to SCCM 2012 R2 SP1 CU1 . Luckily, I dont have any existing clients to push, but I am going live in 2 weeks.  I need to deliver it in 4 ways (4rd way is optional).  OSD, Client package in SCCM 2007, Login Script, client push from console.

OSD: From what I have seen, you can do it using the PATCH property like I have done in the past or using  the sccmclienthotfix.wsf script mentioned here: http://blogs.technet.com/b/deploymentguys/archive/2012/10/11/automatically-populate-the-patch-property-for-the-configmgr-client-installation-updated-for-configmgr-2012.aspx .

SCCM 2007 Upgrade Client package: Could do the same PATCH commandline in a script, then call the script. THe only other thing, that I dont think would work is to have the patch install program call the base client install as a "run this program first" package. But not sure that works cause it affects the client, which may stop it from working.

Login script: curently using a simple VB script that will upgrade the client if it isnt on 2012. command line is .\ccmsetup propert1 property 2 etc., so it runs from the DC. Can I simply call the .msp or does it behave as stated above? PATCH property?

Console Client push: From what I have seen, the only way to do it is to uses the PATCH property, but having to use UNC paths to the update, all clients would have to pull across the WAN, which I don't want to do.

I apologize as some of this has been asked before, but the posts are a little old and want to make sure of my options.

Thanks!

August 20th, 2015 10:17am

Well honestly i would not bother with the patch.

If since 2012 r2 SP1 CU1 you could use the Automatic Client upgrade (it work for CU now)

This will make it easy just install the 2012 r2 SP1 basic client and the rest will be done automatically.

If you want to know more about this feature look http://www.systemcenterdudes.com/step-by-step-sccm-2012-r2-sp1-cu1-installation-guide/ go to the updating the clients section.

But the old way of doing things with the patch still work and did not change.

Free Windows Admin Tool Kit Click here and download it now
August 20th, 2015 10:23am

Hi Anati,

How many client's are we talking about?

Client push now supports automatic client upgrade which include's CU's as of R2 SP1 :)

http://www.danielclasson.com/how-to-configure-automatic-client-upgrade-for-configuration-manager-2012-r2-sp1-cu1/

I have used it over the past few weeks on multiple migrations and it's great

If you are migrating to 2012 I would just push out the client from the new console via client push and let it work it's magic

  • Edited by Richard.Knight 17 hours 26 minutes ago
  • Marked as answer by anati 14 hours 40 minutes ago
August 20th, 2015 10:24am


Client push now supports automatic client upgrade which include's CU's as of R2 SP1 :)


Automatic client update, not client push if I am not mistaken. Haven't tried push yet though.
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2015 10:27am


Client push now supports automatic client upgrade which include's CU's as of R2 SP1 :)


Automatic client update, not client push if I am not mistaken. Haven't tried push y
August 20th, 2015 12:52pm

Thanks to everyone for the insite.
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2015 1:13pm

Hi Anati,

How many client's are we talking about?

Client push now supports automatic client upgrade which include's CU's as of R2 SP1 :)

http://www.danielclasson.com/how-to-configure-automatic-client-upgrade-for-configuration-manager-2012-r2-sp1-cu1/

I have used it over the past few weeks on multiple migrations and it's great

If you are migrating to 2012 I would just push out the client from the new console via client push and let it work it's magic

  • Edited by Richard.Knight Thursday, August 20, 2015 2:24 PM
  • Marked as answer by anati Thursday, August 20, 2015 5:11 PM
August 20th, 2015 2:23pm

Hi Anati,

How many client's are we talking about?

Client push now supports automatic client upgrade which include's CU's as of R2 SP1 :)

http://www.danielclasson.com/how-to-configure-automatic-client-upgrade-for-configuration-manager-2012-r2-sp1-cu1/

I have used it over the past few weeks on multiple migrations and it's great

If you are migrating to 2012 I would just push out the client from the new console via client push and let it work it's magic

  • Edited by Richard.Knight Thursday, August 20, 2015 2:24 PM
  • Marked as answer by anati Thursday, August 20, 2015 5:11 PM
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2015 2:23pm

Sorry, need to pick your brains again.

I am being told that since our users do not reboot or logon for weeks, that I cannot rely on a startup script to catch machines.

My plan is to use sccm 2007 package to migrate the clients to sccm 2012.  I know about haveng overlapping boundaries for client site assignment.  I told them that I would expire the client package at say 9 am and catch the others with the startup script.  But being told I cant, is there any reason I cannot leave everything as is ( even for several days) meaning having 2007 up to have the client get the 2012 upgrade package ?

I believe this may cause issue with clients trying to find content when using AD for DP locations.

Thanks

August 24th, 2015 4:22pm

if you deploy the package using SCCM 2007 to install and assign the new client to the new site the boundaries will not matter as long as you make sure you point the client to the new site. So don't worry about those.

By doing this you can leave the SCCM 2007 up and running and remove it when all the client are connected to the new one SCCM.

If people don't reboot the computer the script would take forever to get everyone

Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 5:37pm

Hi Frederick,

Thanks for your info.

I am just being parnoid, so I want to ask again.  Overlapping boundaries:

Not using auto for site assignement, so not an issue.

I have been asking to change how I am doing my pilot.  I was going to use a single AD site and flip it.  Now I have been asked to target only 4 subnets in my current 2007 subnet boundary.  basically want to chop out the 4.  I know I can add them to 2012 for content location and they will checking and report to 2012.  But I keep reading that overlapping boundaries are still frowned upon.  And because of that, in my original testing, I setup a VLAN.  

What is the best way to go about this?  I am thinking that overlapping between 2007 and 2012 is not a big deal anymore, since I have a single 2012 site.  If I look in this link: http://www.css-security.com/blog/sccm-2012-migration-made-easy-part-1/ it says "It is vital to eliminate any overlapping boundaries particularly in regards to Active Directory Sites."

On this site: http://blog-en.netvnext.com/2011/09/planning-migration-from-sccm-2007-to.html it says " Just make sure that you don't have overlapping boundaries in AD from the SCCM 2007 and the SCCM 2012 hierarchies."

Excellent article:  http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/

August 27th, 2015 9:40am

I would overlap the boundaries you don't have a choice in this case and il explain why.

one of the way to migrate client is using the existing infrastructure when you want to upgrade client that are connected to the SCCM 2007 to the SCCM 2012 you can make a package in the SCCM 2007 that send this to the client install the new client and point to the new site. The only way to do this is to have the right boundaries in the SCCM 2007 and SCCM 2012.

So don't worry about that. Like i said the client are already assign to the site they wont change unless ask to via GPO/script/manual intervention and so on. Especially since you said you aren't using any boundaries for site assignment.


  • Marked as answer by anati 17 hours 43 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2015 9:50am

Yes, I am pushing a 2012 upgrade package through 2007, as well as startup script.  Also can use push to at some point. 

So, No need to remove any boundaries from 2007, just add them to 2012. That way, I can advertise the package out in 2007 and when laptops come back online well after the initial push, they will just get the package and migrate.

August 27th, 2015 10:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics