Solved

MSG from  Windows 2003 server to windows 7

Posted on 2011-03-08
3
725 Views
Last Modified: 2012-05-11
I'm trying to send a message over the network to multiple PC's that are on a different versions of windows, mainly windows 7 and xp. With XP the net send command works fine. With windows 7 I understand we cant use the net send so instead use  msg.

I struggled with this first but managed to get it to work between PC's i.e windows 7 to windows 7 by enabling a registry setting. I think  it was "AllowRemoteRPC".

The problem I have is that when I try sending msg on server 2003 to my pc which is on windows 7. A message comes up saying RPC server is unavailable. I don't really want to use third pary software so if anyone has any ideas that would be great.

This is the command I use:

msg /server:computer user "This should work on windows 7"

0
Comment
Question by:Michael Roodt
3 Comments
 
LVL 23

Expert Comment

by:redrumkev
ID: 35078114
mjroodt,

How are you doing?

msg.exe is only available on windows 7 in the Professional or Ultimate versions, not on home premium or starter.

See this link to which states the only way to get around this is via a 3rd party app:
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/msgexe-netsend-anything-availible-on-windows-7/e9743edc-afa9-4942-b1c7-66baf443067b

Sorry,
Kevin

0
 
LVL 2

Author Comment

by:Michael Roodt
ID: 35082260
Thanks Kevin,

I have windows 7 professional.  and i can use the msg command, I just can't do it from the server to my windows 7 professional. It only seems to work between terminals but not when it originates from the server
0
 
LVL 69

Accepted Solution

by:
Qlemo earned 500 total points
ID: 35087616
You should be able to circumvent the restrictions by using a 3rd-party tool on the machine sending the messages, called psexec (http://technet.microsoft.com/de-de/sysinternals/bb897553). It installs a service (remote) to be able to start a process on the remote machine. Using it would look like this:
    psexec \\computer msg * "This should work on windows 7"
if you do not need to provide user credentials. If you need to, you can add -user and -password to psexec.

I know you said you do not want to use a 3rd-party tool, but since psexec is from SysInternals (now owned by Microsoft), it isn't really a 3rd-party tool ;-). And you only need it on the controlling PC, without installing something.
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
This Micro Tutorial will teach you the basics of configuring your computer to improve its speed. It will also teach you how to disable programs that are running in the background simultaneously. This will be demonstrated using Windows 7 operating…
This Micro Tutorial will go in depth within Systems and Security in Windows 7 and will go into detail regarding Action Center, Windows Firewall, System, etc. This will be demonstrated using Windows 7 operating system.

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question