During install and during normal work, SCOM 1801 will not validate a service account if you are running the installer or console under a Smart Card credential.  Running the installer or console under a username/password account does correctly validate service accounts.

This problem prevented me from installing SCOM 1801 for multiple days.  I am able to add agents to computers as long as I click through the account validation error that shows up after entering a service account for the agent service to run under.

Hello,

We have a Service Monitor targeted to a group, few servers have service available and few don't. We are seeing floods of alerts on one or two servers from this group which don't have the service installed on it. Not sure why the state keep on changing to running and not running frequently for a server which don't have service at all. Can someone help here pls.

Regards

SK

Hi Team,

While installing SCOM 2019 I m getting the error as " one or more accounts provided could not be validated. Please provide valid user name and passwords". 

Created the secuirty Group for SCOM and added the service accounts under this group. Added this group as local admin on the SCOM Management Server where I'm trying to install.

Please suggest on what could be the issue

Regards

SK

Is the powershell widget in SCOM 2019 limited to only scom related items? I am interested in creating a powershell widget to monitor O365 services with the following script but nothing is happening. I get a blank screen. It works well in powershell itself.

Thanks,

Rene 

Import-Module PSWinDocumentation.O365HealthService -Force
$ApplicationID = 'xxxxxxxxxxxxxxxxxxx'
$ApplicationKey = 'xxxxxxxxxxxxxxxxxxxx'
$TenantDomain = 'xxxxxxxxxxx' 
$O365 = Get-Office365Health -ApplicationID $ApplicationID -ApplicationKey $ApplicationKey -TenantDomain $TenantDomain -ToLocalTime 
$O365.CurrentStatus | Format-Table -AutoSize

I am have performed a health maintenance, were resetting monitors which their respective alert has been closed prior the upgrade to 2019. I have an issue with 3 monitors where after resetting, they return to warning but the alert is not fired.

1. Checked overrides

2. Disabled and re enabled the monitor

3. Disabled discovery, run remove disabled class powershell script and re discover

4. Cleared cache

All in vein, anything else i am missing ?

Hi,

When I click "Create HealthService Login as SysAdmin Task" I got this error:

'sqlcmd.exe' is not recognized as an internal or external command,
operable program or batch file.

This is happen just in one of SQL servers.

How can I resolve it?

Thanks

Hi,

I'm using the Clustered Data ONTAP management pack to monitor my netapp storage.

In the monitoring pane there is a view called volumes. When i open this i get aloading in the middle pane but never any results. When i do the same in the webconsole web interface it shows all my volumes.

How can i resolve this to get is working in the operations manager console?

Regards

Thomas

I am having an issue logging into the new web console after the ver 1807 to 2019 upgrade.  This was working before the upgrade.  This issue is when I try to log in as an operator role.  I can successfully login using my administrator role account.  When I try to go to https://...../operationsmanager I get the popup seen below.  I also see the corresponding event viewer message 

OpsMgr SDK Service   Event ID:   26319

"An exception was thrown while processing GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions for session ID uuid:abf33888-7f7f-4e2e-8143-e6c6124e5411;id=11.
 Exception message: The creator of this fault did not specify a Reason.
 Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Incorrect syntax near the keyword 'CREATE'.)."

Hello.

SCOM 1807
issue only affecting DB2 monitored servers.

Some of my sample rates are super high causing false alarms for disk, cpu and memory metrics. 

That pictures is from percentmemoryused... Ive no idea whats causing this.. any ideas?

Hi all !

 Here I am again 8) because I am in complete stuck (as it was many times before), so I hope for a your help.

 I have couple of agents installed on Windows 10 Workstation. Almost all of them were push-installed so their agents have settings similar to other installed on servers  (an action account is LocalSystem, and an additional admin account (g_adm)is in "LocalAdmin" group). Despite it a lot of issues with poweshell scripts running  raise  kind of " The PowerShell failed to execute successfully."

 They notice run timeout as a reason (over 300 sec) 

I checked out all the rights of  g_adm . It has  full administrative access to computer as a member of admins group. No other errors except Powershell scripts run .

What could be wrong ? What should I check additionally to find the root cause ?

Thanks in advance

Andrii

Hi guys,

have a look of these two screenshots... I do see the SQL 2017 Cluster as discovered and healthy but if I have a look at the SQL 2017 View it is displayed as "not monitored" ... we already cleared cache etc etc but no effect ... anyone seen this before or any idea?

Thanks in advance,

Markus

Hi All,

After upgrading to UR14 we received the Alert in SCOM as "Operations Manager Reporting Console Unavailable" we are able to access the link manually from one of our management server. kindly assist on this.

