Partilhar via

How to obtain 100 % ConfigMgr Client Installation

  • Artigo

Question:
Is there any possibility, or third party tools, that will make me sure that 100% of computers that I want it to install the client, has the SCCM client installed... and if they don't, is there any way to initiate installation and to be sure 100% that the SCCM Client is installed.

Answer:
To ensure that all systems that are intended and targeted for the ConfigMgr client installation. The best client deployment method I have used here at Microsoft is using AD GPO that will apply 3 settings.

1. the ccmsetup parameters are place in the registry
2. the WSUS URL is place in the registry.
3. applies the ADM Client Assignment template.

Enable WSUS/SUP Client Installation. In the GPO add the WSUS URL for your SUP Site Role. As clients join the domain or connects to the network, the Windows Update Agent will scan against your WSUS server and the ConfigMgr client will be detected as not installed and WSUS will install the client treating the client as if it was a critical update.

The installation will start about 2 to 3 minutes after the client is detected as not installed. This method will also upgrade a client that is lower than the published version in WSUS. If a client is already installed with the right version, the client will be re-assigned to your site if not already assigned. Also as part of this GPO you will want to add the ADM Client Assignment template. This is comes with ConfigMgr 2007. This template will keep clients assigned to the site of choice.

Two things will happen automatically for you. If the client is un-installed for any reason, WSUS will re install the client on the next WSUS scan. If the client is re assigned to another site, the ADM template with automatically reassign the client back to the originating site code immediately.

Let me know if you need to help setting this up. Its the best client deployment method I recommend. Works great. Client upgrades would also be made simple as well. All an admin would have to do is publish the new latest client to WSUS, client upgrades will happen automatically on the next Windows Update scan.

Technorati Tags: Configuration Manager 2007,Client Installation,WSUS,SUP ADM Template

Comments

  • Anonymous
    January 01, 2003
    Great post! I've always only used either Push install or a GPO with ccmsetup.msi. I like the idea of using the WSUS that's already installed on my SCCM site server(s). One question though, my clients already get the url for their SUP through my SCCM client, so I wouldn't have to specifically add it through a GPO, correct?

  • Anonymous
    January 01, 2003
    I am seeing all over the place people referring to running ccmsetup.msi for client istallation. This is an inaappropriate method for the client install. Any script dealing with client install should point to the CCMSetup.exe located in the client share on your primary site server. The problem that occurs is that if there is an update to the client via service pack or upgrade the MSI does not install those updates.

  • Anonymous
    January 01, 2003
    Does anyone have a walk through of how to accomplish this setup in full? jaredlarkins@live.com Thanks!

  • Anonymous
    January 01, 2003
    No, you don't have to apply the WSUS URL via the GPO. Using the GPO in (Microsoft's case) ensures the client keeps this URL specified. We have a lot of clients managed by different group and sometimes clients move by getting picked up by other over lapping client deployment efforts. Using the GPO forces the clients to remain assigned and homed to a site of choice.

  • Anonymous
    January 01, 2003
    Noted, yes the ConfigMgr client does configures the WSUS URL. In fact we use GPO to place the WSUS URL on systems that doesn't not have a client, this redirects clients from using External Microsoft Updates and points clients to the ConfigMgr WSUS/SUP Role, Then WSUS itself pushes the client to systems that did not have a client originally. So for initial deployment of the client via WSUS, applying the WSUS URL via a GPO would be required. Hope that makes since.

  • Anonymous
    January 01, 2003
    Yes it does make sense. My only issue would be that after the ConfigMgr clients are configured with the WSUS url, wouldn't the url be overwitten again with the GPO url at the next Group Policy refresh?

  • Anonymous
    January 01, 2003
    Yes, the GPO would try to over write the WSUS URL after the ConfigMgr client configures it, but since the WSUS URL from the GPO is the same as what ConfigMgr client is setting, there is no impact and no change. You will see "GPO conflict" in the LocationServices.log if the GPO is attempting to set the WSUS URL value different that what ConfigMgr set.

  • Anonymous
    January 01, 2003
    It does look that, at least in our environment, our client machines get the WSUS url via the configmgr client and it's link to their nearest SUP/WSUS server. I have created a GPO that runs ccmsetup.msi and also populates systems with the ccmsetup command lines as well as the defaul configmgr site. I really like the idea of using SUP/WSUS to push clients down and wonder if I really need to even GPO the install in the first place. We're currently using our WSUS/SUP to push ForeFront Defs down to our clients and it really is pretty slick.

  • Anonymous
    June 14, 2012
    I'm with Jared on this... a walkthrough guide on how to set this up will be greatly appreciated. ruffwise@yahoo.com thanks

  • Anonymous
    December 19, 2012
    I'm also with Jared on this. any technical guid will be highly appreciated. rakesh.kr.2008@gmail.com

  • Anonymous
    December 24, 2014
    How do we track client deployment via group policy by referring log files globally