Wednesday, June 1, 2011
6:08 PM | Posted by Andreas Panagopoulos | |
Remember the glorious days of net send? Admittedly some of us used to scare the lives out of our 'favourite' users by sending them "C Drive format commencing in 30 seconds" and the such... I will not disclose names but what I can say is that it was in the early, immature days in their careers.
In actual fact, the 'net send' command was an extremely useful tool for sending messages to users that they simply couldn't ignore and what's more, couldn't claim they didn't notice. There were of course some security concerns, which is why in most environments the messenger service stayed disabled in user workstations.
Well, with the introduction of Vista and 2008 Server we waved the good ol' days of 'net send' goodbye! Enter msg.exe which was well... the same bar one little but very important detail: you cannot send messages to multiple PCs! The dependence of some IT departments on this functionality was lost on me until a recent case with a client. Apparently, being able to message multiple computers in one command was very important and some form of alternative was needed.
To avoid going with 3rd-party software, I came up with this command line script workaround. Here it is:
Copy-paste the following lines into a text file and rename it to netsend.bat
set /P INPUT=Type input: %=%
if "%INPUT%"=="" goto input
echo Your input was: %INPUT%
echo Hit any key to proceed, or CTRL-C to cancel
FOR /F %%p IN (pcs.txt) DO msg * /server:%%p %INPUT%
Now create another text file and name it pcs.txt. List all workstations that you want to message in it, but make sure there are no spaces or empty lines. Here's an example:
Last but not least you'll need to change a registry setting in all workstations you want to message. Copy-paste the following text into a text file, and rename it to netsend.reg
Windows Registry Editor Version 5.00
Now run the file on each target workstation to import the setting into the registry.
If you're managing a large domain network you can put the reg file in a GPO and link it to the OU(s) of the target workstations. Similarly, to avoid having to manually type tens or hundreds of PC names in pcs.txt, you can use PowerShell to export the workstation names from Active Directory to a text file.
So, there you go! Just open a command line window, run netsend.bat, type in the message you want to send and voila!! Faith in the 2008/R2 system restored!!!
Well, the title says it all! You will have to excuse my lack of use of images, I'll have to get back to this post and add some la...
Workaround for Citrix EdgeSight Process Usage report showing average times instead of time sums and a quick insight into using MS SQL Report Builder with queries to generate custom SQL reportsWhy oh why did Citrix botch up their great "Process Usage" report? Why do software vendors tamper with great product features ins...
Annoying "You cannot access VMM management server scvmm.domain.local" 1604 error: "Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again."Seen this before?? I just introduced SCVMM 2012 RC to my Hyper-V cluster lab environment. Set it up on a VM, it immediately saw my...
EDIT: This post is receiving a surprising amount of hits, and is being debated amongst colleagues in forums, events and gatherings, in my...
"The trust relationship between this computer and the primary domain failed" messing about with SCVMM 2012 RCI love all things Microsoft, but SCVMM turns out to be a real pain... even in its latest version. Looks like 2012 will stay in my lab envir...
Got SCVMM 2012 RC on a Windows 2008 R2 Virtual Host. When I tried to add a new Library Share with Default Resources on an existing Library...
Remember the glorious days of net send? Admittedly some of us used to scare the lives out of our 'favourite' users by sending them...
PRE-REQUISITES: Configure network access account SCCM Console --> Administration --> Site Configuratio...
First post of many to come... I'll try to keep this one short and just share what this blog will be about. We'll talk about bot...
With a mind on the cloud, eyes on virtualization and feet planted firmly on the (datacenter) ground...Hindsight is great! Too bad it comes from mistakes. Not too long ago in human time but light-years in IT time there were mainframes and...