Explore topic-wise InterviewSolutions in .

Open SCCM console; navigate to “All systems” collections where your CLIENT COMPUTER will be POPULATED. Right click on the client computer->Start->Remote TOOLS.

Open SCCM console; navigate to “All systems” collections where your client computer will be populated. Right click on the client computer->Start->Remote tools.

You can verify the status of a distribution by checking the execmgr.log file in c:windowssystem32ccmlogs folder, and SEARCH for the particular software distribution using the packaged. If the package is success then “installation succeeded with the exit CODE 0” will be written into the log file.

You can also verify it by checking the registry key on a CLIENT computer, HKLM->Software->Microsoft->SMS->Mobile Client->Software Distribution->Execution History->SYSTEM-><Package ID>->success or failure code will be written.

You can verify the status of a distribution by checking the execmgr.log file in c:windowssystem32ccmlogs folder, and search for the particular software distribution using the packaged. If the package is success then “installation succeeded with the exit code 0” will be written into the log file.

You can also verify it by checking the registry key on a client computer, HKLM->Software->Microsoft->SMS->Mobile Client->Software Distribution->Execution History->System-><Package ID>->success or failure code will be written.

OPEN control panel, NAVIGATE to Configuration manager icon and click on it. As the ConfigMgr window pops up switch to action tab and initiate the “Machine policy Retrieval &AMP; Evaluation CYCLE” by clicking on “Initiate Action” BUTTON as shown below.

Open control panel, navigate to Configuration manager icon and click on it. As the ConfigMgr window pops up switch to action tab and initiate the “Machine policy Retrieval & Evaluation Cycle” by clicking on “Initiate Action” button as shown below.

Open SCCM console, navigate to Site Database->Computer management->Reporting and click on reports where all the required reports will be listed. Right click on any report and click run to EXECUTE the report (assuming that the report is already been created).

In the below SCREENSHOT “All advertisements for a Specific computer” has been executed.

The client computer name has been entered and click on display to run the query and the ADVERTISEMENT for the specific client will be displayed as SHOWN below.

Click on “Export” option as shown below to export the result to the excel sheet.

Open SCCM console, navigate to Site Database->Computer management->Reporting and click on reports where all the required reports will be listed. Right click on any report and click run to execute the report (assuming that the report is already been created).

In the below screenshot “All advertisements for a Specific computer” has been executed.

The client computer name has been entered and click on display to run the query and the advertisement for the specific client will be displayed as shown below.

Click on “Export” option as shown below to export the result to the excel sheet.

Open SCCM console; navigate to Site Database->Computer Management-> All SYSTEMS, RIGHT Click->View->Export List as shown below. This list contains the client computer names and it can saved as notepad or in excel format.

Select the client computer for which the list needs to be EXPORTED and Right Click->Start->Resource Explorer. GO to “Action” tab and select export list as shown below.

Open SCCM console; navigate to Site Database->Computer Management-> All Systems, Right Click->View->Export List as shown below. This list contains the client computer names and it can saved as notepad or in excel format.

Select the client computer for which the list needs to be exported and Right Click->Start->Resource Explorer. Go to “Action” tab and select export list as shown below.

Open SCCM console, NAVIGATE to SITE Database->Computer management->Reporting and click on reports. You can a list of default and customized reports which can be executed by Right click-> run (this runs the query which is being used to create the report) to view the web reports as shown below.

If the report ID is KNOWN then the particular report can be searched using “Look for” OPTION as shown in the screenshot below.

Open SCCM console, navigate to Site Database->Computer management->Reporting and click on reports. You can a list of default and customized reports which can be executed by Right click-> run (this runs the query which is being used to create the report) to view the web reports as shown below.

If the report ID is known then the particular report can be searched using “Look for” option as shown in the screenshot below.

Remote into the CLIENT COMPUTER and open control panel and navigate to “CONFIGURATION manager” icon as shown below.

Then Switch to Actions TAB and select “Hardware inventory CYCLE” and click on initiate action repeat the same step for forcing software inventory cycle on SCCM client computers.

Remote into the client computer and open control panel and navigate to “configuration manager” icon as shown below.

Then Switch to Actions tab and select “Hardware inventory cycle” and click on initiate action repeat the same step for forcing software inventory cycle on SCCM client computers.

The CLIENT installation status can be verified using the LOG FILE or Control panel icons.

