What is Sqoop and why it is used ?

Sqoop:

Sqoop is an open source framework provided by Apache. It is a command-line interface application for efficiently transferring bulk data between Apache Hadoop and external datastores such as relational databases, enterprise data warehouses. It is used to import data from relational databases such as MySQL, Oracle to Hadoop HDFS, and export from Hadoop file system to relational databases. 

Sqoop Import:
The import tool is used to imports individual tables from RDBMS to HDFS. Each row in a table is treated as a record in HDFS. 

Sqoop Export:
The export tool exports a set of files from HDFS back to an RDBMS. The files given as input to Sqoop contain records, which are called as rows in table.

Why Sqoop is used?
For Hadoop developers, the work starts after data is loaded into HDFS. For this, the data residing in the relational database management systems need to be transferred to HDFS and might need to transfer back to relational database management systems. So developers can always write custom scripts to transfer data in and out of Hadoop, but Apache Sqoop provides an alternative.
Sqoop uses MapReduce framework to import and export the data, which provides parallel mechanism as well as fault tolerance. Sqoop makes developers life easy by providing command line interface. Developers just need to provide basic information like source, destination and database authentication details in the sqoop command. 

Sqoop Connectors:
All the existing Database Management Systems are designed with SQL standard in mind. However, each DBMS differs with respect to dialect to some extent. So, this difference poses challenges when it comes to data transfers across the systems. Sqoop Connectors are components which help overcome these challenges. Data transfer between Sqoop and external storage system is made possible with the help of Sqoop's connectors. Sqoop has connectors for working with a range of popular relational databases, including MySQL, PostgreSQL, Oracle, SQL Server, and DB2. Each of these connectors knows how to interact with its associated DBMS. There is also a generic JDBC connector for connecting to any database that supports Java's JDBC protocol. In addition, Sqoop provides optimized MySQL and PostgreSQL connectors that use database-specific APIs to perform bulk transfers efficiently.

What are Daemons in Hadoop and types of dameons

Daemons:
Daemons are resident programs which constitute to hadoop running. In computing terms it is a process that runs in the background.
Hadoop has five such daemons. They are 1.NameNode,
2.Secondary NameNode
3.DataNode
4.JobTracker
5.TaskTracker.

Each daemons runs separately in its own JVM. We discuss about these daemons in this post as they are associated with HDFS and MapReduce.

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 Log File for Software Updates and Network Access Protection issues

Software Updates and Network Access Protection

The following table lists the log files that contain information related to software updates and Network Access Protection.

Log name	Description	Computer with log file
ccmcca.log	Records details about the processing of compliance evaluation based on Configuration Manager NAP policy processing, and contains the processing of remediation for each software update required for compliance.	Client
ccmperf.log	Records activities related to the maintenance and capture of data related to client performance counters.	Client
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
PolicyEvaluator.log	Records details about the evaluation of policies on client computers, including policies from software updates.	Client
RebootCoordinator.log	Records details about the coordination of system restarts on client computers after software update installations.	Client
ScanAgent.log	Records details about scan requests for software updates, the WSUS location, and related actions.	Client
SdmAgent.log	Records details about tracking of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance. This log file is shared with compliance settings.	Client
ServiceWindowManager.log	Records details about the evaluation of maintenance windows.	Client
smssha.log	The main log file for the Configuration Manager Network Access Protection client and it contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.	Client
Smsshv.log	This is the main log file for the System Health Validator point and records the basic operations of the System Health Validator service, such as the initialization progress.	Site system server
Smsshvadcacheclient.log	Records details about the retrieval of Configuration Manager health state references from Active Directory Domain Services.	Site system server
SmsSHVCacheStore.log	Records details about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.	Site system server
smsSHVQuarValidator.log	Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL	Site system server
smsshvregistrysettings.log	Records any dynamic change to the System Health Validator component configuration while the service is running.	Site system server
SMSSHVSetup.log	Records the success or failure (with failure reason) of installing the System Health Validator point.	Site system server
SmsWusHandler.log	Records details about the scan process for the Inventory Tool for Microsoft Updates.	Client
StateMessage.log	Records details about software updates state messages that are created and sent to the management point.	Client
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
UpdatesDeployment.log	Records details about deployments on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.	Client
UpdatesHandler.log	Records details about software update compliance scanning and about the download and installation of software updates on the client.	Client
UpdatesStore.log	Records details about compliance status for the software updates that were assessed during the compliance scan cycle.	Client
WCM.log	Records details about software update point configurations and connections to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.	Site 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 server
WUAHandler.log	Records details about the Windows Update Agent on the client when it searches for software updates.	Client

