0% found this document useful (0 votes)
18 views3 pages

SCCM Software Update Server Side Log Flow

The document outlines the server-side log flow and troubleshooting steps for SCCM Software Update, detailing the installation and configuration of WSUS and IIS, as well as the setup of the Software Update Point (SUP). It provides a step-by-step guide, including log files to monitor, success and failure signs, and common causes of issues at each stage. Key steps include synchronization with Microsoft Update, deployment creation, content distribution, and compliance reporting.

Uploaded by

mrronaldperez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views3 pages

SCCM Software Update Server Side Log Flow

The document outlines the server-side log flow and troubleshooting steps for SCCM Software Update, detailing the installation and configuration of WSUS and IIS, as well as the setup of the Software Update Point (SUP). It provides a step-by-step guide, including log files to monitor, success and failure signs, and common causes of issues at each stage. Key steps include synchronization with Microsoft Update, deployment creation, content distribution, and compliance reporting.

Uploaded by

mrronaldperez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SCCM Software Update Server-Side Log Flow & Troubleshooting

Step 1: IIS & WSUS Installation

Install WSUS and IIS components and configure WSUS via SCCM. Check [Link] and [Link] for signs of
success or failure.

Step Log File Success Signs Failure Signs Common Ca

Install WSUS and IIS components [Link] - WSUS Setup Successful.- Connected
- WSUStoSetup
DB successfully.
Failed.- SQL errors-
- SQL
IISServer
bindingnot
er

Configure WSUS via SCCM [Link] - Successfully connected to server-


- WSUS
Created/Upgraded
Configuration failed-
WSUSVersion
- WSUS
notversion
compatim

Step 2: Software Update Point (SUP) Setup

Install the SUP role on the site server. Use [Link] to track installation and linking to WSUS.

Step Log File Success Signs Failure Signs Causes

Install SUP role on site server [Link] - Completed SUP setup.- Installation
- Installation
successful
failed- Error connecting
- WSUS
to WSUS
service s

Step 3: WSUS Synchronization with Microsoft Update

Sync updates metadata from Microsoft Update. Monitor [Link] and SMS_WSUS_SYNC_MANAGER.log.

Step Log File Success Signs Failure Signs Causes

Sync updates metadata [Link], SMS_WSUS_SYNC_MANAGER.log


- Sync finished- Successfully synced
- Sync
WSUS
failed:server
HTTP 503- Content
- Network
downloadproxy/fi
failed

Step 4: Update Metadata Processing

WSUS updates categorized and metadata parsed.

Step Log File Success Signs Failure Signs Causes

Categorize & parse update metadata


[Link] - Language/classification downloaded-
- Missing
Updates
updateappear
classifications-
in console
-Sync
Wrong
hangs
syncorsch
er

Step 5: Create Deployment

Admin creates or updates update deployments. [Link] tracks deployment creation.

Step Log File Success Signs Failure Signs Causes

Create/update deployment [Link] - Deployment package created- -Deployment


Save errors-saved
Package creation -fails
SQL DB issues-

Step 6: Distribute Content to Distribution Points

Distribute update content to DPs. [Link] and [Link] show transfer status.
SCCM Software Update Server-Side Log Flow & Troubleshooting

Step Log File Success Signs Failure Signs Causes

Distribute update content to DPs [Link], [Link]


- Package distributed to DP- STATMSG
- Failed to
ID=2301
send content- ErrorCode=0x80070002
- Source files mis

Step 7: Client Location Request Handling (MP Side)

Client requests content location; MP_Location.log tracks these requests.

Step Log File Success Signs Failure Signs Causes

Client requests content location MP_Location.log - Provided content location - Failed to find location- HTTP 401/403
- MP permissions
errors

Step 8: Co-Management Workload Routing

Client chooses update workload (SCCM or Intune). [Link] (client) tracks this.

Step Log File Success Signs Failure Signs Causes

Workload routing (SCCM or Intune)[Link]


- Workload
(client) set to SCCM or Intune
- Updates not delivered due to workload
- Wrong mismatch
co-mana

Step 9: Unified Update Platform (UUP) and Delta Download Support

Enable express updates, delta files. SMS_DP_Express.log tracks express support.

Step Log File Success Signs Failure Signs Causes

Enable express/delta updates SMS_DP_Express.log - Express update support initialized


- Failed to add express content - DP lacks expres

Step 10: Delivery Optimization (DO) & BITS Transfer

Use DO or BITS to transfer update content. [Link] and [Link] track transfers.

Step Log File Success Signs Failure Signs Causes

Use DO or BITS for transfer [Link],


- Using
[Link]
Delivery Optimization- Download
- BITS error
completed
0x80072EE2- DO download
- Networkfailed
restricti

Step 11: Client Scan Reporting

Client reports scan results to MP. [Link] tracks messages.

Step Log File Success Signs Failure Signs Causes

Client reports scan [Link] - Forwarded state message - Failed to send state message - MP unreachable

Step 12: Compliance Reporting


SCCM Software Update Server-Side Log Flow & Troubleshooting

Compliance data visible in SCCM Console. [Link] and SQL replication logs involved.

Step Log File Success Signs Failure Signs Causes

Reports show compliance [Link], SQL replication


- Reports show compliance - Reports stale/incorrect - SQL replication

You might also like