High level of Tech Talk :- Take this Print

Communication errors between Site’s
SQL Server Errors

For Every Term you need to get a log file Name, Glossary should learn it

Site Server issues :-

1. Not able to connect to the Console
2. Site is not sending status messages, the procedure to confirm and the default report
3. Site Server Slow or CPU High Utilization
4. backlogs finding
5. Backlogs Story…
6. MY Script to check the Backlogs
7. Database errors related to Site Server and SQL
8. Importance of SMS Provider
9. Collections are not appearing in the hierarchy log file
10. Some of IMP Log Files
11. Status messages not for set to clear you must understand what happens when we set to clear and act to the situation
12. SMS 2003 Troubleshooting Workflow
13. News / MYITForum Group Importance
14. Backup of Sites
15. Uninstallation of Sites
16. Planning of Sites “”Configuration Manager Preplanning Worksheets””
17. Primary Site
18. Secondary Site
19. Just the DP
20. Boundaries
21. Boundary Overlapping
22. FSP and it’s history why we need FSP?
23. Site to Site key exchange
24. Possibility of NLBs and for MP and WSUS
    
25. OSD Coverage and steps
26. lets try MDT also
27. If possible Lets try Native Mode also

Client Issues:-

1. Client Installation Methods
2. Software Update point Based Client installation
3. Disadvantages of Client Push
4. Client installation Log files

Client Installation Troubleshooting:-

1. WMI Connectivity check
2. WMI Rebuild
3. WMI Log Files
4. MOF FILES RELATED TO WMI
5. Drive Space issues, FS.exe
6. Permissions, admin$, 64 bit ccm folder location & 32 bit control panel
7. Not found MP
8. not detecting the site code
9. client not assigning to site code and trying to install\
10. possible of command line option of ccmsetup.exe
11. ccmclean.exe
12. IMP log Files related to Client
13. patching related log file and issue
14. patching is failing to install
15. is sms/sccm client is manacle of things to automate?
16. Trace32.exe
17. Client Status Reports
18. SMS Client Health Monitor
19. Some of the “”State Messages in Configuration Manager 2007”

 

• MP Troubleshooting
• Reporting Point Troubleshooting
• Secondary Site Installation
• Ports Document
• patching the Systems
• Workstation Patching style and server patching status
• maintenance window
• SCCM R2 Advantages
• SCCM Features comparison with SMS

 

Inventory:-

Software inventory
Hardware inventory
SMS_def.mof File and tool from MYITFORM for registry key
mof compile
no idmif
idmif

 

 

Log files for Communication

1. Component Configuration Manager Troubleshooting
2. ADMINUI.log file
3. Delegation of Configuration / SMS Console
4. Status messages

Package Distribution Issues

1. Procedure to Confirm the Package  is reached to the DP And  Log File
2. Procedure to Package Source Version and Current Version finding
3. What is refresh and Update package and resend to DP?
4. How to Distribute the Packages to Multiple DPs? DP Groups?
5. IMP Log Files related to Distribution:- Sender and Scheduler and Distmgr.log
6. Compressed files like .Pck story
7. What is the Compressed Package?
8. What is Binary replication in Distribution?
9. What is the Package Creation Flow, I mean what kind of files gets changed in the work flow, like Dispooler and etc…
10. Importance of BITS on DP
11. Distribution points Related reports to the DP and Database Tables
12. Troublshooting steps for a Package is not reaching DP
13. Download package and run from DP
14. Virtual Applications and relationship with DP
15. In the Event of Distribution Point OS Failed how to proceed further to get it corrected?
16. Document from my blog DP in and Outs

Distribution Point Family and its Terms:-

 

1. Understanding of Advertisement?
2. Standard DP
3. Protected DP
4. Branch Distribution Point
5. peer DP
6. Nomad DP
7. Check in IE
8. More than 700 do we need another DP?
9. DFS and DP ?
10. File Server and DP ?
11. For each above Log files

Advertisement:-

1. Working style of Advertisement..
2. When we advertise the Command line Options that we can see…. for executing style
3. Default report that we can check for advertisement
4. Log files for advertisement
5. From console view of Advertisement status
6. If Advertisement failed how to make sure it to run again
7. Suppressing the Advertisement
8. how to use toolkit to see advertisement history
9. related information in control panel for advertisement
10. maintenance of Cache folder
11. If report is not showing more than 10000 rows for any advertisement
12. Advertisement to advertise Users and User groups
13. Advertisement interaction with user
14. Advertisement running with the administrator privileges and Logged in user account rights
15. Administrator Flow for Advertisement
16. advertisement to be appear in the add and remove programs

 

Other Topics

WOL in and Outs from my blog document

MP Issues

DP Issues

Preinst.exe

How to find the What deployment that are using… currentsly for this month

notification for Technet patching

PXE Issues and ports and fast port and iphelper

