System Center Blog By Birojit

Error: “Object reference not set to an Instance of an Object” System Center Operation Manager 2012 Connector.

2012-07-07T02:29:49Z

I was trying to configure a internal connector in SCOM 2012. The console stuck at loading for sometime

After some time it gives the below error

hmmm Error!!!!!

On further troubleshooting I could find there was Operation Manager Alert Connector in SCSM 2012 was some how not configured properly. Trying to delete the connector from the SCSM 2012 and then sync removed the stale connector from the OpsDB.

After removing the Connector I was able to open the Internal Connector

Now on creating the Operation Manager Alert Connector in SCSM 2012, created Connectors with same name of the alert connector in SCOM 2012 in Internal Connector Tab

Configuring the Subscription in the SCOM 2012 Internal Connector helped to create incident in SCSM 2012 when there is alert in SCOM 2012.

Connector sync can be verified from the Event Viewer in SCSM 2012.

Cheers

Birojit

Set Up Self Service Portal SCVMM 2012

2012-01-27T19:46:41Z

Self Service Portal for SCVMM 2012 can help user to Provision the Virtual Machine Based on the Template available to the User.

At the Time of Installing the Self Service Portal please provide the FQDN of the SCVMM 2012 Server Name

System Requirements for VMM Self-Service Portal

Please refer to the System Requirement before deploying Self Service Portal for SCVMM 2012

http://technet.microsoft.com/en-us/library/gg697607.aspx

Support Statement

Installing the VMM Self-Service Portal on a domain controller is not supported.
To use the VMM Self-Service Portal, client computers must be running Internet Explorer 8 or Internet Explorer 9.
For better performance, it is recommended that you install the VMM Self-Service Portal on a separate computer from the VMM management server.

Before you give access to user you need to create Self Service User Role in SCVMM 2012 console

Click in Settings->User Roles:

Click On New User Role

Select Self Service User

Add User or Group as a member of the Self Service User Role

Select the Scope of the Cloud

Select the Quota You want to assign

Select the Action you want to Provide user Access to

Select Run As Account

Click Finish

Browse the Site and try to login to the site

That’s the Place you want to be in……

Cheers

Birojit

Failed to get WebDAV setting on the Machine (0x80070003)

2011-04-22T09:50:31Z

After Installing SCCM 2007 Server on Windows 2008 R2 SP1 was getting the error on MPSetup.log

I could See the WebDAV was installed and Configured

Allow anonymous property queries to True.
Allow Custom Properties to False.
Allow property queries with infinite depth to True.
Allow hidden files to be listed to True.

On Checking the WebDAV_Schema on c:\Windows\System32\inetsrv\schema I could find that it was not on sync.

Changed the value as highlighted from False to True and True to False

WebDAV_Schema file after Modification

Now on Restarting the SMS_SITE_COMPONENT_MANAGER I could see below error

Resolution of the Issue I could find that BITS was Installed but Service was stopped and Startup was manual

On changing the startup to Automatic and Starting the BITS service. Restarting the SMS_SITE_COMPONENT_MANAGER . Installation was Successful…

Cheers

Birojit

Announcing System Center Service Manager 2010 RTM

2010-04-24T21:02:12Z

I wanted to share some good news with you all. Our SCSM 2010 is RTM.

A 180 day Evaluation of the Service Manager 2010 RTM is available right now! Download here.

Enjoy working with the product. Am also making myself comfortable with the product. Will keep you Posted with new resource and finding.

Cheers

Birojit

Error-Unable to load portal ActiveX control. Automation server can't create object. Please contact your administrator regarding any issues

2010-04-15T18:28:28Z

Recently i was working with Service Manager Self Service Portal. When creating request and then selecting Software It gave me following error.

Resolution:

You need to install the portalclient MSI file first. It is on the installation CD.

Cheers

Birojit

SQL Server 2008 Cluster Monitoring Using SCOM 2007 R2

2010-04-14T11:30:08Z

1) Open System Center Operations Manager R2 Operations Console.

