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!