软件分发、补丁推送排错

最新推荐文章于 2024-04-27 20:15:48 发布

weixin_34032827

最新推荐文章于 2024-04-27 20:15:48 发布

阅读量455

点赞数

文章标签：操作系统 ui

原文链接：http://blog.51cto.com/ericfu/1893123

版权

组件功能：

sms_distribution_manager：处理包，将其分发到分发点
distmgr.log 更新包的日志

sms-package_transfer_manager

client download setup log:c:\windows\ccmsetup\ccmsetup.log

applicationhost.config

ccm client安装排查日志：

查看客户端Windows目录下有没有出现ccmsetup文件夹，如果没有则在服务器端查看ccm.log，需要设置客户端请求安装账户，然后即可成功

补丁更新失败日志：
C:\Windows\CCM\Logs\WUAHandler.log
C:\Windows\Windowsupdate.log

补丁更新：
创建软件更新组（就是补丁分组）-->下载创建部署包（就是把补丁下载下来放到一个目录中）-->部署到集合
软件更新组--部署--计划：改为尽快，可以让客户端立即再次下载该包

软件推送：
新建包---分发内容（选择分发点）--部署
软件推送排错过程如下（完整过程已测ok）：

客户端日志位于：C:\Windows\CCM\Logs

软件下载成功后，位于客户端的 CCM\Cache\相应包的目录下，没有的话则表示包没有下载成功

1.先查看服务器端包的创建过程：serverlog：policypv.log根据创建包的时间查找policyid

2.找到后再到clientlog中的policyagent.log中找该policyid，往下看可以看到策略下载成功　　　　　　　　　　　　　　　　　　　　　　　　　datatransferservices.log只是记录了客户端下载到了DTS任务（DSTjob记录了客户端要下载的内容，到什么地方去下载包等等信息），而真正去下载包的过程记录　　在cas.log中
然后看execmgr.log，记录了客户端下载安装软件的log

注：在DP上无法按照包名称搜索到该软件信息，其文件位于 SCCMContentLib\FileLib中，可以根据创建日期找到该包

在SCCM2007的客户端CAS.log中，如果客户端始终无法下载到包，可能是找不到DP（No matching DP location found；；或者download request only,ignoring location updagte后没有继续下去的log，如果找到DP的话，会有“Download location found 0 http://sccm03\sms_dp_smspkgc$/C0000003/”或者“Download location found 1 - h\\sccm03\smspkgc$\c0000003”类似的log。

找不到DP，查看其DP的 configMgr站点系统的边界保护配置，是否包含客户端所在的范围

PkgXferMgr.log---服务器端相互之间信息

在sccm的软件分发中，经常会需要通过查看客户端的sccm日志来进行排错，下面是个人在sccm日常排错中经常查看的一些客户端日志，供大家参考：
PolicyAgent.log -察看联系MP获取Policy的信息。
DataTransferService.log - 察看从MP下载Policy的信息。 记录策略或包访问的所有 BITS 通信
LocatoinServices.log - 客户端获取MP和DP位置的信息。

CAS.log -客户端下载包的过程。 内容访问服务，维护本地数据包缓存

ContentTransferManager.log - 客户端下载program的信息。 计划后台智能传输服务 (BITS) 或服务器消息块 (SMB) 以下载或访问 SMS 包
execmgr.log -program执行的信息
CcmExec.log --ccm client是否运行正常

C:\Windows\ccmcache下有已下载成功的更新或程序安装包

UpdatesDeployment.log----补丁更新日志，可以找到该补丁包kb号
UpdatesStore.log---补丁日志
windowsupdate.log---windows补丁更新日志

补丁推送排查过程：

服务器端：
1.policypv.log：
可以根据包id（xly00015查找到该部署包是否创建成功）

2.distmgr.log:
Content definition already exists: \\?\C:\SCCMConten
tLib\DataLib\1e9f9b4a-4199-411b-a50e-e061510a96f1 通过该文件夹可以找到该补丁已经在站点上部署成功，可以在站点上搜索kb，然后再在该log里面搜索包含该kb的文件夹名称，搜索不到表示有问题

