Monitoring

Last Updated on 10 March 2014, Total: 19 Blog Posts

  1. Windows Reliability Monitor

    I rarely come across systems administrators that use Windows reliability monitor when troubleshooting server or client platforms! I guess we either completely forget about this tool or the issue at hand is so critical that the tool is unavailable or even inadequate. However, I do recommend administrators to become acquainted with Reliability Monitor and leverage the power of its graphical... Read More

  2. Quick resource utilization check on Windows 2008 Servers

    There are a number of tools which give you details about resource utilization on Windows based machines. Detailed reports are best used when digging further down into an existing problem or analyzing a complex problem that requires a lot of details but an ad hoc quick performance check would suffice with few details. Actually, routine quick checks would benefit most... Read More

  3. Customizing a Data Collector Set

    As we have seen in the previous post creating a customized Data Collector Set is pretty straight forward. Go here to read the post! In addition we have seen that the data sources defined were derived from a set template. In this post we are going to see how you can add your own data sources to a previously created... Read More

  4. Data Collector Sets

    Most Systems Administrators have used Performance Monitor to view real-time performance data on Windows servers and identify bottlenecks. Some may have also recorded sessions and later analyzed log files for performance issues. In fact, this is what I will be talking about in the couple of posts to come, mainly about Data Collector Sets. Data Collector sets gather system information,... Read More

  5. Using HTTPS in Event Forwarding

    As we have seen in Setting up an Event Collecting Computer you can use either Http or Https protocol to transfer data from the forwarding to the collecting computer. Although standard Http transport uses encryption for forwarded events, you can configure event forwarding to use the encrypted Https protocol. However, using Https requires the following additional tasks to be performed... Read More

  6. Event Subscription delay

    Events are collected or sent (when subscription configuration is set to normal) every 15 minutes which is quite adequate for normal operations; however, there might be critical periods for some resources that we need to reduce this delay and get critical events faster. As already noted in Setting up an Event Collecting Computer, with the help of the wecutil command-line... Read More

  7. Setting up an Event Collecting Computer

    Having set up all remote hosts that you will be retrieving Events from, it is time to configure the Collecting workstation. The collecting computer would normally be an admin computer running Windows Vista, Windows 7 or Windows Server 2008. Assuming our collecting computer is named env1client01 then, from an elevated command prompt type: wecutil qc This command will set Windows... Read More

  8. Setting up an Event Forwarding Computer

    Windows Event forwarding requires the setup of forwarding computers and a collecting computer as we have seen in Managing Windows Events. In this post we start by setting up a typical forwarding computer and proceed to the collecting computer setup in another post. Let's assume that we are collecting events from a Windows 2008 server named Win2k8Web, hence our first... Read More

  9. Managing Windows Events

    The wealth of info stored in Windows event logs is astonishing. But most often we miss what we are looking for as the amount of information stored may be overwhelming at times. There are various third-party tools out there that manage and organize event logs in a useful manner; however, I would like to share with you some Event Forwarding... Read More

Featured Links