Quantcast
Channel: Operations Manager - General forum
Viewing all 11941 articles
Browse latest View live

A scheduled discovery task was not started

$
0
0

Event ID 10000: A scheduled discovery task was not started because the previous task for that discovery was still executing. 

Discovery name: Microsoft.SystemCenter2012.ConfigurationManager.ClientDiscovery.

I get these warnings on all managed servers for the same discovery type. They come every 1.5 to 4 hours on each system, which makes a mess of the event logs. The default appears to be 14400 seconds, which I have not modified.

Has this been problematic for anyone? Is there a recommended setting if this threshold is too low, or does the fact that discovery is not completing in 4 hours indicate a bigger problem?

Thanks.


Monitoring Exchange across multiple forests using single SCOM Management Group ?

$
0
0

Was not sure whether I should post here or in the Exchange forum but I will start here !  Is it possible to monitor multiple Exchange organizations running in different forests using a single SCOM management group ?  Would the Exchange and AD management pack handle this sceanrio properly ?  Would a SCOM gateway need to be installed in each forest and event after this would it be too difficult to manage ?  I am interested to hear other people's experience who have had to do similar things in the past.

Thanks in advance.

Management Pack issues following upgrade from SCOM 2007 R2 to SCOM 2012 ?

$
0
0
Has anyone experienced issues with management packs following upgrade from SCOM 2007 R2 to SCOM 2012 ?

OpsMgr SDK Service Event ID: 26319 on RMS

$
0
0

Hi,

On the management server where also SQL Server is installed, i get these errors. I checked the permissions written in "OpsMgr 2007 SP1 Security account Matrix v1.0.xls" momdatareader permissions seem to be okey.

Whot could be the reason?

An exception was thrown while processing SetupAlertsByCriteriaReaderWithProperties for session ID uuid:d82a3318-7477-4b3f-82bf-306f5b91f0ea;id=1129.
 Exception message: The creator of this fault did not specify a Reason.
 Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Id='' -- Unrecognized Guid format.Id='' -- Unrecognized Guid format.).

SCOM 2012 R2 & Exchange 2007 A scheduled discovery task was not started because the previous task for that discovery was still executing.

$
0
0

Hi,

I had recive the follwoing error in CCR Nodes, and unable to discover the CCR or SCCR nodes due to below error:

A scheduled discovery task was not started because the previous task for that discovery was still executing.

Discovery name: Microsoft.Exchange2007.ServerRole.CcrNode.Standalone.Discovery
Discovery name: Microsoft.Exchange2007.ServerRole.Mailbox.OnCluster.Discovery
Discovery name: Microsoft.Exchange2007.ServerRole.CcrNode.WithCluster.Discovery

I found Similar Question, but there are no answer for them

http://social.technet.microsoft.com/Forums/en-US/22f269c3-3036-4c0c-9ef4-b0b72fc4d6a9/a-scheduled-discovery-task-was-not-started?forum=operationsmanagergeneral

http://social.technet.microsoft.com/Forums/en-US/326517a8-e427-412f-bbe0-84bc7721ac47/health-service-event-10000-a-scheduled-discovery-task-was-not-started-because-the-previous-task-for?forum=operationsmanagergeneral

Data Warehouse issues

$
0
0

Hi there.

I'll try and be to the point as I can. I undertook an upgrade from SCOM 2012 SP1 to R2, this was successful. However after a few days had past, I noticed that the log file for the DW DB was growing rapidly, to the point where we hit a real issue. The drive was a comfortable 50GB drive, but in the end had to be increased to just short of 500GB !! Long story short, I wasn't allowed to get a consultant in to help diagnose the issue, therefore, I was consulting Google, Technet articles etc.

The end decision was to DELETE the Data Warehouse DB & log file and create them again from scratch. I've done this, and used the following instructions on how to do so (http://www.3packetsofcrisps.com/2014/04/reset-scom-2012-data-warehouse-database.html). I have data going into the DW DB, or rather did up until midnight, so had around 3.5 hrs worth. 

After checking the Operations Manager event log on one of the Management Servers, I can see numerous errors, these include:2115, 4506 and occasionally 8000. 

The event 4506 states: "Data was dropped due to too much outstanding data in rule "Rule Name" running for instance "instance name" with id "ID name" in management group "xxx". 

After some consulting Google, I read that this might be expected because a lot of data is trying to be written to the DW DB, however, that doesn't explain why it was writing and for some reason randomly stopped. 

A quick summary of our environment:

2x Management Servers running Win 2012 Std x64
1x Operations Database server running Win 2012 Std x64 & SQL Server 2012 Std x64
1x Data Warehosue DB server running Win 2012 Std x64 & SQL Server 2012 Std x64

I've checked account permissions using http://technet.microsoft.com/en-gb/library/hh457003.aspx

If you need any more information, please say, I've tried to keep the post as small as possible.

Dave.


What are different between gateway and mangement server in scom ?

$
0
0

Hi all,

can anyone let me know What are different between gateway and mangement server in scom ?

thanks,

Sengottuvel M

SCOM services System Center Data Access Service and System Center Management Configuration use?

$
0
0