To check the log file, NAVIGATE to C:WindowsSystem32ccmsetup of the client computer and open the ccmsetup.log and clientmsi.log file. If the installation is success then you can SEE a “Installation Succeeded” line updated in the log file.

Also you can navigate to Start->Control panel and look for configuration manager icon entry (assuming that the control panel view is set to small icons).

The client installation status can be verified using the log file or Control panel icons.

To check the log file, navigate to C:WindowsSystem32ccmsetup of the client computer and open the ccmsetup.log and clientmsi.log file. If the installation is success then you can see a “Installation Succeeded” line updated in the log file.

Also you can navigate to Start->Control panel and look for configuration manager icon entry (assuming that the control panel view is set to small icons).

No. Configuration Manager 2007 delivers COMMAND lines to CLIENTS and can force those command lines to run with administrative RIGHTS using the Local System account. Configuration Manager 2007 command lines can be batch FILES, scripts, Windows Installer files with .msi extensions, executable files – any file that the operating system can run, Configuration Manager 2007 can distribute. However, Configuration Manager 2007 does not ACTUALLY package any software for distribution.

No. Configuration Manager 2007 delivers command lines to clients and can force those command lines to run with administrative rights using the Local System account. Configuration Manager 2007 command lines can be batch files, scripts, Windows Installer files with .msi extensions, executable files – any file that the operating system can run, Configuration Manager 2007 can distribute. However, Configuration Manager 2007 does not actually package any software for distribution.

No.If you have a SECONDARY site, the client must be assigned to the primary parent of the secondary site. However, Configuration Manager KNOWS how to MANAGE clients at the child secondary site. If there is a distribution POINT at the secondary site that has the content the clients need, the clients will probably get the content from the local distribution point instead of crossing the WAN LINK to the primary site.

No.If you have a secondary site, the client must be assigned to the primary parent of the secondary site. However, Configuration Manager knows how to manage clients at the child secondary site. If there is a distribution point at the secondary site that has the content the clients need, the clients will probably get the content from the local distribution point instead of crossing the WAN link to the primary site.

The SMS Provider is a WMI provider that allows both READ and write access to the CONFIGURATION Manager 2007 site database. The SMS Provider is used by the Configuration Manager console. The SMS Provider can be installed on the site database server computer, site server computer or another server class THIRD computer during Configuration Manager 2007 Setup. After setup has completed, the current installed location of the SMS Provider is displayed on the site PROPERTIES GENERAL tab.

The SMS Provider is a WMI provider that allows both read and write access to the Configuration Manager 2007 site database. The SMS Provider is used by the Configuration Manager console. The SMS Provider can be installed on the site database server computer, site server computer or another server class third computer during Configuration Manager 2007 Setup. After setup has completed, the current installed location of the SMS Provider is displayed on the site properties general tab.

• WINDOWS Server Update Services (WSUS) 3.0
• WSUS 3.0 Administration CONSOLE
• Windows Update Agent (WUA) 3.0
• Site server communication to the active software update point
• Network LOAD Balancing (NLB)
• Background INTELLIGENT Transfer Server (BITS) 2.5
• Windows Installer

SMS 2003 INVENTORY TOOL for Microsoft UPDATES.

SMS 2003 Inventory Tool for Microsoft Updates.

This is required COMPONENT of software updates, and after it is installed, the SUP is displayed as a site system role in the Configuration Manager console. The software update point site system role MUST be CREATED on a site system SERVER that has Windows Server Update Services (WSUS) 3.0 installed.

This is required component of software updates, and after it is installed, the SUP is displayed as a site system role in the Configuration Manager console. The software update point site system role must be created on a site system server that has Windows Server Update Services (WSUS) 3.0 installed.

CLIENT PUSH Installion, SOFTWARE update point based INSTALLATION, GROUP Policy Installation, Logon Script Installation, Manual Installation, Upgrade Installation(software Distribution).

Client Push Installion, Software update point based installation, Group Policy Installation, Logon Script Installation, Manual Installation, Upgrade Installation(software Distribution).

To create a scheduled BACKUP TASK, EXPAND the Site Settings node and expand the Site Maintenance node, CLICK on Tasks.
For Manual backup - Start SMS_SITE_BACKUP SERVICE

To create a scheduled backup task, expand the Site Settings node and expand the Site Maintenance node, click on Tasks.
For Manual backup - Start SMS_SITE_BACKUP service

