Software96432

prajwaldesai.
comhttp://prajwaldesai.
com/configuration-manager-2012-r2-client-installation/PrajwalDesaiConfigurationManager2012R2ClientInstallationInthispostwewilldiscussabouttheConfigurationManager2012R2ClientInstallationmethods,wewillalsoconfigurethenetworkaccessaccountthatisamustbeforeyouperformConfigurationManager2012R2ClientInstallation.
ConfigurationManager2012R2ClientInstallationcanbedoneinvariousways,beforeyoucanuseConfigurationManagertomanageasystem,youmustdiscoverthesystemandinstalltheclient.
InmypreviouspostswehaveseenhowtoconfigureConfigurationManager2012R2BoundariesandDiscoveries,sooncethesystemsarediscoveredyoucanproceedwithConfigurationManager2012R2ClientInstallation.
Atanypointoftimeyoucanjumptoconfigurationmanager2012R2stepbystepguideformypreviousposts.
LetslookatthemethodsavailableforConfigurationManager2012R2ClientInstallation,wewillbedeployingtheclientsusingclientpushinstallationinthispost.
1)ClientPushInstallation–ClientPushInstallationhappenswhenantheSCCMservermakesanetworkconnectiontotheclient(amachinewhereconfigurationmanagerclientistobeinstalled)andthenbeginstheclientinstallationprocess.
Forthisthesystemmustbediscoveredandtheadministratorshouldhaveconfiguredthefirewallexceptions.
Thismethodrequirestheadministratortostarttheclientpushinstallationonselectedcomputers.
2)AutomaticSitewideClientPushInstallation-InAutomaticsitewideClientPushInstallationmethodyoucanconfigureclientpushinstallationforasite,andclientinstallationwillautomaticallyrunonthecomputersthatarediscoveredwithinthesite'sconfiguredboundarieswhenthoseboundariesareconfiguredasaboundarygroup.
3)Softwareupdatepointinstallation-ThismethodinstallstheclientbyusingtheConfigurationManagersoftwareupdatesfeature.
Nopriordiscoveryofsystemisrequiredinthismethod.
4)ManualInstallation–Thismethodallowsyoutoinstalltheconfigurationmanagerclientsmanually.
TheinstallationcanbeinitiatedbycopyingtheCCMSetup.
exefileonthesystemandrunningitwithanuseraccountwhichhasenoughpermissionstoinstallthesoftware.
ThisprogramanditssupportingfilescanbefoundintheClientfolderoftheSystemCenter2012ConfigurationManagerinstallationfolderonthesiteserverandonmanagementpointsinyoursite.
5)GroupPolicybasedInstallation–AsthenamesaysyoucaninstalltheConfigurationManagerclientusinggrouppolicy.
WhenyouassigntheConfigurationManagerclienttocomputersbyusingGroupPolicy,theclientinstallswhenthecomputerfirststarts.
WhenyoupublishtheSystemCenter2012R2ConfigurationManagerclienttousersbyusingGroupPolicy,theclientdisplaysintheControlPanelAddorRemoveProgramsforthecomputerfortheusertoinstall.
6)UsingLogonScripts–ConfigurationManager2012R2supportslogonscriptstoinstalltheSystemCenter2012R2ConfigurationManagerclientsoftware.
YoucanusetheprogramfileCCMSetup.
exeinalogonscripttotriggertheclientinstallation.
7)UsingComputerImaging–YoucanpreinstalltheConfigurationManager2012R2clientsoftwareonamasterimagecomputerthatwillbeusedtobuildcomputersinyourenterprise.
Whencomputersareimagedfromthismasterimage,theywillcontaintheConfigurationManager2012R2clientandmustcompletesiteassignmentwheninstallationiscomplete.
8)UpgradeInstallation–Thismethodusesyourexistingsoftwaredistributioninfrastructuretoupgradetheclient.
Upgradeinstallationrequirespriordiscoveryandsiteassignmentofthesystem.
TheabovemethodsaresomeofthewayswheretheSCCMadmincanuseforConfigurationManager2012R2ClientInstallation.
InthispostwewillinstalltheConfigurationManager2012R2Clientbyenablingtheautomaticsitewideclientpushinstallationmethod.
ForClientpushinstallationyoucancheckthispost.
FromtheConfigurationManagerConsoleClickAdministration,UnderSiteConfiguration,ClickSites,atthetopribbonunderClientInstallationSettings,clickClientPushInstallation.
IntheGeneraltabchecktheboxforEnableAutomaticsitewideclientpushinstallation.
UnderSystemtypesselectServersandWorkstations.
Ifyouwanttoinstalltheclientagentondomaincontrollerschoosetheoption"AlwaysInstallconfigurationManagerClientonDomainControllers",withthistheclientagentswillbeinstalledonallthenewlydiscoveredDomaincontrollers.
Ifyouwanttohaveanoptionofpushingtheclientagenttodomaincontrollersduringclientinstallationwizardthenchoosetheoption"NeverInstallConfigurationManagerClientonDomainControllerunlessspecifiedinClientPushInstallationWizard".
ClickonApply.
SelecttheAccountstab,theaccountthatyouwilladdheremusthavelocaladministratorrightsoneverycomputeronwhichyouwanttoinstalltheclient.
.
Iwillchoose"PRAJWAL\sccmadmin"astheuseraccountfordeployingclientagentonsystems.
Onceyouhaveaddedtheaccount,ClickApplyandOKtoclosethepropertiespage.
Afterfewminutesweseethatccmsetup.
exe*32processisseenonthesystems.
ThebelowscreenshotisfromoneofthemachinenamedWIN7.
PRAJWAL.
LOCAL.
SimilarscreenshotfromoneofthemachinenamedWIN8.
PRAJWAL.
LOCAL.
Beforetheclientagentisinstalled,thefilesrequiredforinstallationisfirstcopiedtothesystemunderthepath\windows\ccmsetup.
Afterfewminutesweseethattheconfigurationmanager2012R2clienthasbeeninstalledon2machines(WIN7andWIN8)andtheClientActivitystatusisActive.
InstallingtheConfigurationManagerClientthroughClientPushWizardIntheaboveexampleweenabledautomaticsitewideclientpushinstallationandtheclientwereinstalledonfewsystems.
Whileconfiguringclientpushinstallationwehadspecifiednottoinstalltheconfigurationmanagerclientsondomaincontrollersautomaticallywhendiscovered,howevertheclientcouldbeinstalledthroughclientpushinstallation.
InthisexamplewewillinstalltheconfigurationmanagerclienttoonemachineNamedAD(Domaincontroller).
FromtheConfigurationConsole,ClickAssetsandCompliance,UnderDevicesSelectAllSystems.
RightClickonthesystemwheretheclienthastobepushed.
ClickInstallClient.
ClickNext.
SpecifyClientPushOptions–Sinceweareinstalledtheclientonthesystemwhichisadomaincontroller,checktheboxforAllowtheclientsoftwaretobeinstalledondomaincontrollers.
AlsocheckInstalltheclientsoftwarefromaspecifiedsiteandclickNext.
ClickClose.
Ifwetakealookatccm.
logfileontheSCCMserver,weseethecompleteprocessrightfromhowtherequestissenttoserverandhowtheclientisinstalled.