Hi all,

 

Can anyone tell me what exactly in background below two services doing in SCOM 2012 ?

System Center Data Access Service

System Center Management Configuration

Thanks


Is it possible to update SCOM 2012 R2 directly to UR3 ??

$
0
0
Is it possible to update SCOM 2012 R2  directly to UR3 ??

SCOM 2012 R2: Sporadic "MOM AD Admin Not Run" alerts, but ADI seems healthy (AD updating correctly)

$
0
0

Once every other day I get an alert in OpsMgr with the title "MOM AD Admin Not Run."  This is in the System Center Core Monitoring management pack and it's monitoring the event log for certain entries that indicate that AD Integration may not be healthy.  The rule alerts when it sees Event ID 11463 from the Health Service Modules source in the Operations Manager log.  The event occurs when, presumably, OpsMgr can't update the OperationsManager container in AD. 

Looking at the logs, I can see that this occurs once every other day or so (seems random, sometimes twice in one day), but then an hour later it is followed up with event ID 11468 which says that the management server has recovered from the previous ADI error.

I have, indeed, run momadadmin on the target domain and tested ADI and it appears to be working.  When I check the OperationsManager container I can see it is updating the groups and all the agents are seeing their AD assigned management servers when I look at it in Control Panel module on the hosts.

Is this is a false positive or a bug or do I have some sporadic AD issue?  There are no AD alerts at all in OpsMgr and otherwise AD seems to be working correctly as nobody has every had issues logging on or querying AD.

Detailed event log messages are below with server names and such sanitized from the output.

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          9/9/2014 4:38:20 AM
Event ID:      11463
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SCOM1A.domain.com
Description:
OperationsManager container doesnt exist in domain domain.com or the Run As Account associated with the AD based agent assignment rule does not have access to the container. Please run MomADAdmin before configuring agent assignment rules and make sure the associated Run As Account is the member of the Operations Manager Administrator role. 

Workflow name: _DOMAIN_SCOM1A_domain.com 
Instance name: AD Assignment Resource Pool 
Instance ID: {529CF61E-A357-5AED-73CC-81D48E4327CA} 
Management group: OpsMgr-Main
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Health Service Modules" /><EventID Qualifiers="49152">11463</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2014-09-09T08:38:20.000000000Z" /><EventRecordID>352999</EventRecordID><Channel>Operations Manager</Channel><Computer>SCOM1A.domain.com</Computer><Security /></System><EventData><Data>OpsMgr-Main</Data><Data>_DOMAIN_SCOM1A_domain.com</Data><Data>AD Assignment Resource Pool</Data><Data>{529CF61E-A357-5AED-73CC-81D48E4327CA}</Data><Data>domain.com</Data></EventData></Event>
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          9/9/2014 5:38:14 AM
Event ID:      11468
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SCOM1A.domain.com
Description:
The agent assignment rule for domain domain.com and ManagementServer SCOM1A.domain.com has recovered from previous error condition. The SCPs and security groups were successfully created. 

Workflow name: _DOMAIN_SCOM1A_domain.com 
Instance name: AD Assignment Resource Pool 
Instance ID: {529CF61E-A357-5AED-73CC-81D48E4327CA} 
Management group: OpsMgr-Main
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Health Service Modules" /><EventID Qualifiers="16384">11468</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2014-09-09T09:38:14.000000000Z" /><EventRecordID>356241</EventRecordID><Channel>Operations Manager</Channel><Computer>SCOM1A.domain.com</Computer><Security /></System><EventData><Data>OpsMgr-Main</Data><Data>_DOMAIN_SCOM1A_domain.com</Data><Data>AD Assignment Resource Pool</Data><Data>{529CF61E-A357-5AED-73CC-81D48E4327CA}</Data><Data>domain.com</Data><Data>SCOM1A.domain.com</Data></EventData></Event>





OM DW Sizing tool and retention Days

$
0
0

We are using OM sizing tool to estimate DB DW size. Sizing tool only contains one parameter: Number of Days for Data Retention (default is 365)

However, different data set has different days for retention:

Data Set

Aggregation Type

Days To Be Kept

Alert

Raw data

400

State

Raw data

180

State

Hourly aggregations

400

State

Daily aggregations

400

Event

Raw data

100

….

If we only need 90 days of data retention, and using sizing tool to calculate the DB DW size.

, how to modify the “days to be kept” parameter of each data set in the above table? For example: modify “400” to “90”, “180” to “90”..

Health Service cannot verify the validity of the RunAsAccount

$
0
0

Hi,

I have a SCOM 2012 SP1 UR2 installation with 2 management servers. My Operations Manager eventlog still keeps registering events with ID 7016:

The Health Service cannot verify the future validity of the RunAs account SUB-DOM\SCOMAccount for management group SCOMManagementGroup due to an error retrieving information from Active Directory (for Domain Accounts) or the local security authority (for Local Accounts).  The error is Access is denied.(0x80070005).

I get one event for each service account I have configured in SCOM - Action, DataReader, DataWriter, ADAgentBasedAssignmentAccount.

