Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MSG.exe 4
- Thread starter ken07734
- Start date
Smah,
Did you test on a LAN between machines, or a Domain between machines?
I have not been able to get MSG to work on a LAN and I am tending toward the thoughts that it is only available on a Domain with the Business, Ultimate, or Enterprise versions (Home versions don't have MSG). I could be wrong but Googling finds no successful stories for using it in a Workgroup on a LAN.
I thought I had find a solution here (link), tried it, but that didn't work though.
I used your syntax, and about a hundred variable syntax with out success. I did get it to display a message on the "sending" machine, but that was the only recipient of any message.
I had to laugh when one of my messages which was "God help me" returned the usual sorts of error 5 about "Session Name", or "Session ID", but also added, "God doesn't exist or has been disconnected". I thought that was a good time to give up.
The link I mentioned was this one.
Sending a message to Win 7 host with msg.exe
Did you test on a LAN between machines, or a Domain between machines?
I have not been able to get MSG to work on a LAN and I am tending toward the thoughts that it is only available on a Domain with the Business, Ultimate, or Enterprise versions (Home versions don't have MSG). I could be wrong but Googling finds no successful stories for using it in a Workgroup on a LAN.
I thought I had find a solution here (link), tried it, but that didn't work though.
I used your syntax, and about a hundred variable syntax with out success. I did get it to display a message on the "sending" machine, but that was the only recipient of any message.
I had to laugh when one of my messages which was "God help me" returned the usual sorts of error 5 about "Session Name", or "Session ID", but also added, "God doesn't exist or has been disconnected". I thought that was a good time to give up.
The link I mentioned was this one.
Sending a message to Win 7 host with msg.exe
Linney, I didn't read the original post well, and did exactly what I wrote - I sent the message to myself (which obviously works fine, more on why below). So after reading your reply, I tried a few combinations of domain & non-domain systems which did not work. After these failed attempts, I did a little thinking about the available options (msg /?) and realized that this is not a traditional network tool; it's actually a terminal server utility. The clue is the 'sessionname' & 'sessionid' options. It would be useful if this were clearly stated somewhere, but it doesn't seem to be. The only case were there would be multiple sessions to msg with, would be a terminal server, since none of the client operating systems can have more than 1 active session (think remote desktop). The windows server operating systems can have 2 simultaneous sessions (remote desktop). So using 2 different machines, I remoted into a Server 2003 machine for testing. After confirming 2 concurrent sessions in task manager, I tried using msg, and sure enough, it worked correctly between the 2 active sessions. This is also why it does work when sending a msg to yourself on your own machine- because itself is the only possible session that a normal client machine could interact with (see user tab of task manager for session info). It might also work for a 'helper' connected by remote assistance (I didn't test, but I suspect 2 sessions would be active in a remote assistance scenario). But basically, this utility is really only for terminal server clients.
Old documentation:
Old documentation:
-
4
- #6
dilettante
MIS
Yes, the msg utility is part of Terminal Services, Remote Desktop being a limited version of Terminal Services. Vista Home doesn't even include it in any useful form - just a form of Remote Assistance I believe.
There are lots of UDP and Mailslot based chat and alert utilities out there though. The downside is you have to install them of course, and some are simple user programs instead of a background Service like the old Messenger Service.
And it means one more goofball tray icon in many cases!
There are lots of UDP and Mailslot based chat and alert utilities out there though. The downside is you have to install them of course, and some are simple user programs instead of a background Service like the old Messenger Service.
And it means one more goofball tray icon in many cases!
This is a crazy situation. MS has just made my life more difficult or more expensive.
Unless someone knows of a utility that works and is free.
All the ones I keep finding you have to buy!
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
Unless someone knows of a utility that works and is free.
All the ones I keep finding you have to buy!
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
There are many, but this one looks fairly clean & capable
- Thread starter
- #9
dilettante
MIS
It is tough to give one perfect solution because the utilities out there do differnt things and often in different ways.
Some are like the old Win9x WinPopup GUI utility, others are like a mini chat application. Some offer a command line mode or separate EXE that can be used in a script like NET SEND. Some allow sending to users, some to computers, some both. Others send among "nicknames" like using some 3rd party chat server. Some of them install as a Service like the previous Messenger Service while others must be run by users after logon, be placed in the Startup folder, etc.
Others have hidden gotchas like using a dedicated UDP or TCP port number, that might collide with other network usage at your site.
Some are like the old Win9x WinPopup GUI utility, others are like a mini chat application. Some offer a command line mode or separate EXE that can be used in a script like NET SEND. Some allow sending to users, some to computers, some both. Others send among "nicknames" like using some 3rd party chat server. Some of them install as a Service like the previous Messenger Service while others must be run by users after logon, be placed in the Startup folder, etc.
Others have hidden gotchas like using a dedicated UDP or TCP port number, that might collide with other network usage at your site.
so what's the gotcha with the link posted for lanmessenger
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
It's OK I found the gotcha -> it doesn't work on Vista.
It just errors with a exception handling error.
Back to the drawing board, any other messaging programs, preferably that don't come with a chatroom.
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
It just errors with a exception handling error.
Back to the drawing board, any other messaging programs, preferably that don't come with a chatroom.
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
dilettante
MIS
Hmm, most of the "chatroom" ones I have seen could be modified to remove that feature. Of course many are closed source too.
Are you basically looking for something that works like NET SEND from the command line and pops up a simple MessageBox on alerted clients?
Are you basically looking for something that works like NET SEND from the command line and pops up a simple MessageBox on alerted clients?
Yes , that's exactly what I need.
I need to be able to send an instant message like net send to tell people to close the company DB or log out as server needs rebooting, etc. etc..
You send them emails, but the get ignored, they forget, don't read it.
I need an instant pop-up message system, and i find it crazy MS have removed this facility. Vista sucks!
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
I need to be able to send an instant message like net send to tell people to close the company DB or log out as server needs rebooting, etc. etc..
You send them emails, but the get ignored, they forget, don't read it.
I need an instant pop-up message system, and i find it crazy MS have removed this facility. Vista sucks!
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
dilettante
MIS
Here's a quicky I threw together and have cast into the public domain. Full source is there, and a link to a precompiled MSI package that I hope makes it easy to use.
It might be closer to what you are after, and I won't be surprised if others improve on it. Buyer beware, there is no offer of support implied here. ;-)
Utility: LANegram - NET SEND Replacement
It might be closer to what you are after, and I won't be surprised if others improve on it. Buyer beware, there is no offer of support implied here. ;-)
Utility: LANegram - NET SEND Replacement
err, call me thick, but I've just installed it, and nothing has happened.
there is nothing in start->programs, nor can i find any notes / manual after install
if i drop to cmd prompt, and issue send /? or send.exe it says it doesnt' exist?
I've scoured the link you provided, and the release notes readme, but there is no mention of a working directory or paths to the files / executable.
I finally did a search for all files and folders to find the send.exe file.
dilettante -> a well earned star for you, but I would suggest updating the accompanying notes for thicko's like me ;-)
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
there is nothing in start->programs, nor can i find any notes / manual after install
if i drop to cmd prompt, and issue send /? or send.exe it says it doesnt' exist?
I've scoured the link you provided, and the release notes readme, but there is no mention of a working directory or paths to the files / executable.
I finally did a search for all files and folders to find the send.exe file.
dilettante -> a well earned star for you, but I would suggest updating the accompanying notes for thicko's like me ;-)
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
dilettante
MIS
I'll get on that, sorry.
I'm wondering now if the installer shouldn't add to PATH so people can get to Send directly, without typing the full path. Otherwise you need to CD to the folder or type something like:
[tt]"c:\program files\lanegram\send" * hello[/tt]
...which is painful.
You could manually go to Computer Properties and choose "Advanced system settings" and change the PATH environment variable to include this path. Add:
[tt];C:\Program Files\LANegram[/tt]
You can test this temporarily from a command prompt by entering:
[tt]set path=%PATH%;C:\Program Files\LANegram[/tt]
After that you can simply enter Send without specifying the full path.
Actually the "receiver" part should auto-start on boot or logon, via the shortcut in Startup for all users. I'll reinstall clean and verify this... Yes, it seems to start upon a fresh logon here.
The only glitch I can think of is when a non-admin user tries to install it pre-Vista, which could trigger per-user installation. Have you looked in Start|Programs|Startup?
The readme also gets dropped into the Program Files folder on installation, but I can add something to make it more obvious. The notes clearly need work as well, and the installer could even display them during installation or right after. I didn't want to litter the system with shortcuts though.
The paperwork is the hardest part of any job.
I'm wondering now if the installer shouldn't add to PATH so people can get to Send directly, without typing the full path. Otherwise you need to CD to the folder or type something like:
[tt]"c:\program files\lanegram\send" * hello[/tt]
...which is painful.
You could manually go to Computer Properties and choose "Advanced system settings" and change the PATH environment variable to include this path. Add:
[tt];C:\Program Files\LANegram[/tt]
You can test this temporarily from a command prompt by entering:
[tt]set path=%PATH%;C:\Program Files\LANegram[/tt]
After that you can simply enter Send without specifying the full path.
Actually the "receiver" part should auto-start on boot or logon, via the shortcut in Startup for all users. I'll reinstall clean and verify this... Yes, it seems to start upon a fresh logon here.
The only glitch I can think of is when a non-admin user tries to install it pre-Vista, which could trigger per-user installation. Have you looked in Start|Programs|Startup?
The readme also gets dropped into the Program Files folder on installation, but I can add something to make it more obvious. The notes clearly need work as well, and the installer could even display them during installation or right after. I didn't want to litter the system with shortcuts though.
The paperwork is the hardest part of any job.
exactly part of the problem I first had!! , in the end I just coppied it to the c:\Windows folder so it would be found from any dos prompt ;-)
yup finally found where it was and how it would run as at first i couldn't find the system tray icon!
The only other 'criticism' , if it's fair to call it that, is the message isn't MODAL and doesn't require user intervention (click OK to acknowledge) as it did with net send.
those sys tray messages tend to get ignored, like 'your icons on desk top ....' or that annoying 'file printed' popup.
Any improvement so you can be pretty sure the user saw and acknowledged the message would be handy!
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
dilettante
MIS
I'm not entirely sure what sort of "saw and acknowledged" feedback you are looking for. NET SEND pretty much tosses things into the void itself, there is no returned feedback though it may check for the existance of a NetBIOS name used as a destination first.
The Messenger Service message box isn't modal either. It is a simple message box with "topmost" Z-order.
In any case I have posted an updated version. It can be started using an alternative "simple" user interface more like what you were seeing with the Messenger Service popups. If you need something different the source is posted there, so customize away!
The Messenger Service message box isn't modal either. It is a simple message box with "topmost" Z-order.
In any case I have posted an updated version. It can be started using an alternative "simple" user interface more like what you were seeing with the Messenger Service popups. If you need something different the source is posted there, so customize away!
- Status