I promised you the sourcecode of the Jabber Logging Client Service I’ve written. You can read about it here.
It’s now a fully blown Windows Service which monitors the EvenLog Datasource you specify. You can specify filters now so that you won’t get overwhelmed by uninteresting messages from the Windows Event Log of the monitored machine. You don’t need to restart the service if you changed a filter – it’ll pick the new filter up automatically. The same stands for the target users. Just change the XML and the Service will pick that information up. If you change the EventLog Datasource or the Jabber-Settings you’’ll need to restart the service.
So here it is: JabberLoggingService Version 0.2
If you’re going to use it and you like it please drop me a line. Oh and don’t forget to read the readme.txt for full instructions.
Oh I almost forgot: You can grab the Sourcecode of the Linux version here: http://www.ahzf.de/itstuff/XMPPLogger/
Source 1: http://www.schrankmonster.de/2009/01/22/UsingJabberToMonitorWindowsEventLogs.aspx
Source 2: http://www.schrankmonster.de/content/binary/JabberLoggingService0_2.zip
Source 3: http://www.ahzf.de/itstuff/XMPPLogger/
I found out what to do to get the Jabber Eventlog Service to display status information in the Jabber Client…
nice, eh? ;)
I tried to install a Data Protection Manager 2007 Remote Agent remotely and on the machine locally. Trying to install it remotely will always fail with this error message:
Since “tfs” is the only x86 server we have and everything else including the DPM 2007 Server is x64 this is my only bet – but so far even the local installation (which worked) did not change anything. I installed the remote agent and did the console setup setting the dpm server. I then added the production server to the DPM 2007. But the error message remained. I just don’t know what else to do.
Like every company we also got several machines working just for our infrastructural needs like Sharepoints, Activedirectory, Databases, Backup-Servers and so on.
To monitor many machines we came across the idea to use Jabber Instant Messaging to monitor the machines. For example the VPN should drop a line to specified jabber adresses if someone connects or disconnects. Every single machine is maintaining it’s own log – which means you would have to consolidate them in some ways. And since consolidation is not the masterplan – since you would need an event alarm system which sends out alarm calls if something weird is happening, you would need that alarm system too.
So we wrote (while waiting for the machines to install) several small tools which provide a gateway between syslog-ng, windows event logs and Jabber.
Since we are using this productively my Jabber Client Window looks something like this:
As you can see there are 3 machines online right now – and since these are Linux machines they also provide some status information like load averages and free memory. The Linux version was written by ahzf in perl – and obviously his library can handle the presence and status information much better than the one I used for the Windows version :-) – So there are no presence and status informations for the Windows machines right now.
The Windows version is written in C# and relies on the Jabber.NET library. It comes with a small setup and runs as a windows service.
In the setup you have to enter the username+password of a user that can access the local Windows Event Log. After the successful setup you need to edit the config file:
It’s XML and quite easy to understand (I think) – so you define the jabber server, the user, the password, the Users that you want to receive the messages and the EventLog you want to monitor.
After starting the service you get the startup message via the jabber server and from now on everything that is written into the Windows Event Log is sent to the accounts you specified. Easy eh?
P.S.: sourcecode release will be after we packaged everything.
We wanted to have a separate Office wireless network and a separate guest wireless network in our new Office here at sones. So it was decided to take the old and working wireless router and dedicate him as the guest wirless network base station and buy a new one with 802.11n capabilities to work as the brand new office wireless network base station.
Since we had great experiences with older Linksys WLAN routers we first decided to buy this one:
This one was promised to work as a 802.11n capable router but it just did not. There’s nothing more to say about this thing besides: horrible UI, not working, no 5ghz capabilities – we returned this router immediately to the dealer and ordered a new one. This time:
AVM Fritz!Box 3270
And this one is a winner! Not only was our network up and running within 45 minutes – it also is faster than anything I’ve seen so far. There are even some very very cool frequency monitoring capabilities:
Not to mention the energy saving functionalities: