SCOM 2012 R2 Console crashes after October Windows Update -Hotfix KB3200006

SCOM 2012 R2 Console crashes after October Windows Update

• The SCOM 2012 R2 Console crashes after installing the Latest October patches.
• This is know issue and microsft has released a Hotfix KB3200006.
• https://support.microsoft.com/en-us/kb/3200006.
• Please downaload the hotfix and install to resolve the Console Crash issue.
• It affects all OS versions. So you need to install on App OS where there is SCOM 2012 R2 Console irrespective of the UR 

SCCM 2012 R2 Log File for Windows Update Agent and WSUS Server issues

SCCM 2012 R2 Log File for Windows Update Agent and WSUS Server issues

Windows Update Agent

The following table lists the log files that contain information related to the Windows Update Agent.

Log name	Description	Computer with log file
WindowsUpdate.log	Records details about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.	Client

WSUS Server

The following table lists the log files that contain information related to the WSUS server.

Log name	Description	Computer with log file
Change.log	Records details about the WSUS server database information that has changed.	WSUS server
SoftwareDistribution.log	Records details about the software updates that are synchronized from the configured update source to the WSUS server database.	WSUS server

SCCM 2012 R2 Software Update Point Log file

SCCM 2012 R2 Software Update Point Log file

Software Update Point Log Files

he following table lists the log files that contain information related to the software update point.

Log name	Description	Computer with log file
objreplmgr.log	Records details about the replication of software updates notification files from a parent to child sites.	Site server
PatchDownloader.log	Records details about the process of downloading software updates from the update source to the download destination on the site server.	The computer hosting the Configuration Manager console from which downloads are initiated
ruleengine.log	Records details about automatic deployment rules for the identification, content download, and software update group and deployment creation.	Site server
SUPSetup.log	Records details about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.	Site system server
WCM.log	Records details about the software update point configuration and connections to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.	Site server that connects to the Windows Server Update Services (WSUS) server
WSUSCtrl.log	Records details about the configuration, database connectivity, and health of the WSUS server for the site.	Site system server
wsyncmgr.log	Records details about the software updates synchronization process.	Site system server
WUSSyncXML.log	Records details about the Inventory Tool for the Microsoft Updates synchronization process.	The client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Dell Client Management Pack Version 5.1 for SCOM 2012 R2

Dell Client Management Pack Version 5.1 for SCOM 2012 R2

The Client Management Pack enables the following operations to manage Dell client systems:

• Discover and monitor Dell Latitude, Dell Precision, and Dell OptipPlex computers running supported OMCI and client Windows operating systems.
• Group Dell Clients without instrumentation and client systems running without OMCI service under the Dell UnManaged Clients group.NOTE: Dell Vostro systems are displayed under the Dell UnManaged Clients group.
• Monitor the health status for client hardware components by polling at periodic intervals, and update the state of each component in the diagram view. A health status is a standardized description of the functional performance of a component, system, or service. For more information, see Tasks
• Perform client shutdown and reboot tasks.
• Launch remote desktop for Dell client systems.
• Generate reports on Dell Windows

SCOM 2012 R2 Windows Server 2012 R2 Storage Direct Management Pack

SCOM 2012 R2 Windows Server 2012 R2 Storage Direct  Management Pack

• Microsoft has released a new Storage Management Pack for Window Server 2012 R2.
• This management pack supports up to:
  16 Storage Nodes
  12 Storage Pools
  120 File Shares.
• This Management Pack contains rules to monitor physical disk and enclosure state in storage spaces.
• Health is calculated by the storage service and is passed to Virtual Machine Manager (VMM) using the Storage Management API (SM-API), and is in turn passed to Operations Manager (OM) through the OM connector for VMM.
  
  
• There are no state or alert visualizations as part of this MP. 
• All alerts for physical disks and enclosures must be manually closed and any health state impact manually reset.
• You can see file share and storage pool health on the VMM Fabric Dashboard or you can build your own views in a custom MP. 
• If OM agent proxy setting is not enabled for file server nodes and VMM server, it needs to be turned on. This can be done from Administration space in OM console.

You can see the Rollup Model below for the MP

You can Download the Management pack from here -->Click here to download

Lync 2013 MP Install Step by Step SCOM 2012 R2

Lync 2013 MP Install Step by Step:

• Lync has taken over the entire communication channel.
• Gone are the VOIP IP Cisco Phones which use to sit on your Desk.
• Today everything is going to Mobile and Lync is the best and cheapest option from Micrososft.
• So almost all enterprise have decided to migrate to Lync. So much is the Lync affects today that, we need a realtime monitoring more critical then outlook.
• So Microsoft has worked on it very hard and have brought the realtime Monitoring using SCOM for Lync 2013.

Microsoft Lync Server 2013 includes two SCOM management packs:

• The Component and User Management Pack (Microsoft.LS.2013.Monitoring.ComponentAndUser.mp):

• This MP Monitors Lync Server issues recorded in event logs, registered by performance counters, or logged in the call detail records (CDR) or the Quality of Experience (QoE) databases.

Active Monitoring Pack (Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp):

• This MP proactively tests key Lync Server components such as logging on to the system, exchanging instant messages, or making calls to a phone located on the public switched telephone network (PSTN). These tests are conducted using the Lync Server synthetic transaction cmdlets. 

Example:

Test-CsIM: cmdlet is used to simulate an instant messaging conversation between a pair of test users. If this simulated messaging conversation fails an alert will be generated.

Steps to Install MP:

• Download the files Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp and Microsoft.LS.2013.Monitoring.ComponentAndUser.mp.

• In System Center Operations Manager, click Administration.In the Administration pane, right-click Management Packs, and then click Import Management Packs.

• In the Select Management Packs dialog box, click Add, and then click Add from disk.

• In the Online Catalog Connection dialog box, click Cancel to prevent Operations Manager from going online to see if any dependencies exist for the Lync Server management packs. If you are using System Center Operations Manager 2012, click No.

• In the Select Management Packs to import dialog box, locate and select the files Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp and Microsoft.LS.2013.Monitoring.ComponentAndUser.mp and then click Open. To select multiple files in the dialog box, click the first file, hold down the Ctrl key and then click the second file.

• In the Select Management Packs dialog box, click Install. If you get an error message and installation fails, that typically means that the management pack files are in a folder protected by the Windows User Account Control. If this occurs, copy the files to a different folder and then restart the import and installation process.

• In the Select Management Packs dialog box, click Close. Note that the import and installation process might require several minutes to complete.

New Features added in SCOM 2016

New Features added in SCOM 2016

• SCOM 2016 is the next version of SCOM after SCOM 2012.
• There architecture remains the same, but the support for dasboard has been improved vastly.
• If you have see the SQL mp then you could see cool charts being displayed.
• The same has been extended to all the MP's and given as a template which you can extend it to your MP as well.
• The support for Azure is also improved,earlier you have connect through certificates to establish connection, but now you connect through Azure AD,so you just have to enter the username and password and it will connect you to the Azure platform from scom.This is a huge welcome move.
• Also it will support Windows 2016,and SQL 2014.

VBSCript to check if file exist and update scom

VBSCript to check if file exist and update scom



Dim oAPI, oBag
Set oAPI = CreateObject("MOM.ScriptAPI")
Set oBag = oAPI.CreatePropertyBag()
Set objFSO = CreateObject("Scripting.FileSystemObject")
strFile = "C:\MYFILE.LOG"
If objFSO.FileExists(strFile) Then
Call oBag.AddValue("Status", "OK")
Else
Call oBag.AddValue("Status", "Error")
Call oAPI.Return(oBag)
End If