Answered by:
What is the best way to manually install the SCCM 2012 client from a newly deployed machine?

Question
-
Hey guys,
90% of the time my Helpdesk team will have the luxury of being able to deploy a new computer and just wait for the SCCM client to auto install via push from the server. However there are a few cases where we need to get a laptop or desktop out the door very quickly and they want the ability to manually install the 2012 client in those cases. Obviously I want to make sure it is correctly configured to talk to my SCCM server when such cases arise. In my mind it seems liek thsi would be as simle as having them navigate to the folowing path:
"\\<MySCCMServerName\SMS_<MySiteName>\Client"
and having them run "ccmsetup.exe" but is it really that simple? Are there some switches I need to run against ccmsetup.exe to make sure its properly configured for my environment? Should I run it from that path or create the "ccmsetup" folder int he Windows DIR and run it frorm there?Friday, June 8, 2012 5:30 PM
Answers
-
How are you deploying new clients? Can't you just add a step that will install the client? See http://technet.microsoft.com/en-us/library/gg712298.aspx. It basically is as simple as running ccmsetup.exe (if the AD schema is extended for ConfigMgr and client installation properties are published).
Torsten Meringer | http://www.mssccmfaq.de
Yes that would be fine as well, can I also add a step to install Endpoint Protection right away too?
FYI - Your link appears to be broken...
UPDATE: It worked when I took the "." off the end like so:
http://technet.microsoft.com/en-us/library/gg712298.aspx
This was what i was looking for, thank you!Friday, June 8, 2012 9:02 PM
All replies
-
How are you deploying new clients? Can't you just add a step that will install the client? See http://technet.microsoft.com/en-us/library/gg712298.aspx. It basically is as simple as running ccmsetup.exe (if the AD schema is extended for ConfigMgr and client installation properties are published).
Torsten Meringer | http://www.mssccmfaq.de
Friday, June 8, 2012 7:19 PM -
How are you deploying new clients? Can't you just add a step that will install the client? See http://technet.microsoft.com/en-us/library/gg712298.aspx. It basically is as simple as running ccmsetup.exe (if the AD schema is extended for ConfigMgr and client installation properties are published).
Torsten Meringer | http://www.mssccmfaq.de
Yes that would be fine as well, can I also add a step to install Endpoint Protection right away too?
FYI - Your link appears to be broken...
UPDATE: It worked when I took the "." off the end like so:
http://technet.microsoft.com/en-us/library/gg712298.aspx
This was what i was looking for, thank you!Friday, June 8, 2012 9:02 PM -
See http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/operating-system-deployment-and-endpoint-protection-client-installation.aspx for OSD and SCEP.
Torsten Meringer | http://www.mssccmfaq.de
Friday, June 8, 2012 9:26 PM -
See http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/operating-system-deployment-and-endpoint-protection-client-installation.aspx for OSD and SCEP.
Torsten Meringer | http://www.mssccmfaq.de
Hey Torsten,
We plan to move to OSD but have not done so yet because (right now) we have a working MDT-based imaging infrastructure. We have only had SCCM 2012 in our environment for a short while and the time we have to work on it is limited so we had to focus on some specific features first. With SCCM 2012 our initial goals were to get Endpoint Protection deployed, automate Microsoft Updates through the SUP, get the Application Catalog stocked with company apps and THEN we would focus on OSD. We have not quite made it to the OSD phase of our project yet so I was looking for a way to just have our helpdesk team install the client manaully on the end of an MDT deployment. Now (thanks to your first link) I think i can just auto-install it as part of our MDT task sequence. I wil save that second link though and take a look at it.
Appreciate the follow-up!Friday, June 8, 2012 11:02 PM -
See http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/operating-system-deployment-and-endpoint-protection-client-installation.aspx for OSD and SCEP.
Torsten,
Torsten Meringer | http://www.mssccmfaq.de
Thank you again for this link. At a glance I assumed that it was more OSD-focused and out of scope with what I was trying to achieve. After reading it I see now that it provides a lot of insight into what actually happens when you install the Endpoint Protection Client and SCCM Client (which was really what I was looking for). Thank you for this! It was very helpful!Saturday, June 9, 2012 5:30 AM