SCCM 2012 R2 Compliance Settings and Computer resource Access issues

SCCM 2012 R2 Compliance Settings and Computer resource Access issues

Compliance Settings and Company Resource Access

The following table lists the log files that contain information related to compliance settings and company resource access.

Log name	Description	Computer with log file
CIAgent.log	Records details about the process of remediation and compliance for compliance settings, software updates, and application management.	Client
CITaskManager.log	Records information about configuration item task scheduling.	Client
DCMAgent.log	Records high-level information about the evaluation, conflict reporting, and remediation of configuration items and applications.	Client
DCMReporting.log	Records information about reporting policy platform results into state messages for configuration items.	Client
DcmWmiProvider.log	Records information about reading configuration item synclets from Windows Management Instrumentation (WMI).	Client

SCCM 2012 R2 Log File for Backup and Recovery issue

SCCM 2012 R2 Log File for Backup and Recovery issue

Backup and Recovery

The following table lists log files that contain information related to backup and recovery actions including site resets, and changes to the SMS Provider.

Log name	Description	Computer with log file
ConfigMgrSetup.log	Records information about setup and recovery tasks when Configuration Manager recovers a site from backup.	Site server
Smsbkup.log	Records details about the site backup activity.	Site server
smssqlbkup.log	Records output from the site database backup process when SQL Server is installed on a different server than the site server.	Site database server
Smswriter.log	Records information about the state of the Configuration Manager VSS writer that is used by the backup process.	Site server

SCCM 2012 R2 Log Files for Deployment and Packages

SCCM 2012 R2 Log Files for Deployment and Packages

The following table lists the log files that contain information related to deploying packages and programs.

Log name	Description	Computer with log file
colleval.log	Records details about when collections are created, changed, and deleted by the Collection Evaluator.	Site server
execmgr.log	Records details about packages and task sequences that run.	Client

SCCM Log Files for Apple Mac,ipad and iPhone

SCCM Log Files for Apple Mac,ipad and iPhone

Client for Mac Computers

For System Center 2012 Configuration Manager SP1 and later:

The Configuration Manager client for Mac computers records information in the following log files.

Log name	Details
CCMClient-<date_time>.log	Records activities that are related to the Mac client operations, which includes application management, inventory, and error logging. This log file is located in the folder /Library/Application Support/Microsoft/CCM/Logs on the Mac computer.
CCMAgent-<date_time>.log	Records information that is related to client operations, which includes user logon and logoff operations and Mac computer activity. This log file is located in the folder ~/Library/Logs on the Mac computer.
CCMNotifications-<date_time>.log	Records activities that are related to Configuration Manager notifications displayed on the Mac computer. This log file is located in the folder ~/Library/Logs on the Mac computer.
CCMPrefPane-<date_time>.log	Records activities related to the Configuration Manager preferences dialog box on the Mac computer, which includes general status and error logging. This log file is located in the folder ~/Library/Logs on the Mac computer.

Additionally, the log file SMS_DM.log on the site system server records communication between Mac computers and the management point that is enabled for mobile devices and Mac computers.

SCCM 2012 R2 Log files for Linux and Unix Machines - Troubleshooting

SCCM 2012 R2 Log files for Linux and Unix Machines - Troubleshooting

Client for Linux and UNIX

For System Center 2012 Configuration Manager SP1 and later:

The Configuration Manager client for Linux and UNIX records information in the following log files.

Tip
Beginning with client for Linux and UNIX from cumulative update 1, you can use CMTrace to view the log files for the client for Linux and UNIX.

Note
When you use the initial release of the client for Linux and UNIX and reference the documentation in this section, replace the following references for each file or process: Replace omiserver.bin with nwserver.bin Replace omi with nanowbem

