October 2005 - Posts
Application development and application maintenance are no longer separate. Closing the loop between operations and development is critical for keeping the total cost of operations down. In this webast, learn how Microsoft Visual Studio 2005 Team System and AVIcode Intercept Studio 2.3 extend the capabilities of Microsoft Operations Manager (MOM) 2005. AVIcode Intercept Studio and MOM 2005 provide the foundation for "friction-free" application health modeling and operational monitoring of distributed Microsoft .NET applications. Find out about the powerful capabilities this solution provides for software architects, systems operators and administrators.
Presenters: Stephen Pelletier, VP Business Development, AVIcode, Inc., and Dhananjay Mahajan, Program Manager, Microsoft Corporation
Webcast
Microsoft System Center Capacity Planner 2006 (BETA Refresh) delivers state of the art easy-to-use modeling technology to bring unprecedented functionality and flexibility to the process of performance analysis and planning of system deployments of Microsoft Exchange Server 2003 and Operations Manager 2005. Microsoft System Center Capacity Planner 2006 (BETA Refresh) provides the IT professional with the tools and guidance required to architect a deployment in the most efficient manner, while facilitating future planning by allowing for "what-if" analysis.
System Center Capacity Planner 2006 (Beta Refresh) provides the following benefits:
- Proactive Performance Planning
- Infrastructure Planning and Optimization
- Performance Analysis and Predictive Reporting
- Cost Analysis and Justification
Download and Try
Action Account
To change the Management Server action account that was configured by MOM Management Server Installation, You need to use a command line tool - SetActionAccount.exe to view and modify the action account on the Management Server of the existing MOM deployment.
*The Management Server's Action account is used to gather information about, and run responses on, the Management Server and can be used for installing and uninstalling agents on remote computers and updating settings on agents. The agent's action account is used to gather information about, and run responses on, the managed computer. Several MOM processes run under the action account, including the processes that host MOM response scripts and managed code responses. The main purpose of the action account is to control the permissions and security for these processes, and the scripts and assemblies that they execute.
To view the existing action account:
SetActionAccount.exe ManagementGroupName -query
To Change the existing action account:
SetActionAccount.exe -set DomainName UserName
DAS Account
Sometimes, you may need to change the password of the existing DAS Account to meet the company's password policy.
To update the DAS Account Password:
|
1. |
Change the accounts password on the local computer or the domain. If this is a local account you can do this using the Local Users and Groups snap-in. If this is a domain account, you can use the Active Directory Users and Computers snap-in. |
|
2. |
Update the password for the Identity for the Microsoft Operations Manager Data Access Server COM+ application. You can do this in the Component Services snap-in. And then stop the MOM service if needed*. |
|
3. |
Stop the COM+ application and then restart the MOM service and COM+ application. |
* If you are changing the Management Server Action Account and the DAS account at the same time, you must change the Action Account first, then the DAS account, and then stop the MOM Service before stopping the COM+ application. Starting the MOM Service will also start the COM+ application.
If the MOM Service will not start, it might be because the DAS account has not been changed properly or the password has expired.
To change the DAS Account:
You can change which account MOM uses for the Data Access Service (DAS) functionality. If the Management Server and MOM Database are installed on different computers, the account used for the DAS can be a domain user account. If the Management Server and MOM Database are installed on the same computer, the DAS account can be the LocalService account. The account with at least the following properties:
| • |
Member of the MOM Users group on the Management Server. |
| • |
A SQL Server Logon with "Permit" server access and "db_owner" (DBO) access to the OnePoint database on the MOM Database Server. |
| • |
A SQL Server Security Login with "Permit" server access. |
| • |
The DAS account must also be a member of the SC DW DTS security groups on the MOM Reporting Server and MOM Database Server, if MMPC is installed using the DAS account. |
In this article, I will show you the flow of the Data Protection Manager 2006 server archive/backup and restore procedure.
I recommend that you should have the basic concept and knowledge of DPM 2006 first, you can read the DPM Planning and Deployment Guide and Operations Guide to learn more about DPM 2006. They are very useful!
Archive/Backup
1. Backup the System State, Services, Applications by using ASR backup in Windows backup.
2. Backup the Shadow Copies of Replicas, DPM Database (DPMDB.mdf) and Report Database (ReportServer.mdf) by using DpmBackup.
3. Store the archive/backup files to tape or other media.
Restore System State, Services and Applications
4. Run the Windows Setup and start the ASR restore or reinstall Windows Server and DPM if needed. Please remember to use the same computer name as the old DPM server.
Restore Databases
5. Use DpmSync -DpmDbLoc and -DpmReportDbLoc to restore the DPM Database and Report Database.
6. Run DpmSync -Sync to synchronize the databases.
7. Remove the missing disks and add the new disks to DPM storage pool if needed.
8 . Run DpmSync -ReallocateReplica to reallocate disk space for the replicas.
Restore Replicas
9. Use the backup software to restore the replicas' shadow copies backup.
10.
a)If the tape backup from which you restored data was created by using DpmBackup and the protected volume GUID has not changed since backup, run DpmPathMerge to delete extraneous path information.
b)Use FsPathMerge to delete extraneous path information if
|
• |
You are restoring a replica where the backup hierarchy and the replica folder hierarchy do not match, and the backup was not created by using DpmBackup. |
|
• |
The backup was created by using DpmBackup and the volume GUID of the protected volume changed between the backup time and restore time. |
11.
a)If you need to restore the volume on protected files server, Create a shadow copy of the restored replica at this point in the process, you can restore the volume to the file server. Do not run the consistency check on any replica in the protection group until all replicas in the protection group are restored.
b)If it is the restoration on a new DPM server, Please uninstall the File Server agent locally, Remove the agent record in DPM, and then use DPM administrator console to reinstall the agent.
12. Run synchronization with consistency check
Configure Microsoft Operation Manager 2005 to monitor devices by using SNMP
If you are using Microsoft Operation Manager 2005 and want to monitor non-Windows devices by MOM Operator Console, You must need to configure the non-Windows devices to forward the SNMP traps to the MOM Agent Computer, and the MOM Management Server to receive and handle the SNMP traps.
On the SNMP traps receiver
1. In Control Panel, Open Add/Remove Programs, Click Add/Remove Windows Components, Select Management and Monitoring Tools, Click Details, and install the SNMP and WMI SNMP Provider.
2. Open Services.msc, right click SNMP Service and click properties, In the General Tab, configure the Startup type to Automatic. Open Security Tab, in the Accepted community names, Click Add, choose READ CREATE in Community rights and enter Public for Community Name. Click Add. Also, choose Accept SNMP packets from any host and click OK.
3. Compile the MIB file for the SNMP traps you get from other vendors using the SMI2SMIR utility. This will load the MIB information into the WMI \\.\root\snmp\smir namespace. (example: smi2smir.exe /sa /t <MIB file> or smi2smir.exe /a <MIB file> or smi2smir.exe /g <MIB file> <MOF file>)
On the MOM Management Server
1. In MOM Administrator Console, Right click Computer Groups and click Create Computer Group, enter the name SNMP Receiver for the name of that computer group, and then add the SNMP receiver computer to it.
2. Right click Rule Groups and click Create Rule Group. Enter the name SNMP for that rule group and check the Enable checkbox. Click Next and Finish.
3. Associate that SNMP rule group to the SNMP Receiver computer group.
4. In that SNMP rule group, create a Collect Specific Events (Collection) rule for each SNMP Trap Catcher and SNMP Extended Trap Catcher Data Provider. And Enable both of these collection rules.
5. In that SNMP rule group, create an Alert on or Respond to Event (Event) rule with SNMP Trap Catcher Data Provider. Enable Generate Alert of that rule.
6. Add the VBScript as the response to this rule. The VBscript is used to generate an additional alert to display the SNMP traps sender's IP address directly.
Set objEvent = ScriptContext.Event
Set objAlert = ScriptContext.CreateAlert()
objAlertLevel = 50
objAlert.AlertSource = "SNMP"
objAlert.Name = "SNMP Alert"
objAlert.Description = objEvent.Message
objAlert.Computer = Replace(objEvent.EventParameter(11),".","-")
objAlert.ComputerDomain = "SNMP"
ScriptContext.Submit objAlert
7.Enter the name SNMP Alert for this VBscript and this rule and then Enable this SNMP Alert rule.
On the SNMP traps sender
Configure the Community name Public and the Target SNMP traps receiver.
Source: My 7th Microsoft KB Article
Configure Microsoft Operation Manager 2005 to monitor Unix devices by using Syslog
If you are using Microsoft Operation Manager 2005 and want to monitor the Unix devices by MOM Operator Console, You must need to configure the Unix devices to forward the Syslog messages to the MOM Agent Computer, and the MOM Management Server to receive and handle the Syslog messages.
On the MOM Management Server
To create a Syslog port provider
1. In the left pane of the MOM Administrator console, right-click Providers.
2. On the context menu, click New Provider, specify Application Log as the data provider type, and then click Next.
3. For the provider name, enter Syslog port provider.
4. For the provider log type, select Syslog port, and then click Finish.
To create an event rule that uses the Syslog port provider
1. First create a rule group named Syslog and associate this rule group with a computer group named Syslog messages receiver that included the Syslog message receiver computer (MOM Agent Computer).
2. In the left pane of the MOM Administrator console, expand the rule group, right click Event Rules, and then click New Event Rule.
3. Select Collect Specific Events (Collection), and then click Next.
4. In the list, select the Syslog port provider and then click Next.
5. Enter Collect Syslogs for the name of the rule, ensure that the Enabled check box is selected, and then click Finish.
6. In the left pane of the MOM Administrator console, expand the rule group, right click Event Rules, and then click New Event Rule.
7. Select Alert on or Respond to Event (Event),click Next.
8. In the list, select the Syslog port provider and then click Next.
9. In the Criteria Page, click Advanced button, and choose Parameter 1 in field, choose contains substring and enter the Syslog message level (example: crit, err, warning..) in value. Click Add to List.
10. Click Close and then click next. Check the Generate Alert in the Alert Page and configure the Alert properties.
11. Enter the name Received Syslog message level from Syslog for the rule name (example: Received Warning from Syslog). Click Finish.
12. Create additional rules for other syslog message level to generate alerts.
On the Unix device
1. Configure the entry in system logger configuration file (Syslog.conf) that maps syslog messages to the IP address of a Syslog message receiver (MOM Agent Computer). In the Syslog.conf file, tabs separate the message type and the IP address. The message type is of the form facility.level, such as kern.error, which signifies a kernel error.
The following facility values are recognized by MOM: auth, cron, daemon, ftp, kern, local0, local1, local2, local3, local4, local5, local6, local7, lpr, mail, mark, news, syslog, user, and uucp.
The following priority levels, from highest to lowest, are recognized by MOM: emerg, alert, crit, error, warning, notice, info, and debug.
Example: *.err @192.168.0.150
2. Restart the system logger daemon (syslogd) on the UNIX device.
System Center Reporting Manager 2005 (Beta) consolidates your change and configuration information from SMS 2003 and your event and performance information from MOM 2005 to give you easy access to the reports you need to manage your enterprise.
Please visit beta.microsoft.com and use the Guest ID
SCGUEST
Complete the survey to join this beta testing.
Although MOM 2005 has been released (as of August 25, 2004) beta code for MOM 2005 is no longer available. However, periodically betas of management packs and other tools will be made available on this site.
Please visit beta.microsoft.com and use the Guest ID
MOM2004Beta
Complete the survey to join this beta testing for the latest MPs and Tools.
Business needs
The need for an organization to deploy an operations management solution depends
primarily on the quality of service expected and the complexity of the IT infrastructure.
An operations management solution is essential for organizations that require:
High availability and optimal performance of systems.
Centralized management of a distributed IT infrastructure.
Effective change management and capacity planning.
High service availability and optimal performance
For many organizations, high system availability and optimal system performance are
critical business needs. For example, service interruptions and inconsistent
performance can lead to dissatisfied customers and lost revenue, placing the
organization at a competitive disadvantage. Despite all this, software and hardware
systems fail in unpredictable ways. For many IT systems, it is simply not reasonable to
expect one hundred percent uptime and flawless performance over the course of an
entire year. It is important for business decision makers to distinguish between what is
acceptable and unacceptable availability and performance. For this reason, managers of
critical systems and their customers enter into what is known as a service level
agreement (SLA). An SLA specifies the quality of service required to support an
organization’s business functions.
Operations management enables systems administrators to ensure that their
organizations’ IT infrastructures consistently deliver the quality of service specified by
their SLAs. Systems administrators can proactively monitor systems, identify potential
health issues, and quickly resolve these issues. Such preventive maintenance minimizes
service outages and performance losses and helps reduce unplanned downtime.
Centralized administration
If an organization has offices in several locations, its IT infrastructure spans a wide
geographical area. For single-point administration of such a distributed infrastructure,
systems administrators need a centralized monitoring and management system.
Operations management enables systems administrators to monitor applications,
services, and the performance levels of distributed systems from a central location. This
gives systems administrators an organization-wide view of IT health issues. If a problem
is identified on a computer, the problem can be corrected locally or remotely, depending
on the nature of the problem.
Effective change management and capacity planning
Organizations need to expand their IT infrastructures to meet growing business
requirements. The IT department must methodically scale up an organization’s IT
infrastructure so that new services are smoothly deployed.
Operations management enables systems administrators to identify IT infrastructure
changes that can increase operational efficiency and effectively implement these
changes without disrupting existing services.
In addition, operations management supports capacity planning. Systems
administrators can collect operations data over a period of time, analyze this data, and
identify performance trends. Based on these trends, system administrators can predict
the demand for IT services and determine the resources that will be required to meet the
demand.
Hello, I'm Daniel, Microsoft MVP for Windows Server Management Infrastructure.
I enjoy to share my technical and product knowledge/experience of management tools to each other.
Please leave your comments and questions in here. You can also add my MSN contact too. =)
My MSN contact is laidaniel@msn.com.