2) Open the Administration view, and select Agent Managed under Device Management.

3) Right-Click on the SQL Server 2008 Cluster Nodes and choose Properties.

4) Choose security tab tick on Allow this agent to act as a proxy and discover managed objects on other computers.

5) Press OK.

6) On the Cluster Nodes restart the System Center Management Service.

7) Open the Administration view, and select Agentless Managed under Device Management.

8) You should be able to see Cluster Virtual Servers.

9) Select Windows Server State under Microsoft Windows Server. You should be able to see the all Cluster resource with IP address.

10) Right-Click the Cluster Virtual Servers select Properties.

11) Check line saying “Is Virtual Node” is True

12) Select Database State under Monitoring Tab Select Microsoft SQL Server->Databases-> Database State

Cheers

Birojit

Deploying Remote Operations Manager

2010-03-02T08:10:09Z

Service Provider Management Pack is now available to download. If you are looking to manage the server in your customer datacenter you can try System Center Remote Operation Manager 2007.

Deployment Steps:

Technologies

System Center Remote Operations Manager 2007 makes use of the following technologies:

· System Center Operations Manager 2007 at your service provider data center to provide the top-tier management experience.

· System Center Essentials 2007 at your customer locations as the remote end-point for monitoring the customer’s environment.

· The Service Provider Management Pack to enable remote management tasks from within your installation of Operations Manager 2007.

· Remote Web Workplace to control Windows Server 2003 and Windows XP computers inside the customer’s network in a remote desktop session. For Windows Vista clients, you might need the newest Remote Desktop Protocol Web client (ActiveX control) on the Essentials 2007 Management Server.

Scaling Limitations

Remote Operations Manager 2007 cannot be scaled upward without limitations. It is designed for a single Operations Manager management server to manage customer sites running Essentials 2007 up to the limitations imposed by each individual product.

Scaling Limits

The following list details the scale limitations inherent in Remote Operations Manager 2007.

· The maximum number of agents that can be monitored through one Operations Manager 2007 management server is 2000.

· The maximum number of agents that can be monitored through one gateway management server is 530.

Deploying Remote Operations Manager with Operations Manager 2007 Service Pack 1 and Essentials 2007 Service Pack 1

If you are deploying Remote Operations Manager 2007 for the first time with Operations Manager 2007 SP1 and Essentials 2007 SP1, use the Remote Operations Manager 2007 Deployment Guide for guidance. However, if you have already deployed Remote Operations Manager 2007 using the RTM versions of each underlying product, upgrade the components to Service Pack 1 in the following order:

Upgrade Operations Manager 2007 infrastructure (RMS, DW, MS and Gateways) according to the Operations Manager 2007 SP1 Upgrade Guide.
Upgrade Operations Manager 2007 consoles.
Upgrade the Essentials 2007 management server to Service Pack 1 at each customer site according to the Essentials 2007 Upgrade Guide.
Upgrade agents at each customer site that has its Essentials 2007 management server upgraded using pending actions in Operations Manager 2007 console.
Upgrade agents at each customer site that has its Essentials 2007 server upgraded using pending actions in Essentials 2007 console.
Upgrade any remote Essentials 2007 consoles.

Remote Operations Manager 2007 Deployment Guide and RelNotes

http://www.microsoft.com/downloads/details.aspx?FamilyID=4b621eb7-01bb-45f5-9a77-52853f06eec9&DisplayLang=en

Service Provider Management Pack

Import the Service Provider Management Pack into Operations Manager 2007 to enable its service provider capabilities

The Service Provider Management Pack is provided as example for how to provide remote monitoring using System Center Operations Manager. The management pack defines a ‘customer’ class and includes example tasks to discover and administer customer sites. The example tasks only work with System Center Essentials 2007 servers in Service Provider mode. The management pack will need to be edited to work with Operations Manager gateway management server.

You can download the Service Manager Management Pack from

http://pinpoint.microsoft.com/en-US/PartnerDetails.aspx?PartnerId=4297702754&ProductId=12884904038&CurrentTab=1

