best way to send console message and use of messenger service

[Paul]

I've got an AD network with 2003 standard servers and XP workstations. I
want to be able to send messages to workstations that are connected for
things like server reboot warnings but I read a couple of warnings about
having the messenger service running.

Is this considered an acceptable risk by most admins and is there a better
utility than 'net send'?

Thanks Paul

 

[Ehren]

I have always had the messenger service disabled, however I know of a few
places that use it on a regular basis for such things. If your network is
properly firewalled and monitored you need to worry about it less, at least
being attacked from the outside, however internal threats could be an issue
depending on your environment.

I would reccomend not using it...I have gotten around it by either sending
out a mass email or using a corporate instant messaging system. Of course if
you use exchange and do not allow cached mode and you are taking the exchange
server down an email wouldnt help anyone much.

Bottom line is I think a lot in this issue comes down to your environment,
your managment style and largely your oppinion.

Take mine for what it is worth...2 cents

"Paul" wrote:

> I've got an AD network with 2003 standard servers and XP workstations. I
> want to be able to send messages to workstations that are connected for
> things like server reboot warnings but I read a couple of warnings about
> having the messenger service running.
>
> Is this considered an acceptable risk by most admins and is there a better
> utility than 'net send'?
>
> Thanks Paul

 

[Ryan Hanisco]

Ehren,

I agree. This is usually disabled in most networks in favor of more robust
messaging and collaboration platforms. Think of the evil everyone got away
from when they pulled away from NetWare sending out blanket messages to
everyone on the wire...

You can use it if you don't have any other options, but usually if you are
to the point where you have to send out blanket messages, you are probably
already in hot water as it means you don't have time to develop and execute a
communication plan for your change. This combined with the fact that the
messenging service doesn't really work well if you're jumping across routed
boundaries, and you usually can find a better plan.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Ehren" wrote:

> I have always had the messenger service disabled, however I know of a few
> places that use it on a regular basis for such things. If your network is
> properly firewalled and monitored you need to worry about it less, at least
> being attacked from the outside, however internal threats could be an issue
> depending on your environment.
>
> I would reccomend not using it...I have gotten around it by either sending
> out a mass email or using a corporate instant messaging system. Of course if
> you use exchange and do not allow cached mode and you are taking the exchange
> server down an email wouldnt help anyone much.
>
> Bottom line is I think a lot in this issue comes down to your environment,
> your managment style and largely your oppinion.
>
> Take mine for what it is worth...2 cents
>
> "Paul" wrote:
>
> > I've got an AD network with 2003 standard servers and XP workstations. I
> > want to be able to send messages to workstations that are connected for
> > things like server reboot warnings but I read a couple of warnings about
> > having the messenger service running.
> >
> > Is this considered an acceptable risk by most admins and is there a better
> > utility than 'net send'?
> >
> > Thanks Paul