Post Views: 120 You can get the Script from the below link. https://github.com/souravmahato7/Codes/blob/SCOM/Get_All_The_ServiceMonitor.PS1 ################################################################## #Author: Sourav Mahato #Created Date:08/26/2019 #Modified Date:12/22/2019 #Purpose: Script for get all the service Monitor in SCOM #How to run: You just need to run it from SCOM Management Server and create Temp Continue Reading
Post Views: 86 $Alert = Get-SCOMAlert -Name “Alert Name” $MonitorID = $Alert.MonitoringRuleId $MonitorName = Get-SCOMMonitor -id $MonitorID $managementpack = $MonitorName.GetManagementPack() $managementpackname = $managementpack.DisplayName $managementpackname
Post Views: 89 Action Plan: Please upgrade the agent first by running the following command line. msiexec /i MOMAgent.msi /qn /l*v “C:\New folder\amd64\AgentUpgrade.log” AcceptEndUserLicenseAgreement=1 https://docs.microsoft.com/en-us/system-center/scom/deploy-upgrade-agents?view=sc-om-2019 Now we need to add the management group and management server name by following any of the below process. Continue Reading
Post Views: 113 Windows server 2016 Operating System is not supported for SCOM 2012 SP1. So I would recommend to upgrade the OS to Windows server 2012 R2. https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/jj656654(v=sc.12) Before proceeding with any of the below action plan, please make sure you have full backup (working) Continue Reading
Post Views: 183 Select mh.INSTALLTIME,mh.INSTALLEDBY,bm.displayname,av.isAvailable from dbo.MT_HealthService mhinner join BaseManagedEntity bm on mh.basemanagedentityid=bm.basemanagedentityidinner join dbo.Availability av on av.basemanagedentityid =mh.basemanagedentityidWHERE bm.DISPLAYNAME IN(‘ServerName’) Query to Update for all Manually installed Agent: UPDATE MT_HealthService SET IsManuallyInstalled=0 WHERE IsManuallyInstalled=1 Query to Update for specific Manually installed Agent: UPDATE MT_HealthService SET IsManuallyInstalled=0 WHERE Continue Reading
Post Views: 78 I was working on a case where live migration was failing for a cluster due to unwanted disk was attached on the virtual machine VM1. Here is the troubleshooting which I did to fix the issue. Issue ======================================================= Live migration is Continue Reading
Post Views: 107 For DBA Team: Before changing the SQL configuration, we need the following backups. 1. Please make sure you have the password for all the accounts which are being used in Orchestrator 2. Back up SQL Server service master key Sqlcmd -Q “BACKUP SERVICE MASTER KEY TO Continue Reading
Post Views: 259 For the Orphan instances to clean, please follow the below process. Script is located here: https://github.com/souravmahato7/SQL/blob/SCORCH/SCORCH_Orphan_Data_Purge.sql 1. Take full backup of Orchestrator database. – Need to stop the Runbook services on the Runbook servers. 2. Execute below SQL queries to check Continue Reading
Post Views: 62 Issue: Found that after installing the UR5 patch for Runbook servers, Runbook service account is getting reverted back to its old account when we have already changed the account with a new one. Workaround: Firstly, we need to change the below registry key value for Continue Reading
Post Views: 110 TLS 1.2 is the secure way of communication suggested by Microsoft with best-in class encryption. SSL and early TLS are not considered strong cryptography and cannot be used as a security control. Microsoft has added official support for TLS1.2 security protocols in SCORCH 2012 Continue Reading