:::: MENU ::::
Browsing posts in: SCCM Super Flows

Configuration Manager Action cycles

Action tab has different Action cycles that will run automatically as per schedule mentioned in SCCM server.

  • Application Deployment Evaluation Cycle: This cycle will check new application deployment polices available to client computer & start installation as per schedule.
  • Data Discovery Collection Cycle: It generates a new discovery data record (DDR). When the DDR is processed by the site server, Discovery Data Manager adds or updates resource information from the DDR in the site database.
  • File Collection Cycle: When a file is specified for collection, the Microsoft System Center Configuration Manager software inventory agent searches for that file when it runs a software inventory scan on each client in the site. If the software inventory client agent finds a file that should be collected, the file is attached to the inventory file and sent to the site server. This action differs from software inventory in that it actually sends the file to the site server, so that it can be later viewed using Resource Explorer. This is a part of SCCM inventory functionality.
  • Hardware Inventory Cycle: Collects information such as available disk space, processor type, and operating system about each computer. This is a part of SCCM inventory functionality.
  • Machine Policy Retrieval & Evaluation Cycle: The client downloads its policy on a schedule. By default, this value is configured to every 60 minutes and is configured with the option Policy polling interval (minutes).
  • Software Inventory Cycle: Collects software inventory data directly from files (such as .exe files) by inventorying the file header information. SCCM can also inventory unknown files — files that do not have detailed information in their file headers. This provides a flexible, easy-to-maintain software inventory method. Software inventory and collected file information for a client can be viewed using Resource Explorer. This is a part of SCCM inventory functionality.
  • Software Metering Usage Report Cycle: collects the data that allows you to monitor and client software usage.
  • User Policy Retrieval & Evaluation Cycle: Similar to Machine Policy Retrieval & Evaluation Cycle, it will initiate user policies.
  • Windows Installer Source List update Cycle: causes the Product Source Update Manager to complete a full update cycle. When you install an application using Windows Installer, those Windows Installer applications try to return to the path they were installed from when they need to install new components, repair the application, or update the application. This location is called the Windows Installer source location. Windows Installer Source Location Manager can automatically search SCCM distribution points for the source files, even if the application was not originally installed from a distribution point.

 

 

 


OSD scenarios

 

In a short one line i can describe like below

 

  • – Bare metal – Deploying a new  version of Windows to a system that  currently has nothing installed on it.
  • – Refresh – Wiping an existing  system and  deploying a new  version of Windows to it migrating any user  settings and  data  that  need to be kept.
  • – Replace – Replacing an existing System with a new  one by installing  a new operating system on the  new  computer and  then optionally transferring over  any user  settings and  data  that  need to be kept  from  the  old System
  • – Upgrade – Upgrading the  existing  operating system from  Window 7, 8.x to 10 whilst retaining all of the  existing  applications, settings and  user  data  that  is already on the computer.

 

 



SCCM Different types of Views

 

SCCM Different types of Views :—(In one line )

V_*                 — > By default view(EX:-V_add_remove)

V_R_  *          — > It will fill the values with Discovery data

V_RA_  *      — > It will, fill the values Once Discovered and Assigned

V_GS_*         —-> HINV/SINV/Software Granular data- Present/Current inv data

V_HS_*         —-> Historical data-After 90 days Task mainenance data HINV/SINV/Software Historical data

V_AI_*         —-> Asset Intelligence related

V_LU_*         —–> Part of AI(Localized Unit)

V_CI_*          ——> Configuration Item 5 types

V_CH_*         —–> Client Health validation related

V_CM_RES_COLL_<SMS00012>  ——> Member Class name / Machine details of that collection

 

Download Reference -SCCM 2007 SQL Views SCCM 2007 List of views from Technet

Download  ConfigMgr2012R2_SQLViews SCCM 2012 List of views from Technet

Download  Configmgr Tech Preview Default Reports   SCCM 2012 List of Reports Technet

Download  ConfigMgr 2012 R2 Status Messages  SCCM 2012 List of  Status Messages from Technet

 


SCCM 2012 Roles

In order to learn the SCCM, We requires to know what are the roles available .

