Search the Community
Showing results for tags 'SCOM2012'.
hi I have a scom2012 r2 installed and exchange 2013 management pack imported .after installing agent on the exchange server agent , scom discovered components and .... . accourding to this article I've realized that I should change StorageLogicalDriveSpaceMonitor threshold , so I did that . But it doesnt show me mailbox database size as it was showing at the beginning of installing exchange mp . at first it was showing exchange mailbox count .but Now its not . whats the solution ?
hi I have scom 2012 installed and I installed agent on multiple servers such as sql server 2008 2012 2014 . it was working fine and monitored all servers .bu today I just saw that sql server 2012 monitoring dashboard is all grayed I waited for a while but nothing happens .I Installed agents again on that server .but nothing is showing in dashboard .the agent is showing healthy .and I can see the server computer in my console ,but not in sql 2012 instance summary and database engines. please help me .thanks a millions
Hi, My SCOM 2012 SP1 server is running on Windows 2008 R2. The database is SQL Standard 2008. I was planning on rebuilding the server since I have more storage. However, when I rebuilt it before I ran into the issue of all clients still attempting to communicate with the previous MP. Which led me to having to go to each PC and Server and manually removing the old MP. What would be the best way to avoid this issue?
The management pack for SharePoint 2013 (including server and foundation) is available here: http://www.microsoft.com/en-us/download/details.aspx?id=35590 As of this writing – the version on the download site is 15.0.4425.1000 however the ACTUAL version of the management packs are 15.0.4420.1017. I have no idea why we don’t make these match up. First – import the MP’s: As a best practice, also ensure you have imported and configured the Windows Server Operating System, SQL Server, and IIS management packs for your OS versions. Then – the SharePoint MP’s: We will assume you have installed SharePoint 2013, and deployed an agent to these servers. When monitoring a farm, you need to ensure agents are deployed to all farm role computers, including the SQL database servers. Next – I recommend you perform this step on your management server. We need to copy the configuration file “microsoft.sharepoint.foundation.library.mp.config” that shipped with the management pack files, to the following location: C:\Program Files\System Center Management Packs This MUST be placed in this specific location. You might have to create the directory if it does not exist. If you had previously configured SharePoint 2010 on this same server, you will see your SharePoint 2010 config file present, as seen in the graphic above. Open the microsoft.sharepoint.foundation.library.mp.config file using NotePad, and find the section “<Association Account” <Association Account="SharePoint Discovery/Monitoring Account" Type="Agent"> <Machine Name="" /> < /Association> We need to create a RunAs account for the SharePoint 2013 MP to use. This RunAs account display name MUST match the “Association Account” in the config file. Here is where we need to have a quick discussion. The SharePoint 2010 MP’s and config file use the SAME default name of “SharePoint Discovery/Monitoring Account” If you are NOT monitoring SharePoint 2010, then you can continue and use the default name. If you ARE monitoring SharePoint 2010 already – then you have two choices. If your CURRENT SharePoint monitoring RunAs account credential is also a Farm Admin in SharePoint 2013 – you can just use your existing RunAs Account and continue. If you are monitoring SharePoint 2010 already, and you wish to use a DIFFERENT credential for monitoring SharePoint 2013, then you will need to modify the config file. Honestly – the config files for SharePoint 2010 and 2013 should not have used the same default name for the RunAs account and the profile. I’m hoping they change this in future versions because it just makes everything harder to support. At any rate – I was not able to get the 2013 MP to use a unique RunAs account… no matter what I did it was always using the SharePoint 2010 MP’s credential, even when it was not distributed to my SharePoint 2013 servers, which is bizarre. At this point I’d recommend using the same credential for all Farms if you are trying to monitor SharePoint 2013 and 2010. I continue to investigate this. Next – I will create a new Run As account – with this EXACT name (unless it already exists) Open the RunAs account we just created – and on the distribution tab – add in the servers that are part of the farm, or SQL servers that host farm databases: At this point – I need to ensure that my RunAs account credential that I just used is a Farm Admin, and has full access to all SharePoint SQL servers/databases. Next – we need to configure the SharePoint config file for the server names for our SharePoint 2013 and SQL servers. If you don’t edit the file with specific Farm Server and Database Server names, then SCOM will try and discover SharePoint 2013 on EVERY server in the management group. It is best to scope this down in advance. Open the file in NotePad, and under "Association Account” add a “Machine Name=” line for each server in your farm. For instance, my Farm consists of “shpt2.opsmgr.net” and “db1.opsmgr.net” so my file will look as follows: <Association Account="SharePoint Discovery/Monitoring Account" Type="Agent"> <Machine Name="shpt2.opsmgr.net" /> <Machine Name="db1.opsmgr.net" /> < /Association> Save and close the config file. In the monitoring view – Expand Microsoft SharePoint > Administration and select the “Microsoft SharePoint Farm Group” In the Tasks pane – run the task “Configure SharePoint Management Pack” *** Note – if the task fails – or throws an error – try running it again a few times, or closing and opening the SCOM console – and running it again. If it continues to fail – investigate and ensure you have the config file on your management server, and you are running the console on the management server when calling the task. You should see output similar to this: Output Load configuration file Microsoft.SharePoint.Foundation.Library.mp.config Configure Microsoft.SharePoint.Foundation.Library version 15.0.4420.1017 Create override management pack Microsoft.SharePoint.Foundation.Library.Override Account SharePoint Discovery/Monitoring Account is associated to DB1.opsmgr.net for Microsoft.SharePoint.AdminAccount Account SharePoint Discovery/Monitoring Account is associated to SHPT2.opsmgr.net for Microsoft.SharePoint.AdminAccount Allow DB1.opsmgr.net as a proxy Allow SHPT2.opsmgr.net as a proxy Create 'Enabled' property override with value true for Microsoft.SharePoint.2013.WSSInstallation.Discovery Create 'SyncTime' configuration override with value 18:43 for Microsoft.SharePoint.2013.WSSInstallation.Discovery Create 'IntervalSeconds' configuration override with value 28800 for Microsoft.SharePoint.2013.WSSInstallation.Discovery Microsoft.SharePoint.2013.WSSInstallation.Discovery does not have configuration TimeoutSeconds Create 'SyncTime' configuration override with value 18:45 for Microsoft.SharePoint.2013.SPFarm.Discovery Create 'SyncTime' configuration override with value 18:51 for Microsoft.SharePoint.2013.SPService.Discovery Create 'SyncTime' configuration override with value 18:57 for Microsoft.SharePoint.2013.SPSharedService.Discovery Create 'SyncTime' configuration override with value 19:03 for Microsoft.SharePoint.2013.SPHARule.Discovery Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Availability Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Security Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Performance Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Configuration Create 'SyncTime' configuration override with value 19:09 for Microsoft.SharePoint.2013.SPHARuleMonitor.Custom Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Availability Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Security Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Performance Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Configuration Create 'SyncTime' configuration override with value 19:15 for Microsoft.SharePoint.2013.SPHARuleMonitor.SPServer.Custom SharePoint management pack configuration completed successfully This task is really a “discovery helper”. It will create the necessary RunAs profile associations to the RunAs account for each server, and it will enable agent proxy for each server, and will create some overrides to space out all the discoveries so they run in order, and can discover all Farm components as quickly as possible. From the time you run the task, to full Farm, Role, Server, and Service discovery, should be around 40 minutes. After 40 minutes – check in the console and see if your Farm, Servers, and Services have all been discovered. If not – check in the “Unidentified machines view”. If your farm servers show up there, it is likely a permissions issue with your RunAs account, either on the Farm servers or on the SQL server. On the SharePoint servers, make sure this account can log in and execute the SharePoint command shell without errors. Some good troubleshooting blogs on this topic: http://thoughtsonopsmgr.blogspot.com/2013/04/sharepoint-server-2013-mp-useful-links.html http://thoughtsonopsmgr.blogspot.nl/2013/04/troubleshooting-sharepoint-server-2013.html http://thoughtsonopsmgr.blogspot.nl/2013/04/sharepoint-server-2013-mp-configure.html Refrence this post is http://blogs.technet.com/b/kevinholman/archive/2013/05/14/configuring-the-sharepoint-2013-management-pack.aspx