How to change the OpsMgr SDK Service and the OpsMgr Config Service to use a domain account
Before you follow these steps make sure that you have already created the necessary domain account in the Active Directory directory service. Also, we recommend that you back up the Microsoft SQL Server database before you follow these steps.
1.
Click Start, click Run, type services.msc, and then click OK.
2.
In the details pane, right-click OpsMgr SDK Service, and then click Stop.
3.
In the details pane, right-click OpsMgr Health Service, and then click Stop.
4.
In the details pane, right-click OpsMgr Config Service, and then click Stop.
5.
Right-click OpsMgr SDK Service, and then click Properties.
6.
On the Log On tab, click This account.
7.
Type a domain account in the This account box, type the corresponding password in the Password box, and then re-type the password in the Confirm password box.
8.
Click OK.
9.
Right-click OpsMgr Config Service, and then click Properties.
10.
On the Log On tab, click This account.
11.
Type a domain account in the This account box, type the corresponding password in the Password box, and then re-type the password in the Confirm password box.
Important To start the OpsMgr SDK Service and the OpsMgr Config Service, you must use the same account. Therefore, the account that you specify in step 10 must be same as the account that you specified in step 6.
12.
Click OK.
13.
Close the Services snap-in window.
14.
Click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
15.
In the Connect to Server dialog box, specify the server name and the instance on which the Operations Manager Database is installed.
16.
In the console tree, expand the Database node, right-click Operations Manager Database, and then click New Query.
17.
Type the following SQL statement, and then execute it.
Note The <Domain> placeholder represents the domain name, and the <User> placeholder represents the user account on which you want to run the OpsMgr SDK Service. If the Operations Manager Database is configured to use a case-sensitive collation, you must type the account name exactly as it appears in the Active Directory Users and Computers snap-in.
18.
Type the following SQL statement, and then execute it.
Note The <Domain> placeholder represents the domain name, and the <User> placeholder represents the user account on which you want to run the OpsMgr Config Service. If the Operations Manager Database is configured to use a case-sensitive collation, you must type the account name exactly as it appears in the Active Directory Users and Computers snap-in.
Note: The <Domain> placeholder represents the domain name, and the <User> placeholder represents the Action Account the Management Server is configured to use.
The account being used by the Management Server can be confirmed by examining the Default Action Account Run As Profile in the MOM Operator console.
20.
Start the Services snap-in as you did in step 1.
21.
In the details pane, right-click OpsMgr Health Service, and then click Start.
22.
In the details pane, right-click OpsMgr SDK Service, and then click Start.
23.
In the details pane, right-click OpsMgr Config Service, and then click Start.
24.
Close the Services snap-in window.
25.
Click Start, click Run, type eventvwr.msc, and then click OK.
26.
In the console tree, select the Operations Manager event log, and then examine the event log entries for the OpsMgr SDK Service and for the OpsMgr Config Service to verify that these two services are running correctly.
How to change the OpsMgr SDK Service and the OpsMgr Config Service to use the Local System account if the Management Server and the Database Server roles reside on the same computer
1.
Click Start, click Run, type services.msc, and then click OK.
2.
In the details pane, right-click OpsMgr Health Service, and then click Stop.
3.
In the details pane, right-click OpsMgr SDK Service, and then click Stop.
4.
In the details pane, right-click OpsMgr Config Service, and then click Stop.
5.
Right-click OpsMgr SDK Service, and then click Properties.
6.
On the Log On tab, click Local System account.
7.
Click OK.
8.
Right-click OpsMgr Config Service, and then click Properties.
9.
On the Log On tab, click Local System account.
10.
Click OK.
11.
Close the Services snap-in window.
12.
Click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
13.
In the Connect to Server dialog box, specify the server name and instance on which the Operations Manager Database is installed.
14.
In the console tree, expand the Database node, right-click Operations Manager Database, and then click New Query.
15.
Type the following SQL statement, and then execute it.
Note If the Operations Manager Database is configured to use a case-sensitive collation, you must type the account name exactly as it appears in this SQL statement.
16.
Type the following SQL statement, and then execute it.
Note If the Operations Manager Database is configured to use a case-sensitive collation, you must type the account name exactly as it appears in this SQL statement.
17.
Type the following SQL statement, and then execute it.
Note The <domain> placeholder represents the domain name, and the <managementservercomputer$> placeholder represents the Action Account the Management Server is configured to use. You can examine the Default Action Account Run As Profile entry in the MOM Operator console to confirm the account that the Management Server uses.
18.
Click Start, click Run, type services.msc, and then click OK.
19.
In the details pane, right-click OpsMgr Health Service, and then click Start.
20.
In the details pane, right-click OpsMgr SDK Service, and then click Start.
21.
In the details pane, right-click OpsMgr Config Service, and then click Start.
22.
Close the Services snap-in window.
23.
Click Start, click Run, type eventvwr.msc, and then click OK.
24.
In the console tree, select the Operations Manager event log, and then examine the event log entries for the OpsMgr SDK Service and for the OpsMgr Config Service to verify that these two services are running correctly.
How to change the OpsMgr SDK Service and the OpsMgr Config Service to use the Local System account if the Management Server and the Database Server roles reside on different computers
1.
On the computer that is running the Management Server role, click Start, click Run, type services.msc, and then click OK.
2.
In the details pane, right-click OpsMgr Health Service, and then click Stop.
3.
In the details pane, right-click OpsMgr SDK Service, and then click Stop.
4.
In the details pane, right-click OpsMgr Config Service, and then click Stop.
5.
Right-click OpsMgr SDK Service, and then click Properties.
6.
On the Log On tab, click Local System account.
7.
Click OK.
8.
Right-click OpsMgr Config Service, and then click Properties.
9.
On the Log On tab, click Local System account.
10.
Click OK.
11.
Close the Services snap-in window.
12.
On the computer that is running the database server role, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
13.
In the Connect to Server dialog box, specify the server name and the instance on which the Operations Manager Database is installed.
14.
In the console tree, expand the Database node, right-click Operations Manager Database, and then click New Query.
15.
Type the following SQL statement, and then execute it:
Replace <managementserverdomain\managementservercomputer$> with the domain and with the computer account. For example, replace <managementserverdomain\managementservercomputer$> with Contoso\Opsmgr01$.
Note If the Operations Manager Database is configured to use a case-sensitive collation, you must type the account name exactly as it appears in this SQL statement.
16.
Type the following SQL statement, and then execute it:
Replace <domain\managementservercomputer$> with the domain and with the computer account. For example, replace <domain\managementservercomputer$> with Contoso\Opsmgr01$.
Note If the Operations Manager Database is configured to use a case-sensitive collation, you must type the account name exactly as it appears in this SQL statement.
17.
Type the following SQL statement, and then execute it:
Note The <domain> placeholder represents the domain name, and the <managementservercomputer$> placeholder represents the Action Account that the Management Server is configured to use. You can examine the Default Action Account Run As Profile entry in the MOM Operator console to confirm the account that the Management Server uses.
18.
On the computer that is running the Management Server role, click Start, click Run, type services.msc, and then click OK.
19.
In the details pane, right-click OpsMgr Health Service, and then click Start.
20.
In the details pane, right-click OpsMgr SDK Service, and then click Start.
21.
In the details pane, right-click OpsMgr Config Service, and then click Start.
22.
Close the Services snap-in window.
23.
Click Start, click Run, type eventvwr.msc, and then click OK.
24.
In the console tree, select the Operations Manager event log. Examine the event log entries to verify that the OpsMgr SDK Service and the OpsMgr Config Service services are running correctly.
How to change the Management Server Action Account
Before you follow the steps that are described in this section, we recommend that you do the following:
•
Make sure that you have already created the necessary account in Active Directory or on the local computer.
•
Make sure that you have created all necessary new Run As Accounts of the Action Account type by using the Create Run As Account Wizard.
Note For more information about an issue that may occur when you create Run As Accounts, click the following article number to view the article in the Microsoft Knowledge Base:
936221 (http://support.microsoft.com/kb/936221/) The Run As Account that you create in System Center Operations Manager 2007 or in System Center Essentials 2007 does not run a task successfully
1.
Click Start, point to Programs, point to System Center Operations Manager 2007, and then click Operations Console.
2.
Select the Administration view, expand Administration, expand Security, click Run As Profiles, right-click Default Action Account in the Run As Profiles pane, and then click Properties.
3.
Click the Run As Accounts tab.
4.
In the Run As Accounts list, select the computer on which you want to change the action account, and then click Edit.
5.
In the Run As Accounts list, select a domain account or Local System Action Account, and then click OK.
6.
Click OK to close the Run As Profiles Properties dialog box.
Note These steps change the Management Server Action Account. If you change the Management Server Action Account from a domain account to the Local System account, this operation may affect some actions that are performed by the Management Server. Such actions include the following:
From time to time I find it useful to schedule tasks to run on my machine. I often realize that many people are unaware that windows 2003 has a built in task scheduler; and even more of a rarity for them to be aware it can be managed via the command line.
In the past I would crate a batch file to create the schedules; just to make it easy and repeatable. Having the setup separate from the batch file that does the work always bugged me.
The other day I when I found the need to have a task run every five minutes, I did it in powershell. I thought to myself hey this is powershell, we’ve got some more power here; what if this script could schedule it’s self? And that’s how this idea was born.
When run without parameters it executes normaly. Specify the -schedule switch to have it schedule itself. For details on schtasks options see: http://support.microsoft.com/kb/814596/
Boris Yanushpolsky in the OpsMgr product team has made a tool to look at overrides in Ops Mgr 2007. You ar with this tool able to browse overrides based on type or computer. get the tool here
System Center Operations Manager 2007 includes a script library that you can use to create custom runtime scripts. When they are added to a Management Pack, these scripts allow you to do the following:
Discover class instances that you want to monitor.
Create monitoring data that can later be used by rules, tasks, or monitors.
After what seems like a very very long time to put together all of the pieces required to make it happen, the "ReSearch This!" management pack is available for download!
ReSearch This! is a common repository for information on how to resolve alerts for Operations Manager 2007, System Center Essentials and Microsoft Operations Manager 2005. It provides a method to search a community repository for alert resolutions and to submit information to share how you have resolved alerts in your environment.
These management packs are available for download at:
SystemCenterForum is proud to announce the creation of a shared repository for how to resolve alerts for Operations Manager 2007, System Center Essentials and Microsoft Operations Manager 2005.
This functionality is available through a management pack called "ReSearch This!" which was created through contributions from the team at SystemCenterForum and the MVP community members.ReSearch This provides a task which does a lookup based upon the alert information in the SystemCenterForum knowledgebase articles. We have currently uploaded over a hundred articles based upon work done by many individuals including Pete Zerger, Kerrie Meyler, and Cameron Fuller. The goal of this functionality however is to provide an easy to use method for users of OpsMgr, SCE and MOM to be able to share what they have found worked for their environment to resolve the variety of alerts which these products generate. After the management pack is imported, you can click on an alert and from the Alert Tasks choose "ReSearch This!" to search for the alert in the repository. To submit alert information to the shared repository right-click on the alert and from the Alert Tasks choose "Share This!".
In this post I will show how to setup SQL logon auditing. You will have to complete a number of steps before you have a complete auditing. Beware that logging all logon events can fill up your database. This post includes the following steps:
Configure SQL to audit logon events
Configure Ops Mgr to collect logon events
Create a report to show the collected data
Configure SQL to audit logon events
Login auditing can be configured to write to the error log on the following events.
Failed logins
Successful logins
Both failed and successful logins
To configure login auditing
In SQL Server Management Studio, connect to an instance of the SQL Server Database Engine with Object Explorer.
In Object Explorer, right-click the server name, and then click Properties.
On the Security page, under Login auditing, click the desired option.
After you have applied this setting you might need to restart the SQL service before it take effect. After that you should see logon events in the local application log, in event viewer.
Configure Ops Mgr to collect logon events
You will need some suitable class to target your rule to. If you import the SQL MP you will get a number of SQL classes.
In the Ops Mgr Console click Authoring
Right-click Rules and choose to create a new rule
Create Rule Wizard - Rule Type: Choose to create a Collection Rules/Event Based/NT Event log. Choose a suitable management pack and click next
Create Rule Wizard - General: Input a rule name for example “SQL Auditing - Success Logon”. Choose a target, for example “SQL 2005 DB Engine”. Click Next
Create Rule Wizard - Event Log Type: Log Name should be Application then click Next
To collect also failed logon you need to create a rule to collect event ID 18456.
You can use the Effective Configuration Viewer from the Ops Mgr 2007 resource kit to verify if your new rule affect a SQL machine. You can also create a new event view, to show these events, after a couple of minutes you should see them.
Create a report to show the collected data
There is no report model in Ops Mgr by default, so if you want to create a brand new report, you must start with create a report model. You can do that with SQL Server Business Intelligence Development Studio. Take a look at Jonathan Hamb step by step guide how to create a report model here.
What you can do, with default reports, is a linked report. A linked report is like a shortcut to a program, it is a link that provide settings that inputs in a existing report. A linked report always inherits report layout and data source properties of the original report. All other properties and settings can be different from those of the original report, including security, parameters, location, subscriptions, and schedules.
To create a new report, for example a report showing all success logon events,
Start the Ops Mgr console and click Reporting
Click Microsoft Generic Report Library
Click Event Analysis and then Open
In the report select suitable FROM and TO for example
Click Add Group and select SQL 2005 DB Engine Group
Select MSSQLSERVER as SOURCE, 4 as Type, 18453 as Event ID and Success Audit as Event Type
Click Run
Now you can see a report with all Sucess Audit. You can now click the File menu and choose Publish. This report will now be stored as a linked report under Authored Reports. The next time you want to see success logons to SQL you can click this report direct in the console, and all the parameters will be there.
If you select MSSQLSERVER as source and 4 as event type, you will get both Failure and Success audit events, but you must first make sure you have rules to collect them both.
Under årets keynote på Tech-Ed 2007 hvor Bob Kelly virkelige fik vist hvor vi skulle hen
annoncerede han samtidig EDGE. og hvad er så det ???
Alle udviklere i verden kender Channal 9 stedet med mere end 5.mill besøgende hver måned. det samme prøver man nu for IT-Pro's og andre
Her er blogs, How-to, Video,og ufatteligt meget mere. da stedet er nyt er er det jo stadig ikke fuldt klædt på til IT-Pro's endnu Det kræver osse at du deltager kikker ind eller uploader eller blogger. SÅ GO GO GO
Address critical customer initiated issues including roll-up of all hotfixes
Make the product easier to support
Make the product easier to use
Make the product easier to deploy
Key things to note:
Read the release notes and upgrade guide included with this release and carefully follow the instructions
This is a fully supported release - support is available through the standard Microsoft Support channels and also via our newsgroup microsoft.public.opsmgr.sp1
The release candidate will be fully upgradable to the final RTM release of SP1 (currently scheduled for mid-February 2008)
Member of System Center Operations team at Microsoft has made a new version of MPViewer . This tool helps you see all whats in a management pack: Rules, Monitors, Views, Tasks, Console Tasks, and Reports. Download this tool here....
·The Security Guide has been updated to include: Role-Based Security in Operations Manager 2007; Using Certificates with ACS in Operations Manager 2007; Security Considerations for Agentless Management in Operations Manager 2007; Web Console Security, account information, authentication and data encryption.
This guide provides guidance in planning for backup and recovery of System Center Operations Manager 2007 server roles and components. The information in this guide will complement your existing recovery strategy to avoid service disruption.
The Operations Manager 2007 Design Guide takes you through the steps necessary to develop a complete architectural plan for your Operations Manager 2007 implementation
Operations Manager 2007 Performance and Scalability White Paper
The official tool for capacity and sizing guidance for Operations Manager 2007 is System Center Capacity Planner 2007, which is currently in development. You can get the Capacity Planner 2007 Beta at the Microsoft Connect Web site. In the meantime, you can use this document which describes performance and scalability guidelines to consider when planning a Microsoft System Center Operations Manager 2007 deployment.
Operations Manager 2007 Microsoft Management Pack Authoring Guide: This document provides detailed information about how to create a Management Pack for a product. The product can be an application, a service, or a device.
Active Directory Management Pack Guide for Operations Manager 2007
This document includes a Management Pack overview, deployment procedures, and monitoring scenarios for the two Active Directory Domain Services (AD DS) Management Packs
Exchange Management Pack Guide for Operations Manager 2007
This guide includes a Management Pack overview, deployment procedures, and monitoring scenarios for the Microsoft Exchange Server 2003 Management Pack for Microsoft System Center Operations Manager 2007.
Internet Information Services Management Pack Guide for Operations Manager 2007
This guide includes Management Pack overviews, deployment procedures, and scenarios for monitoring Windows Server Internet Information Services (IIS) 2000 and 2003 with Operations Manager 2007.
Microsoft Information Worker Management Pack for Operations Manager 2007
This guide includes an overview of the Management Pack, import procedures, optional configuration, and monitoring scenarios for the Information Worker Management Pack.
Microsoft SharePoint Portal Server Management Pack for Operations Manager 2007
This guide includes an overview of the Management Pack, import procedures, optional configuration, and monitoring scenarios for the SharePoint Portal Server Management Pack.
Microsoft Windows SharePoint Services 2003 Management Pack for Operations Manager 2007
This guide includes an overview of the Management Pack, import procedures, optional configuration, and monitoring scenarios for the Windows SharePoint Services Management Pack.
System Center Management Pack Guide for Operations Manager 2007
This document includes a Management Pack overview, deployment procedures, and monitoring for health of the Operations Manager 2007 components and services.
Windows Server Operating System Management Pack Guide for Operations Manager 2007
The Microsoft Windows Server Management Packs monitor the performance, health, and availability of Microsoft Windows 2000 Server and Microsoft Windows Server 2003.
Windows Client Operating System Management Pack Guide
The Windows client operating system Management Packs are intended for use in gathering data on client computers or individually monitoring designated mission-critical client computers.
Strumenti 
Guida
