Scripted install seems to work best for us. We also use push in cases where the client isn’t getting installed.
Mike From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, July 8, 2014 3:34 PM To: [email protected] Subject: RE: [mssms] More newbie questions There is no “best way” to deploy the ConfigMgr client. You have a few options: 1. Client Push (outbound connection from site server to client, requires firewall openings and administrative permissions) 2. Software Updates (uses GP Preferences + WSUS to deploy client) 3. GPO Software Installation (uses client.msi package + ADMX file to configure client) 4. Manual / scripted install (specify installation args in command line) Here’s my comments on each method: 1. For initial deployment, Client Push generally works pretty well, as long as you don’t have restrictive configurations that would prevent it. 2. Software Updates / WSUS based installation is okay, but I don’t like having to set up a GPO to point clients to the WSUS instance. 3. I try to avoid GPO Software Installation, due to lack of control over it, but it does work okay. 4. Scripted install gives you the most control over execution time, method, and command line parameters If you set up PowerShell Remoting ahead of time, you could use that as a channel to deploy the ConfigMgr client using the scripted installation method. I’d strongly recommend reading the TechNet documentation for client deployment. This, plus all subsections --> http://technet.microsoft.com/en-us/library/gg699391.aspx Cheers, Trevor Sullivan Microsoft PowerShell MVP From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Matthew W. Ross Sent: Tuesday, July 8, 2014 5:08 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] More newbie questions My quest to learn SCCM continues (with interruptions from other duties and holidays)... I have a test client getting updates through the Software Center. (Yay!) I've been following the guides at windows-noob.com for configuration, and I have a question on how he has the client being deployed: In the described setup, they use WSUS to download and install the client. I see in the configuration (under Administration -> Site Configuration -> Sites -> *YSE - Your Site Here* -> Client Installation Settings -> Client Push Installation Properties) the option to push the client to systems as they are found automatically. So, which way is best(TM)? Or, which way is best for which situations? Also, if I use the Client Push method, should I be disabling automatic updates through WSUS Group policies? On my test box, I saw the updates as well as additional updates through Automatic updates. --Matt Ross Ephrata School District