Yes. If you use a discovery method, Configuration Manager can find many resources and create data discovery RECORDS (DDRs) for them, and those DDRs are STORED in the database. However, you cannot use Configuration Manager features such as software distribution, software UPDATES MANAGEMENT, and inventory until you install the client components.

Yes. If you use a discovery method, Configuration Manager can find many resources and create data discovery records (DDRs) for them, and those DDRs are stored in the database. However, you cannot use Configuration Manager features such as software distribution, software updates management, and inventory until you install the client components.

No. Configuration MANAGER 2007 native mode requires a PKI, but Configuration Manager 2007 does not. PKI authentication helps provide a GREATER LEVEL of security, but Configuration Manager 2007 does not help you install or configure the PKI INFRASTRUCTURE. If you do not ALREADY have the expertise to install and configure the PKI infrastructure, you can start with mixed mode and then change to native mode later.

No. Configuration Manager 2007 native mode requires a PKI, but Configuration Manager 2007 does not. PKI authentication helps provide a greater level of security, but Configuration Manager 2007 does not help you install or configure the PKI infrastructure. If you do not already have the expertise to install and configure the PKI infrastructure, you can start with mixed mode and then change to native mode later.

Yes. Client Push INSTALLATION is the only client installation METHOD that requires clients to be DISCOVERED FIRST.

Yes. Client Push Installation is the only client installation method that requires clients to be discovered first.

No. A secondary SITE cannot have a primary or secondary site reporting to it. Secondary SITES are ALWAYS CHILD sites to a primary site.

No. A secondary site cannot have a primary or secondary site reporting to it. Secondary sites are always child sites to a primary site.

No. You can configure more than one management points in a site, but only one of those management points can be configured as the default management point to support INTRANET clients in the site. If you are CONCERNED about performance, you can configure more than one management point, configure them to be PART of a Network Load Balancing (NLB) cluster, and them configure the NLB cluster as the default management point.

No. You can configure more than one management points in a site, but only one of those management points can be configured as the default management point to support intranet clients in the site. If you are concerned about performance, you can configure more than one management point, configure them to be part of a Network Load Balancing (NLB) cluster, and them configure the NLB cluster as the default management point.

No. To distribute software you must have a package, a PROGRAM and an ADVERTISEMENT. Advertisements can only be sent to collections, not to computers. If you want to distribute a package to a SINGLE computer, you must create a collection for that computer.

No. To distribute software you must have a package, a program and an advertisement. Advertisements can only be sent to collections, not to computers. If you want to distribute a package to a single computer, you must create a collection for that computer.

You NEED to add the Software Update Point site role to the site, CONFIGURE the software update point as active, configure the products, classifications, sync settings, ETC. in the Software Update Point properties. THEN, you can go to the Update Repository NODE and run the Run Synchronization action from the central primary site. Once synchronization completes, you will see the metadata in the Configuration Manager console.

You need to add the Software Update Point site role to the site, configure the software update point as active, configure the products, classifications, sync settings, etc. in the Software Update Point properties. THEN, you can go to the Update Repository node and run the Run Synchronization action from the central primary site. Once synchronization completes, you will see the metadata in the Configuration Manager console.

No. A secondary SITE is ALWAYS a secondary site. It cannot be upgraded, MOVED, or changed WITHOUT deleting it and reinstalling it. If you DELETE and reinstall, you lose all secondary site data.

No. A secondary site is always a secondary site. It cannot be upgraded, moved, or changed without deleting it and reinstalling it. If you delete and reinstall, you lose all secondary site data.

Four MAIN characteristics:

• A Secondary SITE does not have access to a Microsoft SQL Database
• Secondary SITES are ALWAYS a Child Site of a PRIMARY Site and can only be administered via a Primary Site
• Secondary Sites cannot have Child Sites of their own
• Clients cannot be assigned directly to the Site

Four Main characteristics:

A Central Site is a Configuration MANAGER Primary Site that resides at the TOP of the Configuration Manager hierarchy. All Database information rolls from the child to the parent and is COLLECTED by the Central Site’s Configuration Manager Database. The Central Site can administer any site below it in the hierarchy and can send data down to those sites as WELL.

