Friday, May 19, 2017

Clustering - Looks alive & IS alive

Looks Alive Check:
This check performs a basic verification that the SQL Server service is running on the hosted node which should be online on a given interval of time. The default time that has been set is 5 seconds.
In case the check fails, the cluster service performs another check which is very thororugh in nature called the IsAlive Check to verify the failure. The LooksAlive check is also known as Basic resource health check in Windows Server 2008.
Is Alive check:
This process checks and verifies the cached result of the internal IsAlive process in the SQL Server resource DLL. The internal IsAlive process runs every 60 seconds and verifies if SQL server is online or not. The check uses SELECT @@SERVERNAME to verify the state of the SQL Server.
In case that the query fails, it runs an additional retry login to avoid failures. On the event of retry logic failure, the internal IsAlive process shuts down the SQL server service and a failover event is triggered. The IsAlive check is also known as the Thorough resource health check in Windows Server 2008.

Saturday, May 13, 2017

WannaCry Ransomware Attack Hits Victims With Microsoft SMB/CIFS Exploit

Ransomware is no longer just a nuisance. Now it's quite literally a matter of life and death. A massive ransomware attack being labeled as "WannaCry" has been reported around the world and is responsible for shutting down hospitals in the United Kingdom and encrypting files at Spanish telecom firm Telefonica.
The WannaCry attack is not a zero-day flaw, but rather is based on an exploit that Microsoft patched with its MS17-010 advisory on March 14 in the SMB Server. However, Microsoft did not highlight the SMB flaw until April 14, when a hacker group known as the Shadow Brokers released a set of exploits, allegedly stolen from the U.S. National Security Agency.
SMB, or Server Message Block, is a critical protocol used by Windows to enable file and folder sharing. It's also the protocol that today's WannaCry attack is exploiting to rapidly spread from one host to the next around the world, literally at the speed of light. The attack is what is known as a worm, "slithering" from one host to the next on connected networks.
Among the first large organizations to be impacted by WannaCry is The National Health Service in the UK, which has publicly confirmed that it was attacked by the Wanna Decryptor.

"This attack was not specifically targeted at the NHS and is affecting organisations from across a range of sectors," the NHS stated. "At this stage we do not have any evidence that patient data has been accessed."
Security firm Kaspersky Lab reported that by 2:30 p.m. ET May 12 it had already seen more than 45,000 WannaCry attacks in 74 countries. While the ransomware attack is making use of the SMB vulnerability to spread, the encryption of files is done by the Wanna Decryptor attack that seeks out all files on a victim's network. Once the ransomware has completed encrypting files, victims are presented with a screen demanding a ransom. Initially, the ransom requested was reported to be $300 worth of Bitcoin, according to Kaspersky Lab.
"Many of your documents, photos, videos, databases and other files are no longer accessible because they have been encrypted," the ransom note states. "Maybe you are busy looking for a way to recover your files, but do not waste your time. Nobody can recover your files without our decryption service."
It's not clear who the original source of the global WannaCry attacks is at this point, or even if it's a single threat actor or multiple actors. What is clear is that despite the fact that a software patch has been available since March for the SMB flaws, WannaCry is using tens of thousands of organizations that didn't patch.
Aside from patching and keeping systems up to date, having backups is always an essential element of good computer hygiene, which can help minimize the risk of ransomware as well.
Ransomware has been a growing problem over the course of the last year, according to multiple industry reports. The 2017 Verizon Data Breach Investigation Report (DBIR) found a 50 percent increase in ransomware over the 2016 report, while Symantec reported in its Internet Security Threat Report (ISTR) that the average ransomware payout increased from $294 in 2015 up to $1,077 in 2016.

Who is impacted?

A number of organizations globally have been affected, the majority of which are in Europe.

Is this a targeted attack?

No, this is not believed to be a targeted attack at this time. Ransomware campaigns are typically indiscriminate.

Why is it causing so many problems for organizations?

WannaCry has the ability to spread itself within corporate networks, without user interaction, by exploiting a known vulnerability in Microsoft Windows. Computers which do not have the latest Windows security updates applied are at risk of infection.

Can I recover the encrypted files?

Decryption is not available at this time but Symantec is investigating. Symantec does not recommend paying the ransom. Encrypted files should be restored from back-ups where possible.

