Microsoft System Center Operations Manager 2012 R2 (((Basics)))

In This post we will go through the very basic definitions and concepts  SCOM  , if you are new to scom this post is definitely for you, every thing in this post is from TechNet (Best reference ever) …     lets start.

 

What is SCOM?

Operations Manager is a part of Microsoft System Center 2012 family, SCOM is software that helps you monitor services, devices, and operations for many computers from a single console.

 

What Operations Manager Does

We all agree that IT departments need to know when there is a problem, identify where the problem is, and figure out what is causing the problem, ideally before the users of the applications encounter the problems. The more computers and devices in the business, the more challenging this task becomes.

Using Operations Manager in the environment makes it easier to monitor multiple computers, devices, services, and applications. The Operations console, shown in the following image, enables you to check the health, performance, and availability for all monitored objects in the environment and helps you identify and resolve problems.

System center configuration manager 2012 R2 (Part 12) Operating System Deployment 2/2

During the last part we have seen how to prepare our environment for OS deployment and how to capture OS we are using as reference image for the deployment .

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

NOTE:

Configuration we did during the last part of our series is only the SCCM related configuration

there is others related to DHCP and Network

DHCP:

Options 66 and 67 must be configured so that a PXE client can locate the PXE point and boot into Windows PE using our boot images

Option 66 is the PXE server name or IP

Option 67 is the file name “SMSBoot\x64\wdsnbp.com”

Network:

If your PXE Client “booting computer” and the PXE enabled DP are not in the same subnet , you have to configure IP Helper on your switch

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

Will continue by creating a new device collection for which the operating system is going to be deployed., Right click on Device Collections, click Create Device Collection.

    

System center configuration manager 2012 R2 (Part 11) Operating System Deployment 1/2

During this first part of SCCM2012 R2 OSD we will see how to prepare our SCCM for OSD an how to capture our customized OS to use it in the next post as a reference image.

System center configuration manager 2012 R2 (Part 10) Migration from SCCM 2007

You already know that there is no in place upgrade from the old SCCM2007 to 2012 what if you had an existing SCCM 2007 …simply you will build your new SCCM 2012 as we did during the last 9 parts and then migrate you data from the 2007 SCCM.

 

 

 

In Microsoft System Center 2012 R2 Configuration Manager, the built-in migration functionality replaces in-place upgrades of existing Configuration Manager Infrastructure by providing a process that transfers data from active Configuration Manager 2007 sites. Migration can transfer most data from Configuration Manager 2007.

Data That You Can Migrate to Configuration Manager 2012

Migration can migrate most objects from Configuration Manager 2007 to System Center 2012 Configuration Manager. The migrated instances of some objects must be modified to conform to the System Center 2012 Configuration Manager schema and object format. These modifications do not affect the data in the Configuration Manager 2007 database.

You can migrate the following types of objects:

·         Collections

·         Advertisements

·         Boundaries

·         Software distribution packages

·         Virtual application packages

·         Software Updates:

o    Deployments

o    Deployment packages

o    Templates

o    Software update lists

·         Operating System Deployment:

o    Boot images

o    Driver packages

o    Drivers

o    Images

o    Packages

o    Task sequences

·         Desired Configuration Management:

o    Configuration baselines

o    Configuration items

·         Asset Intelligence customizations

·         Software metering rules

System center configuration manager 2012 R2 (Part 9) Adding Distribution Points

Distribution Points are helpful when you have a branch office that has number of clients “less than 500 client” connected through WAN to your HO. You can distribute OS images and software packages through a DP which will reduce latency and bandwidth consumption. Packages will be distributed to the DP over the WAN once and the clients pull it from the local DP over the LAN.

First we need to add the SCCMAdmin account and the SCCM Site Server account to local administrators group on the machine that will be a DP, and open the required ports.

System center configuration manager 2012 R2 (Part 8) Adding Secondary Site

We are going to install one secondary site server for SCCM 2012 R2. Generally installing secondary site is recommended if you have Brach with more 500 clients in a remote location, this might overload the network even with the new 2012 Distribution point’s features. if you need software update point or management point at this branch you shoud go for secondary site too.

First we need to add the SCCMAdmin account and the SCCM Site Server account to local administrators group on the machine .

Prerequisites to Install Secondary Site:

Roles / Role Services Required for Secondary Site:

Web Server (IIS) (Can be done by SCCM)   · Application Development: ISAPI Extensions · Security: Windows Authentication · IIS 6 Management Compatibility: IIS 6 Metabase Compatibility IIS 6 WMI Compatibility Features Required for Secondary Site: ·         Remote Differential Compression ·         BITS . NET Requires both of the following: 3.5 SP1 4.0

System center configuration manager 2012 R2 (Part 7) Reporting

We did install the SQL Reporting Services in part1 to verify it is installed and running correctly, open the Reporting Services Configuration Manager.

Click Connect.

System center configuration manager 2012 R2 (Part 6) Deploying Software Updates 2/2

Automatic Deployment Rules in SCCM 2012 R2

During the first Part Part1 we have added the Software updated point and tried the Manual Software updates … Here comes the fun part

Automatic Deployment rule enables you to create update package automatically according to some criteria such as release date. It is possible for example to create update package automatically every month. Once the package is created, it is automatically deployed..

To create Automatic Deployment Rule, go to Software Library and right click on Automatic Deployment Rule and click on Create Automatic Deployment Rule

System center configuration manager 2012 R2 (Part 6) Deploying Software Updates 1/2

There are two deployment type for software updates using SCCM 2012 R2 (Manual and Automatic). In Manual software updates deployment, a set of software updates is selected from Configuration Manager Console and these updates are deployed to the target collection and Automatic software updates deployment is configured by using automatic deployment rules

…

Add Software Update Point Site System Roles in Configuration Manager 2012 R2

 

First we will install the Software Update Point role. From the Configuration Manager Console, open the Administration workspace, expand Overview, click Site Configuration, and Select on Sites. At the top ribbon click on Add Site System Roles.

System center configuration manager 2012 R2 (Part 5) Deploying Applications 2/2

After we have seen how to create Approval pending applications in SCCM 2012 in the last part  of our series  , in this part we are going to see how to deploy .exe applications and how to deploy Applications that has dependencies.

Deploy .EXE Application

On Application Select Create Application.