Kevin Holman's System Center Blog - All Comments

re: OpsMgr: MP Update: New Base OS MP 6.0.7026.0

Kevin Holman — Mon, 20 May 2013 18:56:53 GMT

I recommend disabling the API monitor until the next release of the MP at this point.

re: OpsMgr: MP Update: New Base OS MP 6.0.7026.0

Dom — Mon, 20 May 2013 16:23:37 GMT

Hello,

Same here we are having a lot of alerts with the "Windows Server 2008 Max Concurrent API Monitor".

Should the update done server per server or could we have a parameter in the Monitor to change?

For now what I see on the monitor is:

Alert On State, Alert Priority, Alert Severity, Auto-Resolve Alert, Enabled, Generates Alert, Interval seconds, Sync Time, Time Seconds.

Anything missing on this monitor: Windows Server 2008 Max Concurrent API Monitor?

Which parameter should be fixed?

Thanks,

Dom

re: OpsMgr: MP Update: New Base OS MP 6.0.7026.0

Russ — Mon, 20 May 2013 14:56:16 GMT

We are also experieincing issues with API monitor. In each case that we receive alerts, and then go back to verify that there is an issue, everything is fine. We have been following below as verification:

support.microsoft.com/.../2688798

In order to determine the best MaxConcurrentApi value for your servers, several data points must be brought together and calculated by using a formula. The data to be used to estimate MaxConcurrentApi is as follows:

• Net Logon semaphore acquires

• Net Logon semaphore time-outs

• Net Logon average semaphore hold time

• Duration of the performance logging that is completed, measured in seconds

After the data is obtained, the following formula can be used to estimate the correct MaxConcurrentApi value:

(semaphore_acquires + semaphore_time-outs) * average_semaphore_hold_time / time_collection_length = < New_MaxConcurrentApi_setting

After you collect the Net Logon performance data from when the server was under authentication load, you should determine the duration of the data-collecting process by looking at the Line View beginning and end times.

re: Configuring the SharePoint 2013 Management Pack

Huy — Fri, 17 May 2013 19:53:05 GMT

Hi Kevin,

Thanks for another great post! Is there a simpler way to create a custom alert notification/subscription for all SharePoint 2013 related alerts to route to my SharePoint Support group? My current Subscription Criteria Conditions are: Raised by any instance of a specific class (which I have selected ALL classes from the Microsoft SharePoint Server Core Library and Microsoft Sharepoint Foundation Core Library MP) and of a specific severity (Warning or Critical), and with specific resolution state (New (0)). Is there a single SharePoint class that would include all SharePoint alerts? Too bad I can't just specify the names of the SharePoint 2013 MPs (Foundation and Server) for criteria.

Thanks,

Huy

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Joe — Fri, 17 May 2013 14:21:58 GMT

I have been struggling with this script and trying to get it work. It turns out that many of my servers had bigger problems with the performance counters. To resolve them, I simply rebuilt them using:

lodctr /r

This seemed to take care of the issue. Prior to executing this command, the script would hang for a very long time and then return an error. Now, it returns what looks like XML in about 30 seconds.

re: Windows Server 2012: Creating a NIC TEAM for Load Balancing and Failover

Leigh — Fri, 17 May 2013 01:27:43 GMT

No you not doing anything wrong thats just the way it works. If you were to draw data from the team to 2 different locations (2 different NICs) then you might see the NIC team output up to 2Gbps.

Or you could try this:

Create 2 Virtual Switch each on its own physical NIC then team them within the Guest. ??

www.aidanfinn.com

re: Configuring the SharePoint 2013 Management Pack

Thomas — Thu, 16 May 2013 09:20:52 GMT

Hi,

thanks for this information. This is very helpfull.. Any recomendations when I want to discover multiple farms over different domains using different Farm Administrator accounts.

Should I add the servers one by one to

< /Association>

or is there a way to work with Groups?

Thnxs

Thomas

re: OpsMgr: MP Update: New Base OS MP 6.0.7026.0

Bryan Wilson — Thu, 16 May 2013 07:14:38 GMT

I'm seeing issues with the Windows Server 2012 Max Concurrent API Monitor also. Using perfmon I don't see any related counter under netlogon to see what this current value is.

re: OpsMgr: MP Update: New Base OS MP 6.0.7026.0

Kevin Holman — Wed, 15 May 2013 13:12:52 GMT

Hi Steve - I will. There are other problems with this monitor where it goes red when the script encounters an error... which isn't terribly uncommon.

re: OpsMgr: MP Update: New Base OS MP 6.0.7026.0

Steve — Wed, 15 May 2013 09:27:54 GMT

The Max Concurrent API monitor seems to alert on all non-domain joined computers, due to a lack of NetLogon performance counters, which the data source script does not handle well. Our workaround at present is to create a group of Workgroup computers (manually unfortunately, as we cant identify workgroup computers dynamically), and disable the monitor for this group.

Could you feed this back to the MP developers?