Log name	Details
scxcm.log	This is the log file for the core service of the Configuration Manager client for Linux and UNIX (ccmexec.bin). This log file contains information about the installation and ongoing operations of ccmexec.bin. By default, this log file is created in the following location: /var/opt/microsoft/scxcm.log To change the location of the log file, edit /opt/microsoft/configmgr/etc/scxcm.conf and change the PATH field. You do not need to restart the client computer or service for the change to take effect. You can set the log level to one of four different settings: ERROR: Indicates problems that require attention. WARNING: Indicates possible problems for the client operations. INFO: More detailed logging that indicates the status of various events on the client. TRACE: Verbose logging that is typically used to diagnose problems. To change the log level, edit /opt/microsoft/configmgr/etc/scxcm.conf and change each instance of the tag MODULE to the desired log level.
scxcmprovider.log	This is the log file for the CIM service of the Configuration Manager client for Linux and UNIX (omiserver.bin). This log file contains information about the ongoing operations of nwserver.bin. By default, this log is created in the following location: /var/opt/microsoft/configmgr/scxcmprovider.log To change the location of the log file, edit /opt/microsoft/omi/etc/scxcmprovider.conf and change the PATH field. You do not need to restart the client computer or service for the change to take effect. You can set the log level to one of three different settings: ERROR: Indicates problems that require attention. WARNING: Indicates possible problems for the client operations. INFO: More detailed logging that indicates the status of various events on the client. To change the log level, edit /opt/microsoft/omi/etc/scxcmprovider.conf and change each instance of the tag MODULE to the desired log level.

Under normal operating conditions the ERROR log level should be used. The ERROR level of logging creates the smallest log file. As the log level is increased from ERROR to WARNING to INFO to TRACE, each step results in a larger log file as more data is written to the log file.

Manage Log Files for the Client for Linux and UNIX Client

The client for Linux and UNIX does not limit the maximum size of the client log files, nor does the client automatically copy the contents of its .LOGfiles to another file such as a .LO_ file. If you want to control the maximum size of log files, implement a process to manage the log files independent from the Configuration Manager client for Linux and UNIX.

For example, you can use the standard Linux and UNIX command logrotate to manage the size and rotation of the clients log files. The Configuration Manager client for Linux and UNIX provides an interface that enables logrotate to signal the client as to when the log rotation completes, allowing the client to resume logging to the log file.

For information about logrotate, see the documentation for the Linux and UNIX distributions that you use.

Get-NetAdapter: PowerShell Command to find Network Adapater Alias name and Index Number

PowerShell Command to find Network Adapater Alias name and Index Number

• If you have to do changes to your Network Adapter then you need to know the Alias Name and Index Number
• You can find those easily in PowerShell
• The Command is "Get-NetAdapter"
• You can see the "Name" which is Alias and ifIndex which is the "Index Number"

What is Azure resource group and how to create it PowerShell

What is Azure resource group and how to create it PowerShell

What is Resource group:

• Before deploying any resources to your subscription, you must create a resource group that will contain the resources.

Create a resource group:

• To create a resource group, use the New-AzureRmResourceGroup cmdlet.

New-AzureRmResourceGroup -Name CognosApp -Location "West US"

• Uses the Name parameter to specify a name for the resource group and the Location parameter to specify its location.

Powershell Get-Help Command Usages and uses- Powershell Basics

Powershell Get-Help Command Usages and uses

Get-Help:

• The Help Command in PowerShell cmdlet . You can use this command to get help with any other command. For example, if you want to know how the Get-Service command works, you can type:

Get-Help -Name Get-Service

and Windows will display the full command syntax.

• You can also use Get-Help with individual nouns and verbs. For example, to find out all the commands you can use with the Get verb, type:

Get-Help -Name Get-*

Difference between VHD and VHDx disk

Difference between VHD and VHDx disk

• The .vhd format has been used with Microsoft virtualization products since the days of Virtual Server. 
• The .vhdx format is new to Windows Server 2012.
• VHD:Virtual hard disk files in .vhd format are limited to 2040 GB. Virtual hard disks in this format are supported on Hyper-V hosts running Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.
• Other than the size limitation, the important thing to remember is that you cannot use virtual hard disk files in .vhd format with generation 2 VMs.
• VHDx: Virtual hard disks in .vhdx format have the following benefits:
• Can be up to 64 TB in size,Have larger block size for dynamic and differential disks,Provide 4-KB logical sector virtual disks,Have an internal log that reduces chance of corruption,Support trim to reclaim unused space
• The main limitation of virtual hard disks in .vhdx format is that they cannot be used with Hyper-V on Windows Server 2008 or Windows Server 2008 R2.

Easy way to access your network cards and configure them - ncpa.cpl

Easy way to access your network cards and configure them -ncpa.cpl

