NET SEND vs. MSG vs. DOMAIN MESSAGES

[Gongalong]

Hi folks,

 

I've spotted that NET SEND no longer works with a Win 2008 R2 domain (with Win 7 clients).

 

Reading around the topic MSG is purportedly meant to replace it, but I've had no luck sending a message to a domain (the message only appears on the server).

 

When I send (with /V switched on) I get the following:

 

C:\Users\administrator.ADMIN>msg * /v Test. Please Ignore

Sending message to session Console, display time 60

Async message sent to session Console

Sending message to session RDP-Tcp#0, display time 60

Async message sent to session RDP-Tcp#0

 

C:\Users\administrator.ADMIN>

 

Anyone know how to send a message on a Win 2008 R2 domain to all Win 7 clients?

 

TIA

[fiza]

Have a look here :

Pedro's Blog: A net messenger script for Windows 7/2008 | Um script mensageiro de rede para Windows 7/2008

[Gongalong]

Thanks. I did try this already, but it was linked elsewhere and didn't include the GPO edit.

[Gongalong]

The script doesn't seem to be all that usable sadly. It seems to take a long time to process.

 

How annoying that MS removed it! *shakes fist*

[SYNACK]

The script doesn't seem to be all that usable sadly. It seems to take a long time to process.

 

How annoying that MS removed it! *shakes fist*

 

They removed if for security reasons, it was comped back in 98 and finally disabled in SP2 of XP.

[Gongalong]

But why not replace it with something else? (that worked )

 

I know, I know...

[cpjitservices]

We use Email, or our In house Messenger installed on all machines - or if worst come to the worst go and see the people sat at the machines. Unfortunately I've not found a way to do this, Since our messenger system signs in at logon we just use that.

[cpjitservices]

We have our own Jabber server (open-fire) and we have the spark chat client re-branded to match our organization. It's all synced with AD.