What are best practices for protecting against ransomware?

  • New ransomware variants appear on a regular basis. Always keep your security software up to date to protect yourself against them.
  • Keep your operating system and other software updated. Software updates will frequently include patches for newly discovered security vulnerabilities that could be exploited by ransomware attackers.
  • Email is one of the main infection methods. Be wary of unexpected emails especially if they contain links and/or attachments.
  • Be extremely wary of any Microsoft Office email attachment that advises you to enable macros to view its content. Unless you are absolutely sure that this is a genuine email from a trusted source, do not enable macros and instead immediately delete the email.
  • Backing up important data is the single most effective way of combating ransomware infection. Attackers have leverage over their victims by encrypting valuable files and leaving them inaccessible. If the victim has backup copies, they can restore their files once the infection has been cleaned up. However organizations should ensure that back-ups are appropriately protected or stored off-line so that attackers can’t delete them.
  • Using cloud services could help mitigate ransomware infection, since many retain previous versions of files, allowing you to “roll back” to the unencrypted form.
source :




How to disable CIFS/SMB port 445 on Windows 7 64 bit
So, I had a requirement of disabling the port 445 on a Win 7 64 bit machine. The first thing which we do is to 'google' to find out a solution and I did the same. I found some results and they looked convincing. I tried the first method which was something like:
  • Open registry editor
  • Go to 'HKLM\System\CurrentControlSet\ Services\NetBT\Parameters' key
  • Go to option called TransportBindName (on the right hand side)
  • Empty the value so that Data (value) of 'TransportBindName' is empty. Close Registry Editor.
  • Reboot the PC
  • And you are done

















































 it was so simple I thought and followed the procedure. To my irritation, this didn't work. no problem,

there was another method on some other website:
  • As again, this requires opening the registry editor
  • Go to 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters' key
  • Create a 'REG_DWORD' Entry with the name SMBDeviceEnabled and give it's value 0
  • Close Registry Editor
  • Reboot the PC










it
























also seemed simple. I followed the procedures and waited till the PC rebooted. And again to my greater irritation, it didn't work.

I went on googling and almost experimented all the things I found - none of them worked for me. It took almost one full day :(

Then I started experimenting on my own, and luckily to my great satisfaction, I found it. Here is what worked for me:

  • Open Services by typing services.msc in Run dialog box.
  • Locate the service named 'Server'. The description field for this should be saying something like 'Supports file, print, and named-pipe sharing over the network for this computer. If this service is stopped, these functions will be unavailable. If this service is disabled, any services that explicitly depend on it will fail to start. '
  • Double click on that service
  • Click on the button 'Stop' to stop it.
  • In the Startup Type combo choose 'Disabled' so that on the next boot, this service will not start running. Apply your changes by clicking on Ok.
  • Now locate another service named 'TCP/IP NetBIOS Helper'. The description should read something like 'Enables support for NetBIOS over TCP/IP (NetBT) service and NetBIOS name resolution.'.
  • Do the same with this service - stop it and disable it.
  • Restart the computer
There can be slight variation in names/description as while writing this blog post, I was on a XP machine.

Disclaimer: By reading the descriptions of the services you disabled, you should have a hint that your file sharing and other things will not work on the next reboot.

You can always go to Services again and set the services as 'Automatic' to enable them on the next reboot.

if it also works for you, kindly come back and leave a note of appreciation.

Thursday, May 11, 2017

What are the SCCM 2007 Site System roles?



SCCM 2007 supports the following 14 Site System roles, with those prefixed with [NEW]being new to SCCM:
·         Site Server - The server on which you install the SCCM software.
·         Site Database Server - The server running SQL and hosting the SCCM Site Database (only required for Primary Sites)
·         Configuration Manager Console - The interface for administering SCCM. Installed by default on Primary Site Servers this role can also be installed on workstations to allow remote administration.
·         SMS Provider - The intermediate Windows Management Instrumentation (WMI), layer that sits between the Configuration Manager Console and the Site Database (the Configuration Manager Console accesses the Site Database via the SMS Provider). Only required for Primary Sites.
·         Component Server - All SCCM Site System roles (except for the Distribution Point (DP)), requires SCCM-specific software to be installed in order for the Site System role to function.  When such software is installed on a computer that computer becomes a Component Server.
·         Distribution Point (DP) - Stores SCCM Packages from where Clients can access them to install them.  Only required for the Software Distribution, Software Updates, and Advertised Task Sequences functions of SCCM.
·         [NEW] Fallback Status Point - A “catch all” Site System for Clients that cannot be installed because of various issues such as assignment, or their inability to communicate with their Management Point (MP).  Not required by default, but recommended to help with Client installation issues.
·         Management Point (MP) - SCCM Clients do not communicate directly with the SCCM Site Server and vice versa.  Instead all communication is facilitated via the Management Point.  A Default Management Point needs to be defined in every Site that has Intranet Clients.
·         [NEW] Pre-boot Execution Environment (PXE) Service Point - The Site System that responds to any computers requesting deployment of their Operating System (OS), via a PXE request.  Only required if Operating System Deployments (OSD), are going to take place using PXE boot requests.
·         Reporting Point (RP) - Hosts the Report Viewer component that provides the web-based reporting functionality of SCCM. Only required if Reports need to be run on a particular Primary Site.
·         Server Locator Point (SLP) -  Responsible for informing SCCM Clients which MP they should access in order to install the SCCM Client software. Only required in some Client Deployment scenarios.
·         [NEW] Software Update Point (SUP) - Assigned to the computer running Windows Server Update Services (WSUS).  Only required if the Software Updates feature is going to be used.
·         [NEW] State Migration Point (SMP) - Stores the user’s state migration data when a computer’s OS is migrated.  Only required if the OSD feature is going to be used.
·         [NEW] System Health Validator Point (SHVP) - This role is assigned to the computer running the Network Policy Service.  Only required if the Network Access Protection (NAP) feature is going to be used.

SCCM Logs and Troubleshooting


The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS).

