At Microsoft Lync, we’re focused on delivering the best productivity experience across devices. Today, I’m excited to introduce new Lync mobile clients for Windows Phone, iPhone, iPad, Android, and Nokia Symbian mobile devices. With Lync mobile clients we enable you to stay connected, communicate and conference on the go.

Lync mobile clients are provided at no additional costs to subscribers of Lync Online and Office 365. They are enabled by an update to Lync Server 2010, which is now available to Lync Online and Office365 subscribers.

Lync 2010 for Windows Phone is available today on the Windows Phone marketplace. Lync mobile clients for other platforms have been submitted to their respective mobile application marketplace and should be available soon.

Check out this blog for more information. And to learn how to enable mobility for vanity domains, please see this article.

Brian is the Microsoft Lync Product Manager for Mobility & Emerging Clients and Office365.

http://community.office365.com/en-us/b/office_365_technical_blog/archive/2011/12/12/lync-mobile-clients.aspx

​​

Join conferences with a single touch; no access code or pin number required.

Stay connected, while controlling your availability; see who’s available at a glance and connect over IM, email or a call; set your own status and notification settings so you can stay in touch while protecting your “off-work” time.

Communicate with others using a single, consistent identity.Call-via-work¹ allows outbound calls using your Enterprise Voice number, making it easier for others to recognize calls from the Lync mobile client.

Connect with confidence through channel encryption, transport layer security (TLS) support, and perimeter/internal network protection that help safeguard your communications.

http://lync.microsoft.com/en-us/Product/UserInterfaces/Pages/lync-2010-mobile.aspx

http://technet.microsoft.com/en-us/library/hh691004.aspx

System Center Operations Manager 2012: Infrastructure and Application Performance Monitoring

http://go.microsoft.com/?linkid=9792430

System Center Virtual Machine Manager 2012: Building Your Cloud Infrastructure

http://go.microsoft.com/?linkid=9792431

System Center Virtual Machine Manager 2012: Building a Service Template

http://go.microsoft.com/?linkid=9792432

Introduction to System Center Configuration Manager 2012

http://go.microsoft.com/?linkid=9789981

https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032497154&Culture=en-GB

System Center Operations Manager 2012 provides deep application diagnostics and infrastructure monitoring that can help you ensure the predictable performance and availability of vital applications and offers a comprehensive view of your datacenter, private, and public clouds.

Overview

Operations Manager 2012 provides infrastructure monitoring that’s flexible and cost-effective, helps ensure the predictable performance and availability of vital applications, and offers comprehensive monitoring for your datacenter and cloud, both private and public. Operations Manager helps you better manage your datacenters by:

• Delivering flexible and cost effective enterprise-class monitoring and diagnostics while reducing the total cost of ownership by leveraging commodity hardware, configurations, and heterogeneous environments.
• Helping to ensure the availability of business-critical applications and services through market-leading .NET application performance monitoring and diagnostics and JEE application health monitoring.
• Providing a comprehensive view of datacenters, and private and public clouds.

Feature Summary 

• Setup

Operations Manager 2012 has a new Setup wizard. For important instructions about how to install Operations Manager 2012, see Install Operations Manager 2012 Beta.
• Highly Available Management Group Out of the Box

In Operations Manager 2012, all management servers are peers; there is no root management server. The workload is split among all management servers in a management group, which provides high availability without requiring a cluster.
• Resource pools

A resource pool provides the ability to distribute workloads across multiple management servers, such as availability, network device monitoring, distributed monitor health rollup, and group calculation.
• Agent Configuration

Operations Manager 2012 provides an easy method for configuring agents to report to multiple management servers by adding an Operations Manager Agent application to Control Panel on each agent-managed computer.
• Operations Console

You will notice some subtle changes to the Operations console. The

Actions

 pane is now the

Tasks

 pane, and includes a new section called

Navigation Tasks

 that makes it easy for you to open views for a selected object. The

Tasks

 pane offers two tabs: one for actions and one for resources and Help links. The

Navigation

 and

Tasks

 panes can be hidden or revealed instantly by clicking the arrow in the title bar of the pane.
• Web console

Operations Manager 2012 introduces a new Web console. In Operations Manager 2012, all Operations Manager views are available in the Web console.
• Network monitoring

Operations Manager 2012 provides the ability to discover and monitor network routers and switches, including the network interfaces and ports on those devices and the virtual LAN (VLAN) that they participate in. You can also delete discovered network devices and prevent the deleted network devices from being rediscovered the next time discovery runs. For more information, see Monitor Network Devices.
• Application monitoring

In Operations Manager 2012, you can monitor ASP.NET applications in server- and client-side environments to get details about application availability and performance. Configure monitoring settings, such as polling frequency and transaction threshold. Then use results, including how frequently a problem is occurring, how a server was performing when a problem occurred, and the distributed chain for a transaction in question to pinpoint problems and solutions. For more information, see Monitor a .NET Application.
• Dashboard views

As part of the network monitoring and application monitoring capabilities, Operations Manager 2012 includes new comprehensive dashboard views that combine multiple panels of information into a single view. In Operations Manager 2012, you can add the new dashboard views to My Workspace.
• Display dashboard views using SharePoint

The Operations Manager web part displays specified dashboard views and can be added to Microsoft SharePoint 2010 sites. For more information, see Add a Dashboard View to a SharePoint Site.
• Creating dashboard views

Dashboard views have been significantly upgraded in Operations Manager 2012 from their capabilities in Operations Manager 2007 R2, including custom layouts and nested dashboard views. For more information, see Create a Dashboard View.
• Operations Manager Module for Windows PowerShell