Thank you

Regards,

Kumar B

Morning, I want to ask if anyone here has installed and is using:

Kevin Holman's SCOM Management Properties and Tasks Pack for Agents and Server Roles v7.0.0.66 Management Pack from Kevin Holman.

I have installed it in our new SCOM 2019(on Windows Server 2016) environment to assist me with identifying TLS settings and getting TLS 1.2 implemented across our environment on the servers. However, after install, the only servers it display TLS info on is the SCOM Management servers. On my agent monitored servers, even the bottom 3-4 lines of the TLS info it is looking for are missing.

I am monitoring Windows Server 2012R2 and Windows Server 2016.

Any assistance, reference is greatly appreciated.

TS.

Hi,

We are running SCOM 2016 and configure it for multi-tenants. It's a pretty new setup. We override the seed discoveries of the MPs on per customer basis.

I have received a request from a customer to monitor few of their services. They have shared the server names and the services running on them that needed to be monitored. First I want to share my brain storming: I am thinking that there should be a separate class of discovery where it discovers the monitor via registry entry, then I would override it to run on specific group of servers that related to a specific customer. Why I want to do this because I don't want that SCOM tries to discover those services on all customers' servers.

Please, let me know the correct way of doing it?

Be Vanmost!

Hi Guys, 

I have the following script that is called via command channel and used in a subscription for a few specific alerts. Now it works perfectly and logs the ticket in our ticketing system but it is logging 3 or 4 of the same ticket numbers for different alerts, so for example it would log ticket number 10005 for 2 different servers "Failed to connect to Computer"

Now I have an idea this is possibly got to do with the Foreach when there are multiples but for the life of me I can seem to get it right.

I would appreciate any help.

[CmdletBinding()]
param (
    $AlertName
)

# Execute SOAP Call

function Execute-SOAPRequest

(

        [Xml]    $SOAPRequest,

        [String] $URL

)

{

        $user = 'User';

        $pass = 'pass';

        $pair = "$($user):$($pass)";

        $encodedCreds = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($pair));

        $basicAuthValue = "Basic $encodedCreds";



        $Headers = @{

            Authorization = $basicAuthValue

        };

       

      

        $soapWebRequest = [System.Net.WebRequest]::Create($URL);

        $soapWebRequest.Headers.Add("SOAPAction","`"`"");

        $soapWebRequest.Headers.Add("Authorization",$basicAuthValue);



        $soapWebRequest.ContentType = "text/xml;charset=`"utf-8`"";

        $soapWebRequest.Accept      = "text/xml";

        $soapWebRequest.Method      = "POST";

      

        

        $requestStream = $soapWebRequest.GetRequestStream();

        $SOAPRequest.Save($requestStream);

        $requestStream.Close();

      

        

        $resp = $soapWebRequest.GetResponse();

        $responseStream = $resp.GetResponseStream();

        $soapReader = [System.IO.StreamReader]($responseStream);

        $ReturnXml = [Xml] $soapReader.ReadToEnd();

        $responseStream.Close();

      

        



        return $ReturnXml;

}

# Get Description and insert into Incident

$alerts = Get-SCOMAlert | where {$_.Name -eq "$AlertName" -and $_.ResolutionState -ne "255" -and $_.LastModifiedBy -eq "System"} | Select Name,PrincipalName,Description
$Details = $alerts.Description
$PrincipalName = $alerts.PrincipalName


# Update each alert with the information from the property NetbiosComputerName
foreach ($alert in $alerts)
{
$url = 'https://itsm.cpmany.com/arsys/services/ARService?server=arsystem&webService=HPD_IncidentInterface_Create_WS';



$soap = [xml]@"<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:HPD_IncidentInterface_Create_WS"><soapenv:Header><urn:AuthenticationInfo><urn:userName>orcadmin</urn:userName><urn:password>orcadmin</urn:password></urn:AuthenticationInfo></soapenv:Header><soapenv:Body><urn:HelpDesk_Submit_Service><urn:Assigned_Group>BSI CSD Remote BackOffice</urn:Assigned_Group><urn:Assigned_Support_Company>Global Support Services</urn:Assigned_Support_Company><urn:Assigned_Support_Organization>Altron Group and SME</urn:Assigned_Support_Organization><urn:First_Name>System Center</urn:First_Name><urn:Impact>1-Extensive/Widespread</urn:Impact><urn:Last_Name>company</urn:Last_Name><urn:Reported_Source>Web</urn:Reported_Source><urn:Service_Type>Infrastructure Event</urn:Service_Type><urn:Status>Assigned</urn:Status><urn:Summary>$AlertName $PrincipalName</urn:Summary><urn:Notes>$Details</urn:Notes><urn:Urgency>1-Critical</urn:Urgency><urn:Submitter>orcadmin</urn:Submitter><urn:Login_ID>systemcenterin2food</urn:Login_ID><urn:Action>CREATE</urn:Action></urn:HelpDesk_Submit_Service></soapenv:Body></soapenv:Envelope>"@;



$_.Exception.InnerException

[xml]$ret = Execute-SOAPRequest $soap $url 

$result = $ret.Envelope.Body.ChildNodes.Incident_Number

# Get Incident Number and insert Into Alert
$result

Get-SCOMAlert | where {$_.Name -eq "$AlertName" -and $_.ResolutionState -ne "255" -and $_.LastModifiedBy -eq "System"} | Set-SCOMAlert-TicketId $result
}
Exit

