Ops. Mgr R2 by Example: The Operations Manager Management Pack. Written By: Cameron Fuller . Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations. Hyper-V 2012 R2 Server is the free version of Hyper-V and it offers all the components and features that are available in Windows Server 2012 R2 with Hyper. The Ops. Mgr service was installed and running on the agent but would not show up in the pending management folder. Resolution: Per product knowledge, “Add the security group, which was provided as parameter to MOMADAdmin. Operations Manager Administrators User Role.” In the Ops. Mgr console - > Administration - > Security - > User Roles - > Operations Manager Administrators, added the group specified when using the Mom. ADAdmin. exe program to configure AD Integration. Closed the alert, re- started services on the server where AD agent assignment was failing (no change). Restarted the three services (in SP 1 these were Ops. Mgr Config Service, Ops. Mgr Health service, Ops. Mgr SDK Service, in R2 they are now System Center Data Access, System Center Management, System Center Management Configuration) and the agent appeared in of the Ops. Mgr console - > Administration - > Device Management - > Pending Management as expected. Alert: Agent proxying needs to be enabled for a health service to submit discovery data about other computers. Issue: The agent specified in the alert description does not have agent proxy enabled. Resolution: Found the name of the system within the alert description field (dc. Device Management - > Agent Managed and filtered on the name of the server (pasted in). Right- click on the server, go to the Properties on the Security tab. Check the Allow this agent to act as a proxy and discover managed objects on other computers checkbox. This is an alert rule so it will not auto- close, manually closed the alert on the monitoring section of the Ops. Mgr console. Alert: Backward Compatibility Script Error. Issue: MOM Backward Compatibility Service State Monitoring Script on line # 7. Resolution: This is a bug in WMI. The Black. Berry MDS Connection Service has a very long Image. Path registry entry, when the health service script runs Select Display. Name, State, Name, Start. Mode, Start. Name FROM Win. Connect to the root\cimv. Select Display. Name, State, Name, Start. Mode, Start. Name FROM Win. Tried to obtain the fix mentioned but MS support said that the Bug ID did not exist. The workaround is to change the path so that it uses the short (8. Original Key: “C: \Program Files\Research In Motion\Black. Berry Enterprise Server\MDS\bin\bmds. C: \Program Files\Java\jre. The start name was null, and the service would not start when attempted to start it. Used the sc delete to remove the service, rebooted the system, and it worked like a champ. Alert: Check the application’s security policy. Issue: Two management servers were added into an environment where AD Integration was configured. This alert occurred on both systems when RMS’s Ops. Mgr Health Service was restarted. Resolution: Gave the same access rights to the new management servers as had been given to the RMS by adding the computer accounts into the MOMADSecurity. Group created as part of the process to configure AD Integration in Ops. Mgr. Once this was done, it was verified by checking in Active Directory Users and Computers (View, Advanced Features) and validating that in the Operations. Manager container under the name of the management group that the additional management servers had records defined for them. Alert: Connection Timeout. Issue: On a TCP Port monitor, two alerts are generated when the system cannot be communicated with. The first is a Connection Timeout, and the second is a < Servername> Group Roll- Up Monitor. The server in question was being monitored via a TCP Port monitor to provide rudimentary monitoring through monitoring the RDP port (3. Resolution: The system in question was offline and needed to be brought back online, so the monitor functioned as expected. Alert: Failed Agent Push/Repair – Remote Agent Management operation failed. Issue: Failed attempting to push the agent to the system. Resolution: Logged into the system and manually installed the agent. Alert: Data Warehouse configuration synchronization process failed to write data. Issue: After importing a large number of management pack files, the data warehouse started reporting issues. The health explorer listed an event number 3. SQLException Timeout expired. Resolution: On the data warehouse server, used sp. The alerts were automatically closed after this action was performed. Alert: Data Warehouse failed to deploy reports for a management pack to SQL Reporting Services Server. Issue: The DNS management pack can cause issues in the environment resulting in event ID 2. Ops. Mgr SDK Service (System Center Data Access is the new service name in R2). Resolution: Add the account designated as the Data Reader account to the group designated as Operations Manager Administrators during setup (this group is added to the Operations Manager Administrators role). This issue only exists with the DNS Management Pack (version 6. Alert: Data Warehouse failed to request a list of management packs from SQL RS server. Issue: The data warehouse reporting server was being rebooted. Resolution: Once the reporting server was back online, this alert auto- resolved itself. Alert: Data Warehouse managed object type synchronization process failed to write data. Issue: After importing a large number of management pack files, the data warehouse started reporting issues. The health explorer listed an event number 3. Microsoft. System. Center. Data. Warehouse. Synchronization. Typed. Managed. Entity. Resolution: On the data warehouse server, used sp. The alerts were automatically closed after this action was performed. Alert: Failed to Check for Password Expiration on Run. As Account. Issue: Operations Manager is unable to monitor Run As accounts for account and password expiration for the server specified. Resolution: There was an error on the account (Administration - > Security - > Run As Profiles). In this case, the domain name had a typo on it. Alert: Failed to send notification using server/device. Issue: Issues providing notification via Instant Messaging. Resolution: The Instant Messaging configuration defaulted to port 5. IM server itself was configured to use port 5. Tested connectivity from the Ops. Mgr server to the LCS server with telnet < Server. Name> and it did answer on the telnet. Configured a Run As Account for Notification Account for the Ops. Mgr server using the same account specified in the Notification settings. Tried logging in to LCS using the account configured as the Instant Messaging and sent a test IM message. Does Communicator need to be installed on the Ops. Mgr box? When this server was offline, these alerts occurred (logically). Resolution: Defined additional SMTP servers to provide failover in case of loss of the primary SMTP server system. Used the Alert Forwarding MP to validate connectivity to the connectivity to each SMTP server (discussed at http: //cameronfuller. A2. 31. E4. EB0. 41. CB7. 6! 1. 73. 7. Closed the alert, as it did not recur after communication was re- established. Alert: Failed to send notification using server/device. Issue: Notification in Ops. Mgr was configured for a single SMTP server. When this server was offline, these alerts occurred (logically). Resolution: Defined additional SMTP servers to provide failover in case of loss of primary SMTP server system. Used the Alert Forwarding MP to validate connectivity to the connectivity to each SMTP server (discussed at http: //cameronfuller. A2. 31. E4. EB0. 41. CB7. 6! 1. 73. 7. Alert: Failed to send notification using server/device. Issue: Blocked on Exchange 2. The box that was being pointed to did not respond on port 2. Notification failed later due to security issues from an anonymous connection (the default configuration). Resolution: Re- configured Ops. Mgr to use the client access server that did respond on port 2. Configured the notification to use Windows Integrated authentication. Configured a Run As Account and configured the Run As Profile for the Notification Account for the management server to use the account which was created. Alert: Failed to send notification using server/device. Issue: The RMS lost communication with the various SMTP servers that were defined. Once the network communication was back online, notifications were able to be sent. Resolution: Lowered the priority of this alert to warning, as there is a critical for the alert “Failed to send notification” which appears to occur when not all SMTP servers can be communicated with. Alert: Health service heartbeat failure. Issue: The Ops. Mgr health service on the agent was stopped. Another potential cause is if the Ops. Mgr health service on the agent was running but unable to communicate with the Ops. Mgr management server. Resolution: Restarted the Ops. Mgr agent with Computer Management through the Actions pane. For the unable to communicate issue, the server was running a security application that restricted network traffic and blocked the network traffic from the server to the Ops. Mgr management server via port 5. Alert: Ole. DB: Results Error. Issue: Network communication between the RMS and the Operations Manager database was interrupted. The alert rule which generates this critical alert is the Ole. Db. Probe: Results Error”A good discussion on these types of alerts is available at http: //blogs. Resolution: In this case, once network connectivity was re- established between the RMS and Ops. Mgr database the alert was no longer relevant and was manually closed. Created an override to disable this alert for the RMS that was reporting these occasionally per the link listed in the issue section of this alert. Alert: Ops DB Free Space Low. Issue: The Operations Database for Ops. Mgr 2. 00. 7 has less than 4. Resolution: Operations. Manager database was not large enough to provide seven day (default) retention for the number of agents being monitored. Increased the size of the database using the SQL Server Management Studio (install it on the system running the Ops. Mgr console for ease of use).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2017
Categories |