• Opening the network card is a bit of challenge in the computer. It usually takes to network page from where you have to again click on another tab to go to your network card. I was always feeling if there is easy way to do it and the yes there is
• Click on Start --> in search box type "ncpa.cpl"
• This will directly open the Network card page.
• I hope it makes your life easier like mine :)

Known Issues and Troubleshooting for Windows Server Base OS Management pack

Known Issues and Troubleshooting for Windows Server Base OS Management pack

• Disk Partitions Which Correspond to Mounted Disks Are Not Monitored

Issue: Disk partition discovery is not enabled by default, but when enabled, disk partitions that correspond to mounted disks cannot be monitored properly and will show up as “Not Monitored” in the Operations Console. Management is still provided by way of other means in this management pack, but the disk partition perspective will not work in these instances.

Workaround: There is no workaround currently available. 

• The “Core Windows Services Rollup” Monitor for Windows Server 2008 Includes Services That It Should Not

Issue: The Core Windows Services Rollup monitoring that exists in all server operating system management packs aggregates the state of a number of monitors that are watching the state of various “core services” and will change state if any one of those services is not running. The Windows Server 2008 version of this monitor includes a monitor for the “Computer Browser Service Health,” which is not accurate because the service is no longer required for the Windows Server 2008 operating system to function properly.

Workaround: The monitor can be safely ignored, but it can also be disabled by overriding it.

• Remote Desktop (Admin) Not Always Accessible

Issue: There are times when Remote Desktop (Admin) is not accessible.

Workaround: The new Remote Desktop (Admin) functionality of Windows Server 2008 is supported by way of the /admin switch. However, it is available only in Windows Server 2008 and the Windows Vista operating system with SP1.

• The Console Session Does Not Work in Windows Server 2008

Issue: Attempts to use the /console switch do not work properly.

Workaround: The console session no longer exists in Windows Server 2008. Use of the /console switch will be ignored, and the behavior is the same as a simple Remote Desktop task.

• Behavior for Accessing the Console Session of Windows Server 2003 Has Changed

Issue: There is a change in behavior for accessing the console session of Windows Server 2003.

Workaround: For the Windows XP operating system with SP1 or earlier and Windows Vista, use the Remote Desktop (Console) task in Windows Server 2003. Remote Desktop (Admin) will cause an error dialog. For Windows Vista with SP1, use the Remote Desktop (Admin) task in Windows Server 2008. Remote Desktop (Console) will work as the Remote Desktop task without any notice.

• SUBST Drive Mappings Are Not Supported by Logical Disk Monitoring

Issue: There is a command-line tool (SUBST.exe) that can be used to associate a path (such as c:\windows\system32) with a drive letter (such as D:\). Because these mappings are exposed in WMI, logical disk monitoring discovers them and attempts to monitor them as such, but will subsequently generate errors.

Workaround: There is no workaround currently available, and this configuration is not supported.

Known Issues with Localized Versions of the Management Pack:

•  Object discoveries scoped to Windows Server 2008 Computer and Windows Server 2008 Operating System may not display correctly in the Authoring pane.
• Some instances of localized display strings may not display correctly in the Operations console.

Known Issue: Cluster Disks Managed by Third-Party Software are Not Monitored

• Issue: If the Cluster disks are managed by third party software, and they change the resource type to anything other than “Physical Disk”, these disks will be discovered but we do not provide monitoring for these.
• Workaround: There is no workaround currently available. In future, we will be removing discovery for these too.

Known Issue: PowerShell in 2012 MP failed if .NET is uninstalled from Core OS agent by user

• Issue: .NET 4.5 and PowerShell are installed by default on Core OS and PowerShell depends on .NET, if they are uninstalled from Core OS agent by user, some workflows depending on PowerShell in 2012 MP will be failed.
• Workaround: Install .NET Framework 4.5 and PowerShell on Core Operating System.

Known Issues and Troubleshooting for SSAS 2008 MP

Known Issues and Troubleshooting for SSAS 2008 MP

• Users who had the previous version of SSAS management pack installed should remove Microsoft SQL Server Analysis Services Visualization Library (version 1.0.5.0) manually.

Issue: The library has become a generic component and a new management pack that contains the functionally is released. Since it is impossible to remove the obsolete pack automatically during installation process, users have to do it manually.

Resolution: Remove Microsoft SQL Server Analysis Services Visualization Library (version 1.0.5.0).

• If the last SSAS database or partition is deleted the object will be still displayed in SCOM as if it exists.

