In the first part of this SCCM 2012 and SCCM 1511 blog series, we planned our hierarchy, prepared our SCCM Server and Active Directory.
As far as configuration is concerned in XMLRPC communication between Spacewalk and Cobbler, with one exception (Cobbler back-authentication to Spacewalk), Spacewalk is always the "client", and the client presents UIDs generated by Cobbler as the primary key for the various object types being discussed in XMLRPC conversations.
This allows someone to mostly interact with Spacewalk or Cobbler directly as they see fit.
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.
You can use the information in the client and site server log files to help you troubleshoot issues that might occur in your Configuration Manager 2007 hierarchy.
By default, client and server component logging is turned on in Configuration Manager 2007. Because Configuration Manager 2007 relies heavily on Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server.Check the following locations: The file can occasionally go missing (especially if you reconfigure your distribution point or change multicast settings).Check C:\Program Files\SMS_CCM\Logs on your site server if you can’t find it in the two locations above.Reading the log is cumbersome without the Configuration Manager Trace Log tool (which you can download from here). Open the file, and let’s explore the deployment process for an unknown computer for a bit.Download and own part 1 to 21 of the SCCM Installation Guide in a single PDF file.He is a Microsoft Most Valuable Professional (MVP) in Cloud and Datacenter Management and blogs at Deploy