anyweb

Push the client to Targetted Collections In this example we will push an installation of the client to the All Systems collection, this is in a Lab so this is ok. In a production environment you will want to test this on small groups first and work your way up. Right click on the All Systems collection and choose Install Client set your options making sure that Always Install is selected click Finish when done to verify the installation of the new client is happening, on the clients open task manager and look for ccmsetup.exe after some time you can verify the client version on the client As the client starts getting installed, the report we used in the beginning will show the new numbers increasing

Distribute the Client Package to your Distribution Points If you want to install the latest version of your Client in Operating System Deployments then you'll need the client package from definition updated to your Distribution Points. Expand the client package you just created, click on Distribution Points. Choose New Distribution Points. when the wizard appears click next select your distribution points for the client click next and then close when done.

Create a New Client from Definition Package One of the steps when deploying Operating Systems involves installation of the Configuration Manager Client (Setup Windows and ConfigMgr Step), as a result we want our Client Package files updated to the new version, so If you have not already done so you need to create a client from Definition package. (If you already have a Client Package from definition, simply update that to it's distribution points and you'll be fine.) Expand Software Distribution and right click on it, choose New, Package From Definition click Next when the create package from definition wizard appears choose configuration manager client upgrade and next choose always obtain files from a source directory and click next choose Network Path (UNC Name) and specify the directory containing the source files for this package as \\SERVERNAME\SMS_XXX\Client where SERVERNAME is your SCCM server, SMS_xxx is SMS_ and your site code (eg: SMS_WDN) click Finish at the summary screen

This is one way of updating your SCCM ConfigMgr Client after an upgrade. There are more ways of doing this. This guide is done in a Lab Environment. Please refer to Technet for recommended practise. After you have updated ConfigMgr from Sp1 to Sp2 you will have all your configmgr clients still running the old version of ConfigMgr (Sp1). Identify Client Versions To find out how many are using the old client you can use a built in report called Count SMS Client Versions, right click on the report and choose Run. the report will show you how many clients you have running the old (sp1) client, and if any, how many are running the newer sp2 client. so in this Lab I have 13 clients that need to be updated to the newer client version.

have you tried reading the manual for the switch, sorry but it's not my area at all

I've updated the post to include the download details here

then make the package Mandatory, and in the program options General tab set it to run hidden and on the Advanced tab click on Suppress program notifications

hi all, I know how hard it is to get grips with SCCM, MDT, WDS, PXE, WAIK so windows-noob.com will start doing some webcasts, so, do any of you have any requests ? let me know cheers niall

please attach the SMSTS.log file

either you dhcp server is not working or you need network drivers added to windows PE, i'd try testing the first option (easiest)

setting values using WSIM

are you trying to deploy windows 7 ? did you look at the troubleshooting section here ?

did you configure a DHCP server ?

please raise a new post about this, and one problem at a time, that way when its resolved others can find the info easier. I'm closing this thread as people are just replying to it instead of starting new posts explaining what they are trying to do and what the errors are. cheers niall

your command line should be something like this otherwise the transforms won't be applied msiexec.exe /q ALLUSERS=2 /m MSIHINKJ /i "Pro11.msi" TRANSFORMS=officepro.mst

based on your SCCM version info you are running SCCM 2007 SP1 without the R2 feature pack, so...... consider upgrading to SP2 and then installing R2 then try again.

how are you planning on doing this ?

good to know Peter, so did webdav require any special config ? any other gotchas that you'd like to share ?

are you launching this in a task sequence or as a package advertised to a collection ?

did you set any scope options for DHCP ?

remove the .net and try again, does it work then ?

yes, but its not too easy, you'll need to install and use System Center Virtual Machine Manager to do the conversion

I havnt tried installing SCCM 2007 R2 in Server 2008R2 yet but will do so soon. meanwhile I got this feedback from a user here on the forums about webdav 7.5 to be clear, are you using SCCM 2007 SP2 r2 or SCCM 2007 SP1 r2 ?

the SCOM guides will remain private for the time being. sorry.

welcome to the forums !