客户端：
1.DataTransferService.log - 察看从MP下载Policy的信息。客户端可以找到该KB及其guid号
2012:[LOG[UpdateURLWithTransportSettings(): NEW URL - http://sccm.testj.com:80/SMS_DP_SMSPKG$/1e9f9b4a-4199-411b-a50e-e061510a96f1/sccm?/windows6.1-kb2786081-x64.cab] 1e9f9b4a-4199-411b-a50e-e061510a96f1是站点下文件夹名称，该文件夹下包含有该补丁
2012:[LOG[Added (source=.sms_dcm?Id&DocumentId=1e9f9b4a-4199-411b-a50e-e061510a96f1/MANIFEST&Hash=FB912E99FA59D6470F9654E25169E6C586996E01540D119733E912D0F4785AA1&Compression=zlib,dest={FD13BAC9-2482-4C55-B7C5-7ED001778A40}_1.zip) pair from manifest.]
2007:[LOG[Added (source=.sms_dcm?Id&Name=Site_6595DB9C-36A9-4AF4-9722-FAD4D16AE47B/SUM_0a2945d7-4460-4f95-8d43-64a0cb0ebc15&Version=1&Compression=zlib,dest={6E669683-5C22-4C1D-938A-F1CEC9009AA0}.zip) pair from manifest.]LOG]

2.LocatoinServices.log - 客户端获取MP或者DP位置的信息，可以找到该guid号
2007:WSUS Path='http://SCCM2007.TESTJ.COM:8530', Server='SCCM2007', Version='1'
2007:Distribution Point='\\SCCM2007.TESTJ.COM\SMSPKGC$\MCC00003\0a2945d7-4460-4f95-8d43-64a0cb0ebc15', Locality='LOCAL', DPType='SERVER', Version='6487', Capabilities='<Capabilities SchemaVersion="1.0"/>', Signature='']LOG]!><time="00:50:26.107+000" date="05-04-2013" component="LocationServices"

2012:[Created and Sent Location Request '{257F0CF6-9739-4794-BF82-A484976AEEE0}' for package {223EBD74-FDEA-40B5-A938-CAE1F436504C}]
Distribution Point='http://sccm.testj.com/SMS_DP_SMSPKG$/58d1aef3-d31c-4b19-94cf-162387a289f4（包含补丁的文件夹名称）（这是2012中的信息）

3.CAS.log - 如果没有下载过补丁，则没有该日志
决定使用哪个DP，包的下载过程，可以查询到下载源地址，补丁更新包也在default site，地址如下：http://sccm.testj.com/SMS_DP_SMSPKG$/58d1aef3-d31c-4b19-94cf-162387a289f4（在datalib目录下，可以找到该kb）
以下为一个补丁包的下载过程日志（2007cas.log）：0a2945d7-4460-4f95-8d43-64a0cb0ebc是guid
<![LOG[Requesting locations synchronously for content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1 with priority Foreground]LOG]!><time="00:50:23.595+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="contentaccessservice.cpp:1142">
<![LOG[Calling back with the following distribution points]LOG]!><time="00:50:25.436+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="ccmpkglocation.cpp:264">
<![LOG[Distribution Point='\\SCCM2007.TESTJ.COM\SMSPKGC$\MCC00003\0a2945d7-4460-4f95-8d43-64a0cb0ebc15', Locality='LOCAL']LOG]!><time="00:50:25.436+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="ccmpkglocation.cpp:289">
<![LOG[Requesting content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1, size(KB) 0, under context System with priority Foreground]LOG]!><time="00:50:25.451+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="contentaccessservice.cpp:575">
<![LOG[Submitted CTM job {5B748F81-CF7A-4D1E-9B5E-3471A51F0ECF} to download Content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1 under context System]LOG]!><time="00:50:25.763+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="downloadmanager.cpp:576">
<![LOG[Successfully created download request {58AD5DC5-3969-4E49-8E20-290445C0A48B} for content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1]LOG]!><time="00:50:25.857+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="downloadcontentrequest.cpp:804">
<![LOG[Location update from CTM for content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1 and request {58AD5DC5-3969-4E49-8E20-290445C0A48B}]LOG]!><time="00:50:26.107+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="downloadcontentrequest.cpp:969">
<![LOG[Download location found 0 - \\SCCM2007.TESTJ.COM\SMSPKGC$\MCC00003\0a2945d7-4460-4f95-8d43-64a0cb0ebc15]LOG]!><time="00:50:26.107+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="downloadcontentrequest.cpp:977">
<![LOG[Download request only, ignoring location update]LOG]!><time="00:50:26.107+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1448" file="downloadcontentrequest.cpp:983">
<![LOG[Download started for content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1]LOG]!><time="00:50:26.356+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1112" file="downloadmanager.cpp:1004">
<![LOG[Raising event:
[SMS_CodePage(936), SMS_LocaleID(2052)]
instance of SoftDistDownloadStartedEvent
{
ClientID = "GUID:3C100807-2986-42A6-A638-680A055443FE";
DateTime = "20130503165026.387000+000";
MachineName = "WIN08R2";
PackageId = "0a2945d7-4460-4f95-8d43-64a0cb0ebc15";
PackageName = "0a2945d7-4460-4f95-8d43-64a0cb0ebc15";
PackageVersion = "1";
ProcessID = 1544;
SiteCode = "MCC";
ThreadID = 1112;
};
]LOG]!><time="00:50:26.450+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1112" file="event.cpp:525">
<![LOG[Download completed for content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1 under context System]LOG]!><time="00:50:30.428+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1464" file="contentaccessservice.cpp:1680">
<![LOG[Hash verification succeeded for content 0a2945d7-4460-4f95-8d43-64a0cb0ebc15.1 downloaded under context System]LOG]!><time="00:50:30.646+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1464" file="contentaccessservice.cpp:1927">
<![LOG[Download succeeded for download request {58AD5DC5-3969-4E49-8E20-290445C0A48B}]LOG]!><time="00:50:30.662+000" date="05-04-2013" component="ContentAccess" context="" type="1" thread="1464" file="downloadcontentrequest.cpp:1046">

==========================================================================
bits troubleshooting:
bitsadmin /list /allusers or bitsadmin /list /allusers /verbose > bitslog.txt
bitsadmin /info {guid}
删除bits job：
1.停止bits服务
2.删除 C:\ProgramData\Microsoft\Network\Downloader 下的文件

一般来说, SCCM 客户端代理不会出很大的问题 ,但有的时候也会出现程序列表加载不出来的情况.

这时候重装SCCM代理就可以解决问题

以下是我工作的记录：

CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=S01 FSP=SMSFSP01执行以下操作：

指定名为 SMSMP01 的管理点以请求用于下载客户端安装源文件的分发点列表。
指定在计算机已有 System Center 2012 Configuration Manager 的某个版本或 Configuration Manager 2007 客户端时停止安装。
指示 client.msi 将客户端分配到站点代码 S01。
指示 client.msi 使用名为SMSFP01 的回退状态点。

========SCCM LOGS========================================

C:\Windows\CCM\Logs

I found it's the execmgr.log file. It can be found in C:\Windows\SysWOW64\CCM\Logs (on my machine). See here for more info on SCCM log files

AppDiscovery.log	Detects installed Application Deployment Types and if deployed Deployment Types are not installed, this log file will show you why (only for the new style ConfigMgr Applications)
AppEnforce.log	will show you the actual command-line executed and the resulting exit code for each Deployment Type (only for the new style ConfigMgr Applications)
AppIntentEval.log	evaluates each Deployment Type’s dependencies and policies (only for the new style ConfigMgr Applications)
AssetAdvisor.log	inventories all installed software (not 100% sure)
CAS.log	Content access service, discovers DPs, download sources and maintains local cache
CCM32BitLauncher.log	logs all command-lines for executed packages (old style ConfigMgr)
CCMEval.log	depends on %windir%ccm\ccmeval.xml and checks the CCM client’s health
CCMEvalTask.log	checks if the CCMEval Task has run
CCMExec.log	monitors the client and CCMExec service
ClientIDManagerStartUp.log	creates and maintains the client’s GUID
ClientLocation.log	determines the assigned ConfigMgr site
CMRcService.log	ConfigMgr Remote Control Service
ContentTransferManager.log	controls BITS or SMB download of ConfigMgr packages
DataTransferService.log	monitors all package downloads
dism.log	monitors dism.exe process during OSD (e.g. driver injection)
EndpointProtectionAgent.log	System Center Endpoint Protection is now integrated into ConfigMgr 2012 and this is its log
ExecMgr.log	logs all deployed packages (old-style) and associated programs and policies
FileSystemFile.log	log for software inventory and file collection
InventoryAgent.log	logs DDRs (Discovery Data Records) for hardware and software
LocationServices.log	finds Management Points, Distribution Points, Software Update Points
MaintenanceCoordinator.log	is in control of all the ConfigMgr client’s maintenance tasks
mtrmgr.log	software metering
oobmgmt.log	Out of Band management, for internet-based clients
PolicyAgent.log	requests policies assigned to machine or user
PolicyAgentProvider.log	monitors any changes to policies
PolicyEvaluator.log	keeps track of new policies
pwrmgmt.log	monitors power management activities on the client
RebootCoordinator.log	collects information about reboots after software update installations
ScanAgent.log	scans the client for need of software updates
SCClient_%domain%@%user%1.log	Software Center Client for a specific domain and user, deployments will show up in here
Scheduler.log	records scheduled ConfigMgr tasks
SCNotify_%domain%@%user%1.log	Software Center Client for a specific domain and user, logs notifications regarding deployments
ServiceWindowManager.log	monitors existing service windows for the client in which for example software is allowed to be installed
smscliui.log	records usage of ConfigMgr UI in system panel
smssha.log	log file for Network Access Protection Agent
smsts.log	Task Sequence log
SoftwareCenterSystemTasks.log	logs Software Center’s process (startup, end)
StateMessage.log	sends software update states to MP
StatusAgent.log	logs events created by ConfigMgr Agent components
SWMTRReportGen.log	generates usage data report
TSAgent.log	logs the process before a TaskSequence starts up, e.g. download of policies
UpdatesDeployment.log	shows information regarding Software Updates, if for example updates are enforced or assigned
UserAffinity.log	new model of “User Device Affinity” (UDA), checks if there is an existing UDA for the machine or creates/sends a new UDA to the MP

=======================================================================================================================================================

转载于:https://blog.51cto.com/ericfu/1893123