• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1440
  • Last Modified:

Problem with msg command

Each user on our network is running Windows 7 and might login to a different computer depending on the day and the status of the employee.  Supervisors need a script they can run that will allow the to produce a small nag screen in the form of a broadcast message that the user might have to move out of the way before they can work.  

The nag screen should allow the supervisor to choose from among her own saved list of employees and send a broadcast message or nag screen to one or more of them forcing them to move it from the center of the screen before they can continue their work.

We are not certain that we have any support from the I.T. department on this and we are not allowed to install software.

Initially, I am thinking to use the msg command which replaces the old netsend command.  If I type my username, it displays a message, but if I type someone elses username, I get the message "username does not exist or is disconnected".  I get this message even though I know them to be currently active and logged in.  I have tested this approach with a number of users and get the same message.

Assistance in scripting a solution in powershell is greatly appreciated.
0
frugalmule
Asked:
frugalmule
  • 6
  • 5
6 Solutions
 
Raheman M. AbdulSenior Infrastructure Support Analyst & Systems DeveloperCommented:
check if RPC is allowed on the remote PC where the other is logged on.
on remote PC, open registry:
regedt32
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
See if the following key exists:
AllowRemoteRPC   value 1   (change to 1 if 0)

restart the remote PC and test
0
 
frugalmuleAuthor Commented:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control is listed but \Terminal Server is not, even on my PC
0
 
frugalmuleAuthor Commented:
I openned an Windows remote desktop connection to see what error would be reported and it said "The connection was denied because the user account is not authorized for remote login".
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
CoralonCommented:
The way msg.exe works is either by username (as you have seen), by session NAME, by session ID, or you can do a blast wildcard to get all the users on a machine.

The real question is do you need to specify which machine is getting the message for a specific user?  Msg.exe is not a broadcast command, it is a directed command.  As an example:
msg * /server:servername This is my test message
[code]

This will send a message dialog to all users on servername that says "This is my test message".

If you don't need to worry about what machine a user is on, then you would take a list of computers and do a simple [code]for /f %f in (computerlist.txt) do msg * /server:%f this is my message text

Open in new window


Now, if it *does* matter, then it gets much more complicated, because you will need a list of all the machines, and the specified usernames..  Powershell makes it easier to parse, but you will need to have powershell remoting enabled on all the machines.

But, from a batch file perspective, you could do something like this:
for /f %f in (computerlist.txt) do (
for /f %A in (userlist.txt) do (
for /f %K in ('quser /server:%f') if %K == %A then msg.exe %A /server:%f This is my warning text
)
)

Open in new window


Be aware, the % variables are case-sensitive.  

Coralon
0
 
frugalmuleAuthor Commented:
Hi,

Your suggestion msg * /server:servername This is my test message seems to return a message to me if I put in my computer name or someone elses, but does not display the message for the end user.
0
 
CoralonCommented:
It will show up for everyone logged in interactively. I.e. If you run your msg against a Remote Desktop server, all the users logged into that machine will get the message.

It will not show for users logged into the network.

Coralon
0
 
frugalmuleAuthor Commented:
What I am saying is that it isn't displaying the message.
0
 
CoralonCommented:
Are you an admin on those machines?

Coralon
0
 
frugalmuleAuthor Commented:
Unfortunately not
0
 
CoralonCommented:
I've always been an admin using it.  I will give it a shot over the weekend and see what I can find.

Coralon
0
 
frugalmuleAuthor Commented:
Great.  I woud appreciate that very much.
0
 
CoralonCommented:
I did just test it, and you do have to have admin rights on the box that is receiving the message.  If you do not, it cannot enumerate any sessions and won't send to them.

Coralon
0

Featured Post

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.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now