Showing posts with label OS. Show all posts
Showing posts with label OS. Show all posts

Wednesday, 26 April 2017

Install Azure CLI 2.0 on Apple mac OS Step by Step Tutorial

Install Azure CLI 2.0 on Apple mac OS Step by Step Tutorial


  • To install Azure CLI on your Mac OS type the following command
curl -L https://aka.ms/InstallAzureCli | bash

  • Then restart your command shell for some changes to take effect.
exec -l $SHELL


Wednesday, 1 March 2017

SCCM Query find All Server count with OS Name

SCCM Query find All Server count with OS Name



  • Recently I was asked to count of servers by OS
  • It was quite Challenging as we need to understand the SCCM Structure very well to do the SQL Queries.
  • Following are the Queries to fin the Server by OS Name and the count of Servers
SELECT VR.operatingSystem0,COUNT(VR.operatingSystem0) FROM v_R_System AS VR
WHERE VR.operatingSystem0 LIKE '%Windows Server%'
GROUP BY VR.operatingSystem0

Saturday, 10 September 2016

Troubleshooting OS Deployement errors during SCCM 2012 R2 Push Install

Troubleshooting OS Deployement errors during SCCM 2012 R2 Push Install


  • SCCM is the widely used tool for OS deployement.
  • The reason being very effective Step by Step Install Task equence which give great flexibitly to Administrator to deploy consistent image in the organization.
  • So one of the frequest issues i face is that the OS deploy fails in the middle even if ts standarize image.
  • So to troubleshoot OS deployment errors you need to look for errors in SMSTS.log
  • This task will show in which Task Sequence it got failed.
  • It will also give you the error code which you can then google to get more information.
  • So while the OS is deployed connect to the server where it is deployed and Press F8
  • Then type CMDTRACE command. This will open the Log viewer
  • The location of SMSTS.log is "\WINDOWS\TEMP\SMSTSlog"
  • Open the logfile in CMDTRACE and check for errors.

Thursday, 30 June 2016

Powershell Command to find version of OS


Powershell Command to find version of OS



  • To find which version of Windows you are running, enter the following commands in the Command Prompt or Powershell:


wmic os get caption

wmic os get osarchitecture

Thursday, 31 March 2016

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.

Wednesday, 30 March 2016

Disk Performance dashboard view is empty in SCOM 2012 R2

Disk Performance dashboard view is empty in SCOM 2012 R2


  • Disk Performance Dashboard View is empty. This is because the rule to see this data is not enabled. In order to populate this view, please enable the rules.
In 2012 Monitoring MP:
  • Microsoft.Windows.Server.6.2.OperatingSystem.TotalPercentDPCTime.Collection
  • Microsoft.Windows.Server.6.2.OperatingSystem.TotalPercentInterruptTime.Collection
  • Microsoft.Windows.Server.6.2.Processor.PercentDPCTime.Collection
  • Microsoft.Windows.Server.6.2.Processor.PercentInterruptTime.Collection
In 2012 R2 Monitoring MP:
  • Microsoft.Windows.Server.2012.R2.OperatingSystem.TotalPercentDPCTime.Collection
  • Microsoft.Windows.Server.2012.R2.OperatingSystem.TotalPercentInterruptTime.Collection

Tuesday, 29 March 2016

Upgrading an Operating System from Windows 2003 to Windows 2008: How to Prevent Discovery Problems

Upgrading an Operating System from Windows 2003 to Windows 2008: How to Prevent Discovery Problems


  • Before you upgrade the operating system on a monitored computer, uninstall the Operations Manager agent. After the upgrade, reinstall the Operations Manager agent.

