My GTD for Outlook

Under construction


'Tag !Next and move'
Public Sub SetNext()
SetTag "!Next"
MoveSelectedItemsToFolder "_Ongoing"

End Sub
'Tag @Someday and move'
Public Sub SetSomeday()
SetTag "@Someday"
MoveSelectedItemsToFolder "_Ongoing"



'Tag Reference and move'
Public Sub SetWaiting()
SetTag "Waiting"
MoveSelectedItemsToFolder "_Ongoing"

End Sub

End Sub

'Tag Reference and move'
Public Sub SetReference()
SetTag "Reference"
MoveSelectedItemsToFolder "_Ongoing"

End Sub

'Tag Reference and Archive'
Public Sub Done()
SetTag "Done"
MoveSelectedItemsToFolder "Archive"

End Sub



Private Sub SetTag(Tag As String)

Dim objOutlook As Outlook.Application
Dim objInspector As Outlook.Inspector

Dim strDateTime As String

' Instantiate an Outlook Application object.
Set objOutlook = CreateObject("Outlook.Application")

' The ActiveInspector is the currently open item.
Set objExplorer = objOutlook.ActiveExplorer

' Check and see if anything is open.
If Not objExplorer Is Nothing Then
' Get the current item.
Dim arySelection As Object
Set arySelection = objExplorer.Selection

For x = 1 To arySelection.Count
strCats = arySelection.Item(x).Categories
If Not strCats = "" Then
strCats = strCats & ","
End If
strCats = strCats & Tag
arySelection.Item(x).Categories = strCats
arySelection.Item(x).Save
Next x

Else
' Show error message with only the OK button.
MsgBox "No explorer is open", vbOKOnly
End If

' Set all objects equal to Nothing to destroy them and
' release the memory and resources they take.
Set objOutlook = Nothing
Set objExplorer = Nothing


End Sub

Private Sub MoveSelectedItemsToFolder(FolderName As String)
On Error GoTo ErrorHandler

Dim Namespace As Outlook.Namespace
Set Namespace = Application.GetNamespace("MAPI")

Dim Inbox As Outlook.MAPIFolder
Set Inbox = Namespace.GetDefaultFolder(olFolderInbox)

Dim Folder As Outlook.MAPIFolder
Set Folder = Inbox.Folders(FolderName)

If Folder Is Nothing Then
MsgBox "The '" & FolderName & "' folder doesn't exist!", _
vbOKOnly + vbExclamation, "Invalid Folder"
End If

Dim Item As Object
For Each Item In Application.ActiveExplorer.Selection
If Item.UnRead Then Item.UnRead = False
Item.Move Folder
Next

Exit Sub

ErrorHandler:
MsgBox Error(Err)

End Sub

Windows Live Messenger 9 on XP 64

A topic completly different: Installing WL9 on XP 64.

You need a tool to extract cab file (7zip do it)

Then download the following cab file, extract the content and install the msi file.


Messenger.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/Messenger-ship-en.cab

Contact.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/Contacts-ship-neutral.cab

dw20sharedamd64.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/Watson-x64.cab

dw20shared.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/Watson-x86.cab

SegoeFont.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/SegoeFont.cab

crt.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/crt-neutral.cab

wlc.msi

http://download.microsoft.com/download/E/B/7/EB7AAFE7-514F-495A-A981-99830FE8E99E/en/wlc-ship-en.cab

Enjoy

SCOM - Exchange Baselining

I don't know if people share my tough about Baselining on Exchange counters but I feel that for some of them, this need to be disabled.

Instead, you should create Fixed unit Monitor:

• SMTP Categorizer Queue: should be less than 10
• SMTP Messages Pending Routing Monitor: should be less than 5
  
• Information Store to MTA: should be less than 10
• IS RPC Request: should be less than 25

Perhaps baselining can work but this take too much efforts for a result that is probably not better than using Fixed Unit Monitor.

SCOM -Tunning Thresholds

Hello,

About System Center Operations Manager, I've found very interesting information about Tunning thresholds in SCOM on Kevin Holman's Blog:

* Low: Inner: 4.01 Outer: 4.51 Rule Sensitivity: 4.01
* Low-Mid: Inner: 3.77 Outer: 4.27 Rule Sensitivity: 3.77
* Mid: Inner: 3.29 Outer: 3.79 Rule Sensitivity: 3.29
* Mid-High: Inner: 2.81 Outer: 3.31 Rule Sensitivity: 2.81
* High: Inner: 2.57 Outer: 3.07 Rule Sensitivity: 2.57


Links to the source:

http://blogs.technet.com/kevinholman/archive/2008/03/19/self-tuning-thresholds-love-and-hate.aspx

IBM RSA - The Perl script

So, here is some perl code that can help getting informations from IBM RSA.

Based on Net::SNMP module and on the oid I provided below.


sub get_status

{
my $rsa_status = "unknown";

#Define SNMP Session
my ($session, $error) = Net::SNMP->session( -hostname => $_[0], -community => $_[1], -port => 161 );

#Error Check
if (!defined($session))

{
$rsa_status = "SNMP_Error";
}
else
{
#SNMP Get
my $sysStatus = "$_[2]";
my $result = $session->get_request(-varbindlist => [$sysStatus]);

#Error check
if (!defined($result))
{
$rsa_status = "SNMP_Error";
}

else

{
if ($result->{$sysStatus} == 0)
{$rsa_status = "Critical";}
elsif ($result->{$sysStatus} == 2)
{$rsa_status = "Warning";}
elsif ($result->{$sysStatus} == 4)
{$rsa_status = "System";}
elsif ($result->{$sysStatus} == 255)
{$rsa_status = "Normal";}
}
$session->close;

return $rsa_status;
}

IBM Remote Supervisor Adapter

My firsts articles will be about IBM RSA (and Blade Center).

Less than two year ago, I was asked to find a quick way to monitor our IBM Hardware infrastructure.

I first though about and integration into CA NSM, then I though about IBM director but that wasn't easy to deploy quickly.

Now, with my current knowledge, I think if I had to redo it I will use Spectrum for this as this is very easy to import MIB and to say what to do with events.

But at that time, I started building my own solution based on SNMP Capabilities of IBM RSA. This SNMP agent is able to return all Hardware errors of your IBM server.


In the MIB, I was able to found that the following oid where the status:

• For RSA: '1.3.6.1.4.1.2.3.51.1.2.7.1.0'
• For Blade Center: '1.3.6.1.4.1.2.3.51.2.2.7.1.0'

When you do an SNMP get on this, you'll have one of the following value:

• 0 for Critical
• 2 for Warning
• 4 for System Error
• 255 for Normal.

To have details about the cause of the status, you should look at the following SNMP table:

• For RSA: 1.3.6.1.4.1.2.3.51.1.2.7.2.1.3
• For Blade Center: '1.3.6.1.4.1.2.3.51.2.2.7.2.1.3'

Next post will be some pieces of my Perl code to show how you can do it.

What is this Blog?

This Blog is about Network & System Management as the title said.

I'm working in this world for more than 4 years now and I will try to share some knowledges/resources about this domain.

I'm used to work with CA Network and System Management (NSM), Microsoft Operations Manager (MOM), Microsoft System Center Operations Manager (SCOM), Spectrum but I also do a lot of customisations essentially in Perl.