Issue: Current implementation of SSAS database and partition discoveries incorrectly resolves the situation when the last SSAS database or partition is deleted. In the case the information regarding the deleted object is still visible to the user.

Resolution: There is no resolution. The error may be addressed in future releases of the management pack. A user can either add a SSAS database/partition or remove the SSAS instance.

• ‘An error occurred during execution of a SSAS 2008 MP managed module’ alert rule generates extra alerts for virtual nodes.

Issue: Current implementation of the rule uses ‘SSAS 2008 Seed’ as a target. Virtual nodes have mutual seed, as a result each time an error occurs on a physical machine an alert is automatically reported from every virtual entity which is currently associated with that physical machine.

Resolution: There is no resolution. The error may be addressed in future releases of the management pack.

• Event 6200 “Analysis Services connection failed” error is reported into Operations Manager event log.

Issue: Instance discovery workflows of SSAS management pack require connection to a SSAS instance, if the connection is not provided the workflows report about encountered problems. Such an issue may occur when the instance is stopped during execution of a workflow, or when the instance is incorrectly configured.

Resolution: Set ‘Threadpool\Query\MaxThreads’ property to a value of less than or equal to two times the number of processors on the server.

• Operations Consoles crash when user simultaneously opens two or more Instance/Database Summary dashboards on the same machine.

Issue: It is allowed to run two or more Operations Consoles on the same machine, but opening summary dashboards in more than one of them leads to a crash of all consoles. The issue is not observed in Web-consoles.

Resolution: There is no resolution.

• Operations Console crashes if user who is browsing Instance Summary dashboard selects a SSAS Instance which has already been deleted.

Issue: The action cause a crash of Operations Console.

Resolution: Open Operation console again.

• “Health Service State” monitor is in critical state and Health Service restarts periodically.

Issue: By default the threshold of “Monitoring Host Private Bytes Threshold Monitor” from the System Management Pack is 300 Mbytes. “MonitoringHost.exe” process may exceed the threshold and the “Health Service State” monitor may start the recovery procedure, when SSAS 2008 Monitoring Pack is collecting information about a large number of objects (more than 50 SSAS databases or 1500 partitions per server).

Resolution: Override the threshold of the “Monitoring Host Private Bytes Threshold Monitor” or reduce the number of objects being monitored by disabling discovery of partition objects.

• Event 6200 “Category does not exist” (source – “SSAS 2008 MP”) is being generated on 64-bit operating systems running 32-bit SSAS instances.

Issue: SSAS doesn’t register performance counters properly when a 32-bit SSAS instance is installed on a 64-bit OS. In this case required performance counters cannot be found by Monitoring Pack and SSAS 2008 MP is unable to run properly.

Resolution: This issue cannot be resolved, WoW64 is not supported. It is highly recommended to use either 32-bit SSAS instances on 32-bit OS or 64-bit SSAS instances on 64-bit OS.

• Health Service and Monitoring Host processes consume too much memory on systems running SSAS 2008 instances with large number of databases

Issue: On agent-managed systems that host one or more instance of SQL Server 2008 Analysis Services with large number of databases and/or partitions, “Health Service” and “Monitoring Host” processes may consume too much memory.

Resolution: It is not recommended to monitor more than 50 SSAS Databases on a single server. It is recommended to disable SSAS partitions discovery if you have more than 1500 partitions on a single server.

• SSAS 2008 Summary Dashboards for Instances, Databases and Partitions display all active alerts if nothing is selected in the navigation widget (leftmost widget on the dashboard).

Issue: Dashboards display all active alerts if nothing is selected in the navigation widget (leftmost widget on the dashboard).

Resolution: Make sure that at least one Instance, Database or Partition is selected in the navigation widget.

• WMI errors may occur when SQL Server AS 2008/2008 R2 and SQL Server AS 2012 are installed on the same server.

Issue: Modules can throw an error during WMI query.

Resolution: Update SQL Server 2008/2008 R2 with the latest service pack.

• Partition Storage Free Space Monitor may generate too many alerts.

Issue: The monitor may generate a lot of alerts if database default storage folder and partition storage folder are sharing the same drive.

Resolution: Disable the monitor for all partitions which are sharing the same drive with database storage folder.

• SSAS Seed object cannot be discovered if SQL Server 2008 Express Edition and SQL Server 2008 are installed on the same server.

Issue: SSAS 2008 Monitoring Pack can throw a WMI error during Seed object discovery.

