Skip to main content

Posts about Problem Management published on LinkedIn by Ronald Bartels based on popularity

The list below are my articles about problem management and mostly published on LinkedIn. The articles are listed in order of popularity.
  1. 6 things that will not solve problems in the workplace. (341306)
  2. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2005. (6745)
  3. Lessons from great leaders, Lovell, Kranz and Liebergot #failureisnotanoption. (4811)
  4. ITIL in the enterprise - the cart before the horse. (4283)
  5. The Network Operations Centre (NOC) a.k.a. the Fishbowl. (3190)
  6. Significant havoc in technology (SHIT) happens. (2993)
  7. An integrated approach to working with problems. (2244)
  8. Rapid risk assessment (the Meerkat Method). (2228)
  9. Being Transparent During a Crisis. (1083)
  10. The most important IT process of them all - the Major Incident process. (783)
  11. When two draadtrekkers switched off an airline's mainframe. (635)
  12. Red Teams - specialized Information Security Tiger teams. (539)
  13. Heath Robinson - solving the problems of the Human world with gadgets - the Awesome World of Things. (483)
  14. The causation over the Azure data centre outage leaves more questions than answers. (480)
  15. If you manage a data centre or network you need to look for ugly. (460)
  16. Using tiger teams during a major incident including their incorporation into a Disaster Recovery Plan. (453)
  17. Using LinkedIn Groups: The Pineapple Society of Root Cause Analysis. (358)
  18. Automation is crucial to service assurance success. (318)
  19. Timelines for Significant Havoc In Technology. (255)
  20. Data interpretation can be the problem - memories of eating dogfood. (219)
  21. Social service assurance - the death of voice and tickets via email. (212)
  22. The similarities between IT risk assessments and chess. (211)
  23. When the cloud bursts or in other words even in the cloud you'll have problems (210)
  24. Where legacy operations management including network management products come up short. (141)
  25. Mission Control - building a Network Operations Centre (NOC) in a similar manner to those of the space programme. (135)
  26. The bare necessities of a Network Operations Centre (NOC) Dashboard. (130)
  27. Implementing better data centre racks using best practice. (121)
  28. BMX - a high level 10 step method to work on problems for Tiger Teams. (113)
  29. Causation - the orphan of troubleshooting. (38)
  30. The landscape of Information Technology (IT) risk. (33)
  31. Deconstructing the mountains made from molehills - reversing adverse conditions using problem management. (29)
  32. Kepner-Tregoe - ITIL's recommended problem management technique - the Awesome World of Things. (17)
  33. Ghost Information Technology (IT) - it is not only about Alzheimer induced servers in the data centre (16)
  34. Using checklists in a data centre - making sure nothing is missed. (16)
  35. The curse of climate change in Information Technology - the flooding of the Service Desk (14)
  36. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2018. (13)
  37. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2017. (13)
  38. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2016. (13)
  39. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2015. (13)
  40. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2014. (13)
  41. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2013. (13)
  42. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2012. (13)
  43. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2011. (13)
  44. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2010. (13)
  45. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2009. (13)
  46. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2008. (13)
  47. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South Africa - 2007. (13)
You can also access the world famous "Alpha to Zulu guide to Problem Management" here.

https://www.linkedin.com/pulse/my-top-10-posts-pulse-ronald-bartels/

Comments

Popular posts from this blog

LDWin: Link Discovery for Windows

LDWin supports the following methods of link discovery: CDP - Cisco Discovery Protocol LLDP - Link Layer Discovery Protocol Download LDWin from here.

easywall - Web interface for easy use of the IPTables firewall on Linux systems written in Python3.

Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall

Latest: updatethreatblock.sh

#!/bin/bash # # usage updatethreatblock.sh <configuration file> # eg: updatethreatblock.sh /etc/ipset-threatblock/ipset-threatblock.conf # function exists() { command -v "$1" >/dev/null 2>&1 ; } if [[ -z "$1" ]]; then   echo "Error: please specify a configuration file, e.g. $0 /etc/ipset-threatblock/ipset-threatblock.conf"   exit 1 fi # shellcheck source=ipset-threatblock.conf if ! source "$1"; then   echo "Error: can't load configuration file $1"   exit 1 fi if ! exists curl && exists egrep && exists grep && exists ipset && exists iptables && exists sed && exists sort && exists wc ; then   echo >&2 "Error: searching PATH fails to find executables among: curl egrep grep ipset iptables sed sort wc"   exit 1 fi DO_OPTIMIZE_CIDR=no if exists iprange && [[ ${OPTIMIZE_CIDR:-yes} != no ]]; then   DO_OPTIMIZE_CIDR=yes fi if [[ ! -d $(dirname &q