problem in sccm client setup
hi friends i installed sccm setup to all my clients some of the clients showing successful site but it was shown in server console,apart from that client -no , approved -n/a ,assigned -yes in blocked - -- nothig is there ? what may be the reason
February 18th, 2010 10:23am
Hi,Have you extended the AD schema (http://technet.microsoft.com/en-us/library/bb633121.aspx) ?Have you configured the boundaries on ConfigMgr Console (Site Management/<SiteCode-SiteName>/Site Settings/Boundaries) http://technet.microsoft.com/en-us/library/bb633084.aspx ?Management Point is installed or not (http://technet.microsoft.com/en-us/library/bb632400.aspx ?To approve client, you can do this manually or automatically from ConfigMgr Console (Site Management/<SiteCode-SiteName>/Site Settings/Properties/site mode/Approval Setting) http://technet.microsoft.com/en-us/library/bb694193.aspx .Thank'sBechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2010 10:52am
Hi,
You have not yet responded to my questions above :)Some common client-installation issues include:
Native mode client settings do not work.
Clients cannot be managed because they cannot locate their default management point.
Clients fail to assign to correct site using auto-assignment.
Native mode clients fail to find the NLB management point.
Native mode clients fail to communicate with the site because they have multiple certificates.
Clients fail to approve automatically (in mixed mode).
Clients fail to install using the software update point installation method.
Site Server Log Files
The following site server log files are located in the <InstallationPath>\LOGS folder:
Log file
Description
Ccm.log
Records client Configuration Manager tasks.
Client setup log files
Client information can be found in the client setup log files located in the folder: %windir%\system32\CCMSetup on the client computer. The following table describes the client setup log files:
Log file
Description
CCMSetup.log
Records setup tasks performed by CCMSetup. Can help to troubleshoot client installation problems.
Client.msi.LOG
Records setup tasks performed by client.msi. Can help to troubleshoot client installation problems.
Client computer log files
On client computers that serve as management points, the client log files are located in the SMS_CCM\Logs folder. On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder. The following table describes the client log files:
Log file
Description
CcmExec.log
Records activities of the client and the SMS Agent Host service, and help to troubleshoot scenarios where the client is corrupted or not functioning. For example, this log file applies to a scenario where the client cannot communicate with a management point.
CertificateMaintenance.log
Records certificate maintenance for Active Directory and management points and help to troubleshoot scenarios where the client cannot communicate with a management point or with Active Directory.
ClientIDManagerStartup.log
Records the creation and maintenance of client globally unique identifiers (GUIDs), and helps troubleshoot scenarios where the client changes its GUID after a hardware change or after Windows activation.
ClientLocation.log
Records site assignment tasks. Can help to troubleshoot scenarios where the client is not assigned to a Configuration Manager 2007 site.
LocationServices.log
Records attempts to find management points and distribution points. Can help to troubleshoot scenarios where the client cannot find a management point or distribution point.
PolicyAgent.log
Records policy requests using the Data Transfer service, and help to troubleshoot policy request problems.
PolicyAgentProvider.log
Records policy changes. Can help to troubleshoot policy request problems or (WMI) errors.
PolicyEvaluator.log
Records new policy settings. Can help to troubleshoot policy override issues.
StatusAgent.log
Records status messages that are created by the client components. Can help to troubleshoot scenarios where the client cannot send status to the management point.
Reporting
There are a number of reports that you can use to help determine the success or failure of client deployments and assignment, including:
Client Deployment Failure Report
Client Deployment Status Details
Client Assignment Success Details
Client Assignment Detailed Status Report
Client Assignment Failure Details
Client Assignment Status Details
Client Deployment Success Report
Bechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront
February 18th, 2010 2:22pm
Hi,Me too, I think that AD Schema is not extended ?For that, Extend Ad schema for ConfigMgr : http://technet.microsoft.com/en-us/library/bb633121.aspxIf you have already extended the schema, please check ExtADSch.log Thank'sBechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2010 1:02pm