A Central Site is a Configuration Manager Primary Site that resides at the top of the Configuration Manager hierarchy. All Database information rolls from the child to the parent and is collected by the Central Site’s Configuration Manager Database. The Central Site can administer any site below it in the hierarchy and can send data down to those sites as well.

Manages clients in well-connected networks. Four MAIN characteristics:

• The Site has access to a Microsoft SQL Server DATABASE.
• Can administer or be administered via the CONFIGURATION MANAGER Console
• It can be a child of other Primary SITES and can have Child Sites of its own
• Clients can be assigned directly to the Site

Manages clients in well-connected networks. Four main characteristics:

The SMS Provider is a WMI provider that ALLOWS both read and write access to the Configuration MANAGER 2007 site database. The SMS Provider is used by the Configuration Manager console, Resource Explorer, tools, and custom scripts used by Configuration Manager 2007 ADMINISTRATORS to access site information stored in the site database. The SMS Provider also helps ensure that Configuration Manager 2007 object security is enforced by only returning site information that the USER account running the Configuration Manager console is authorized to VIEW.

The SMS Provider is a WMI provider that allows both read and write access to the Configuration Manager 2007 site database. The SMS Provider is used by the Configuration Manager console, Resource Explorer, tools, and custom scripts used by Configuration Manager 2007 administrators to access site information stored in the site database. The SMS Provider also helps ensure that Configuration Manager 2007 object security is enforced by only returning site information that the user account running the Configuration Manager console is authorized to view.

System Center Configuration MANAGER (CM12 or CM07 or ConfigMgr or Configuration Manager), formerly Systems Management Server (SMS), is a systems management software product by Microsoft for managing large groups of Windows-based computer systems. Configuration Manager PROVIDES remote control, patch management, software distribution, operating system deployment, network access PROTECTION, and hardware and software inventory.

System Center Configuration Manager (CM12 or CM07 or ConfigMgr or Configuration Manager), formerly Systems Management Server (SMS), is a systems management software product by Microsoft for managing large groups of Windows-based computer systems. Configuration Manager provides remote control, patch management, software distribution, operating system deployment, network access protection, and hardware and software inventory.

Configuration Manager Boundaries are defined in the Configuration Manager console and are defined by IP subnet, Active Directory site name, IPv6 Prefix, IP ranges. Boundaries are used to ASSIGN clients to a SPECIFIC Configuration Manager 2007 site and should be unique to each site. When DEFINING site boundaries for sites, ensure that you do not define the same BOUNDARY for more than one Configuration Manager 2007 site, doing so leads to a situation called overlapping site boundaries.

Configuration Manager Boundaries are defined in the Configuration Manager console and are defined by IP subnet, Active Directory site name, IPv6 Prefix, IP ranges. Boundaries are used to assign clients to a specific Configuration Manager 2007 site and should be unique to each site. When defining site boundaries for sites, ensure that you do not define the same boundary for more than one Configuration Manager 2007 site, doing so leads to a situation called overlapping site boundaries.

Discovery Data Records:-

When Discovery runs, it creates discovery data records (DDRs). The information contained in a DDR varies depending upon the discovered resource. For example, it can include the NetBIOS NAME of a computer, the IP address and IP subnet of a computer or device, and the computer operating system name. 

The approximate size of an individual DDR is 1 KB. Discovery Methods:-

1. Active Directory System Discovery – Discovers computers from the specified locations in Active Directory Domain Services.
2. Active Directory User Discovery - Discovers user accounts from the specified locations in Active Directory Domain Services.
3. Active Directory SECURITY Group Discovery - Discovers security groups, including local, global, and universal groups from the specified locations in Active Directory Domain Services.
4. Active Directory System Group Discovery – Discovers additional information about previously discovered computers from the specified locations in Active Directory Domain Services. This information includes the OU and group membership of the computer. Active Directory System Group Discovery does not discover information about new resources that did not previously exist in the Configuration Manager site database.
5. Heartbeat Discovery – USED by active Configuration Manager clients to update their discovery records in the database. Because it is initiated by an active client, Heartbeat Discovery does not discover new resources.
6. Network Discovery – Searches your network infrastructure for network devices that have an IP address. This allows you to discover devices that might not be found by other discovery methods, including PRINTERS, routers, and bridges.
7. Forest Discovery – SCCM 2012 has a new discovery method which discovers other forest in the network.

Discovery Data Records:-

