Windows MSG command: how it works and where it falls short Skip to content

MSG Windows command: Business operation and limitations

« Guided reading

Find the essentials in 60 seconds

The context, key signals and priority actions brought together in this article.

MSG commandWindows NetworkLimitations and alternatives
Coverage: Windows MSG command, operation and limitations

msg.exe is still present on Windows 10 and 11 but its technical constraints make it unsuitable as soon as a large-scale network needs to be alerted.

Net Send no longer exists since Windows Vista: its official successor, msg.exe, relies on Terminal Server session services and is used differently.
The syntax is accessible, the examples are reproducible but three network prerequisites often block sending to remote machines.
In addition to one-off use between two workstations, the lack of traceability and the inability to target by service or by site pose concrete problems.
What is MSG really worth when you have to alert 500, 2,000 or 15,000 workstations with the certainty that the message has been read?

msg.exe, official successor of net send

Since Windows Vista, the net send command no longer exists. It was based on the Messenger service, massively diverted for spam network in the early 2000s and permanently deleted with Vista. Its official successor is called msg.exe, still present in Windows 10 and Windows 11.

Technically, msg.exe operates on a different net send basis: it relies on Terminal Server session services, now called Remote Desktop Services. It is this user-oriented architecture that determines both its syntax and its constraints in the business environment.

The command is only available on the Business, Business and Server editions of Windows. On a heterogeneous network, this restriction excludes some of the workstations from the outset. In business no one is using a Windows Family version.

MSG limits in the business environment

For a one-time exchange between two workstations, MSG may suffice. As soon as an organization-wide network is alerted, its technical and operational constraints become binding.

  • Mandatory requirements to be deployed on each workstation. MSG is missing from Windows Home editions. On compatible editions, remote sending requires manual modification of the AllowRemoteRPC registry key on each recipient machine, authorization of RPC flows in the firewall, and administration rights on the target workstations: all of the conditions to be met and maintained over time.
  • No reading charges, no newspaper. MSG does not keep any trace: no time stamping, no list of workstations affected or in failure, no nominative confirmation. After an incident, it is impossible to determine who was informed and at what time: a dead spot incompatible with any formal crisis management.
  • A machine name targeting, without operating the Active Directory. MSG is not aware of services, sites or buildings. Reaching a precise organizational perimeter requires keeping the correspondence files between job names and business structures yourself, and then scripting sending loops while the Active Directory already contains this information.
  • Typing under pressure without a prepared template. In the event of an incident, the operator must open a command prompt and write the message to the keyboard without a pre-edited model, no visual priority level and no trigger shortcut. The text is raw: a critical alert is visually identical to a meeting reminder.

What dMessage does where MSG reaches its limits

When an incident occurs, the issue is no longer to send a message, but to make sure that it has been received, by whom, and at what time. On the four specific points where MSG blocks, dMessage works as well.

  • Instant broadcast throughout the network, Whatever its size: one single action is enough to reach all the workstations in a few seconds. The pop-up is a key feature of all open applications, including during Teams meetings or presentations, without the user being able to miss it.
  • Nominative and timed reading Accused: each reception is recorded. During and after the incident, the list of workstations reached, users who have paid the message and exact schedules is available in real time for a direct answer to the question posed by the security teams or management once the crisis has passed.
  • Targeting via the existing Active Directory, no correspondence file to be maintained manually: by service, by site, by building. The organizational structure already present in the directory is exploited directly, thus avoiding loop scripts and lists of machine names to keep up to date.
  • Preconfigured models with visual priority levels, prepared out of crisis situation and triggerable in a few clicks: the appropriate message leaves without re-entering under stress. The set works 100% On-Premise, in a closed circuit, with no reliance on messaging, internet or third-party cloud.

Frequently Asked Questions

On Windows 11 editions Professional and Enterprise, msg.exe works with the same syntax as Windows 10. The Home edition does not have one, and sending to a remote machine always requires the modification of the AllowRemoteRPC key on the recipient workstation.

MSG does not propose any native mechanism to reach the entire domain: the * character targets all sessions of a single machine. The usual circumvention is to loop on a machine name file (for /f %i in (postes.txt) do msg /server:%i * "message"), but this method remains sequential, without consolidated status return and without warranty of remission.

On the rights side, sending a message to its own session does not require any particular privilege. As soon as other sessions on the same machine or remote machines are targeted, an account with administrative rights on the target workstations is required, in addition to the network prerequisites already mentioned.

Adopted by the most demanding structures

Where unread information is not an option, dMessage broadcasts vital alerts throughout the network in seconds.

Health

Several CHUs trigger their White Plans and Orsan Plans on all services in seconds, without depending on the messaging.

Industry

A French industrialist +18 000 workstationsdeployed via SCCM, manages its industrial emergencies and cyber incidents on a sovereign channel.

Public sector & finance

National public institutions and asset management actors rely on dMessage for their internal critical communications.

A question?

Frequently asked questions

dMessage requires an internet connection to work?

No. dMessage operates entirely in closed circuit on the organization's local network, without reliance on the internet or third-party cloud service. Alerts are issued even in case of internet access interruptions.

All data remain on the organization's infrastructure: dMessage is deployed 100% On-Premise, without any transit or external storage. The host is the organization itself.

No. dMessage relies on the existing Active Directory for service or site targeting, without infrastructure reconfiguration or maintenance of additional matching files.

No. Unlike msg.exe, which requires changing a registry key on each receiving station and opening RPC streams, dMessage does not require any individual requirements of this type on the targeted machines.

Pop-up is a key feature of all active applications, including a Teams meeting or presentation. On the other hand, dMessage, like any software channel, cannot reach an off workstation or without an open session.

Protect your teams today

Do not entrust your vital alerts to a saturated email system. Take full control of your sensitive information flows with On-Premise technology. Never miss critical information again.

Ask for your demonstration Discover Functions

Sovereign deployment. Zero complex technical engagement.