Explore topic-wise InterviewSolutions in .

The branch distribution points cannot operate if they can't download content from the standard distribution POINT. Branch distribution points are instructed to download packages that have been assigned using client policies, then they download the content using standard client components. If the standard distribution point is configured as a protected SITE system, make sure the branch distribution point is INCLUDED within the protected boundaries. As LONG as the computer running the branch distribution point is not included in the protected boundary of the standard distribution point, BDP cannot install the packages it needs. As an example, here is a LAYOUT for a branch distribution point: 

Having multiple BDPs at the same location will help distribute requests from clients to download package source files. As long as all these branch distribution points have the same protected boundaries, they effectively work together as a group or unit. 

The following are the Objects that can migrate/transfer from CM 2007 to SCCM 2012: 

• Virtual APPLICATION Packages 
• Package Distributing software 
• Collections and Boundaries 
• Configuration baseline 
• Configuration items 
• Software Update DEPLOYMENT Templates 
• Task sequences

In the Inventory module, you can view comprehensive DETAILS of the hardware and software of every WINDOWS system on the network. Inventory in SCCM can be divided into the following: 

• Hardware inventory: By using hardware inventory, you can GATHER data about the hardware configurations of clients' VIRTUAL machines in your entire organization.  
• Software inventory: Software inventory can provide information about files on client devices. It can also record and analyze data from client devices on the SITE server.

With System Center Configuration Manager 2012, a NEW CONCEPT called the content library was introduced. In short, the content library stores everything related to Configuration Manager efficiently on the disk (DISTRIBUTION point). Whenever the same FILE appears in two different packages, the content library only stores one COPY of that file. There are, however, references indicating the file belongs to both packages. The content library is referred to as the "single-instance store" since it contains only one instance of any file. By introducing the content library, we are maximizing storage space and avoiding the distribution of files that are already distributed on the distribution point, so we conserve bandwidth on the WAN. 

Microsoft defines a boundary as a network location on the intranet that can contain multiple DEVICES that you want to manage. Boundary groups are basically the logical groups of BOUNDARIES. Any number of boundary groups can be included in a hierarchy. Each boundary group may contain any combination of the following types of boundaries: 

• IP subnet 
• IPv6 PREFIX 
• Active DIRECTORY site name 
• IP address range 
• VPN

A client on the intranet first evaluates its current network location and then uses this location to determine which boundary groups they belong to.

The PORTS mostly used in SCCM are as FOLLOWS: 

• TCP 2701 
• Default HTTPS port 443 
• Client to site system HTTP port 80 
• SMB 445

LOG files are basically DATA files containing information about usage patterns, applications, and operations within an operating system, application, server, or other devices. Troubleshooting and fixing issues are EASIEST when you have the SCCM logs. These are generated on both the client and site servers. The client and server components maintain INDIVIDUAL log files for logging/recording process information.  You can IDENTIFY SCCM log files with the .log or .lo_ extensions. 

SCCM administrators are those who supervise and manage the use and control of Systems Center Configuration Manager within a business, ensuring that it is USED in the correct way and that it does everything it should.    

SCCM administrator roles and responsibilities:

• An SCCM administrator should have a complete understanding of the operating system they are working with and should ensure that all systems are working smoothly alongside one another.  
• Their responsibilities include deploying DRIVERS updates, BIOS updates for a range of different models, maintaining configuration baselines, preventing configuration drift, assisting and collaborating with all other teams, and many more within the COMPANY to achieve these objectives.  
• SCCM administrators must perform updates when NEEDED, utilizing patches and new builds as necessary to ensure MAXIMUM security and usability. 

SMS Providers are essentially WMI (Windows Management Instrumentation) providers that provide read and write ACCESS to Configuration MANAGER databases. Configuration Manager administrative USERS are able to access information stored in a database by using the SMS Provider. It enables access and modifies Configuration Manager data. There MUST be at least one SMS provider per CAS and primary site. More providers can be installed as necessary. SECONDARY sites do not support SMS providers.

When the Configuration Manager client (software) is installed on your Windows devices, you can monitor their health and activity in the Configuration Manager console. Configuration Manager provides DIFFERENT types of information on the client status, such as client checks, client activity, client ONLINE status, etc. Generally, a Client CHECK describes the status of the periodic evaluation CARRIED out by the Configuration Manager client on the DEVICE. This evaluation can identify some of the problems with the device and remediate them if necessary.

SCCM provides SEVERAL client deployment/installation options, including:   

