引用：http://blogs.technet.com/smsandmom/archive/2008/03/06/configmgr-2007-client-push-installation-method-in-a-workgroup.aspx

ConfigMgr 2007 是不支持在 workgroup 环境下的 Client push 方式安装的。

其他在工作组环境的限制有：

1. Workgoup clients 不能使用 AD domain services 服务，所以即使 site 已经进行了 AD domain services 的发布，workgroup client 也不能从中受益。如 workgroup clients 只能通过 WINS 或 DNS 来定位 default MP，而不能通过 AD domain services；
2. AD system, AD user, AD user group 等 discovery 方式对 workgoup 无效；
3. 针对 user 的 advertiesments 对 workgroup 无效；
4. BDP 不能建立在 workgroup 机器上，必须是域中的机器。

原文：http://myitforum.com/cs2/blogs/spruitt/archive/2007/10/01/using-psexec-to-install-the-sms-client.aspx

 

Sometimes the easiest way to install the client may be running it with psexec. That's especially true if the machine hasn't been discovered by some mechanism. The options for doing this often cause confusion, because there are two files involved - ccmsetup.exe and client.msi. CCMSETUP looks for client.msi in whatever folder ccmsetup is run from. If you use the -c switch that's normal with psexec, to copy the file being executed, it only copies the exe. That then hangs when it can't locate the msi, and the ccmsetup.log file is filled with messages reporting that it can't find client.msi in C:\Windows\System32 and will retry in 20 minutes.

 

The solution is to run ccmsetup from a location containing both files. The easiest is usually on an SMS site server. The proper command line is:

 

psexec -s \\computer \\SMSserver\client\i386\ccmsetup.exe [ccmsetup switches]

 

The -s command says to run using the system account. Do not use -c, as that will cause the errors described above. Using -d is optional; ccmsetup terminates pretty quickly. I generally leave it off so I can see the zero return code.

 

【个人引申】个人觉得 psexec 的最大一个用处是，可以写一个在远程机器上执行的批处理或者其他脚本，然后用 psexec –c 参数将这个脚本拷贝到远程机器上执行。例如本文中的例子可以这样写：

 

需要拷贝到远程机器的批处理文件，假设名称为 ClientInstall.bat，内容为：

\\SMSserver\client\i386\ccmsetup.exe [ccmsetup switches] 

然后可以在机器上执行：

Psexec \\computer –c ClientInstall.bat 

这样就达到了相同的目的。之后如需修改参数，只需要修改 ClientInstall.bat 中的参数即可。

Content Location 是指Client 如何定位 advertisement 和Software update 发布的 Package Source Files。

 

当一个 Client 需要进行 content location 的时候，会发送 content location 的请求到 MP：

1.     当 Client 位于其 assigned site 的边界内，client 会发送 content location 请求到 default MP；

2.     当 client 位于和其 assigned site 有联系的 secondary site 的边界内的时候，如果 secondary site 有 proxy MP，client 会向 proxy MP 发送 contend location 请求；如果没有 proxy MP，client 会向 default MP 发送请求。

3.     当 client 不在其 assigned site 或和其 assigned site 有联系的 secondary site 的边界内的时候，client 可以通过 AD Domain Services (global roaming capability)获取 site 信息，然后向其目前当前roamed site 中的 resident MP 进行 content location；如果 resident MP 不能进行 content location（当前 site 中没有相应的 content 存在），client 会发送请求到其 default MP。

4.     When a client is located within the boundaries of a primary site lower in the hierarchy than its assigned site or a secondary site attached to its assigned site, a client that cannot access site information from Active Directory Domain Services (regional roaming capability), will continue to request content location from its default management point in its assigned site.

一、Client Setup Log Files

位置：%windir%\system32\CCMSetup

Log file name	Description
CCMSetup.log	Records setup tasks performed by CCMSetup. Can be used to troubleshoot client installation problems.
Client.msi.LOG	Records setup tasks performed by client.msi. Can be used to troubleshoot client installation problems.

二、Client Computer Log Files

位置：
1. 在充当 management points 的 client 上，log 位置为 SMS_CCM\Logs
2. 在其他 client 上， log 位置为 %Windir%\System32\CCM\Logs folder

Log file name	Description
CcmExec.log	Records activities of the client and the SMS Agent Host service. Can 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. Can 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 GUIDS. Can help to 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. Can 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.

三、Configuration Manager Site Server Log Files

位置：SMS\Logs