Operations Manager 2012 provides a Windows PowerShell 2.0 module containing a full set of new cmdlets. The cmdlets in this module are only compatible with Operations Manager 2012. You can recognize the Operations Manager 2012 cmdlets by the “SC” preceding the noun. For additional information about the Operations Manager 2012 cmdlets, open the Operations Manager command shell and type

Get-Help about_OpsMgr_WhatsNew

. For information about how the Operations Manager 2007 cmdlets map to the Operations Manager 2012 cmdlets, type

Get-Help about_OpsMgr_Cmdlet_Names

.To use the Operations Manager 2012 cmdlets, you must establish a connection to an Operations Manager management group. You can establish either a persistent connection in which you can run multiple cmdlets, or a temporary connection when running a single cmdlet. For more information about connections, open the Operations Manager Shell and type

Get-Help about_OpsMgr_Connections

.
• UNIX- and Linux-based computers

In Operations Manager 2012, the Discovery Wizard is easier to use for discovering UNIX- and Linux-based computers. You can now use Windows PowerShell to manage UNIX- and Linux-based computers, for more information, see the

UNIX and Linux

section in the release notes. High availability is also supported.

UNIX/Linux Shell Command Template Management Pack
This Management Pack implements authoring templates that allow the creation of rules, tasks, and monitors based on execution of shell commands on UNIX/Linux agents.

JEE Management Packs
These management packs monitor JEE (Java Enterprise Edition) application servers. Management packs are available for IBM WebSphere, Oracle WebLogic, Red Hat JBoss and Apache Tomcat.

Top of page

System requirements

Supported Operating Systems: Windows Server 2008 R2

• Any server role
• .NET 3.5 or 4.0
• Management Server, Reporting Server, Web Console, Gateway Server
• Windows Server 2008 R2 (64 bit)
• Operational & Data Warehouse
• SQL 2008 SP1 and above
• SQL Collation – SQL_Latin1_General_CP1_CI_AS
• Agent
• Windows Server 2003 SP2 and above
• Windows Server 2008 SP2 and above
• Windows Server 2008 R2
• Windows XP Professional SP3 and above
• Windows Vista SP2 and above
• Windows 7

Microsoft Security Compliance Manager 2 (SCM 2) is a free tool from the Microsoft Solution Accelerators team that enables you to quickly configure and manage your computers, traditional datacenter, and private cloud using Group Policy and Microsoft® System Center Configuration Manager.

SCM 2 provides ready to deploy policies and DCM configuration packs that are tested and fully supported. These baselines are based on Microsoft Security Guide recommendations and industry best practices, allowing you to manage configuration drift, address compliance requirements, and reduce security threats.

Easily configure the latest Windows® operating systems, Microsoft Office applications, and Internet Explorer with industry leading knowledge and fully supported tools.

Take advantage of SCM 2 to import the configuration of a “golden master” reference machine or existing Group Policy. Compare your standards to industry best practices, customize them using rich knowledge, and seamlessly create new policies and DCM configuration packs in the user-friendly UI designed to work with Microsoft System Center Configuration Manager 2007 R2.

Key Features Include:

• Gold master support: Import and take advantage of your existing Group Policy or create a snapshot of a reference machine to kick-start your project!
• Configure stand-alone machines: Deploy your configurations to non-domain joined computers using the new GPO Pack feature!
• Updated security guides: Take advantage of the deep security expertise and best practices in the updated security guides, and the attack surface reference workbooks to help reduce the security risks that you consider to be the most important!
• Compare against industry best practices: Analyze your configurations against prebuilt baselines for the latest Windows client and server operating systems!

The latest version of the Microsoft Assessment and Planning (MAP) Toolkit—version 6.5—is now available for beta download. The MAP toolkit is an agentless inventory, assessment, and reporting tool that can securely assess IT environments for various platform migrations—including Windows 7, Windows Server 2008 R2, Hyper-V, Windows Azure, and Hyper-V Cloud Fast Track.

Key Features and Benefits of MAP 6.5 beta

Discover Oracle instances on Itanium-based servers for migration to SQL Server.

MAP 6.5 Beta adds to the heterogeneous database inventory and reporting capability with Oracle compete and the discovery of Oracle instances on Itanium-based servers with HP-UX to assist in the planning of migration to SQL Server. Reporting also provides an estimate of the complexity of migration and suggests candidates for migration to SQL Server. Use this information to determine total cost of ownership for maintaining Oracle and the potential return on investment (ROI) from switching to SQL Server.

Accelerate planning for the private cloud with Hyper-V Cloud Fast Track Onboarding.

Planning your private cloud just got easier. Hyper-V Cloud Fast Track Onboarding, an updated assessment available with MAP 6.5 Beta, provides consolidation guidance and validated configurations with preconfigured Hyper-V Fast Track Infrastructures including computing power, network, and storage architectures. Get a quick analysis of server consolidation on Hyper-V Cloud Fast Track Infrastructures to help accelerate your planning of P2V migration to Hyper-V Cloud Fast Track. Each assessment also provides guidance on next steps using Hyper-V Cloud Fast Track.

Assess your software usage and evaluate your licensing needs. NEW!

The Software Usage Tracking feature in MAP 6.5 includes enhancements in terms of product coverage and the ability to track devices. The Forefront Endpoint Protection (FEP) scenario measures server and client usage for the FEP product, a recent addition to the Microsoft Core Client Access License (CAL) Suite. Active Devices is a new inventory scenario that allows organizations to report Windows devices that are active on the network. This information is useful in Enterprise Agreement scenarios as well as for maintaining Active Directory information for the environment.

http://connect.microsoft.com/site297

The SCCM server log files are located in the\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.