locked
Messenger service and alerter services RRS feed

  • Question

  • vista has remove the Messenger service and alerter services. Is their a work around this to get some programs that would use these services to work in vista?
    Monday, October 23, 2006 10:23 PM

Answers

  • In Vista the command is MSG:

     

    MSG {username | sessionname | sessionid | @filename | *}
        [/SERVER:servername] [/TIME:seconds] [/V] [/W] [message]

      username            Identifies the specified username.
      sessionname         The name of the session.
      sessionid           The ID of the session.
      @filename           Identifies a file containing a list of usernames,
                          sessionnames, and sessionids to send the message to.
      *                   Send message to all sessions on specified server.
      /SERVER:servername  server to contact (default is current).
      /TIME:seconds       Time delay to wait for receiver to acknowledge msg.
      /V                  Display information about actions being performed.
      /W                  Wait for response from user, useful with /V.
      message             Message to send.  If none specified, prompts for it
                          or reads from stdin.

    Wednesday, February 14, 2007 9:05 AM
  • messenger has been replace with Windows Live Messenger which is a download.  what programs are you lookimg to use these services
    Sunday, October 29, 2006 11:45 PM

All replies

  • messenger has been replace with Windows Live Messenger which is a download.  what programs are you lookimg to use these services
    Sunday, October 29, 2006 11:45 PM
  • We have servers (W2K3) setup to broadcast messages to specific client machines (admins) when events happen (i.e. a server fan is out of spec). Without the Messenger (not Windows Messenger) service we can;t receive them.

    This is the old service the net send used.

    Tuesday, November 28, 2006 9:04 PM
  • We have EXACTLY the same problem. We need the "old" messenger service on Vista. We have implemented so many solutions based on this. Could you please help? There must be a work-around on this.

     

     

    Wednesday, February 14, 2007 8:56 AM
  • In Vista the command is MSG:

     

    MSG {username | sessionname | sessionid | @filename | *}
        [/SERVER:servername] [/TIME:seconds] [/V] [/W] [message]

      username            Identifies the specified username.
      sessionname         The name of the session.
      sessionid           The ID of the session.
      @filename           Identifies a file containing a list of usernames,
                          sessionnames, and sessionids to send the message to.
      *                   Send message to all sessions on specified server.
      /SERVER:servername  server to contact (default is current).
      /TIME:seconds       Time delay to wait for receiver to acknowledge msg.
      /V                  Display information about actions being performed.
      /W                  Wait for response from user, useful with /V.
      message             Message to send.  If none specified, prompts for it
                          or reads from stdin.

    Wednesday, February 14, 2007 9:05 AM
  • That would be fine if I were sending a message from a Vista machine - but what do we do if we have a server (i.e. Windows Server 2003) which uses "net send" to send alerts to users who are on a variety of operating systems (XP and Vista)?  Is there any way to allow the Vista machines to still receive the net send alerts?
    Thursday, February 15, 2007 6:33 PM
  • I know this thread has been dead for over a year but I was hoping to hear what your solution was, as we are in the same situation as you.

     

    Thursday, June 5, 2008 5:37 PM
  • Yes, please post a solution to this problem. I'm in the same situation.

     

    Friday, August 15, 2008 11:58 AM
  • All of the additional posts are correct - i.e. sending messages from a W2K3 server does not work on machines with an OS that no longer supports the Messenger service.

     

    Good luck!

    Saturday, August 23, 2008 7:44 AM
  • Fire both a net send (from the W2K3 server) and start an executable on a Vista machine.  The Vista EXE can then send the msg command.

     

    Those machines running XP will get the net send from the W2K3 server.  Those machines running Vista will get the "msg" command from the Vista machine.

     

    That's a guess anyway ... luckily, our company decided to hold off on Vista at this time - so it was no longer a requirement for us.

    Monday, August 25, 2008 9:59 AM
  • I do wonder though...with net send all you had to do was enter c computer name. with MSG I don't see such an option...is there a command to use MSG to send a message to a PC name?
    Tuesday, August 26, 2008 8:08 AM
  • That is what the /SERVER switch is for (i.e. /SERVER:[MachineName] where [MachineName] is the machines NETBIOS name).

     

    Example: MSG 1 /SERVER:MYPC test message

     

    Madrona

    Thursday, August 28, 2008 9:18 PM
  • Just use a third party software such as WinMessenger http://www.winpopup.com/

    Its easy and works fine on Vista...
    Tuesday, November 25, 2008 11:44 PM
  • JAYTF Security Forum Moderator said:

    messenger has been replace with Windows Live Messenger which is a download.  what programs are you lookimg to use these services


    Agreed
    Tuesday, December 30, 2008 4:45 PM
  • No, totally not, the messenger service has nothing to do with live messenger.
    on a vista machine, go to programs and features in the configuration screen and select the Microsoft Message Que (MSMQ) server, this is the replacemant for the messenger service.
    Tuesday, August 18, 2009 1:26 PM
  •     If the tool is truly a service, permissions and domain based to other admins, try utilizing something from a company microsoft acquired.   Sys Internals has many great admin tools, one allows you to use the Vista or Windows 7 box remotely to send itself msgs, thus ensuring remote compatibility.

     I'd recommend you look into:

     psexec.exe  "Execute processes remotely"

    http://technet.microsoft.com/en-us/sysinternals/bb795533.aspx

    It's 8 down the page at the time of this posting.

    Now I will admit you MUST ensure you understand the ramifications of using, storing or encoding usernames to get this to work, but admins of remote machines do not actually require typing passwords if you run the process as a user that is already an admin of the remote machine.  So make sure your team understands the security required to make this type of solution work.  However it's a great way to get legacy type systems to work remotely for machines that do not have licenses for software. 

       An example might be running a macro in a version of office you only have installed on one workstation because it's so old.

    Hope this helps,
    -
    John

    Friday, September 17, 2010 2:53 PM