Wake on LAN ports and difference and unicast and subnet broad cast

Schema Extention two methods

Software Updates desgin and flow for how to create and deploy with the reports and log files

Small talk on OBT

SCCM Client Installation Batch Script

Psexec tool

psexplorer

Collections Database Table

Right Click Tools

System Center Clint Center

SCCM R3

Configuration Manager Preplanning Worksheets

Finally Glossary

IP Sec

Isolation of Domains

VLans

wdsutil

Multicasting

WOL:: Wake ON LAN :: Ins and Outs

With Wake On LAN feature, Configuration Manager 2007 activities can be scheduled to take place outside business hours.

1.                 Wake On LAN (WOL) benefits:

·         Achieve a higher success rate for Configuration Manager Activities.

·         Reduces the associated network traffic during business hours.

·         Conserve power by not requiring computers to be left on outside business hours.

 

2.                 Wake On LAN can be used on the following scenarios:

·         Software updates deployment with deadline:

Configuration manager 2007 Send a wake-up transmission prior to the configured deadline for a software update deployment

Wake-up packets are sent only to computers that require the software updates and have not already installed them.

·         Mandatory advertisement for software distribution or task sequence:

Configuration manager 2007 Send a wake-up transmission prior to the configured schedule of a mandatory advertisement, which can be for software distribution or a task sequence.

 

3.                 Walk On LAN overview:

·         Wake-up packet transmissions are sent only from primary site servers only.

·         The default port used by Configuration Manager 2007 to send wake-up packets to target computers is UDP port 9 and can be changed form site settings

·         Secondary site servers or other computers cannot be configured as proxies to send wake-up packets.

·         Wake-up transmissions are not sent to clients when they are on the Internet. Wake On LAN transmissions are always sent at the scheduled time.

·         Wake On LAN independently enabled or disabled for any site in the Configuration Manager 2007 hierarchy

·         Due to advertisements and software update deployments are inherited to child sites, the site server in the child site is responsible for sending the wake-up transmissions to its assigned clients if the site is enabled for Wake On LAN.

·         If Wake On LAN is disabled on a child site, child site will not send the wake-up transmissions to its assigned clients, and client computers in that site will not be sent wake-up packets.

·         ConfigMgr 2007 Client registers the system as busy for the specific wake-up task it receives, this prevents the computer from going back into a sleep state based on its power management settings before the task can complete.

·         Wake On LAN does not return computers to a sleep state and you need to configure power management schemes to shut down or hibernate after a period of inactivity.

·         Computers are woken up before the scheduled activity by 3 minutes before the scheduled activity to ensure that they have completed startup, this setting can be configured with the transmission offset option in a Wake On LAN advanced setting.

·         Mobile devices do not support Wake On LAN capability.

·         Clients running Systems Management Server (SMS) 2003 do not support Wake On LAN.

·         Wake On LAN in ConfigMgr 2007 supports waking up computers in sleep states S1 through S5

4.                 WOL transmission methods

 

·         Unicast transmission

o    Unicast transmission wake-up packet uses the IP address of the target computer from hardware inventory to route to the target computer's subnet, and it uses the Media Access Control (MAC) address of the target computer from hardware inventory to construct the wake-up packet. When the wake-up transmission reaches the target computer's subnet, the wake-up packet is sent directly to the target computer, and If the target computer has changed its IP address since it last sent its inventory information, the wake-up packet will reach the wrong computer but it will not wake it up because the MAC address in the wake-up packet transmission will not match.

o    Switches must forward UDP packets

o    Unicast transmission is secure solution than subnet-directed broadcasts because the packet is sent directly to a computer rather than to all computers on a subnet.

o    Consumes less network bandwidth than subnet-directed broadcast transmissions.

o    Unicast transmission is supported with IPv6.

 

·         Subnet-directed broadcasts

o    Subnet-directed broadcasts transmission wake-up packet uses the Media Access Control (MAC) address and IP subnet address of the target computer from hardware inventory,  The wake-up transmission is sent to the computer's last known subnet, and it is then broadcast to all computers on that subnet, and the computer that has the MAC address specified in the wake-up transmission will respond.

o    Routers must be configured to forward subnet-directed broadcasts.

o    Subnet-directed broadcasts are not supported with IPv6

5.                 Wake On LAN Prerequisites

·         Network cards must support the standard magic packet format.

·         Computers must be configured for wake-up packets on the network card and in the computer BIOS.

·         If subnet-directed broadcast configured, all routers between the site server and target computers must allow IP directed broadcasts, and support IPv4.

·         Hardware inventory must be enabled, and completed an inventory schedule.

·         Client computers must be running the Configuration Manager 2007 client. 

6.                 Sleep States for Wake On LAN

 

·         S0: The computer is on and fully functional.

·         S1: The computer appears to be off with the CPU stopped. RAM is refreshed, and the computer is running in a low power mode.

