:::: MENU ::::
Monthly Archives: August 2014

Patch installation process in SCCM client side

When we Deploy software updates to SCCM Client what will happens in the client side. Here is the Complete flow with logs:

1. Update Evaluation is triggered either manually , via schedule or due to mandatory patch enforcement.
2. Manual: Users select to begin a software updates or software updates evaluation cycle.    SMScliui is triggered to submit action to updates Deployment : SMScliui.log
3. Updates deployment is called to begin evaluation and application process :Updatesdeployment.log
4. CI agent is called to evaluate Applicalbe CI’s :CIagent.log
5. updates handler is called to handle the scan and patch deployment :Updateshandler.log
6. Scan agent is called to clear the scan history and initiate and scan: scanagent.log
7. Scan agent submit a Location services request to find WSUS server for use in scanning: Locatioservices.log
8. WUAhanlder is called to perform a scan.: WUA handler.log
9. Updatestore called to Adjust setting ion WMI as needed :Updatesstore.log
10. targeted CIs are evaluated and installed where applicable.
11. Updates deployment wakes up to begin CI evaluation and installation: Updatesdeployment.log
12. CI agent start-up to check targeted CIs and download if necessary :CIAgent.log
13. CIA agent calls SDM agent to download packages if necessary.
14. UpdatesDeploymnet calls Updates handler to initiate patch install : updatesdeployment.log
15. updates handler call WUA handler to facilitate patch install : Updateshanlder.log
16. WUAhanlder coordinates with exec mgr during patch install process. :WUAhanlder.log
17. Execmgr monitors software update installation :Execmgr.log


SCCM 2012 New Features

In two ways we can compare the new features

1. Site Level or Administration or Hierarchy level

2. New added features in support side.

 

Site Level  Changes :

  1. SCCM 2012 Introduced Top level hierarchy called CAS (Central Administration Site ). When we installing the SCCM 2012, We have a separate wizard called CAS exist. Which we don’t have  a wizard in SCCM 2007. We used to assume that First installation site will be Central Site. we cont assign clients to CAS, we cont enable all rolls in CAS
  2. SCCM 2012 supports only side by side Migration
  3. SCCM 2012 supports only horizontal hierarchy level. It wont support unlike SCCM 2007 supports primary can contains child primary sites.
  4. In SCCM 2012 to speed up the replication process in secondary site we need to install SQL server or else it automatically installs SQL Server Express
  5. Few rolls are introduces newly and some or merged with existing roles Like SLP role merged with MP and PXE role merged with DP.we will go in detail after few posts

 


SYSTEM CENTER CONFIGURATION MANAGER

 

System Center Configuration Manager its also known as configmgr2012 and configmgr2007 and simply configmgr. Earlier it also known as Systems Management Server. It is a system management software Product by Microsoft for managing large group of computers like Windows, mac OS, Unix,Linux and mobile operating systems also like windows phone, android and IOS.

 

configmgr_history

 

Below are the top features listed using SCCM

  1. Windows 10 Management
  2. Application Delivery
  3. Device Management
  4. Virtual Desktop Management
  5. Endpoint Protection
  6. Compliance and Setting Management
  7. Software Update Management
  8. Power Management
  9. Operating System Deployment
  10. Client health and monitoring
  11. Asset Intelligence
  12. Hardware Inventory and Software Inventory report
  13. Reporting
  14. In Console updates