• Client push installation: This allows you to automatically install the client SOFTWARE on a computer, or on a group of COMPUTERS.
• Manual installation: This allows you to install the client software manually on computers using CCMSetup.exe.
• Group policy installation: This allows users to access the client software under Add or Remove Programs in the Control Panel and install it from there.
• Software update point-based installation: In the case of client software installed on a computer, the computer receives client policies from the site. The policy states the name and port of the software update-point SERVER from which one can obtain software updates.
• Logon script installation: The login script installation is similar to the manual installation. The /logon installation parameter can be specified for CCMSsetup.exe. Whenever a client version is already installed on a computer, this parameter PREVENTS its installation.

No, the SECONDARY site cannot be changed to the PRIMARY site. CHANGING, MOVING, or upgrading a site requires DELETING and reinstalling the site again. Data may be lost when a site is reset. 

It is not POSSIBLE for the SECONDARY SITE to have child sites, since the secondary sites are ALWAYS child sites to the primary sites. 

The following DIFFERENCES exist between the PRIMARY and Secondary sites in SCCM: 

The SCCM Architecture describes the functionalities and how it can run on different operating systems. Here is a diagram showing the SCCM architecture: 

Following are the key components of SCCM system configuration: 

• CAS (Central Administration Site): A CAS or central site is the primary site of SCCM and is located at the top of the configuration manager HIERARCHY. Additionally, it is referred to as the top-level site in the order. Besides providing a central point of administration, it allows you to MANAGE devices that are distributed throughout a global network. In CAS, only primary sites are supported as CHILD sites, and a single CAS can support 25 child primary sites so as to extend the scale of your hierarchy. This configuration is NECESSARY because a CAS cannot manage devices DIRECTLY, which is what primary sites do. CAS is used primarily for reporting and administration purposes.
• Primary site: The site is used to manage devices directly as well as manage bandwidth when your managed devices are distributed across different locations. Almost every client is connected to the primary site. Here, it should be noted that a primary site can only support child secondary sites. Each primary site is capable of supporting up to 250 secondary sites and the hierarchy of more than 100,000 clients.
• Secondary site: Secondary sites should be installed as child sites beneath primary sites. It is used to deliver management capabilities to devices in locations that do not have a reliable connection to a primary site. Despite the fact that a secondary site generally extends the primary site, it is still the primary site that manages all clients. In order to manage secondary sites, primary site servers are used. Each secondary site has its own SQL database server (SQL Express) that helps establish the connection between clients and primary site servers. Secondary site servers support 5,000 client hierarchies, and they also deploy SCCM clients.
• Distribution point: The distribution point helps the client systems obtain the content (files) necessary for installations (Packages, Applications, OS, Driver Packages, etc.). This can be either a local or remote distribution point. Distribution points can support up to 4,000 clients, and by default, primary sites and secondary sites are also distribution points.

Following are some of the major features offered by System Center CONFIGURATION Manager (SCCM):  

• Operation System Deployment: SCCM provides an organization with all the tools it needs to deploy an operating system to client computers in a network - either via an image installation or via a scripted installation.
• Patching & Updating of OS: After installing the operating system successfully, SCCM starts patching and updating the systems. WSUS is used in most organizations to patch and update servers. SCCM, however, leverages WSUS' advantages and provides IT, administrators, with active patching in addition to WSUS.
• Asset TRACKING: Following the installation of a required operating system and any subsequent updates or patches, such systems must be kept up to date with further timely updates or patches. With SCCM, you can keep track of the hardware and SOFTWARE assets of the system.
• Remote Control: Whenever a user or system encounters an issue requiring further assistance from an IT administrator, they can remotely access the system to assess the issue. Using SCCM's remote-control feature, IT administrators and support engineers can access the system remotely.
• Reporting: SCCM COMES with a report generation tool that can generate reports based on the criteria outlined by the IT administrators. There are different types of reports based on what is required, such as reports of missing patches or updates, reports of standard configurations, inventory reports, etc.
• Internet Client: SCCM is a truly powerful tool that enables remote access to devices like mobile devices or remote systems without necessarily bringing them into the VPN network. Now, this can be done via an Internet client and an installed PKI (Public Key Infrastructure) certificate. These prerequisites will enable SCCM to AUTOMATICALLY connect to that system anywhere in the world to inventory, patch, update, and monitor it.
• Desired Configuration Management (DCM): It is the feature that complies with the IT guidelines laid down by an organization, and the standard configuration of a system cannot be modified/altered. With DCM, you can ensure that your managed systems are compliant with key configuration settings that are important to your organization. It ensures that all systems have the same software setup, drivers, updates, and configuration settings.