·         S2: The computer appears to be off with the CPU stopped. RAM is refreshed, and the computer is running in a lower power mode than S1.

·         S3 (Standby): The computer appears to be off with no power to the CPU. RAM is in slow refresh.

·         S4 (Hibernate):  The computer appears to be off with no power to the hardware. System memory has been saved as a temporary file on the hard disk.

·         S5 (Off):  The computer is off with no power to the hardware, and the operating system has been shut down without saving system memory to disk.

-------------------
Thanks,

Stephen Leacock  - "I detest life-insurance agents: they always argue that I shall some day die, which is not so."

All the Third-Party Solutions for SCCM & SMS

Web Sites:

MyITForum is the premier online destination for IT professionals responsible for managing their corporations' Microsoft Windows systems; it is especially useful for IT professionals working with Microsoft Systems Management Server. (http://www.myitforum.com)

FAQshop endeavors to provide a "one-stop-shop" for systems management questions, answers, and utilities. (http://www.faqshop.com)

SMS Alliance is a consortium of companies that leverage joint resources to strengthen the capabilities and benefits of SMS. Their mission is to provide organizations with the best-of-breed solutions and services to enhance and extend SMS 2003. (http://www.sms-alliance.com)

1E is one of the founding members of the SMS Alliance, 1E is a company on the cutting edge of systems management. It enhances and extends Microsoft management and deployment technologies, delivering advanced automation and reporting across the enterprise. (www.1e.com)

Macrovision Corporation, another founding member of the SMS Alliance, Macrovision Corporation is a recognized leader in software deployment packaging, software installation, and software updating solutions. They offer one of the best software packaging tools with AdminStudio.
(http://www.macrovision.com/)

PS'SOFT, as a founding member of the SMS Alliance, offers extenders for SMS 2003 that focus on IT asset management. They offer a web-based software cataloging system called SMS Software Requests. (www.pssoft.com)

Vintela, another founding member of the SMS Alliance, Vintela offers a seamless solution to extend security and compliance of Microsoft Active Directory to Unix, Linux, and other platforms and applications. They offer solutions that help IT administrators manage Unix, Linux, and MAC systems using SMS 2003. Vintela is now part of Quest Software. (www.vintela.com)

iAnywhere, the last founding member of the SMS Alliance, iAnywhere offers frontline security and management to SMS and provides extensions to manage your enterprise's mobile and wireless devices through SMS. (www.iAnywhere.com)

AppDeploy is the Internet resource to go to when you need to script or repackage an application for distribution. Among other points of interest at the site is a massive library of applications, sorted by application name and vendor name. For each application listed, you'll find a community-based thread discussing the best practices, links, scripts, and challenges met/overcome with working with the application in regard to installation scripting/repackaging.(http://www.appdeploy.com/)

DesktopEngineer is perhaps one of the best resources in the Windows Installer arena. This site offers a wealth of information on Windows Installer technology, techniques, and troubleshooting tips. I have noticed that he is starting to increase the content related to Microsoft's upcoming PowerShell scripting language. (http://www.desktopengineer.com/)

Tools

SMSView is a utility that is used to extend the functionality of the Microsoft Systems Management Server 2003 advanced client. SMSView allows you to perform the following actions on an SMS advanced client: All nonadmin users to view current mandatory assignments and advertisement status, View advertisement history (past 60 days), View current mandatory assignments, Rerun advertisements, Remote operations (remotely view and manage the SMS client), Display hardware/software inventory status, Display management point/proxy management point, Repair the SMS advanced client. (http://www.smsview.com/)

SMS 2003 Monster MOF is a MOF file that contains several new classes of MOF that will improve SMShardware inventory capabilities. The Monster MOF will enhance inventory data without requiring intimate knowledge of the SMS_DEF.MOF file. (www.smsexpert.com)

SMS 2003 Web Remote Tools assist SMS administrators and allow client administration from a web page. (http://www.myitforum.com/articles/19/view.asp?id=8662)

Corey Becht's Right-Click Tools is one of the best set of tools for all SMS administrators. This tool allows you to right click on any collection or individual PC within the SMS Administrator console and initiate hardware inventory, reassign the site code, restart the SMS Agent Host service, rerun advertisements without modifying the advertisement, perform discovery, initiate software inventory, create file collections, monitor software metering usage, refresh machine policies, evaluate policies, update Windows installer sources,change port number, and change cache size.These tools can run per computer resource or for all the members of a collection.(www.myitforum.com/articles/8/view.asp?id=7099)

Microsoft SMS Toolkit 2: Microsoft released a very nice set of tools for SMS called the SMS Toolkit version 2 . It contains the following tools: IIS Lockdown 2.1 Template, URLScan 2.5 Template, Policy Spy, SMS Trace, Advanced Client and Management Point Cleaner, Advanced Client Spy, Policy Verifier, Send Schedule, Management Point Spy, Set Preferred Distribution Point and CAP, Delete Certificate, Patch Management Evaluation, Delete Group Class, Transfer SMS ID, Package Loader, Management Point Troubleshooter, Client Site Assignment Verifier, Site Boundary Tool, Create Secondary Site Tool, Create SMS Address Tool.(www.microsoft.com/smserver/downloads/2003/tools/toolkit.mspx)

Security Logon Audit Tool (SLAT) extends SMS hardware inventory to include user logon information.This data can be used in web reports and queries. The tool includes the following samplereports: Top users for all systems, User logon information for a specific computer, Systems where the last logged-on user is not the top user, Systems where a specific user has logged on SLAT searches the security event log for the 528 event, which is created when user logon events occur and is enabled via Group Policy. (http://www.systemcentertools)

Enhanced System and User Discovery Tools, out of the box, SMS 2003 does a pretty good job of discovering systems from Active Directory. It's not perfect, though—there are a few gaps in its methods. The Enhanced System Discovery tool, assists in filling these gaps. Out of the box, SMS 2003 does not perform Windows NT 4 domain discovery. This tool solves that by enumerating all machines from a list of NT 4 domains, resolving their IP addresses from DNS or WINS, and creating data discovery records for each system. (http://www.systemcentertools/)

BITS Bandwidth Manager is an SMS Installer script that lets you throttle BITS bandwidthon Windows XP SP2 systems. You do not need to manually adjust any settings. The script takes care of the Registry key manipulation for you.(http://www.myitforum.com/inc/upload/11332BITSManager.zip)

1E SMSWakeUp: this WOL product is able to turn on computers after they have been shut down by users. The wake cycle can be triggered on a regular schedule to power up systems in preparation for the workday, or to perform software deployment activities. (http://www.1e.com/)

1E NightWatchman: Since we are talking about waking systems that have been shut down, it maybe a good practice to examine how best to shut down those systems in the first place. Why dowe want to shut down systems? We do this to enforce reboot cycles and to save energy costs. (http://www.1e.com/)

1E SMSNomad Branch: Some offices may not have the server hardware to allow for a Distribution Point (DP). But those offices may have a substantial number of users and/or be separated from the rest of the network by a low-speed or saturated WAN link, which you would rather not send multiple copies of a package across. SMSNomad Branch acts similar to a peer-to-peer network, allowing other computers to become DPs. If one machine is shutdown, another is selected as the DP. Included in this technology is multicast, increasing its efficiency to reduce network traffic on the local network segment. (http://www.1e.com/)

1E OSD Plus Pack: This is an enhancement to the SMS OSD Feature Pack. It allows you to leverage the SMS OSD Feature Pack in offices that do not have DPs. OSD Plus Pack offers similar functionality to SMSNomad Branch, but also has a few other applications bundledwith it: State Migration Editor, which is an interface for the User State Migration Tool, AppMigrator, which allows the automatic reinstallation of applications after OS imaging, PXE Lite, which is a local PXE server to allow deployment of OS images to bare-metalmachines booted from the network PXE server. (http://www.1e.com/)

SMS Companion 2006: This product provides WOL capabilities, similar to 1E's SMSWakeUp, but leverages slightly different technologies behind the scenes. A key difference is that SMS Companion puts systems in hibernation, rather than powering them off. The following are some of the key applications included with this product:Wake-on-Schedule: Allows clients to come out of a hibernation state. Service Windows: Allows you to restrict the SMS inventory and software distributions from happening during specific time periods, to reduce or eliminate user interruptions. Load Balancing: Allows you to reduce peak network and SMS server loading by making sure that the clients use these resources in a controlled manner. (http://www.smsexpert.com/)

Quest Management Xtensions for SMS: Since Windows platforms are not the only systems in an enterprise, you may need a way tomanage other platforms, such as Unix, Linux, and Mac OS X. These management extensions offer that capability for SMS 2003. One of the unique aspects of this product is its support route: first-level support is handled by Microsoft Product Support Services. (http://www.quest.com/quest-management-xtensions-for-sms)

-------------------
Thanks,
http://sccm07.blogspot.com/

Microsoft System Center Configuration Manager 2007 Exam Code 70-401

 

Skills measured

This exam measures your ability to accomplish the technical tasks listed in the following table. The percentages indicate the relative weight of each major topic area on the exam.

 

 

Skills measured by Exam 70-401
Deploying a System Center Configuration Manager 2007 (SCCM) Server (9 percent)
Set up and configure an Active Directory schema.
Migrate from an SMS 2003 hierarchy to SCCM 2007.
Configure an SCCM hierarchy.
Set up and configure security accounts.
Configuring an SCCM Infrastructure (19 percent)
Configure client agents.
Configure site boundaries.
Configure core site system roles.
Configure discovery methods.
Configure client installation.
Configure SCCM infrastructure for Internet-based client management.
Managing Resources (14 percent)
Build an SCCM collection by using queries.
Meter software usage.
Manage assets.
Manage inventory flow.
Manage client agents.
Distributing Applications (17 percent)
Manage packages.
Manage programs.
Manage advertisements.
Schedule distribution.
Track success and failure rates for distribution.
Manage distribution points.
Deploying Operating Systems (13 percent)
Capture a reference computer image.
Manage task sequences.
Configure site system roles related to deploying operating systems.
Deploy operating system packages.
Customize user state migration.
Deliver applications.
Securing a Network Infrastructure (13 percent)
Configure Network Access Protection (NAP).
Maintain NAP.
Migrate from Inventory Tool for Microsoft Update (ITMU) to Windows Software Update Services (WSUS).
Deploy software updates.
Manage vulnerability compliance.
Managing and Maintaining an SCCM Infrastructure (15 percent)
Manage system health.
Configure automatic maintenance tasks.
Create custom reports.
Maintain clients.
Manage systems by using configuration management.
Manage Wake on LAN.

 

 

-------------------
Thanks,
http://paddymaddy.blogspot.com/

SCCM It's Ports ; SCCM using Ports

 

Configurable Ports

Configuration Manager 2007 allows you to configure the ports for the following types of communication:

• Client to site system
  
• Client to Internet (as proxy server settings)
  
• Software update point to Internet (as proxy server settings)
  
• Software update point to WSUS server
  
• Client to reporting point
  

By default, the HTTP port used for client to site system communication is port 80 and the default HTTPS port is 443. Ports for client-to-site system communication over HTTP or HTTPS can be changed during Setup or in the Site Properties for your Configuration Manager site.

Reporting point site system roles have configurable port settings for HTTP and HTTPS communication defined on the reporting point site system role property page. By default, users connect to the reporting point using the HTTP port 80 and HTTPS port 443. These ports are defined during installation only. To redefine the reporting point communication port, the reporting point site system must be deleted and reinstalled.

Non-Configurable Ports

Configuration Manager does not allow you to configure ports for the following types of communication:

• Site to site (primary-to-primary or primary-to-secondary)
  
• Site server to site system
  
• Site server to site database server
  
• Site system to site database server
  
• Configuration Manager 2007 console to SMS Provider
  
• Configuration Manager 2007 console to the Internet
  

Port Details

The port listings that follow are used by Configuration Manager 2007 and do not include information for standard Windows services, such as Active Directory group policy and Kerberos authentication. For information about Windows Server services and ports, see http://go.microsoft.com/fwlink/?LinkID=123652.

The following diagram indicates connections between Configuration Manager 2007 computers. The number for the link corresponds to the table that lists the ports for that link. The arrows between the computers represent the direction of the communication.

• -- > indicates one computer initiates and the other computer always responds
  
• < -- > indicates that either computer can initiate
  

1. Site Server < -- > Site Server

Description	UDP	TCP
Server Message Block (SMB)	--	445
Point to Point Tunneling Protocol (PPTP)	--	1723 (See note 3, RAS Sender)

2. Primary Site Server -- > Domain Controller

Description	UDP	TCP
Lightweight Directory Access Protocol (LDAP)	--	389
LDAP (Secure Sockets Layer [SSL] connection)	636	636
Global Catalog LDAP	--	3268
Global Catalog LDAP SSL	--	3269
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

3. Site Server < -- > Software Update Point

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
Hypertext Transfer Protocol (HTTP)	--	80 or 8530 (See note 4, Windows Server Update Services)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 or 8531 (See note 4, Windows Server Update Services)

4. Software Update Point -- > Internet

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 1, Proxy Server port)

5. Site Server < -- > State Migration Point

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135

6. Client -- > Software Update Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 or 8530 (See note 4, Windows Server Update Services)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 or 8531 (See note 4, Windows Server Update Services)

7. Client -- > State Migration Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 (See note 2, Alternate Port Available)
Server Message Block (SMB)	--	445

8. Client -- > PXE Service Point

Description	UDP	TCP
Dynamic Host Configuration Protocol (DHCP)	67 and 68	--
Trivial File Transfer Protocol (TFTP)	69 (See note 5, Trivial FTP (TFTP) Daemon)	--
Boot Information Negotiation Layer (BINL)	4011	--

9. Site Server < -- > PXE Service Point

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

10. Site Server < -- > System Health Validator

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

11. Client -- > System Health Validator

The client requires the ports established by the Windows Network Access Protection client, which is dependent upon the enforcement client being used. For example, DHCP enforcement will use ports UDP 67 and 68. IPSec enforcement will use ports TCP 80 or 443 to the Health Registration Authority, port UDP 500 for IPsec negotiation and the additional ports needed for the IPsec filters. For more information, see the Windows Network Access Protection documentation. For help with configuring firewalls for IPsec, see http://go.microsoft.com/fwlink/?LinkId=109499.

12. Site Server < -- > Fallback Status Point

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

13. Client -- > Fallback Status Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)

14. Site Server -- > Distribution Point

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

15. Client -- > Distribution Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 (See note 2, Alternate Port Available)
Server Message Block (SMB)	--	445
Multicast Protocol	63000-64000	--

16. Client -- > Branch Distribution Point

Description	UDP	TCP
Server Message Block (SMB)	--	445

17. Client -- > Management Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 (See note 2, Alternate Port Available)

18. Client -- > Server Locator Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)

19. Branch Distribution Point -- > Distribution Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 (See note 2, Alternate Port Available)

20. Site Server -- > Provider

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

21. Server Locator Point -- > Microsoft SQL Server

Description	UDP	TCP
SQL over TCP	--	1433

22. Management Point -- > Microsoft SQL Server

Description	UDP	TCP
SQL over TCP	--	1433

23. Provider -- > SQL Server

Description	UDP	TCP
SQL over TCP	--	1433

24. Reporting Point -- > SQL Server / Reporting Services Point -- > SQL Server

The reporting point and the Reporting Services point use the same ports. The Reporting Services point is applicable to Configuration Manager 2007 R2 only.

Description	UDP	TCP
SQL over TCP	--	1433

25. Configuration Manager Console -- > Reporting Point

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 (See note 2, Alternate Port Available)

26. Configuration Manager Console -- > Provider

Description	UDP	TCP
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

27. Configuration Manager Console -- > Internet

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80

28. Primary Site Server -- > Microsoft SQL Server

Description	UDP	TCP
SQL over TCP	--	1433

29. Management Point -- > Domain Controller

Description	UDP	TCP
Lightweight Directory Access Protocol (LDAP)	--	389
LDAP (Secure Sockets Layer [SSL] connection)	636	636
Global Catalog LDAP	--	3268
Global Catalog LDAP SSL	--	3269
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

30. Site Server -- > Reporting Point / Site Server -- > Reporting Services Point

The reporting point and the Reporting Services point use the same ports. The Reporting Services point is in Configuration Manager 2007 R2 only.

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

31. Site Server -- > Server Locator Point

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

32. Configuration Manager Console -- > Site Server

Description	UDP	TCP
RPC (initial connection to WMI to locate provider system)	--	135

33. Software Update Point -- > WSUS Synchronization Server

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 or 8530 (See note 4, Windows Server Update Services)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 or 8531 (See note 4, Windows Server Update Services)

34. Configuration Manager Console -- > Client

Description	UDP	TCP
Remote Control (control)	2701	2701
Remote Control (data)	2702	2702
Remote Control (RPC Endpoint Mapper)	--	135
Remote Assistance (RDP and RTC)	--	3389

35. Management Point < -- > Site Server

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
RPC Endpoint mapper	--	135
RPC	--	DYNAMIC
Server Message Block (SMB)	--	445

36. Site Server -- > Client

Description	UDP	TCP
Wake on LAN	9 (See note 2, Alternate Port Available)	--

37. Configuration Manager client -- > Global Catalog Domain Controller

A Configuration Manager client does not contact a global catalog server when it is a workgroup computer or when it is configured for Internet-only communication.

Description	UDP	TCP
Global Catalog LDAP	--	3268
Global Catalog LDAP SSL	--	3269

38. PXE Service Point -- > Microsoft SQL Server

Description	UDP	TCP
SQL over TCP	--	1433

39. Site Server < -- > Asset Intelligence Synchronization Point (Configuration Manager 2007 SP1)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

40. Asset Intelligence Synchronization Point < -- > System Center Online (Configuration Manager 2007 SP1)

Description	UDP	TCP
Secure Hypertext Transfer Protocol (HTTPS)	--	443

41. Multicast Distribution Point -- > Microsoft SQL Server(Configuration Manager 2007 R2)

Description	UDP	TCP
SQL over TCP	--	1433

42. Client status reporting host --> Client (Configuration Manager 2007 R2)

Description	UDP	TCP
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC
ICMPv4 Type 8 (Echo) or ICMPv6 Type 128 (Echo Request)	n/a	n/a

43. Client status reporting host --> Management Point (Configuration Manager 2007 R2)

Description	UDP	TCP
Server Message Block (SMB)	--	445
NetBIOS Session Service	--	139

44. Client status reporting host --> Microsoft SQL Server (Configuration Manager 2007 R2)

Description	UDP	TCP
SQL over TCP	--	1433

45. Site Server < -- > Reporting Services Point (Configuration Manager 2007 R2)

(See note 6, Communication between the site server and site systems)

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

46. Configuration Manager Console -- > Reporting Services Point (Configuration Manager 2007 R2)

Description	UDP	TCP
Hypertext Transfer Protocol (HTTP)	--	80 (See note 2, Alternate Port Available)
Secure Hypertext Transfer Protocol (HTTPS)	--	443 (See note 2, Alternate Port Available)

47. Reporting Services Point -- > Microsoft SQL Server (Configuration Manager 2007 R2)

Description	UDP	TCP
SQL over TCP	--	1433

Notes

1 Proxy Server port    This port cannot be configured but can be routed through a configured proxy server.

2 Alternate Port Available    An alternate port can be defined within Configuration Manager for this value. If a custom port has been defined, substitute that custom port when defining the IP filter information for the IPsec policies.

3 RAS Sender    Configuration Manager 2007 can also use the RAS Sender with Point to Point Tunneling Protocol (PPTP) to send and receive Configuration Manager 2007 site, client, and administrative information through a firewall. Under these circumstances, the PPTP TCP 1723 port is used.

4 Windows Server Update Services    WSUS can be installed either on the default Web site (port 80) or a custom Web site (port 8530).

After installation, the port can be changed.

If the HTTP port is 80, the HTTPS port must be 443.

If the HTTP port is anything else, the HTTPS port must be 1 higher—for example 8530 and 8531.

5 Trivial FTP (TFTP) Daemon    The Trivial FTP (TFTP) Daemon system service does not require a user name or password and is an integral part of the Windows Deployment Services (WDS). The Trivial FTP Daemon service implements support for the TFTP protocol defined by the following RFCs:

• • RFC 350—TFTP
  
• • RFC 2347—Option extension
  
• • RFC 2348—Block size option
  
• • RFC 2349—Time-out interval, and transfer size options
  

Trivial File Transfer Protocol is designed to support diskless boot environments. TFTP Daemons listen on UDP port 69 but respond from a dynamically allocated high port. Therefore, enabling this port will allow the TFTP service to receive incoming TFTP requests but will not allow the selected server to respond to those requests. Allowing the selected server to respond to inbound TFTP requests cannot be accomplished unless the TFTP server is configured to respond from port 69.

6 Communication between the site server and site systems    By default, communication between the site server and site systems is bi-directional. The site server initiates communication to configure the site system, and then most site systems connect back to the site server to send back status information. Reporting points and distribution points do not send back status information. If you select Allow only site server initiated data transfers from this site system on the site system properties, the site system will never initiate communication back to the site server.

7 Ports used by distribution points for application virtualization streaming    A distribution point enabled to support application virtualization can be configured to use either HTTP or HTTPS. This feature is available in Configuration Manager 2007 R2 only.

Configuration Manager Remote Control Ports

When you use NetBIOS over TCP/IP for Configuration Manager 2007 Remote Control, the ports described in the following table are used.

Description	UDP	TCP
RPC Endpoint Mapping	--	135
Name resolution	137	--
Messaging	138	--
Client Sessions	--	139

AMT Out of Band Management Ports (Configuration Manager 2007 SP1)

When you use the out of band management feature in Configuration Manager 2007 SP1, the following ports are used.

A. Site Server <--> Out of Band Service Point

Description	UDP	TCP
Server Message Block (SMB)	--	445
RPC Endpoint Mapper	135	135
RPC	--	DYNAMIC

B. AMT Management Controller --> Out of Band Service Point

Description	UDP	TCP
Provisioning	--	9971 (configurable)

C. Out of Band Service Point --> AMT Management Controller

Description	UDP	TCP
Discovery	--	16992
Power control, provisioning, and discovery	--	16993

D. Out of Band Management Console --> AMT Management Controller

Description	UDP	TCP
General management tasks	--	16993
Serial over LAN and IDE redirection	--	16995

Ports Used by Windows Servers 

The following table lists some of the key ports that Windows Server uses and their respective functions. For a more complete list of Windows Server services and network ports requirements, see http://go.microsoft.com/fwlink/?LinkID=123652.

Description	UDP	TCP
Domain Name System (DNS)	53	--
Dynamic Host Configuration Protocol (DHCP)	67 and 68	--
Windows Internet Name Service (WINS)	138	--
NetBIOS datagrams	138	--
NetBIOS datagrams	--	139

Connecting with Microsoft SQL Server

If you use the TCP/IP Net-Library, enable port 1433 on the firewall. Use the Hosts file or an advanced connection string for host name resolution.

If you use named pipes over TCP/IP, enable port 139 for NetBIOS functions. NetBIOS should be used only for troubleshooting Kerberos issues.

Note
TCP/IP is required for network communications to allow Kerberos authentication. Named pipes communication is not required for Configuration Manager 2007 site database operations and should be used only to troubleshoot Kerberos authentication issues.

By default, SQL Server uses TCP (not UDP) port 1433 to listen on TCP/IP. To change the port, run SQL Server Setup on the server, and then click Change Network Support. If SQL Server uses port 1433, the client Net-Library works. If SQL Server uses a custom port number, the client must specify that port in the Data Source Name (DSN).

Microsoft does not recommend that you enable UDP ports 137 and 138 for NetBIOS name resolution by using B-node broadcasts. Instead, you can use a WINS server or an LMHOSTS file for name resolution.

Installation Requirements for Internet-Based Site Systems

The Internet-based management point, software update point, and fallback status point use the following ports for installation and repair:

• Site server --> site system: RPC endpoint mapper using UDP and TCP port 135.
  
• Site server --> site system: RPC dynamic TCP ports.
  
• Site server < --> site system: Server message blocks (SMB) using TCP port 445.
  

Distribution points do not install until the first package is targeted to them. Package installations on distribution points require the following RPC ports:

• Site server --> distribution point: RPC endpoint mapper using UDP and TCP port 135.
  
• Site server --> distribution point: RPC dynamic TCP ports.

 

-------------------
Thanks,
http://paddymaddy.blogspot.com/

All SCCM 2007 logs at one Place

Client Log Files

The Configuration Manager 2007 client logs are located in one of the following locations: ·         On computers that serve as management points, the client logs are located in the SMS_CCM\Logs folder. ·         On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder or the %Windir%\SysWOW64\CCM\Logs.The following table lists and describes the client log files.

Log File Name	Description
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.)

Site Server Log Files

Most Configuration Manager 2007 site server log files are located in the <InstallationPath>\LOGS folder. Because Configuration Manager 2007 relies heavily on Microsoft Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server. The IIS log file is located in the %Windir%\System32\logfiles\W3SVC1 folder on the IIS server. The following table lists and describes the site server log files.

Log File Name	Description
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.
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.

The Admin UI log files are located in <InstallationPath>\AdminUI\. The following table lists and describes the Admin UI log files.

Log File Name	Description
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

If management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer. The following table lists and describes the management point log files.

Log File Name	Description
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

If mobile device management is enabled in the site hierarchy, mobile device management point log files are generally stored in the <ConfigMgrInstallPath>\LOGS folder on the mobile device management point computer. The following table lists and describes the mobile device management point log files.

Mobile Device Management Point Logs

Log File Name	Description
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 Management Client Logs

For the locations of log files on managed mobile devices and on computers that are used to deploy the mobile device client, see How to Configure Logging for Windows Mobile and Windows CE Devices. The following table lists and describes the mobile device management client log files.

Log File Name	Description
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

The following table lists and describes the operating system deployment log files.

Log File Name	Description
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.Log file location:·         If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\logs·         If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG·         If task sequence completes when running in WindowsPE: <largest fixed partition>\SMSTSLOG Note <CCM Install Dir> is %windir%\system32\ccm\logs for most Configuration Manager 2007 clients and is <Configuration Manager 2007 installation drive>\SMS_CCM for the Configuration Manager 2007 site server. For 64-bit operating systems, it is %windir%\SysWOW64\ccm\logs.
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

By default, client log files related to Network Access Protection are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs.The following table lists and describes the Network Access Protection log files.

Log File Name	Description
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.

The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs, and they are listed and described in the following table.

Log File Name	Description
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

Setup information for the System Health Validator point can be found in a setup log file, described in the following table, on the computer running the Network Policy Server.

Log File Name	Description
<ConfigMgrInstallationPath>\Logs\SMSSHVSetup.log	Records the success or failure (with failure reason) of installing the System Health Validator point.

Desired Configuration Management Log Files

By default, the Configuration Manager 2007 client computer log files are found in %windir%\System32\CCM\Logs or in %windir%\SysWOW64\CCM\Logs. For client computers that are also management points, the client log files are located in the SMS_CCM\Logs folder. The following table lists and describes these log files.

Log File Name	Description
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

The Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder <ConfigMgrInstallationPath>\Logs on the site server. There are no client-side log files for Wake On LAN. The following table lists and describes the Wake On LAN log files.

Log File Name	Description
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

The Configuration Manager 2007 site server log files are found, by default, in <InstallationPath>\Logs. The following table lists and describes the software updates site server log files.

Log File Name	Description
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. Note On 64-bit operating systems and on 32-bit operating systems with no Configuration Manager 2007 installed, PatchDownloader.log is created in the server logs directory. On 32-bit operating systems, if the Configuration Manager 2007 client is installed, PatchDownloader.log is created in the client logs directory.
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

By default, the log files for WSUS running on the software update point site system role are found in %ProgramFiles%\Update Services\LogFiles. The following table lists and describes the WSUS server log files.

Log File Name	Description
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

By default, the Configuration Manager 2007 client computer log files are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs. The following table lists and describes the software updates client computer log files.

Log File Name	Description
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

By default, the Windows Update Agent log file is found on the Configuration Manager Client computer in %windir%. The following table provides the log file name and description.

Log File Name	Description
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.

-------------------
Thanks,
http://paddymaddy.blogspot.com/