Which account is doing the verification? I think it is the Health Service account. In the RunAsProfiles I searched for "Default Action Account" and I can see that the Default Action Account on both management servers is domain account (SUB-DOM\SCOMAction). So I looked into the Active Directory and I am sure that SCOMAction account has the READ permissions on all SCOM service accounts. I'm always sure the management server computer account has the READ permissions as well.

All service accounts have the flag PASSWORD NEVER EXPIRES checked.

Management Servers and Agents are located in the child domain: sub.domain.local. This subdomain has the NetBIOS name different from domain name: SUB-DOM. I have RunAsAccounts configured in SCOM in format SUB-DOM\SCOMAccount. I tried to change it toSCOMAccount@sub.domain.local, but errors keeps generating.

Thanks for replies...


Jan Marek MCT | MCITP | MCTS

All Agents Greyed Out or Not Monitored

$
0
0

Hello,

I am running SCOM 2012 R2.  All of my clients were re-imaged (Over 500) during the summer.  Each image that was created had the SCOM 2012 R2 Agent installed.  The images were installed on all of my clients.  Now, most of the clients are listed as greyed out or not monitored.  The server has Event Log entries of the following:

Operations Manager has received a connection from a system running an older version of Operations Manager

None of my clients are running an older version of the agent.  What's also new is that I cannot tell if my clients are turned on or not.  The clients that are green are always green.  Even when they are powered off, they are never grey in the console.  Even after I ping them or refresh.  They always stay green.  Any help would be appreciated.

No Response SNMP (sysContact OID noSuchName (2))

$
0
0

I'm trying to monitor a temperature sensor via the Network Device monitoring capability of Operations Manager. The device supports MIB-II, except that is does not support OID: 1.3.6.1.2.1.1.5 (sysContact). Which according to this link: http://www.systemcentercentral.com/snmp-discovery-fails-scom-2012/, will cause Operations Manager to fail to discover the device as an SNMP device. I've confirmed the failure via Microsoft Network Monitor, where I can see the response from the device back to the Management Server with the ErrorStatus: noSuchName (2), ErrorIndex: 3.

Is there a way to make Operations Manager ignore just the OID: 1.3.6.1.2.1.1.5 (sysContact) ? I'll be authoring a custom MP but I need the device to be added as a network device into Operations Manager first...

Thanks,

Upgrading from SCOM 2007 R2 to SCOM 2012 R2

$
0
0
Am I correct that you need to upgrade agents first and that it is OK to upgrade 2007 R2 agents directly to SCOM 2012 R2 agents ? and that they will be backward compatible with SCOM 2007 R2 management group ?

server grayed out in the console

$
0
0

Hello,

I have several servers which are becoming grayed out in the console very often.

I found the article http://support.microsoft.com/kb/974722 but it did not apply as I have already SCOM 2007 R2 CU7 .

on #1 the event 

Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7031
Date:		9/15/2014
Time:		10:24:36 AM
User:		N/A
Computer:	VOSMARTPUMP1
Description:
The System Center Management service terminated unexpectedly.  It has done this 5 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

is happening after each restart of the healthservice then it becomes event id 7034

Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7034
Date:		9/15/2014
Time:		10:25:57 AM
User:		N/A
Computer:	VOSMARTPUMP1
Description:
The System Center Management service terminated unexpectedly.  It has done this 7 time(s).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

any idea?

Thanks,

DOm


System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

extest accounts

$
0
0
what are these extest accounts in AD for? The description is Exchange 2010 scom management account health check reporting. Can I delete them and where are they used at and for?

Software Installation Processing Alerts - Group Policy Failures?

$
0
0

Hello,

I am getting several errors reported by SCOM Software Installation Processing alert

In the local event log I have:

Warning	9/15/2014 11:09:37 AM	GroupPolicy				1112	None
Warning	9/15/2014 11:09:37 AM	Application Management Group Policy	108	None
Error	9/15/2014 11:09:37 AM	Application Management Group Policy	103	None
Warning	9/15/2014 11:09:37 AM	Application Management Group Policy	101	None

with the details:

101   - The assignment of application SMS Client Setup Bootstrap from policy MITS Servers Software failed.  The error was : %%1274
103   - The removal of the assignment of application SMS Client Setup Bootstrap from policy MITS Servers Software failed.  The error was : %%2
108   - Failed to apply changes to software installation settings.  The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon.  The error was : %%1274
1112 - The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.

Computer Configuration > Policies > Administrative Templates > System > Group Policy > Policy > Startup policy processing is enabled 


what does exactly this means?

Thanks,

Dom


System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager


management packs to scom agent server ?

$
0
0

How SCOM agent will get Management Packs from Management server ? Will all Management Packs will get downloaded to all SCOM agent server?

Or how does Management server will come to know only required Management Packs for agent server? (I heard Management Server  will scan the registry to of agent server to understand the application and requirement , then it sent Management Packs for agent server , is that correct ? )

SCOM agent communicating with server?

$
0
0
 

Dear all,

After SCOM agent installation how that agent will start communicating with server? Is there any flowchart (like first how the communication will start , then when the MP will get download ..etc..)

Thnaks,

Sengottuvel M

Viewing all 11941 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>