Hi All,

We are updating the SCOM 2012 R2 with UR14 soon.

Got a doubt with the user account to be used to install the UR14. Currently we are planning to use two seperate accounts.

One account to install the UR14 and another account to run the UR14 SQL queries.

This is becase the SCOM team do not have permission to login to the SCOM Database and Datawarehouse Servers, this is managed by a seperate team.

So, the question is by using seperate accounts will the UR14 update be affected in any way. Like Agents do not show up in Pending Management after UR14 update, etc...

I had read in Kevin Holman's bolg for updating Update Rollups in SCOM "we MUST log on to each server role as a Local Administrator, SCOM Admin, AND the account must also have System Administrator role to the SQL database instances that host your OpsMgr databases "

Please advice, thanks in advance!

Sreejeet

Hi all,

We have successfully updated SCOM 2012 R2 with UR14. Few tasks are pending, one among them is tofix a bug in business hours based reporting.

We are following the Microsoft article for this:

https://support.microsoft.com/en-us/help/4024942/update-rollup-14-for-system-center-2012-r2-operations-manager

As per the above link after the Management Server is updated with UR 14 the updated RLD files wil be available on the updated Management Server. But we noticed the RDL file on the updated Management Server is from theyear 2016 and the RDL file running in our Production enviroment is formyear 2020. So its strange that without we upgrading SCOM with UR14 earlier how do we have RLD file which is later than the RLD file available in UR14. Also we see in the test lab the RDL file from UR14 is from the year 2016. Could you please assist on this.

Thanks,

Sreejeet

Hi All, 

Asking the general Population to see whether this is a 'just me' situation. 

I have recently upgraded to SCOM 2019 from SCOM 1807 and am now trying to reconnect to my azure environment. i was eager to see what the possibilities were with the log analytics connection however when i click 'register to azure Log analytics' i immediately receive the below unhandled exception. 

I have tried this from my management server and my widnows 10 VM and cannot get this to load.  

as always any suggestions would be greatly appreciated 

Richard Scott

Hi,

How can i troubleshoot the error

Data Warehouse object health state data writer process failed to perform maintenance operation

Google shows there are tasks submitted from SCOM tot the database but the SQL server also has it's own tasks.

Activity monitor shows insert and rollback actions.

Why is a management server talking to the DW server.

Lots of errors in the eventlog operations manager, don't know where to begin.

Thank for the help

The Update Rollup 1 for System Center 2019 Operations Manager is now available:
Update Rollup 1 for System Center 2019 Operations Manager

Introduction

For the list of features released in Update Rollup 1, please refer:

What’s New in System Center Operations Manager 2019 Update Rollup 1 here.

Improvements and issues that are fixed

Web Console Fixes/Changes:

• State widget now supports sorting by health and age. 
  
• Alert widgets can now be searched on Date Time and sorted based upon age and severity.
  
• The alert link in email notification when browsed throws an error, “Your session with the Web Console server expired" even though the user was not logged in web console . You will now see the login page post this fix.
  
• Alert summary view in SCOM Web console was fixed in size.  This can be expanded as required now.
  
• When Alert state is changed to some custom state, then these alerts are not displayed in web console. Alerts with custom resolution states will be displayed now.
  
• Few additional scrollbars appear when a customer widget is created in web console or browser window size is reduced.
  
• Improvement: SCOM views will load/save much faster than before. 
  

Unix/Linux/Network Monitoring Fixes/Changes:

• SCX by default does Info level logging which causes SCX logs to be filled up soon. With 2019 UR1, Warnings and Errors will be logged by default not Info.
  
• In the network device monitoring, if the node property is changed to null/empty, it displays the old value of the property not the null value. The actual value will be displayed now which includes null.
  
