« On being overly cautious | Main | Steffan Soule - Fantastic magician in Seattle »

October 04, 2005



It seems to me Jabber would be the way to go. I know that a Jabber server can be configured to auth against LDAP (which the DC should be exposing via AD, right?).... all Jabber users configs are stored on the server, you could easily connect to various jabber servers securely using SSL, it's got broadcast support, it's got conferences, about the only thing it doesn't have is MSFT-specific stuff like "Remote Assistance"... but otherwise, it's absolutely stellar for your purpose.

I'm not sure if there's a windows server available that will also do the LDAP stuff, I deployed that all under Linux, but I have to believe *someone's* done that already. :-)

Tim Farley

You might give Ipswitch Instant Messenger a look. I'm not sure if it meets absolutely all of your requirements, but I've seen it demoed and its pretty slick.


Corey Collins

I don't think Jabber is the way to go. We tried that with one of our products, EIOBoard and it did not run so well. It was mostly because we were trying to run JabberD on a windows server. From your specs it looks like you want to run it on a windows server.

We have something that you might be able to work with. It's a little immature right now, for it's a fairly new product addtion. Right now it only works with our In Out Board EIOBoard, but there is no reason why we couldn't develop a stand-alone application version with a lot of the features you want.

Take a look at our product EIOBoard at http://www.eioboard.com, download the application, and play around with the Chat. We already have some of the things you want in our EIOBoard product such as Windows Authentication for the login; and we would be able to port it over to a stand alone chat program.

If you think our way is an option. Let us know and we can work on pricing, timeline, and answer any questions.

I found your blog post from Jerry over at the UAA. He is an EIOBoard customer of ours.

Edward Lim

Hi Steve,

I'm a consultant like yourself in Asia. We had a bid for a project previously for an internal IM solution but we never got it due to reasons unknown to us. However, we did finish the R&D process. Please allow me to elaborate:

For platform, we used Debian.
The packages and its dependencies you will need are simply:
1) ejabberd
2) erlang

So if you can get erlang to run on Windows, I don't see why you can't run ejabberd.

Why ejabberd? It is scalable, fault tolerant and supported LDAP w/o any problems. All other jabber implementation at that point in time were giving us alot of headaches when it comes to LDAP. It is also compliant to the newer v2 of jabber protocol.

As for jabberd clients, we used exodus for windows (since all PCs were windows). http://exodus.jabberstudio.org
But I am not sure if it's well maintained nowadays.

I'm not so sure about Remote Desktop assistance but its worth a look for sure. Cheers.


I installed OmniPod for a customer and they love it. Easy setup, low cost, and it even runs in Citrix.


The comments to this entry are closed.


  • Steve Friedl is a software and network security consultant in Southern California. He has been a C and UNIX developer since 1981 and has an exceptionally broad background in this area. Some areas of expertise include:

    • C and C++ systems software development on the UNIX and Win32 platforms
    • Communications, including serial and TCP/IP based controllers
    • Enterprise internet security administration and configuration
    • Penetration tests, audits, and network reviews
    • Security forensics, reverse engineering, and tools development
    • General UNIX and Windows system/network administration
    • The Windows Printing System
    • Database software development
    • Technology problem solving and research
    • Technical writing and standup training

Unix Wiz

Stephen J. FriedlSoftware ConsultantOrange County, CA USASteve@unixwiz.net