What is Role :– With SCCM we have many features. In-order to use those feature we requires to enable these roles. Most of the roles as similar to SCCM 2007. If something is added I’m pointing at the line

Site Servers:

Using installations with Software Media Wizard server Called as Site Server. Without Site Server You can’t install SCCM in our hierarchy. While installing Site Serve we will mention Site Server Name with 3 digit (alpha-numeric) code.It hosts the configuration manager components and services

Site System:

Once we have the Site Server, site system roles can be hosted on site server Or Installing the roles on different server. A server or server Share that hosts one or more site system roles for Configuration Manager site Manage content distribution

Site Database Server:

A site system role that runs Microsoft SQL server and hosts the configuration Manager Site Database

Management Point:

A site system role that replies to configuration Manager Client’s requests and accepts management data from configuration manager clients

Distribution Point:

A configuration manager role that stages packages for Distribution to clients

Application Catalog Website Point:

A site system role that serves as an application catalog website point

Application Catalog Web service point :

A site system role that serves as application catalog web services point

Asset Intelligence Synchronization Point :

A site system role that connects to system center online to download asset intelligence catalog information and upload uncategorized titles that can be considered for future inclusion in the catalog

Reporting services Point:

A site system role that provides integration with SQL server reporting services to create and manager reports for configuration manager

Software update point:

A site system role that runs Microsoft windows server update services and allows configuration manager to use the WSUS catalog to scan configuration manager clients for software updates

State migration Point:

A site system role that store user state and settings migrated during the Operating system deployment

Fallback Status Point:

A site system role that receives messages from ConfigMgr clients that cannot communicate with their management point

 


Central Administration Site:

A Central Administration Site (CAS) is the top level or Root level Site server in the hierarchy .CAS is dedicatedly for administration purpose. We cannot assign Clients to the CAS or we can’t manage clients with help of CAS. We can’t enable all roles in CAS.

CAS can’t support grandchild primary sites [Vertical] architecture. However, CAS can have multiple child primary sites [Horizontal]. Which they send the client data to CAS, It will stores in the SQL database which is nothing but CAS site database. In CAS we will be installing Administrator console from which we can manage our SCCM infrastructure.

Without CAS also we can install and manage the SCCM with Standalone Primary site .When we have more than one Primary site we required the CAS.

We install standalone primary site server, In future, based on business we need to expand the sites or need to add some more primaries. Then that time if we have the SCCM 2012 R2, we can install a CAS after we installed a primary site. Before SP1(service pack1),We have to install the CAS First.

CAS can support max 25 child primary sites

 

For roles supporting configuration http://technet.microsoft.com/en-in/library/gg682077.aspx#BKMK_SiteAndRoleScale

Primary SITE

Clients can assigned only to a Primary site. At least 1 Primary site requires in SCCM environment.Assigned clients data will be stored in SCCM database .Primary site can have multiple secondary sites.All these secondary will report to Primary site. Primary can be standalone or It may report CAS Site. Primary site have both Primary site client machines information and Secondary site data. Primary site requires the SCCM License

Primary site can support up to 250 secondary sites (It’s completely depends on WAN speed)

In SCCM 2007:

Not much difference but in SCCM 2007 Primary can have multiple primary sites.

 

Secondary Sites

Client won’t assign to Secondary sites .Secondary sites are always child site of the primary sites. So it managed through the console connected to parent primary site. Secondary wont requires SCCM license

Secondary site is a mediator or forwarder, it gathers the information like inventory, system status info, etc. from clients and sends to parent site. Secondary site are more useful where we have remote locations where we need links where we need to control bandwidth

In generally we used to implement on following circumstances :

Remote location has around 500+ clients

If required to use software update point

To control the Bandwidth like upward flowing traffic

In SCCM 2012 : It requires SQL database  atleast SQL server Express edition will fine. Most of the client to server data will be replicated with help of database in SCCM 2012. so they have introduced database to secondary site . Unlike in SCCM 2007 ,we have to install the secondary site from it parent site console wizard in CM 2012, at that time if database not exist , it automatically installs SQL Server Express edition

 


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