The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder.

IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.



You can use Trace32.exe found in the 
Sccm2007 Toolkit, to interpret the logs easily (errors in Red, warnings in Yellow).

Posted Image





Client Log Files

* CAS - Content Access Service. Maintains the local package cache.
* Ccmexec.log - Records activities of the client and the SMS Agent Host service.
* CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.
* ClientIDManagerStartup.log - Creates and maintains the client GUID.
* ClientLocation.log - Site assignment tasks.
* ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
* DataTransferService.log - Records all BITS communication for policy or package access.
* Execmgr.log - Records advertisements that run.
* FileBITS.log - Records all SMB package access tasks.
* Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.
* InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.
* LocationServices.log - Finds management points and distribution points.
* Mifprovider.log - The WMI provider for .MIF files.
* Mtrmgr.log - Monitors all software metering processes.
* PolicyAgent.log - Requests policies by using the Data Transfer service.
* PolicyAgentProvider.log - Records policy changes.
* PolicyEvaluator.log - Records new policy settings.
* Remctrl.log - Logs when the remote control component (WUSER32) starts.
* Scheduler.log - Records schedule tasks for all client operations.
* Smscliui.log - Records usage of the Systems Management tool in Control Panel.
* StatusAgent.log - Logs status messages that are created by the client components.
* SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

* Ccm.log - Client Configuration Manager tasks.
* Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
* Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
* Compsumm.log - Records Component Status Summarizer tasks.
* Cscnfsvc.log - Records Courier Sender confirmation service tasks.
* Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
* Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
* Despool.log - Records incoming site-to-site communication transfers.
* Distmgr.log - Records package creation, compression, delta replication, and information updates.
* Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.
* Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
* Inboxmgr.log - Records file maintenance.
* Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.
* Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
* Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.
* MPMSI.log - Management point .msi installation log.
* MPSetup.log - Records the management point installation wrapper process.
* Ntsvrdis.log - Configuration Manager 2007 server discovery.
* Offermgr.log - Records advertisement updates.
* Offersum.log - Records summarization of advertisement status messages.
* Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.
* Replmgr.log - Records the replication of files between the site server components and the Scheduler component.
* Rsetup.log - Reporting point setup log.
* Sched.log - Records site-to-site job and package replication.
* Sender.log - Records files that are sent to other child and parent sites.
* Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.
* Sitecomp.log - Records maintenance of the installed site components.
* Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
* Sitestat.log - Records the monitoring process of all site systems.
* Smsdbmon.log - Records database changes.
* Smsexec.log - Records processing of all site server component threads.
* Smsprov.log - Records WMI provider access to the site database.
* SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
* SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.
* Srvacct.log - Records the maintenance of accounts when the site uses standard security.
* Statmgr.log - Writes all status messages to the database.
* Swmproc.log - Processes metering files and maintains settings.


Admin Console Log Files


* RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.
* ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.
* SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

* MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the site server.
* MP_GetAuth.log - Records the status of the site management points.
* MP_GetPolicy.log - Records policy information.
* MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the site server.
* MP_Location.log - Records location manager tasks.
* MP_Policy.log - Records policy communication.
* MP_Relay.log - Copies files that are collected from the client.
* MP_Retry.log - Records the hardware inventory retry processes.
* MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the site server.
* MP_Status.log - Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files
* DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
* DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.
* DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.
* DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.
* DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.
* DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.
* DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.
* dmpMSI.log - Records the MSI data for Device Management Point setup.
* DMPSetup.log - Records the mobile device management setup process.
* DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.
* DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.
* FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

* DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
* DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
* DmClientSetup.log - Records client setup data on mobile device clients.
* DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
* DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.
* DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
* DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
* DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

* CCMSetup.log - Provides information about client-based operating system actions.
* CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
* DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.
* MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
* MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
* MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
* Pxecontrol.log - Provides information about the PXE Control Manager.
* PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
* PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
* Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
* SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.
* Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.
* SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
* Smsprov.log - Provides information about the SMS provider.
* Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
* SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
* Smsts.log - General location for all operating system deployment and task sequence log events.
* TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.
* USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
* USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

* Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
* CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.
* locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
* SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
* SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

* Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
* SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
* SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
* SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
* SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.
* SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

* ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.
* dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
* discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.
* sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.
* sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

* Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
* WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.


Software Updates Site Server Log Files


* ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.
* distmgr.log - Provides information about the replication of software update deployment packages.
* objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.
* PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
* replmgr.log - Provides information about the process for replicating files between sites.
* smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
* SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
* WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
* WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
* wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

* Change.log - Provides information about the WSUS server database information that has changed.
* SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

* CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.
* CIAgent.log - Provides information about processing configuration items, including software updates.
* LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.
* PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
* PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.
* PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.
* RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.
* ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
* ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
* SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
* ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.
* smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
* SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
* StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.
* UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
* UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.
* UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
* WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.
* WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.


Windows Update Agent Log File

* WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components. 

Software Distribution Troubleshooting Flowcharts


The following flowchart shows the process for Microsoft System Center Configuration Manager 2007 package creation and distribution.

flowchart: software distribution package creation

SCCM troubleshooting log files


Site Server logs:

ciamgr.log: Provides information about the addition, deletion, and modification of software update configuration items.

distmgr.log : Provides information about the replication of software update deployment packages.

objreplmgr.log : Provides information about the replication of software updates notification files from a parent to child sites.

PatchDownloader.log : Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.

replmgr.log : Provides information about the process for replicating files between sites.

smsdbmon.log : Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.

SUPSetup : Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.

WCM.log : Provides information about the software update point configuration and connecting to the WSUS server for subscribed update categories, classifications, and languages.

WSUSCtrl.log : Provides information about the configuration, database connectivity, and health of the WSUS server for the site.

wsyncmgr.log : Provides information about the software updates synchronization process.

WSUS Server Log Files

Change.log: Provides information about the WSUS server database information that has changed.

SoftwareDistribution.log : Provides information about the software updates that are synchronized

Client Computer Log Files

CAS.log: Provides information about the process of downloading software updates to the local cache and cache management.

CIAgent.log:Provides information about processing configuration items, including software updates.

LocationServices.log: Provides information about the location of the WSUS server when a scan is initiated on the client.

PatchDownloader.log:Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

PolicyAgent.log: Provides information about the process for downloading, compiling, and deleting policies on client computers.

PolicyEvaluator:Provides information about the process for evaluating policies on client computers, including policies from software updates.

RebootCoordinator.log:Provides information about the process for coordinating system restarts on client computers after software update installations.

ScanAgent.log: Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.

ScanWrapper.log:Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.


SCCM Logs


The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS).
The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder. IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.

