Chris Stauffer at myITForum.com

You want me to do What?

Syndication

News

Links to blogs i like

Links

GPO Client install Directions for ConfigMgr 2007

I put together directions for Deploying the ConfigMgr client via GPO because I felt that the information provided was lacking and confusing. After working with my TAM for the last several day I was able to get the client to install via a GPO. These directions explain how I got it workng.

(these are my opinions and not those of my TAM)

NOTE: In doing the research for this deployment method it was discovered that this will only deploy the client once. If you wanted to redeploy the client to a machine that already received the deployment you would have to go into the GPO and choose to redeploy the software. This causes every machine in the OU to re-run the application. It is recommended that this only be used as a once and done policy if at all. Personally I would recommend using a “Startup Script” as was used in SMS 2003. This way there is some logic build into the deployment.

Published Wednesday, November 19, 2008 12:11 PM by cstauffer

Comments

# re: GPO Client install Directions for ConfigMgr 2007@ Friday, November 21, 2008 9:22 AM

At my old company, it didn't take long for me to decide the official Microsoft GPO client install method wouldn't be appropriate in our environment.  I had been using the GPO machine startup script method for SMS2003 for so long, and it was so rock solid, I knew it could be easily modified for ConfigMgr.

# re: GPO Client install Directions for ConfigMgr 2007@ Friday, February 27, 2009 1:31 PM

I noticed that we have several ways to Install the Client. Does all logs are the same with the various method? in ccm.log how do you identify the Method used?

Especially as I have 20% of the machines not receiving the Client by GPO I have no ccmsetup.log and/or client.log on the client side even the ccm folder does not exist so I want to identify this GPO run on the server side logs.

Thank

Dom