Skip to main content

How to show remote notifications in PowerShell

This snippet code below shows how to set notifications using PowerShell.

If you’re shutting down a computer, it’s good to show a message to alert the user that the computer is going to shutdown.

If Winrm or Windows Remote Management is already configured on the Active Directory environment, you can just run the script remotely.

Provided that the user account that invokes or run the script has the proper rights to access the remote computer.

Net send was quite useful during Windows XP glorious days.

Msg.exe can do the same job with net send, provided that Windows Remote Management is properly setup.

Like winrm quickconfig has been configured, and proper ports are open and of course Windows Remote service is running.

Different versions of Winrm have different ports to open that make msg.exe not as popular as net send.

To check the version of Winrm, open command prompt and type “winrm id”.
Don’t include the double quotes when typing at command prompt.

Running winrm id, will show the version of winrm running on the system.

This link below from Technet got helpful information about winrm.   

Installation and configuration of windows management:

WinRM 2.0:  The default HTTP port is 5985, and the default HTTPS port is 5986
From Technet link port TCP 5985 has to be open for Winrm if 2.0 version is running on the system.

Displaying remote messages using PowerShell alone is quite a huge task.

But using other tools such as msg.exe or PS tools would make life easier.

Here’s the code snippet on how to display notifications remotely:


$MsgCommand = { Msg UserName  "Alert or Display Message"}

Invoke-Command  -Computername 'Remote_Computer_Name'  -Scriptblock $MsgCommand

(Note Invoke-Command has to be in one line)

Replace UserName with the name of the actual user.
Replace Remote_Computer_Name with the hostname of the machine.

That’s a wow; using  two lines of code in PowerShell messages or notifications can be displayed remotely.

Of course, proper configuration of Winrm has to be done for these two lines of PowerShell command to run successfully.

Code snippet above can be tweak and configured in GPO as a Logon script.
And display a customized message, with the name of the logged on user.

Never tested this using GPO but I had run it using PowerShell ISE. You can read the code and check whether it will work or not.

Life is full of surprises, when you expect it to work and that would be the time that it will just not work for whatever reason.


$GetUserName = [Environment]::UserName

$CmdMessage = {C:\windows\system32\msg.exe $GetUserName 'Hello' $GetUserName 'your PC will shutdown in 1 nano second}

Invoke-Command -Scriptblock $CmdMessage

(Note that the $CmdMessage has to be in one line)

It will display a message box like: 

     Hello Bob your PC will shutdown in 1 nano second

The beauty of the script is it will just get the name of the logon user and used it as a parameter of the script. 

This command below will also connect to a remote computer provided that the PowerShell in which this code is exectued has the rights to logon to the remote computer.

Enter-PSSession -ComputerName Computer_Name

This link below provide more detailed example:

Use this script to send a message to a group of computers or servers:

$GetUserName =[Environment]::UserName

$CmdMessage = {C:\windows\system32\msg.exe $GetUserName  'Hello' 

$GetUserName 'your PC/Server will shutdown in 1 nano second' }

$pcListing = get-content d:\pc_server_Listing.txt

foreach($Computerx in $pcListing) {
  Invoke-Command -Computer $Computerx -Scriptblock $CmdMessage


Cheers!! Till next time!!!           


Free Android App:

Catholic Rosary Guide  for Android:
Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully.


Popular posts from this blog

Run PowerShell script in Task Scheduler

How to run a PowerShell script using Windows Task Scheduler? Please see image below on how to setup PowerShell script using Windows Task Scheduler. In Program/Script textbox, type: PowerShell.exe or type the whole path to PowerShell.exe In Add arguments (optional) textbox type:    -WindowStyle Hidden -File c:\Monitor.ps1    -WindowStyle Hidden === optional parameter to hide the PowerShell script when it runs    -File c:\Monitor.ps1 === path parameter where the script resides Check out this Technet link for optional parameters on how to launch PowerShell. Or you can just put the parameters on batch file and call the batch file via the task scheduler. Type line below on a notepad and save it as a batch file ".bat". PowerShell.exe -WindowStyle Hidden  -File c:\Monitor.ps1   Directly setting the PowerShell file on Task Scheduler may resolve to indefinite task that is running, above solutio

Copy a single file using robocopy

Copy a single file using robocopy from a local folder to a shared folder on the network. A simple rule of thumb before any disaster strike, don't interchange the source and the destination. If source and destination is mistakenly reverse, files might get overwritten. To avoid any loss of data do a test with a dummy file to ensure things work perfectly. Robocopy [source]    [destination]   [file to be copied] robocopy c:\local_c_folder  \\PC_network\shared_folder   file_to_be_copied_xx.txt The command will be completed successfully provided the network access right has no issues. Robocopy works quite good on large files. A simple copy or xcopy command will also work but the speed might vary. However, if the file (ex. an ISO file) and is more than 4GB and the filesystem  of the thumbdrive or the storage is FAT system, then robocopy or any methods of copying will not work. Since FAT has a file size limitation of less than 3GB. Robocopy is free it can be acce

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample Outpu