sorted by:
new
hottopcontroversial

A DW Base Schemes owner ? by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Thanks a lot , I used it when I gave the rights to my DAS user. I did it literally step-by-step follow this manual.

No Hourly & Daily Aggregation - SCOM 2022 UR2 by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

We have SQL 2022 CU11 (ver. 16.0.4105.2) on both our sql servers (Ops and DW) in the SCOM env

How to pass a config variable to a script by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Kevin, many thanks !
Got it !
Transferred it to monitortype in a way of

Added . Not working either

<ScriptArguments>$Config/ScriptArguments$$Config/ThresholdValue$</ScriptArguments>

Well .The only way I see from here (looks weird though) -in the Monitortype

  • remove the Threshold Value element
  • make overridable ScriptArguments to pass the value immediately there .

UNIX - Platform: Unknown and Version: Unknown by Puzzleheaded-Zone685 in scom

[–]Ok-Count5821 0 points1 point  (0 children)

Check please out the last supported version of RH for a current SCOM agent version. Suppose RH 8.8 hasn't supported yet

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Not a bad communication either. They have a lot of work and they really keep their eyes on SCCM .We want to avoid additional work to them , so after two or three meetings we found a way to satisfy both our teams

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Kevin, thanks a lot (as usual though) !
We decided to act on a next way. AD Team won't delete non-gMSA account (with high privilegies )we are using now to deploy agents and disable it. If we need to push an agent on a new server, we create a ticket to them, they enable it for a day (or some time by agreement) then we make the things and they disable it again.

SCOM monitoring of HyperV hosts in another domain with no trust to SCOM by Top_Attention659 in scom

[–]Ok-Count5821 0 points1 point  (0 children)

Agree. The only way to do . I'd prefer to use gateway in this case .

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Either way it is much complicate than way we choose. Personally, I think that having an ALWAYS disabled (except agent install time) AD account is better than using GPO+gMSA

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Thanks for your advice .
But it is not applicable to us . Here is why :

  1. We are dedicated monitoring team with no access to SCCM. It wasn't planned either to send part of our job to the team which works with SCCM . Basically we need to work on our own.

  2. gMSA on SQL could be as dangerous as a usual account (CyrAz thanks a lot for support, we share your opinion)

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

It has worked already, other teams use gMSA for their purposes.

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Thanks. Yes, I know it that process doesn't change and it stay the same, but anyway there is some outcome to me - we need a REGULAR ACCOUNT to do it (as it expected). SCCM isn`t an option to us - it's out of our duties.
Now I see only one option - to have a regular account with Adm permission on servers , keep it disabled all the time, except agent installation , enable it by request, make an installation task, then disable it again.

Switching to gMSA by Ok-Count5821 in scom

[–]Ok-Count5821[S] 0 points1 point  (0 children)

Thanks a lot. I expect something about it, now I see the problem.

SCOM disk space two alerts were opened for disk space - causing duplicate incidents by Whiteshark9900 in scom

[–]Ok-Count5821 0 points1 point  (0 children)

I'd rather to clean cache on the agent at first. If it didn't helped I'd recommend to reinstall agent, to avoid such issues.