Cheers

Birojit Nath

How to Configure Asset Intelligence for License Tracking report

2010-03-02T06:37:05Z

Step1) Create the CSV file as shown in the screenshots below

Step 2) Logon to SCCM 2007 Server and import the CSV File.

Run License 15 A to get the report

Open Configuration.mof file using notepad and edit below parameter to track the CAL usage

Sample Reports

Cheers

Birojit

How to Create Slip Stream Media

2010-02-12T17:49:56Z

Hi friends

Many of us wanted to know how can we create Slip Stream Media for SQL 2008 with SP1.

I found a very good article which has very good explanation of steps.

Wanted to broaden to larger audience.

Thanks Peter for the contribution.

http://blogs.msdn.com/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx

Cheers

Birojit

Microsoft® System Center Configuration Manager 2007 Dashboard

2010-02-06T18:35:18Z

Hi Friends …..

IT administrators and IT support staff need easier access to key information about software and operating system deployments, client health, and compliance with regulations. They must ensure that their systems and software meet the configuration requirements established for the organization. And they need the ability to track this information without having access to a System Center Configuration Manager console

How the Dashboard Works

The Configuration Manager Dashboard is designed to work with an existing Configuration Manager 2007 infrastructure. The Dashboard queries the Configuration Manager site database and uses the resulting data set to present key infrastructure metrics in a graphical format.

The Configuration Manager Dashboard uses SharePoint Web parts to manage and display data sets:

Microsoft Dashboard Configuration Web Part. Use this Web part to create and modify the SQL queries that produce the data sets and the other properties that govern how the Dashboard displays the data sets.
Microsoft Dashboard Viewer Web Part. Use this Web part to display the data sets. A Dashboard Viewer Web Part displays one data set at a time. The Configuration Manager Dashboard can contain multiple copies of the Dashboard Viewer Web Part at once, each copy displaying a different data set.

The following figure shows how users can interact with the Web parts to retrieve and display data.

Figure 1. Configuration Manager Dashboard Process Flow

The Configuration Manager Dashboard process flow involves the following sequence of activities:

An IT Service Manager requests a new data set.
The IT Administrator uses the Dashboard Configuration Web Part to define the new data set.
The IT Administrator stores the configuration information for the new data set (the information is saved in the Windows SharePoint Services Content database).
The IT Administrator adds a new copy of the Dashboard Viewer Web Part to the default Configuration Manager Dashboard and then modifies the Web part to display the new data set.
The IT Service Manager browses to the Configuration Manager Dashboard site.
Windows SharePoint Services queries the Configuration Manager site database as specified by the data set configuration.
Windows SharePoint Services renders the new data set using the Dashboard Viewer Web Part.

Join the Beta Program for the Dashboard

The Configuration Manager Dashboard is now in Beta release (English only). Click here to join the beta.

Link: https://connect.microsoft.com/InvitationUse.aspx?ProgramID=4505&InvitationID= SCD-BGMB-FK9M&SiteID=14

Further Ref:http://technet.microsoft.com/en-us/library/ff369719.aspx

I will Keep you Posted on the configuration Steps Soon…

Cheers

Birojit

Introducing Microsoft System Center Essentials 2010

2010-01-20T18:41:18Z

Overview

Microsoft System Center Essentials 2010 provides a unified management solution that enables IT professionals in midsize organizations to proactively manage their IT environment. Features include monitoring computers, deploying software and updates, and virtualization management.

Download Deployment Guide

Download SCE 2010 RC

Announcing System Center Configuration Manager 2007 R3

2010-01-20T18:28:31Z

This latest release of System Center Configuration Manager will help customers reduce their operational costs by providing flexible, centralized power management planning and application.

http://blogs.technet.com/systemcenter/archive/2009/09/08/announcing-system-center-configuration-manager-2007-r3.aspx

Windows 7 Deployment Using SCCM 2007 SP2

2010-01-20T17:31:44Z

