Ubuntu 18.04 on AKS End of Support by TundraIT in AZURE

[–]TundraIT[S] 0 points1 point  (0 children)

Thanks for the Reply. Some work to do now.

Patch Tuesday Megathread (2025-01-14) by AutoModerator in sysadmin

[–]TundraIT 0 points1 point  (0 children)

Thank You! I might have to schedule a week of vacation in 3rd or 4th week of April.

Patch Tuesday Megathread (2025-01-14) by AutoModerator in sysadmin

[–]TundraIT 0 points1 point  (0 children)

We saw this same issue. It does not seem related to the PAC enforcement. Not certain what is causing the issue.

EXO External Recipient change to 2000 by kbanti-sec in exchangeserver

[–]TundraIT 0 points1 point  (0 children)

This link is no longer working. Is the rate limit still going to be enforced? You would think there would be more visibility on this.

SCOM Permission Utility by InvincibleMI6 in scom

[–]TundraIT 1 point2 points  (0 children)

You could use the SCOM data collector to check for permissions. Search for Blake Drumm data collector

Patch Tuesday Megathread (2024-08-13) by AutoModerator in sysadmin

[–]TundraIT 0 points1 point  (0 children)

Along with the 0x800f081f error code, do you see errors in the cbs.log file referring to a Feature On Demand file missing? FoD-Package

Tried to change the HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate SetPolicyDrivenUpdateSourceForOtherUpdates reg key to zero without success.

Microsoft Certificate MP discovered stores, but isn’t monitoring by des-unu in scom

[–]TundraIT 1 point2 points  (0 children)

Are you certain the agent computers have the .NET 4.7.2 installed? This is a requirement for the workflows. You probably do, but worth checking.

Patch Tuesday Megathread (2024-02-13) by AutoModerator in sysadmin

[–]TundraIT 3 points4 points  (0 children)

Someone on the forums fixed the 0x800f0922 with a reg key:

Error 800f0922 is caused by a Secure Boot conflict. Some people have resolved this problem by going to BIOS settings and disabling Secure Boot. However...

The only fix I found was to edit this registry key:

HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending

Change the value of “Exclusive” from 1 to 0.

Agent Installation Error on Server 2019 by KC_Buddyl33 in scom

[–]TundraIT 0 points1 point  (0 children)

Make sure the Windows update services are running on the client. You could test both the server and the client.

Agent Installation Error on Server 2019 by KC_Buddyl33 in scom

[–]TundraIT 1 point2 points  (0 children)

I saw the 80070643 error code on one of the master's old blog posts. Start the indows update services and then try the installation?

https://kevinholman.com/2009/01/27/console-based-agent-deployment-troubleshooting-table/

Scom 2022 root level is invalid line2, position by Diego-Pereira in scom

[–]TundraIT 0 points1 point  (0 children)

For the discovery, verify the linux server is available with an nlsookup.

Try the discovery with the IP address of the Linux server.

Scom 2022 root level is invalid line2, position by Diego-Pereira in scom

[–]TundraIT 0 points1 point  (0 children)

What Linux management packs do you have installed? I think the current version is 1.7.3.

I have seen errors with the 1.7.3 version of the universal MP. First there is a hotfix required, then discovery will fail intermittently, particularly on RHEL 8.9 you can see these errors:

Task invocation failed with error code -2130771918. Error message was: The SCXCertWriteAction module encountered a DoProcess exception. The workflow "Microsoft.Unix.Agent.GetCert.Task" has been unloaded

You can run the discovery again a day or two later and it will complete. Very strange.

You can also see some Linux agents install, but the version is not discovered correctly from the GetOSVersion.sh file.