User Notifications

Ever wanted to tell your users that something needs to be rebooted and knew they just do not read their emails that quickly?

This type of application may not be suited for all network types or situations, but if you believe this application can benefit you as an IT Administrator in certain scenarios, then read below what it can do for you.

You can even run this application only for a few key users.   


  • See active clients on your network.
    • Shows Active/InActive status of user based on 5 minutes of mouse movement.
  • Send messages to users logged into Workstations or RDS Servers.
    • Can send message to a single user, multiple or All active users.
  • Shows when Messages are Displayed to the user and Clicked.
    • User has Ok and No option, which will be indicated on the Console screen.
  • Works over HTTP, so can be used with internal network users or remote users using a NAT on your router.
  • Console App Requires DotNetCore.
  • Clients only require DotNet Framework 4.5, which should be installed already on most workstations. 
  • Works on standalone desktops and Terminal Servers (RDS)
  • Does not require domain authentication. 

User Popups

  • Set to always on top
  • Popup are displayed on the window where the user's mouse is.
  • Popup stays visible for 5 seconds before user can close it.
  • Popup also fades in slowly. 

How It Works

  • Clients connect to the computer running the console using a silent agent that can be copied manually or using GPO. It then runs in the background.
  • Console Application listens on the required port and displays the input that the clients send it.
  • It shows if the user is active, has seen the message or if they clicked it. 
  • The console hosts the message via HTTP and the clients check every 10 seconds for new messages, either to itself or everyone. 
  • Clients can only get the messages while the console is open (which opens the network port). 
  • Messages clear when application is closed as to not send old messages to clients who were not online the next time the console opens. 

How to run it

  • Ensure port 80 is available to listen on, on the workstation that will be used to run the console. Can also be switched to another port.
  • Ensure DotNetCore is installed on the device where the Console is run.
  • It is recommended to run the console on some management server, but not a requirement. 
  • Open the Console Application and it should bring up a firewall prompt to allow the application to listen on the network. 
  • Copy the UserAgent.exe file with a Servers.txt file that points to the Console server/workstation Example :
  • Create a shortcut in the user's startup folder to that .exe so that it runs on startup.

The client and console is very lightweight and can be run indefinitely.
The code for the Agent is also semi open source.
There is a link to the code from the download page. 

This tool is for members only.