Log file name	Description
Ccm.log	Records client configuration manager tasks. Can help to troubleshoot scenarios where the site cannot connect to computers because of permissions or name resolution.
Fspmgr.log	Records fallback status point activities. Can help to troubleshoot problems with the fallback status point.
Hman.log	Records site configuration changes and publishes site information in Active Directory. Can help to troubleshoot site control serial number or delta serial number issues, or scenarios where the site cannot publish site information to Active Directory.
Mpcontrol.log	Records the registration of the management point with WINS. Records the availability of the management point every ten minutes. Can help to troubleshoot possible IIS issues if the management point is unavailable.
Policypv.log	Records updates to the Advanced Client policies to reflect changes to client settings or advertisements. Can help to troubleshoot scenarios where policy updates do not occur after you make changes to advertisements or to client settings.
Sitecomp.log	Records maintenance of the installed site components. Can help to troubleshoot upgrade issues, registry or file system permission issues, or scenarios where the site cannot publish site information to Active Directory.

Clients Fail to Assign to a Site Because the Site Compatibility Check Fails

当 SCCM 2007 的客户端被成功安装，但是不能委派到站点中时，一个可能的原因是在委派的过程中 site compatibility 失败。

解决方法：

首先确定 client 具有检查 site compatibility 的机制，用如下两种方法：
• Active Directory Domain Services is extended for Configuration Manager 2007, and clients belong to this forest.
• Clients can find a server locator point that's published in WINS, or they are reinstalled and assigned to a server locator point during installation.

延伸知识

• What's New in Client Deployment for Configuration Manager
• About Client Assignment
• Determine If You Need a Server Locator Point
• How to Specify the Server Locator Point for Client Computers

Clients Cannot be Managed Because they Cannot Locate their Default Management Point

如果 client 以及被成功安装，并且被委派到一个站点中，但是不能下载 policy，一个可能原因是站点中没有 management point，或者 client 找不到 management point。

解决方法：确认站点中存在 management point。

client 通过以下方法中的一种找到 management point：
1. AD Domain service(if the schema is extended for Configuration Manager 2007)
2. DNS (if Configuration Manager 2007 is configured for DNS publishing)
3. WINS
4. Server locator point.

Clients Fail to Install Using Client Push Because Windows Firewall Blocks Installation

需要在防火墙设置例外规则，如下：

1. File and Printer Sharing
2. Windows Management Instrumentation (WMI)

For more information, see Firewall Settings for Configuration Manager 2007 Clients.

Missing Data in Client Deployment and Assignment Reports

If you view the following reports and they do not contain client data, ensure that clients are assigned to a fallback status point:
• Client Assignment Detailed Status Report
• Client Assignment Failure Details
• Client Assignment Status Details
• Client Assignment Success Details
• Client Deployment Failure Report
• Client Deployment Status Details
• Client Deployment Success Report

解决方法：
Assign a fallback status point to Configuration Manager 2007 clients and view the reports from the site in which the fallback status point is installed.

Attention!!!

1. SMS 2003 clients do not use these reports.
2. 在同时布署许多台 client 的时候，client 反馈到 Fallback status point 的消息会有延迟的问题。一个变通的方法是在 fallback status point 上设置 throttling settings。

延伸知识：
1. How to Assign the Fallback Status Point to Client Computers 2. Determine If You Need to Configure Throttle Settings for the Fallback Status Point

Clients Fail to Install Because the Management Point is Not Operational

当一个站点的所有 client 都不能被管理时，这只能是 mangagement poing 的问题了。

解决方法：
Ensure that the management point has the required dependencies in the section "General Site Server Prerequisites" in the following topic: Prerequisites for Installing Configuration Manager.
Also reference Configuration Manager Supported Configurations to verify that you running in a supported environment.
Consider manually running the Configuration Manager 2007 Setup Prerequisite Checker to identify any missing dependencies for the management point.

Solution For more information about running the Setup Prerequisite Checker, see How to Start the Setup Prerequisite Checker.

Clients Fail to Assign to Correct Site Using Auto-Site Assignment

If you install clients using auto-site assignment which either fails or the client is assigned to the wrong site, the most likely reason for this failure is that boundaries are not configured correctly for the Configuration Manager 2007 sites, or that the client roamed into another site during the upgrade process.

解决方法：
Check that boundaries are configured correctly for each site in the Configuration Manager 2007 hierarchy.

For more information about boundaries, see the following topics:
• Planning Configuration Manager Boundaries
• Choose Configuration Manager Boundaries
• How to Configure Configuration Manager Boundaries

If clients are likely to roam during the upgrade process, do not use auto-site assignment.