Resolution: Update SQL Server 2008/2008 R2 with the latest service pack or disable Seed object discovery for a given server if that server is not running an Instance of SQL Server 2008 Analysis Services.

• SSAS 2008 Monitoring Pack generates an alert: “An error occurred during execution of a SSAS 2008 MP managed module”.

Issue: Alert “An Error occurred during execution of a SSAS 2008 MP managed module” can be found in global “Active Alerts” view.

Resolution: This alert is generated if SSAS 2008 Monitoring Pack cannot execute one of workflows due to unknown issue. Examine alert message and alert context to determine the root cause.

• SSAS 2008 Monitoring Pack may register Errors in the event log during installation of a new instance of SQL Server Analysis Services.

Issue: SSAS 2008 Monitoring Pack may generate a lot of errors in event log during installation of a new instance of SQL Server Analysis Services.

Resolution: The issue occurs because Monitoring Pack cannot get all required properties from the registry and WMI during installation process. Once the installation process is completed, the Monitoring Pack will be able to operate properly.

• SQL Server 2008 Analysis Services reports incorrect value for Total and Low memory limit performance counters.

Issue: SQL Server Analysis Services may report incorrect values for Total and Low memory limit performance counters after reconfiguration.

Resolution: SQL Server Analysis Services doesn’t apply new configuration values immediately. SSAS service should be restarted to apply new settings.

• SSAS 2008 Monitoring Pack generates an alert: “Could not find a part of the path to configuration file 'msmdsrv.ini'”

Issue: SSAS 2008 Monitoring Pack reports an error in the Event log and generates an alert “Could not find a part of the path to configuration file 'msmdsrv.ini'”. The issue occurs during cluster failover.

Resolution: There is no resolution. The issue may occur when monitoring workflow is trying to collect information during cluster failover. Once the failover is completed, the Monitoring Pack will be able to operate properly.

• SSAS 2008 Monitoring Pack may not collect OS performance counters with localized names

Issue: SSAS 2008 Monitoring Pack may not collect OS performance counters with localized names.

Resolution: Workaround: set English display language for user accounts associated with SSAS Discovery and Monitoring Run AS Profiles. Also apply English as display language for system accounts.

What does Sealed and Unsealed Management Packs mean

What does Sealed and Unsealed Management Packs mean

• Management packs are either sealed or unsealed. A sealed management pack is a binary file that cannot be edited. An unsealed management pack is an XML file that can be edited. Sealed management packs should have an .mp extension, while unsealed management packs should have an .xml extension.

• In general, management packs obtained from an application or hardware device vendor are sealed.

Although you cannot change the settings in a sealed management pack, you can still customize the applied settings of a management pack after it is imported by using overrides or by creating additional settings such as rules, monitors, and tasks that supersede the management pack's default settings. All customizations that you create are saved to a separate management pack file.

PowerShell Command to get Specific Alert in SCOM 2012 R2 and SCOM 2016

PowerShell Command to get Specific Alert in SCOM 2012 R2 and SCOM 2016

• Powershell Command to get only Specific alert with Specific Name is something we are asked frequently
• Use the Below Command to get it done
• GET-SCOMAlert Where {$_.Name --eq "Alert You want to get"}

SCOM 2012 R2 Data warehouse command to get information on Various Tables and how much space they are talking

SCOM 2012 R2 Data warehouse command to get information on Various Tables and how much space they are talking

• SCOM Data warehouse is the one where we store all data for longtime.
• Usually this will be in terabytes of data and will fill very fast if not confiureged properly
• Most offten you can see that the Datawarehouse if Full or going to be full and you want to find out what is the configuration and which Table is taking the most data
• Microsoft has pushed a command line tool in SCOM 2012 R2 called dwdatarp.exe
•  To get the list of tables using more space and configuration use the below command

dwdatarp.exe -s SQLServer\DatabaseName -d OperationsManagerDW > c:\dwoutput.txt

• This will give you the output with Space used and the How many days of data is stored.

Command to Get List of Patches installed on Windows 2008 R2 and Windows 2012

Command to Get List of Patches installed on Windows 2008 R2 and Windows 2012

• Manytime we get request from application owners who request for list of patches instaled and on what date
• You can use the below command to get the list of Patches from the server. This will Create a html file called hotfix.html in your C: drive.

• wmic qfe list brief /format:htable > "c:\hotfix.html"