Upgrade SCCM 2007 SP1 to SP2

Step1: Uninstall the Windows Automated Installation Kit (AIK) version 1.1 from the SMS Provider computer and then restart the computer before beginning the upgrade process.

Step2: Insert SP2 Media on SCCM 2007 Server. And run Setup.exe

Figure 1

Step 3: Select Upgrade option

Figure 2

Step 4: Select the Patch where you want to download the Updates and click on next

Step 5: Click Next

Step 6: On Successful download of Updates Click on Next

Step 7: Click on Begin Install

Step 8: On Successful Installation click on Next

Step 9: Click on Finish to Complete SCCM 2007 SP2 Upgrade

On Successful upgrade to SCCM 2007 SP2 you can run R2 to get some additional functionality

The following features are new to Configuration Manager 2007 R2:

Application Virtualization Management. For more information about managing virtual applications created using the Microsoft Application Virtualization platform
Forefront Client Security Integration. For more information, see About Forefront Client Security Integration with Configuration Manager 2007 R2.
SQL Reporting Services Reporting. Allows you to report on Configuration Manager activity using SQL Reporting Services.
Client Status Reporting. Provides a set of tools and Configuration Manager 2007 reports to assess the status of client computers, sometimes referred to as "client health." Clients that show a change in activity patterns might need administrative intervention.
Operating System Deployment Enhancements. The following enhancements are included in Configuration Manager 2007 R2:
- Unknown computer support—In Configuration Manager 2007 R2, you can deploy operating systems to computers using a PXE service point without first adding the computer to the Configuration Manager database.

For more information, see About Unknown Computer Support for Operating System Deployment.

Multicast deployment—Previously, all operating system deployments used unicast. Multicast can make more efficient use of network bandwidth when deploying large images to several computers at the same time.

For more information, see About Multicast for Operating System Deployment.

Running command lines in task sequences with credentials other than the local system account

Operating System Deployment Using SCCM 2007

Step 1: Install WDS on SCCM 2007 Server or on Different Server. On Successful Installation Configure WDS Server

Step 2:

Once WDS is Configured Click on the

Configure DHCP Server and If DHCP and WDS are in Same box then click on Check box marked in red. If DHCP and WDS are in different box uncheck both the box below and configure DHCP Option 66 and 67.

If WDS is installed on Different Server in SCCM 2007 Server Console Add the Server and Assign PXE Service Point.

If SCCM 2007 and WDS is running on the Same Server then Assign PXE Service point role on the SCCM 2007 Server.

To Confirm Successful Installation of PXE Service Point please confirm on PXE Setup.log c:\Program Files\Microsoft System Center Configuration Manager \logs

Enable Unknown Computer Support on PXE Service Point. Right Click on ConfigMgr PXE Service Point and click on properties

Injecting Drivers

Download Drivers and install on a folder. From SCCM 2007->Operating System Deployment->Click on Drivers ->Import

Click on Next

Select the Drivers if you want to inject in Boot Images.

Once completed you will be able to see drivers in Drivers Tab

To Inject Drivers in the boot Images Right Click on Boot Images->Properties->Windows PE tab.

To Categories the Drivers Click on Drivers->Select the drivers

Click On Categories and Create your Own Category.

Boot Images:

Add Distribution Point on the Boot Images. Click on the Distribution point Tab->New Distribution Point ->Server Share as Shown in Screen Shots Below.

Note: on Successful Configuration of PXE Service Point You will see the Server share in Distribution point List

Add Operating System Images

1) Right Click on Operating System Image ->Add Operating System Image->Select the Path for the WIM File.

2) On Successful addition of Image Close the Tab

3) Add Distribution Point to the OS package.

Create Package for SCCM 2007 Client

Add Distribution Point to the package

Create Task Sequence

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Operating System Deployment / Task Sequences.

To start the New Task Sequence Wizard, right-click the Task Sequences node, and then click New/Task Sequence.

2. On the Create a New Task Sequence page, select Install an existing image package, and then click Next.