• In a scenario where multiple (~500) virtual network interfaces are running on agent, SCOM sometimes received heartbeat failure alerts for such agents. SCOM will monitor only physical interfaces hosted on these machines. For monitoring virtual interfaces, you need to set "enumvif" to true. 
  
• SNMP GET or SNMP WALK resulted monitoring host to crash when the network object ID is equal to ULONG Max. There is an error with event ID 4000 due to this crash.
  
• For linux distros servers, when the kernel version >= 4.18, then file system related performance data is shown as 0 in SCOM. This is fixed in FS provider to make it kernel version agnostic and collect file system stat info.
  
• Use of Async Windows Management Infrastructure (MI) APIs is default functionality from SCOM 2019 UR1 for scalability improvements.
  More details here. [Insert URL here}
  

Admin Console Fixes:

• When admin created “one-time maintenance mode schedule” for non-English locales, SCOM console displays an error “The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection”. Admin would be able to create one-time maintenance schedule now.
  
• When SCOM agent is multihomed, then SCOM 2019 MS always displays logon type as “Interactive” for this agent. The correct logon type will be displayed now.
  Unit monitor to check correct logon type for Run as Account had incorrect name and Operational State.
  
• “Operations Manager Products” view in Admin console did not update the “Version” column for the installed component version. This column will now reflect the updated version of all the components listed.

Others:

• When system proxy is configured on the Reporting Server; proxy overrides are ignored by the “Report Console Watcher Monitor” and “Web Console Watcher Monitor” and as a result HTTP/HTTPS access fails.  With UR1 fix, “Set proxy Direct” parameter of the mentioned monitors can be set to true and URLs will be accessed.
  
• SCOM did not discover Windows Cluster which are deployed on servers with IPV6 network only enabled. IPV6 network will be supported for cluster monitoring now.
  
• When the Domain controller is moved to a different AD site, then SCOM does not display the correct site name. Any dynamic group which are created for SiteName will also fail

In addition to these, all the issues fixed in SCOM 2016 UR8 and prior UR for SCOM 2016 are also fixed in SCOM 2019 UR1. Details of the fixes are below.

• In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-v server; every hour the healthservice.exe of each Virtual machine write into the VM page file simultaneously. Due to this concurrent paging, every hour disk I/O increases and database becomes unresponsive. HealthService.exe now have Memory Trimming enabled by default on an hourly schedule. A registry key is provided to disable the memory trimming and control the duration.

         Registry key is: "HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\MemoryTrimming"

         Enable – 0 (Trimming is disabled);1 (trimming is enabled)

         DelayInSeconds – Time period agent waits to start trimming (default is 120s)

         PeriodInSeconds – Recurring period at which the working set should be trimmed (default is 3600s)

• Historical data do not appear, if input reporting end time is before group creation time. With this fix, historic data for a group (if data is available for objects in the group) would be displayed irrespective of group creation time.
  
• Maintenance mode state changes which are recorded in MaintenanceModeStage table requires grooming when table grows. If the table is large, grooming takes longer and the operation times out with SQLTimeOut exception.
  
• If a group is renamed in a Management pack, then console shows the new value but Powershell command Get-SCOMGroup returns the old name of group. Database Updates functionality was inconsistent for SCOM group renaming through MP and SCOM Console.
  
• CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time. 
  
• Improvement: Sometimes SQL stored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDK service fails to start. This is fixed and above SQL stored procedure will complete faster now.
  
• Improved the performance of SCOM console in listing the groups.
  
• Users of a scoped group are not able to use the Console.
  
• SCOM console crashes while trying to connect to Azure Log Analytics and Azure Monitor.
  
• SCOM Network Device Re-Discovery now probes for SNMP V3 devices too.
  
• Agents by Health State report shows duplicate agent names.
  
• Fixed an issue that prevented addition of a group in the Storage Spaces Direct 2016 management pack dashboard.
  
• Linux agent is not able to get the correct version and port details for JBoss EAP 7.1.
  
• An issue that lead to creation of multiple empty temp files in the /tmp directory of Linux servers has been fixed.
  
• Fixed the formatting issue with the output for the task ‘Top10 CPU Processes' when using Windows Management Infrastructure (MI) APIs.
  
• Fixed an issue that caused the corruption of /etc/login.cfg file on AIX 7 machines during install/upgrade of the agent.
  
• AIX Agent is now transitioned to 64-bit package to accommodate more stack and heap space if needed to avoid any stack/heap overflow which occasionally leads to heartbeat failure.
  
• Free memory calculation accommodated appropriately on RHEL-7 platform.

Blog:https://thesystemcenterblog.com LinkedIn: