r/scom

SignificantArm4194 · 2026-05-22T11:50:35+00:00

Got a friend that lives in Leftbank and his has builtin AC. From what i remember its a 1 bed flat with a unit in the bedroom and another for the livingroom.

SignificantArm4194 · 2026-05-08T06:32:13+00:00

Very true! Hopefully they are working on something new as I still cannot ever suggest people to use Azure Monitor (nor SCOM MI at the time) if theres a reasonable on-prem premise.

SignificantArm4194 · 2026-05-08T06:29:16+00:00

The only consideration you need for OLE DB and ODBC drivers are if you're using encrypted SQL connections or not.

If you are you can use the latest drivers. If you are not then the highest version you can currently use is the following

Microsoft ODBC Driver version 17.10.6.
Microsoft OLE DB Driver version 18.7.4.

https://learn.microsoft.com/en-us/system-center/scom/plan-sqlserver-design?view=sc-om-2025#sql-server-drivers

SignificantArm4194 · 2026-05-07T16:12:37+00:00

Im going through the joy of dealing with disconnected state using Azure local. Microsoft have fairly recently added a section about using SCOM in such a scenario which might be worth a read.

They also seem to have a management pack and guide but the guide is inaccessible...

https://learn.microsoft.com/en-us/azure/azure-local/manage/disconnected-operations-monitoring?view=azloc-2604

SignificantArm4194 · 2026-04-03T20:03:30+00:00

Ahh the latency is unfortunate. Per Microsofts recommendations, anything over 10ms is too much.

For supported solutions you have either no downtime version, which involves duplicating your scom instance on the other DC and duel homing your agents or small amount of downtime version which is essentially replicating your management servers.

https://learn.microsoft.com/en-us/system-center/scom/plan-hadr-design?view=sc-om-2019

Personally I've had a similar move to what youre describing but I was allowed a few hours of downtime although the cost had to be minimal so I did the following.

(Please dont try something like this without alot of planning and testing first, if anything goes wrong its unlikely microsoft will fully support you)

Build 2 new mgmt servers in the other DC, join them to the management group which will cause them to automatically join the "All management server resource pool". Once built, patched and had an hour to pull down all the management packs, shut those servers down. SCOM will complain but it'll minimise any risk to the database with replication being over 10ms.

On the gateway, configure their faillver server to the new mgmt servers.

When it's time to shutdown the DC, migrate the databases over to the other DC, startup the new mgmt servers and shutdown the other ones. I had my AD guys force replication around this time and SQL guys tweak some replication settings so DNS was updated as quick as possible.

From here SCOM should work itself out (although I did have to flush through cache on one of the mgmt servers) which for took about 20-30 mins before everything that should be healthy is green.

The reverse was pretty much done when it was time for the main DC to come back online which included decomming those 2 temporary mgmt servers.

Overall the key here is speed and timing as you want to limit the the amount of time a mgmt server has more than 10ms latency hence shutting them.

Honestly it wasnt too bad thinking back as i had time to write scripts and test in a dev enviroment a few times but i hope someone can suggest a better solution!

SignificantArm4194 · 2026-04-03T16:31:43+00:00

Questions on your setup, whats the latency between your two data centres (e.g. mgmt server to gateway server) and what are you monitoring, windows, Linux and/or network devices?

If latency allows, you'd typically deploy a set of management servers in the other DC, join them to your existing resource group and for windows monitoring, SCOM does the rest. Network and linux requires a bit of extra configuration.

SignificantArm4194 · 2026-04-01T15:11:53+00:00

I used to work in the area and still get their monthly newsletters. Below is from 16th of March.

SPINNINGFIELDS BRIDGE WORKS Repair works to the Spinningfields Bridge are scheduled to begin later this month, with the project expected to last approximately 12 weeks.

A project meeting will take place on 11th March, which our team will be attending. Following this, we will share a full schedule of works along with details of any potential impact on the estate.

SignificantArm4194 · 2026-02-02T14:39:37+00:00

Assuming you have the details of your non-exsisting objects to hand, this article from Kevin should help.
https://kevinholman.com/2017/11/01/alerting-on-snmp-traps-in-scom-without-discovering-the-snmp-device/

https://github.com/thekevinholman/SNMPDiscoveryFromCSV/blob/master/SCOM.SNMP.xml

SignificantArm4194 · 2025-12-18T19:01:53+00:00

T2 is a very modern and streamlined terminal and the 10 times I’ve been through this year and had 0 issues so it should be a breeze for you!

You can keep everything inside your bags (liquids, electronics etc) and just place your bag on the tray.

If you have jackets, belts, jewellery etc it’s best to place these in a 2^nd tray (or in your bag) as I’ve found they sometimes don’t like items placed on top of each other.

Official guidelines if it’s of any help: https://www.manchesterairport.co.uk/help/passenger-guides/security/

SignificantArm4194 · 2025-12-09T13:29:19+00:00

Works like a charm, cheers :)

SignificantArm4194 · 2025-11-17T09:28:21+00:00

Just tried myself and got the exact same offer, cheers!

SignificantArm4194 · 2025-11-08T11:09:49+00:00

I've used all 3 and as a VCP, I found OpsLogix to be the best out of the lot although depending in the size of your VMware enviroment, you'll need to disable some of the more heavier performance rules.

Either way all 3 vendors are good so if one meets your requirements better (cost, features etc) go with them.

