quick message to domain users, can this be quickly done

is there anyway of sending a quick on-screen message to users on our network to advise of animportant happening. I don't want to use email or im but rather something that pops up on your screen immediately--no reply is needed from the user.

thanks in advance
Who is Participating?
usachrisk1983Connect With a Mentor Commented:
Have you tried something like:

NET SEND /DOMAIN "Hello Crazy Users!"

I haven't done it, only seen it in the help file, not sure what router/firewall/port blocking issues you'd run into.
PberSolutions ArchitectCommented:
Further to usachrisk1983 post, for this to work you need to have to using WINS as well as the messenger service running on all machines.
And keeping the Messenger service on all of the time is not always a security best practice.
You can write a WMI script that can run through your domain computers, if Messenger is off, turn it on, send the message, then turn it off.
Should be pretty simple as it would essentially just be a loop. The only parameter would be the message.
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Altough net send is good builtin utility but the problem with net send is if the client pc's have Xp And firewall is configured than it wont work otherwise it is the best & the easient way of sending msgs on network just type
net send 192.x.x.x or net send computername & if u want to send a msg tou All users than net send *.*
hope it might help you
Jared LukerConnect With a Mentor Commented:
you could use PSEXEC (www.sysinternals.com) inside a script to launch a VBScript somewhere on your network that would pop up a message box with the information that you are wanting to give out.

You could get even more complex if you wanted to.  For example, you could enumerate the OU in AD that has all your computers and try to ping them.  If you get a response back, then you can have it execute the PSEXEC command.  If you don't get a ping back, then you can move on.  This will also make your script go much faster as it's is not trying to communicate with machines that are not on.
Great idea Jared!  Just to put it out there, remember that PSEXEC is not free in a commercial environment, something to keep in mind if that applies to the original poster.

Also, you can save yourself the ping and use PSEXEC with the "-d" switch (double check that) and PSEXEC will launch the application but will not wait aroudn for a result, it'll succeed or fail, but not tell you what.  Goes much faster this way.

Also, I think you can psexec * to send the script to the enter domain.
Jared LukerCommented:
I didn't know that about psexec's licensing...
Snip from the Sysinternals License:

A commercial license is required to use the software in any way not covered above, including for example:

    * Redistributing the software in any manner, including by computer media, a file server, an email attachment, etc.
    * Embedding the software in or linking it to another program including internal applications, scripts, batch files, etc.
    * Use of the software for technical support on customer computers

Found Here:

(Note specifically #2)
Jared LukerCommented:
Isn't ignorance bliss when it comes to stuff like that? :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.