SCCM Software Update Deployment flow

-
The SCCM clients receive their SUP/WSUS settings as a local policy on the clients,
Scan gets initiated as per configured schedule and happens on base of update GUID. Location services looks for our nearest SUP. This also can be checked in windowsupdate.log

When scan is completed. ScanAgent reports that the scan is complete and records the results of the scan in the updatestore. Information can be checked in updatestore.log

Client sends result of scan cycle through status massages with topic ID 501 and 500 to MP and site server for each the update that are missing on machine. This can be checked in statemassage.log

Once all this process completes updates evaluation gets start by receiving policy for applicable updates. Scan gets initiated for to have latest scan data update applicability and report status, This information can be checked in updatedeployment.log

Client Retrieve needed update components through CIAssignment and then SDM agent checks what binaries are included in the patch package,
After that patches get started to download and information can be checked in Patchdownloader.log

Once patches get downloaded windows update agent Apply and install the updates, this can be checked in Updatehandler.log

Once the installation is completed, Scan for update status gets start to record update installation compliance and sent to site server through WMI.


Cheers...

Comments

  1. AnonymousApril 8, 2015 at 9:56 PM

    Hi Ankur, "Client sends result of scan cycle through status massages", this is incorrect. The state messages are used for that. Also "


    Client Retrieve needed update components through CIAssignment and then SDM agent checks what binaries are included in the patch package,
    After that patches get started to download and information can be checked in Patchdownloader.log". This is an incorrect statement. PatchDownloader.log doesn't exists on the client side. This log is there on site systems.

    ReplyDelete
    Replies
    1. Ankur PathakApril 9, 2015 at 11:43 PM

      Hi thanks for letting me know

      Could you please explain how it happens

      Delete

Post a Comment

Popular posts from this blog

Windows Deployment Service ( WDS ) and Errors and Solutions

-
Image
Hi Guys... This post is all about Windows Deployment service WDS and its Errors and solutions. WDS is used to deploy Operating System Images and also is SCCM OSD Component. Many times we all have faced WDS issues and errors. Following are Some of Issues and their solutions Error 10048 Description: The Windows Deployment Services Server service terminated with service-specific error 10048 This issue occurs if the following conditions are true: ·          The DHCP server and the WDS server are installed on the same computer. ·          The  Do not listen on port 67  option is  NOT  enabled in the DHCP tab. Cause When the DHCP server and the WDS server are installed on the same computer, the WDS Service tries to use the port 67. However, the DHCP server already uses this port. Solution: Method 1 At the command prompt, type the following command, and then press ENTER: wdsutil /set-Server /UseDhcpPorts:No Method 2 1.       Click  Start , click
Read more

Hyper-V Questions and answers !

-
Hyper-V Questions and answers ! VIRTUAL MACHINE TECHNOLOGY Q.   What is virtual machine technology? A.    Virtual machine technology applies to both server and client hardware. Virtual machine technology enables multiple operating systems to run concurrently on a single machine. In particular, Hyper-V, a key feature of Windows Server 2008 R2, enables one or more operating systems to run simultaneously on the same physical system. Today, many operating  systems are supported by Virtual PC 2007, Virtual Server 2005, and Hyper-V. Q.   What is virtual machine technology used for? A.    Virtual machine technology serves a variety of purposes. It enables hardware consolidation, because multiple operating systems can run on one computer. Key applications for virtual machine technology include cross-platform integration as well as the following: Server consolidation. If several servers run applications that consume only a fraction of the           avail
Read more

DHCP, WDS, PXE Boot and Common Issues

-
Image
Hi Guys, Again i am back with very common information about DHCP,WDS & PXE and issues troubleshooting and their solutions. DHCP, WDS, and PXE are the main and needed components which plays very important role in SCCM OSD. They function and provide a very cool and automatize the OS installations (Network based). So why is the Need? DHCP : DHCP offers automatic ip address assigning functionality to machines at both booting state and online state. DHCP Scope options are one main key component. WDS : WDS offers the PXE functionality (Not SCCM) for network based OS installation (boots machine in to windows installation mode from network) So when we install the SCCM PXE service Point on WDS Server, It just overrides the settings of WDS PXE. Now Common PXE Boot Issues: ·         PXE-E53: No boot filename received   ·         PXE-T01: File not found ·         PXE-E3B: TFTP Error - File not Found   ·         PXE-E55 Proxy DHCP Service did no
Read more