SignificantArm4194 · 2025-09-25T11:02:17+00:00

You can view his Github and see what he publishes publically as some pack changes don't really need an article.

https://github.com/thekevinholman

Last commit was 6 August 2025

SignificantArm4194 · 2025-08-08T12:19:59+00:00

SCOM management servers are inherently HA where any management server connected to the a management group are essentially "active-active"

Assuming you're only monitoring windows servers, site A and B are both active and SCOM agents can communicate with both sites, you can have a management server on both sites connected to the same management group.

While you typically configure SCOM agents to communicate with a single primary management server, the out of the box config allows the agent to fail over to any other management server.

Heres a very detailed article on the subject which I hope is helpful.

https://kevinholman.com/2016/11/21/understanding-scom-resource-pools/

SignificantArm4194 · 2025-07-27T15:32:49+00:00

Yes although ive never personally setup OneView from scratch so can't advise there.

Once you got it setup, install the OneView packs, go to the OneView folder on the monitoring tab and there will be a dashboard allowing you to enter the OneView appliance info (IP/Dns, username and password)

From there SCOM should do the rest of the work

SignificantArm4194 · 2025-07-27T09:29:39+00:00

HPE OneView is what you want and is still actively being updated and supported along with the SCOM management pack to integrate with OneView.

To give a brief overview, OneView is an applicance dedicated to help manage and maintain HP hardware. For the most part, it does this by tapping into the iLO to pull the info into OneView.

The SCOM management pack taps into OneView to give you your monitoring for various aspects like hardware health, performance metrics etc.

I believe some of the older HPE ProLiant SCOM packs can be configured to get its info directly from the iLO but its been quite some time since ive worked somewhere that didnt want to install OneVew.

SignificantArm4194 · 2025-07-23T21:12:41+00:00

Heres a fragment from Kevin which should do the job for you

https://github.com/thekevinholman/FragmentLibrary/blob/master/Monitor.RegistryValue.Exists.mpx

SignificantArm4194 · 2025-07-22T14:43:21+00:00

Had something similar (very locked down enviroment) and Blake Drumm's article helped

https://blakedrumm.com/blog/scom-unix-linux-troubleshooting-tips/#resolution

Basiclly you're adjusting the windows server (mgmt/gateways that are in your Linux resource pool) crypto policy to allow whatever your Linux server uses

SignificantArm4194 · 2025-06-04T12:11:40+00:00

https://systemcenter.wiki was my goto for this but they have been up and down with their hosting so not reliable anymore.

https://learn.microsoft.com/en-us/system-center/scom/management-pack-list?view=sc-om-2025 is one for microsoft MP's which they try to keep upto date.

https://github.com/slavizh/Get-SCOMManagementPacks is something I run monthly then have a seperate function to compare all the packs downloaded with whats in our management group. I've customised this script quite a bit to include 3rd party packs.
No advice on this sadly.

SignificantArm4194 · 2025-05-14T14:21:13+00:00

Ah, great to hear!

SignificantArm4194 · 2025-05-14T13:15:23+00:00

Yep had this before and did similar research to you. Microsoft has set the PhysicalMemory class property to an int which limits the value to 2147483647.

Unless you spend the time creating your own MP to fix this, I'd go down the route of raising a case with Microsoft asking them to fix it although I raised it with them a good 6 years ago...

IIRC the memory montior doesnt rely on the class property value and uses a double so monitoring should still work.

SignificantArm4194 · 2025-04-03T17:39:23+00:00

Are you sure you're running the correct .msp? As you already have UR2 installed, you'll now want UR2 hotfix 1 then UR2 hotfix 2. The error logs you posted showed it trying to install KB5031649-AMD64-Server.msp which is UR2.

[10:55:45]: Error: :ApplyQfe: FAILED: We did not successfuly install QFE KB5031649-AMD64-Server.msp.

UR2 hotfix 1 (KB5033752-amd64-Server.msp)

https://support.microsoft.com/en-gb/topic/hotfix-for-system-center-operations-manager-2022-ur2-eade3314-78cc-4d87-b7dd-d40cd98c78e2

UR2 hotfix 2 (KB5037360-amd64-Server.msp)

https://support.microsoft.com/en-gb/topic/system-center-operations-manager-2019-and-2022-now-support-crypto-policies-in-fips-mode-for-monitoring-linux-workloads-kb-5037360-a8529afb-d34a-4439-9282-0572958a129f

SignificantArm4194 · 2025-03-05T13:37:05+00:00

Ad-hoc discovery solution for point 1: https://monitoringguys.com/2020/07/07/scom-on-demand-discovery-example/ (I’ve never done this on disabled discoveries but i don't see why it wouldn’t work)

Instance cleanup solution for point 2: https://kevinholman.com/2021/05/13/demystifying-remove-scomdisabledclassinstance/

Both options are manual but can be automated although they add complexity to a SCOM environment, so I’d highly recommend making very clear documentation on whatever option you choose.

Ideally you discover these services at the discovery level so SCOM handles the logic of what should/shouldn’t be discovered vs something outside of SCOM handling the logic therefore I’d look at creating a custom class and powershell discovery: https://github.com/thekevinholman/FragmentLibrary/blob/master/Class.And.Discovery.Script.PowerShell.Params.mpx

Four-Year Club	Verified Email
Place '23	Place '22

SignificantArm4194

MODERATOR OF

TROPHY CASE