When Discovery runs, it creates discovery data records (DDRs). The information contained in a DDR varies depending upon the discovered resource. For example, it can include the NetBIOS name of a computer, the IP address and IP subnet of a computer or device, and the computer operating system name. 

The approximate size of an individual DDR is 1 KB. Discovery Methods:-

1. Active Directory System Discovery – Discovers computers from the specified locations in Active Directory Domain Services.
2. Active Directory User Discovery - Discovers user accounts from the specified locations in Active Directory Domain Services.
3. Active Directory Security Group Discovery - Discovers security groups, including local, global, and universal groups from the specified locations in Active Directory Domain Services.
4. Active Directory System Group Discovery – Discovers additional information about previously discovered computers from the specified locations in Active Directory Domain Services. This information includes the OU and group membership of the computer. Active Directory System Group Discovery does not discover information about new resources that did not previously exist in the Configuration Manager site database.
5. Heartbeat Discovery – Used by active Configuration Manager clients to update their discovery records in the database. Because it is initiated by an active client, Heartbeat Discovery does not discover new resources.
6. Network Discovery – Searches your network infrastructure for network devices that have an IP address. This allows you to discover devices that might not be found by other discovery methods, including printers, routers, and bridges.
7. Forest Discovery – SCCM 2012 has a new discovery method which discovers other forest in the network.

Native Mode: More secure solution than mixed mode because it PROVIDES better authentication, encryption, and signing using standard industry security PROTOCOLS. Supports Internet-based client management and Can integrate with EXISTING PKI deployment.

Mixed Mode: Does not require a PKI deployment, so it has no external dependencies. Supports clients running SMS 2003. Supports WINS for the means by which clients locate their default management point if Active Directory and DNS cannot be used.

Native Mode: More secure solution than mixed mode because it provides better authentication, encryption, and signing using standard industry security protocols. Supports Internet-based client management and Can integrate with existing PKI deployment.

Mixed Mode: Does not require a PKI deployment, so it has no external dependencies. Supports clients running SMS 2003. Supports WINS for the means by which clients locate their default management point if Active Directory and DNS cannot be used.

Site Server: The site server is the computer on which you install Configuration Manager 2007 or 2012, and it HOSTS services required for Configuration Manager.

Site SYSTEM: A site system is any computer running a supported version of Microsoft Windows or a shared folder that hosts one or more site system ROLES.

Site System Role: A site system role is a FUNCTION required to be able to use Configuration Manager 2007 or to use a feature of Configuration Manager.

Site Server: The site server is the computer on which you install Configuration Manager 2007 or 2012, and it hosts services required for Configuration Manager.

Site System: A site system is any computer running a supported version of Microsoft Windows or a shared folder that hosts one or more site system roles.

Site System Role: A site system role is a function required to be able to use Configuration Manager 2007 or to use a feature of Configuration Manager.

1. CAS (Central ADMINISTRATION site):- The central administration site coordinates inter site data replication across the hierarchy by using Configuration Manager Database replication. It also enables the administration of hierarchy-wide configurations for client agents, discovery, and other operations. Use this site for all administration and reporting for the hierarchy.
2. Primary Site: Manages clients in well-connected NETWORKS.
3. Secondary site: Controls CONTENT distribution for clients in remote locations across LINKS that have limited network bandwidth.

1. CAS (Central administration site):- The central administration site coordinates inter site data replication across the hierarchy by using Configuration Manager Database replication. It also enables the administration of hierarchy-wide configurations for client agents, discovery, and other operations. Use this site for all administration and reporting for the hierarchy.
2. Primary Site: Manages clients in well-connected networks.
3. Secondary site: Controls content distribution for clients in remote locations across links that have limited network bandwidth.

Primary Site: Manages clients in well-connected networks. 
SECONDARY site: Controls content distribution for clients in remote LOCATIONS across links that have LIMITED network bandwidth. 
Parent Site: It is a site at the top LEVEL in the hierarchy & it does not come under any other sites. 
Child Site: A site which comes under a site in a structure & gets information from that site (Higher Level) KNOWN as child site.

Primary Site: Manages clients in well-connected networks. 
Secondary site: Controls content distribution for clients in remote locations across links that have limited network bandwidth. 
Parent Site: It is a site at the top level in the hierarchy & it does not come under any other sites. 
Child Site: A site which comes under a site in a structure & gets information from that site (Higher Level) known as child site.