Member Avatar for Barbara Pierce

We have Windows 2003 server SP2 software on our office network and prior to its installation, I used to be able to send out broadcast messages to everyone in the office (i.e. the server is going down in 10 minutes, etc) I can no longer find how to send a broadcast message from our server. I do this as opposed to any type messenger or email as I need to get the info to the users fast and many times they don't open emails or look at messages until later. We are on two floors and it used to allow me to get to everyone at a computer quickly. Does anyone know how to send messages to all network computers from a 2003 server? thanks

Barbara Pierce

  • 3 Contributors
  • 4 Replies
  • 119 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by DimaYasny

Dani AI

Generated

A few targeted options that still work on a Windows Server 2003 SP2 network and will give a real desktop pop-up (not email):

Echoing points from and , check the domain/AD role and test in a small group first. Two practical, commonly used approaches follow — one ad-hoc, one persistent — plus short cautions.

Option A — remote run into the interactive session
Use the built-in message utility together with Sysinternals PsExec to invoke a popup on each workstation’s interactive session. This requires administrator credentials and that the target user has an interactive desktop (and appropriate firewall/Admin$ access). Example workflow:

  • Export a computer list from AD.
  • Use PsExec to run the message command on each machine (one-line loop from the server).
    See the official command docs for details: msg command reference and PsExec download/usage.

Option B — lightweight client that polls a network file/share
Deploy a tiny script that runs in the user context (logon script or scheduled task via GPO). The script checks a central share for a plain-text “alert” file and shows a MsgBox when it finds a new timestamped message. That avoids remote-admin access per machine and is simpler to firewall rules. Steps: place the message on the share, the client script reads it, displays it, then archives/clears the file. Test the timing/interval and error handling before wide rollout.

Cautions and tips

  • Test on a handful of machines first.
  • Both methods require administrative planning (permissions, firewall rules, interactive session behavior).
  • For a longer-term solution, consider a dedicated internal-alerting/notification tool (agent-based) so messages can be tracked and acknowledged centrally.

Recommended Answers

All 4 Replies

Member Avatar for DimaYasny

net send * is currently disabled by default as an option, because users are abusing it

so instead of doing this, just install a mail service (Exchange?) and send emails to distribution lists

Member Avatar for Barbara Pierce

net send * is currently disabled by default as an option, because users are abusing it

so instead of doing this, just install a mail service (Exchange?) and send emails to distribution lists

I do have Exchange installed. Unfortunately many people won't check their email but will look at their screen to see a message flash on it.

Member Avatar for DimaYasny

I do have Exchange installed. Unfortunately many people won't check their email but will look at their screen to see a message flash on it.

in that case you might want to consider an internal IM server - free jabber, or MScommunicator server

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.