Client Log Files

  • CAS - Content Access Service. Maintains the local package cache.
  • Ccmexec.log - Records activities of the client and the SMS Agent Host service.
  • CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.
  • ClientIDManagerStartup.log - Creates and maintains the client GUID.
  • ClientLocation.log - Site assignment tasks.
  • ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
  • DataTransferService.log - Records all BITS communication for policy or package access.
  • Execmgr.log - Records advertisements that run.
  • FileBITS.log - Records all SMB package access tasks.
  • Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.
  • InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.
  • LocationServices.log - Finds management points and distribution points.
  • Mifprovider.log - The WMI provider for .MIF files.
  • Mtrmgr.log - Monitors all software metering processes.
  • PolicyAgent.log - Requests policies by using the Data Transfer service.
  • PolicyAgentProvider.log - Records policy changes.
  • PolicyEvaluator.log - Records new policy settings.
  • Remctrl.log - Logs when the remote control component (WUSER32) starts.
  • Scheduler.log - Records schedule tasks for all client operations.
  • Smscliui.log - Records usage of the Systems Management tool in Control Panel.
  • StatusAgent.log - Logs status messages that are created by the client components.
  • SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

  • Ccm.log - Client Configuration Manager tasks.
  • Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
  • Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
  • Compsumm.log - Records Component Status Summarizer tasks.
  • Cscnfsvc.log - Records Courier Sender confirmation service tasks.
  • Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
  • Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
  • Despool.log - Records incoming site-to-site communication transfers.
  • Distmgr.log - Records package creation, compression, delta replication, and information updates.
  • Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.
  • Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
  • Inboxmgr.log - Records file maintenance.
  • Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.
  • Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
  • Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.
  • MPMSI.log - Management point .msi installation log.
  • MPSetup.log - Records the management point installation wrapper process.
  • Ntsvrdis.log - Configuration Manager 2007 server discovery.
  • Offermgr.log - Records advertisement updates.
  • Offersum.log - Records summarization of advertisement status messages.
  • Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.
  • Replmgr.log - Records the replication of files between the site server components and the Scheduler component.
  • Rsetup.log - Reporting point setup log.
  • Sched.log - Records site-to-site job and package replication.
  • Sender.log - Records files that are sent to other child and parent sites.
  • Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.
  • Sitecomp.log - Records maintenance of the installed site components.
  • Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
  • Sitestat.log - Records the monitoring process of all site systems.
  • Smsdbmon.log - Records database changes.
  • Smsexec.log - Records processing of all site server component threads.
  • Smsprov.log - Records WMI provider access to the site database.
  • SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
  • SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.
  • Srvacct.log - Records the maintenance of accounts when the site uses standard security.
  • Statmgr.log - Writes all status messages to the database.
  • Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

  • RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.
  • ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.
  • SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

  • MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the site server.
  • MP_GetAuth.log - Records the status of the site management points.
  • MP_GetPolicy.log - Records policy information.
  • MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the site server.
  • MP_Location.log - Records location manager tasks.
  • MP_Policy.log - Records policy communication.
  • MP_Relay.log - Copies files that are collected from the client.
  • MP_Retry.log - Records the hardware inventory retry processes.
  • MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the site server.
  • MP_Status.log - Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files

  • DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
  • DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.
  • DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.
  • DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.
  • DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.
  • DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.
  • DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.
  • dmpMSI.log - Records the MSI data for Device Management Point setup.
  • DMPSetup.log - Records the mobile device management setup process.
  • DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.
  • DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.
  • FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

  • DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
  • DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
  • DmClientSetup.log - Records client setup data on mobile device clients.
  • DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
  • DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.
  • DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
  • DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
  • DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

  • CCMSetup.log - Provides information about client-based operating system actions.
  • CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
  • DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.
  • MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
  • MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
  • MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
  • Pxecontrol.log - Provides information about the PXE Control Manager.
  • PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
  • PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
  • Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
  • SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.
  • Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.
  • SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
  • Smsprov.log - Provides information about the SMS provider.
  • Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
  • SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
  • Smsts.log - General location for all operating system deployment and task sequence log events.
  • TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.
  • USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
  • USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

  • Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
  • CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.
  • locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
  • SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
  • SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

  • Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
  • SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
  • SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
  • SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
  • SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.
  • SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

  • ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.
  • dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
  • discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.
  • sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.
  • sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

  • Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
  • WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

  • ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.
  • distmgr.log - Provides information about the replication of software update deployment packages.
  • objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.
  • PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
  • replmgr.log - Provides information about the process for replicating files between sites.
  • smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
  • SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
  • WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
  • WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
  • wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

  • Change.log - Provides information about the WSUS server database information that has changed.
  • SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

  • CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.
  • CIAgent.log - Provides information about processing configuration items, including software updates.
  • LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.
  • PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
  • PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.
  • PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.
  • RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.
  • ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
  • ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
  • SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
  • ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.
  • smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
  • SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
  • StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.
  • UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
  • UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.
  • UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
  • WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.
  • WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File


  • WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.