Reason:

  • The objects that the management pack discovers, such as logical disks, are hosted by a parent class that is not version-specific. When you upgrade the operating system, the order in which discovery occurs can result in duplicate objects being discovered.
  • For example, you upgrade a computer running Windows Server 2003 to Windows Server 2008. 
  • If the Windows Server 2003 discovery rules run first after the upgrade, the instance of the computer running Windows Server 2003 and its objects will be removed from discovery because the operating system base class has been removed. When the Windows Server 2008 discovery rules run, the computer and its objects will be discovered again.
  • If the Windows Server 2008 discovery rules run first after the upgrade, the computer running Windows Server 2008 and its objects will be discovered. When the Windows Server 2003 discovery rules run, the instance of the computer running Windows Server 2003 will be removed from discovery, but the objects hosted by that instance will not be removed.
  • So If you upgrade a computer without uninstalling the agent first and then discover duplicate objects, uninstall the agent to mark all hosted objects as deleted in the database. Next, reinstall the agent to only discover existing applications/objects.  


Thursday, 10 March 2016

Dont install the latest Window OS Management pack -Serious Issues can mess up your monitoring

Dont install the latest Window OS Management pack -Serious Issues can screw up your monitoring


  • Recently released Microsoft OS MP has some serious issues.
  • There is total broken up and the Disk Monitoring is totally mess up.
  • People around the world are complaining about it.
  • I cant imagine when the product has so much investment each time when the OS MP comes it causes lot of issue.
  • I dont know when Microsoft is going to stick to the standard and release a quality OS MP without any issue.
  • Latest verison of this MP is 6.0.7297.0 and it a total avoid :)

Thursday, 5 November 2015

How to Install Zabbix on Red Hat Linux or Cent OS Step by Step



How to Install Zabbix on Red Hat Linux or Cent OS


Zabbix is the fastest growing monitoring tool today in market. Lot oc companies want to cut down the cost on monitoring and move to Opensource and Zabbix has emerged as the prefered choice.

Step 1: Installing repository configuration package


  • Install the repository configuration package. This package contains yum configuration files.


Command:

# rpm -ivh http://repo.zabbix.com/zabbix/2.4/rhel/6/x86_64/zabbix-release-2.4-1.el6.noarch.rpm



Step 2: Installing Zabbix packages

Install Zabbix packages. This example  install Zabbix server and web frontend with mysql database on same server

Command:

# yum install zabbix-server-mysql zabbix-web-mysql zabbix-agent

If you want to install agent only for monitoring follow the below steps

# yum install zabbix-agent



Step 3:Creating initial database

Create zabbix database and user on MySQL. Import initial schema and data.

Command:

# cd /usr/share/doc/zabbix-server-mysql-2.4.0/create
# mysql -uroot zabbix < schema.sql
# mysql -uroot zabbix < images.sql
# mysql -uroot zabbix < data.sql

Edit database configuration in zabbix_server.conf

# vi /etc/zabbix/zabbix_server.conf
DBHost=localhost
DBName=zabbix
DBUser=zabbix
DBPassword=zabbix

You can give any complex password you want.

Step 4:Start Zabbix server process:

# service zabbix-server start

Step 5:Editing PHP configuration for Zabbix frontend

Apache configuration file for Zabbix frontend is located in /etc/httpd/conf.d/zabbix.conf. Some PHP settings are already configured.

# vi /etc/httpd/conf.d/zabbix.conf

php_value max_execution_time 300
php_value memory_limit 128M
php_value post_max_size 16M
php_value upload_max_filesize 2M
php_value max_input_time 300
# php_value date.timezone Europe/Riga
It's necessary to uncomment the “date.timezone” setting and set the right timezone for your location.

After changing the configuration file restart the apache web server.

# service httpd restart

Step 6: Done Your server is ready


  • Zabbix frontend is available at http://ipddress/zabbix in the browser. 


Default username/password is Admin/zabbix.


Enjoy!






Thursday, 15 December 2011

How to Find your OS Version


  • Click -->Start-->Run
  • Type cmd
  • Type --> Ver
This will give you the Version of your OS.

There also a video for the same. http://youtu.be/VmPIdbXssdE