Windows Messenger for corporate users only?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jake - 16 Apr 2007 17:16 GMT

Is there a way to configure Windows Messenger such that individuals in your
organization with MS Exchange ID's can IM? Also, is there a way to prevent
IM traffic from being seen outside of the organizations network.

I have heard there was a way using Exchange to run an IM service internally
to your Windows network, but that has since been removed.

We want IM conversations within our organization to be seen within our
network only.

Thanks!

Reply to this Message

Jonathan Kay [MVP] - 18 Apr 2007 03:24 GMT

Greetings Jake,

There's no way to magically make Windows Messenger restrict itself to the local network
without a local Exchange 2000 IM Server or Live Communications Server (or some other
third-party SIP-based communications service).

Signature

Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2007 Jonathan Kay.
You *must* contact me for redistribution rights.
--

> Is there a way to configure Windows Messenger such that individuals in your
> organization with MS Exchange ID's can IM? Also, is there a way to prevent
[quoted text clipped - 7 lines]
>
> Thanks!

Reply to this Message

JS - 24 Apr 2007 20:21 GMT

Hi Jonathan,

Just wondering if you can tell me how to limit the IM client to just the internal Exchange 2000 Ent. server and to have no contact with the outside world? I was looking for a way to disable the .NET login on Windows Messenger but have been unable to find it. I was thinking of a registry hack to just grey out/disable that account connect option if possible. I did see reference to GPO but that was only for LCS which we haven't migrated to yet (Q4). So far, the only way I can see to do this is if I deny access via hosts to msgr.hotmail.com and block TCP port 1863. Seems just a bit too extreme...

Thanks,
Jack

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Reply to this Message