3. On the Task Sequence Information page, specify a descriptive name for the task sequence, and then add an optional comment. To specify the boot image that will be associated with the task sequence, click Browse to open the Select a Boot Image dialog box, select the boot image, and then click Next.

Important

The boot image you specify must match the chip architecture installed on the target computer or the task sequence will fail

4. On the Install the Windows Operating System page, specify the operating system image package that will be used to install the operating system image by clicking Browse button to open the Select an Operating System Image dialog box, and then selecting the operating system package. If there are multiple images in the image package, use the drop-down to specify the Image that should be associated with the image package. To partition and format the target computer's hard disk prior to installing the operating system image, select the Partition and format the target computer before installing the operating system check box.

Important

Do not select the option to format and partition the target computer hard disk if you have saved the user state locally or the saved user state will be erased. For more information about saving the user state locally on the target computer for in-place operating system deployment scenarios

5. Additionally, on the Install the Windows Operating System page, specify the Windows Product key and Server license mode. If you specify Per server as the license mode, configure the Maximum server connections that will be permitted. You must also specify if the local administrator account should be disabled, or if you want to use the same administrator account for all target computers by selecting the appropriate option. Click Next

6. On the Configure the Network page, specify if the target computer will join a Workgroup or a Windows Domain.

If you are adding the target computer to a Workgroup, you must type the name of the workgroup in the space provided.
If you are adding the target computer to a Windows domain, click the Set button to open the Windows User Account dialog box and specify the user account and password that should be used to add the computer to the Windows domain. You must also specify the name of the Windows Domain and Windows Domain OU that the target computer will be added to by clicking the Browse button. Click Next

7. On the Install ConfigMgr page, click the Browse button to launch the Select a Package dialog box and select the Configuration Manager 2007 package that will be used to install the Configuration Manager 2007 client. Specify the Configuration Manager 2007 client installation properties that will be used in the Installation properties window. Click Next

8. On the Include Updates in Image page specify how the target computer will install assigned software updates by selecting the appropriate option.

9. On the Install Software Packages page, click New to open the Program Select dialog box. Click Browse to open the Select a Package dialog box. Select the Configuration Manager 2007 packages you want to include, and then click OK. Use the drop down to select the associated programs that should be used.

10. To complete the creation of the new task sequence, on the Summary page, click Next.

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Operating System Deployment / Task Sequences.

To start the Task Sequence Editor, select the task sequence you want to update, right-click the task sequence, and then click Edit.

To partition the hard drive select the partition disk tab in the task sequence. Select the highlighted section

Give partition name and partition type. And press OK

Task Sequence Advertisement

Right Click on Task Sequence and click on advertise

Please Tick on Make this Task Sequence Available to Boot Media and PXE

Click on Next

Click on Next to Finish

To verify the Advertisement click on the collection->Properties and select Advertisement Tab

Boot the Computer from Network

Cheers

Birojit

Monitoring Linux Using SCOM 2007 R2

2010-01-20T17:18:01Z

SCOM 2007 R2 can help you with out of box functionality to monitor Linux /Unix. With SCOM 2007 SP1 you need to get Management Pack from Quest/Jalasoft to name few partner who had developed MP to monitor Unix/Linux.

With the release of SCOM 2007 R2 Unix and Linux MP come along with product.

To Monitor Linux Server you can follow steps below…….

RunAs accounts that will be used by Operations Manager 2007 to install, and to monitor/manage the target Linux machines. For this, two user accounts are created:

· Non-privileged user, used to remotely monitor the Linux/Unix server.

· Privileged User, used to deploy the Unix/Linux agent, as well as to restart processes where privileged rights are required.

Creating a Non-Privileged UNIX User Run As Profile

1. In the Operations console, click Administration to open up the Administration space

2. Under the Run As Configuration node of the tree, click Profiles

3. In the Profiles pane, look for the Unix Action Account profile. Right-click on Unix Action Account and select Properties. This opens the Run As Profile Wizard

4. At the Introduction screen, click Next >

5. At the General Properties screen, click Next >

6. At the Run As Accounts screen, click Add... to create a new Run As Account. The Add a Run As Account dialog will open. NOTE: If you examine the list of current Run As accounts you will see none for UNIX/Linux, so we have to create one.

7. Click New... to open the Create Run As Account Wizard

At the Introduction screen, click Next >

9. Under the General Properties screen a. Select Basic Authentication from the Run As Account type drop-down list. b. Set the display name to "UNIX non-privileged account"

Click Next >

Provide Credential for Non Privileged Account

Click Next >

Under Distribution Security, select the More Secure... option.

When the creation is complete, you will see a warning message that the Run Account must be associated with an appropriate Run As profile. We will do this in just a moment. Click Close to return to the Add a Run As Account dialog

Click Select ... and choose Class... from the drop down.

In the Class Search dialog, enter Unix in the Filter By text box, and click Search

From the list of items returned from the search, select Unix Computer and click OK

Unix Computer now appears as the selected class against which the Run As Account will be applied. Click OK to close the Add a Run As Account dialog

You will now see the UNIX non-privileged account Run As Account just created within the list of accounts for this profile. Click Save.

We now have to associate the Run As account with the RMS management server. Click on the UNIX non-privileged account hyperlink to open the Run As Account properties.

Check to see you are in the Distribution tab.

Click Add

In the Option: drop down, select Show Management Servers and click Search.

Select RMS Server Name from the results, and click Add

Creating a Privileged UNIX User Run As Profile

In the Profiles pane, look for the Unix Privileged Account profile.

Right-click on Unix Privileged Account and select Properties. This opens the Run As Profile Wizard

At the Introduction screen, click Next >

At the General Properties screen, click Next >

At the Run As Accounts screen, click Add... to create a new Run As Account. The Add a Run As Account dialog will open.

Click New... to open the Create Run As Account Wizard

At the Introduction screen, click Next >

Select Basic Authentication from the Run As Account type drop-down list . Set the display name to "UNIX privileged account

Under the Account screen Set The credential for Privilege

Click Next >

Under Distribution Security, select the More Secure... option. Click Create.

Notice that the UNIX privileged account you just created now appears as the selected option in the drop down box.

Click Select ... and choose Class... from the drop down

In the Class Search dialog, enter Unix in the Filter By text box, and click Search

From the list of items returned from the search, select Unix Computer and click OK

You will now see the UNIX privileged account Run As Account just created within the list of accounts for this profile. Click Save.

We now have to associate the Run As account with the RMS management server. Click on the UNIX privileged account hyperlink to open the Run As Account properties

Check to see you are in the Distribution tab

Select RMS Server Name from the results, and click Add and Click OK

Open the Operations console with an account that is a member of the Operations Manager 2007 R2 Administrator profile

Select the Administration view.

At the bottom of the navigation pane, select the Discovery Wizard link.

In the Computer and Device Management Wizard, select Discovery Type, choose Unix/Linux Discovery Wizard, and then click Next.

On the Discovery Method page, click Add to specify criteria for discovering UNIX-based systems and Linux-based systems on your network.

On the Define discovery criteria page, type the credentials and necessary information to locate the computer you want to discover, and then click OK

Enable SSH

Click Discover to initiate system discovery

On the Discovery results page, in the Select the systems you want to manage: list, select the check box for the system or systems that you want to manage, or click Select All to include all discovered systems

If there are systems listed in the Select the systems you want to manage list on the Discovery results page that the wizard was unable to discover, you can click Details to get information about why the discovery failed. Correct the problem and repeat the discovery step

After you have selected the systems you want to manage, click Next to start the deployment, and to close the Discovery results page

On the Deployment complete page, the Computer and Device Management Wizard displays the agent deployment status in the Status menu.

Click Done to close the wizard.

IMPORT MP For Linux

Performance Monitoring by Using Default MP

Active Alert

Health Explorer

Performance Report

Cheers

Birojit