|
Team MSG net send Command line format: user- Username. Important! msg Parameter AllowRemoteRPC type REG_DWORD and equal 1 AllowRemoteRPC 0 msg.exe 445 Examples of using MSG: Server 192.168.0.1 TSServer Windows7 To execute a command msg PSExec from the package PSTools or standard means runas.exe msg |
MSG command – send a message to the user.Team MSG existed back in Windows 2000/XP and was intended for exchanging messages between users logged in locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later family operating systems Windows command MSG has become mainstream standard means messaging because the team net send This OS is no longer supported. Command line format: MSG (user | session name | session ID | @filename | *) Description of command line parameters: user- Username. |
How to send a message to all computers on a local network?
Important!
The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers local network, you will need to change some default security settings in Windows Vista, 7 and later operating systems.
With standard settings, messages are not sent to users of remote computers and are accompanied by the following message:
Error 1722 when retrieving session names
This means that the computer where the message is to be received cannot obtain information about the logged-in users. The reason may be that the firewall is blocking incoming connections, the user's rights in relation to the remote system are insufficient, or remote procedure calls are prohibited in the terminal server service parameters. At a minimum, for messaging using the command msg between computers, you must have account user valid for the remote system and make the following settings:
On each computer to which messages will be sent, add to the registry key HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server parameter AllowRemoteRPC type REG_DWORD and equal 1 To change the settings, you can use the .reg file with the following content:
Windows Registry Editor Version 5.00
"AllowRemoteRPC"=dword:00000001
In Windows Vista, Windows 7, 8, 10 registry key AllowRemoteRPC exists, but has the same value 0 what needs to be fixed. A reboot is required for changes to take effect.
Because the messaging utility msg.exe uses SMB protocol(Server Message Block), each computer to which messages will be sent must have an open TCP port 445
Examples of using MSG:
msg * /server:Server "Test message"— send a test message to all computer users Server
msg * /server:192.168.0.1 "Test message"— send a test message to all users of a computer with an IP address 192.168.0.1
msg RDP-Tcp#0 /server:TSServer "Test message"— send a test message to a terminal session user named RDP-Tcp#0 on the computer TSServer
msg console /server:Windows7 "Test message"— send a test message to the current local user computer Windows7
msg console "Test message"— sending a test message from an RDP session user to a local user. If this command is not executed by a terminal session user, then the message will be sent by the local user to himself.
To execute a command msg You can use the utility on behalf of another user PSExec from the package PSTools or standard means runas.exe
psexec -u otheruser -p otherpass msg * /server:win10 TEST message
runas /user:otheruser "msg * /server:win10 Test message"
Messages sent by the team msg local user of a computer with an operating system Windows system XP, which is missing (not yet included in Windows) are displayed in the window prompting you to register on the system and may be accessible to outsiders.
Full list of CMD Windows commands
MSG command – send a message to the user.Team MSG existed back in Windows 2000/XP and was intended for exchanging messages between users logged in locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows family operating systems, the MSG command became the main standard messaging tool because the command net send This OS is no longer supported. Command line format: MSG (user | session name | session ID | @filename | *) Description of command line parameters: user- Username. Important! The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some default security settings in Windows Vista, 7 and later operating systems later With standard settings, messages are not sent to users of remote computers and are accompanied by the following message: Error 1722 when retrieving session names This means that the computer where the message is to be received cannot obtain information about the logged-in users. The reason may be that the firewall is blocking incoming connections, the user's rights in relation to the remote system are insufficient, or remote procedure calls are prohibited in the terminal server service parameters. |
Sending a message via the command line to another computer
At a minimum, for messaging using the command msg between computers, you must have a user account valid for the remote system and make the following settings:
On each computer to which messages will be sent, add to the registry key HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server parameter AllowRemoteRPC type REG_DWORD and equal 1 To change the settings, you can use the .reg file with the following content:
Windows Registry Editor Version 5.00
"AllowRemoteRPC"=dword:00000001
In Windows Vista, Windows 7, 8, 10 registry key AllowRemoteRPC exists, but has the same value 0 what needs to be fixed. A reboot is required for changes to take effect.
Because the messaging utility msg.exe uses the SMB (Server Message Block) protocol; a TCP port must be open on each computer to which messages will be sent 445
Examples of using MSG:
msg * /server:Server "Test message"— send a test message to all computer users Server
msg * /server:192.168.0.1 "Test message"— send a test message to all users of a computer with an IP address 192.168.0.1
msg RDP-Tcp#0 /server:TSServer "Test message"— send a test message to a terminal session user named RDP-Tcp#0 on the computer TSServer
msg console /server:Windows7 "Test message"— send a test message to the current local computer user Windows7
msg console "Test message"— sending a test message from an RDP session user to a local user. If this command is not executed by a terminal session user, then the message will be sent by the local user to himself.
To execute a command msg You can use the utility on behalf of another user PSExec from the package PSTools or standard means runas.exe
psexec -u otheruser -p otherpass msg * /server:win10 TEST message
runas /user:otheruser "msg * /server:win10 Test message"
Messages sent by the team msg local user of the computer with operating system Windows XP that is missing (not yet logged into Windows) are displayed in the login prompt and may be accessible to others.
Full list of CMD Windows commands
net send command reference
1. General information about the net send command
2.Usage net commands send
3. Net send command syntax
4. Notes on using the net send command
5. Examples of using the net send command
6. Enabling and disabling the messaging service and net send
7. How to send net send messages in Windows 7
Understanding the net send command
Net send is a console application included with some versions of Windows and designed to send messages over a local network to another user, computer, or alias. The command is only available on Windows NT, 2000, XP, 2003 and is not available on Windows 7, Vista, ME, 98, 95 and older. In Windows XP, starting with Service Pack 2, the net send command is disabled by default.
Using the net send command
The net send service must be running for the net send program to work. Windows messages. In fact, the net send command is just a command line interface to the messaging service, which directly deals with sending and receiving messages. To be able to receive messages, the computer to which the message is sent must also be running Messenger Service or another program that uses the same messaging protocol. The message can only be sent to an active entity on the network. If a message is sent to a user, they must be logged in using their username.
To send messages with the net send command, launch the command interpreter ( command line). To start the command interpreter, select Run from the Start menu, type cmd, and click OK. Use the net command with the send parameter and other parameters in accordance with the command syntax. The messaging service displays received messages in a standard Windows message dialog box.
net send command syntax
The net send command has the following syntax:
net send (username | * | /domain | /users) message
username— user name, computer name or nickname to whom you want to send a message;
* — sending messages to all members of a domain or workgroup;
/domain— sending a message to all names in the computer domain or in the domainname domain;
/users— sending a message to all users connected to the server;
message- Message text.
Notes on using the net send command
If command parameter arguments contain spaces, they must be enclosed in quotation marks.
It may be difficult to use long message recipient names. Names used by the messaging service are up to 15 characters long.
The maximum length of broadcast messages is 128 characters. The maximum length of personal messages is 1600 characters.
Examples of using the net send command
To send the message “You can send a message over a local network using the net send command” to the user ivanov, enter:
net send ivanov You can send a message over a local network using the net send command
To send a message to everyone connected to the computer from which the message is being sent, type:
net send /users Everyone immediately exit 1C!
To send a message to all users in the ukmz domain, enter:
net send /domain:ukmz Electricity in the building will be turned off in 5 minutes
To send a message to all users in the domain of the computer from which the message is sent, type:
net send * Gentlemen, the meeting with the general director will take place at 13:00
Enabling or disabling messaging and net send
Enabling and disabling the messaging service is possible using both the MMC console (Services snap-in) and using the command line.
To perform these operations, you must have administrator rights.
To enable the messaging service using the MMC console, follow these steps: Go to Control Panel. Open the Administration, Services folder. Find "Messenger" in the list. Open the service properties window. Select 'Auto' from the 'Startup Type' list if you want the service to start automatically when booting Windows. Then click the Start button. Click OK.
To disable the messaging service, follow these steps: Go to the Control Panel. Open the Administration, Services folder. Find "Messenger" in the list. Open the service properties window. Select 'Manual' from the 'Startup Type' list. Then click the Stop button. Click OK.
To enable messaging from the command line, enter the following commands in a shell:
sc config messenger start=auto
net start messenger
To disable the messaging service from the command line, enter the following commands in a shell:
net stop messenger
sc config messenger start= disabled
How to send net send messages in Windows 7
To send net send messages in those versions of Windows where this command is missing (Windows 7, Vista, ME, 95, 98), you can use a third-party software.
Sending messages using msg.exe
We suggest you use two programs: WinSent Messenger and the Sent utility. WinSent Messenger is a messenger for local networks, compatible with net send. The Sent utility is designed to send messages from the command line. More detailed information available on the pages of these software products:
WinSent Messenger - instant messenger for local network
Sent is a utility for sending net send messages from the command line in Windows 7/Vista.
Does your company have difficulty communicating within the team? Tired of calling every colleague to a meeting? Tired of walking all over the office to solve the simplest issue? If you answered “yes” to at least one of these questions, then it’s time to implement a corporate local messenger.
Softros LAN Messenger is a simple and convenient office messenger - a program for messaging on a local network of any size. The company messenger does not require or use an Internet connection and thus guarantees that the transmitted information will not go beyond the local network. The application is easy to install and use, has a nice, intuitive interface and works correctly for users with limited rights. For your convenience, there is also a file sharing function between users of the network messenger. Fine tuning allows the administrator to prohibit the use of certain functions of the application and changing its settings, which can be useful in a large company with a dispersed infrastructure. A serverless messaging and file exchange system allows you to save on hardware. 14 years of continuous improvement guarantee the quality and stability of our messenger for your local network.
brief information
Latest version: 9.2
Supported OS: Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 2008, Windows 7, Windows 8.1, Windows 10, Windows 2012, Windows 2016
Supported network types: LAN, WAN
Key features of Corporate Messenger:
- Messaging with chat option
Create virtual chats within your network with any number of users. - Secure Network Communication
Messages do not go beyond the local network. - Group messages on the local network
Use mass messaging to inform employees about upcoming events. - Quick messages
Customize up to 10 preset template messages with the ability to instantly send via hotkey, for quick answers with typical phrases or sentences. - Huge set of Emoji emoticons
Personalize your messages with the built-in Emoji pack (about 830 emoji) - Transferring files within a network, including mass mailing files
Sharing documents with colleagues has become much easier.Net send in Windows 7
- User grouping
Organize your colleagues by department or position for ease of communication. - Remote desktop sharing
Request remote assistance from your colleague or network administrator directly from Messenger by giving him access to your desktop remotely. Ask the administrator to help you set up any programs or Windows on your computer, ask a colleague to help resolve work issues. - Remote desktop administration
Administrators authorized in the domain as domain administrators, or on the remote computer as local administrators, can connect to user desktops directly, bypassing connection permissions from the user. - User Rights Management
The administrator can prohibit the use of any function if necessary. - Message history
You will never lose a single message because they are all saved in history files. - Serverless architecture of the messenger
LAN Chat does not require a dedicated server installation. - No need for an Internet connection
Messenger for local network works only within your company's network and saves your subordinates from wasting time on ICQ, saving your traffic and minimizing the possibility of attacks. - Terminal Server support
LAN Messenger works successfully on a terminal server from Microsoft or Citrix, and also supports the simultaneous use of several user sessions. (After installing Softros TS Engine.) - Easy to install
You don't need any administrative skills to start using our program. Just install Internal Messenger on every computer on your local network and it's ready to go. - Ease of distribution
Having configured network settings, as well as settings for user groups on one computer, you can export them to a file and then use them on all computers within the company network. This simplifies setting up the program in complex networks.
Top 10: Chat for LAN
Client-server messenger for local network. Integrates with Active Directory, multilevel list contacts, bulletin board, mass notification system, conferences, SSL traffic encryption, offline message and file transfer, flexible system user rights management, file and folder transfer. Built-in Kanban boards for projects
A client-server program for communication in a corporate network, which runs on the Windows OS platform. CommFort includes modules for chat, image sharing, file transfer, VoIP and video communication. Supports video conferencing for up to 32 users
Softros LAN Messenger
A simple and reliable messenger for the local network. Does not require an Internet connection. In addition to sending instant messages and transferring files, it allows you to create virtual rooms, make mass mailings, save message history, and group contacts by department or position.
Corporate mobile messenger V source codes. Includes Corporate mobile messenger in source codes
Multimedia corporate messenger. Supports online status control, chat, voice and video communication, conference calling, video mail, screen-sharing.
Msg Team
Works on PC, Mac and mobile platforms - iPhone, iPad, Nokia, Android and BlackBerry. Uses the open Jabber protocol (XMPP)
Corporate client-server platform for interaction and communication in real time. Integration with Active Directory, access to the archive of all transferred messages and files, delivery of offline data and assignment of documents to employees with strong encryption.
Simple and fast multi-user chat with activity control on the local network. Designed for medium and small local networks (up to 300 computers). Does not require a dedicated server and can be quickly deployed even on a network without a professional administrator.
A simple and powerful cross-platform client-server chat for local networks and the Internet, open source.
Free open-source cross-platform messenger for the local network. Does not require a server. Logging messages. File transfer.
Free cross-platform chat for corporate networks. File transfer. Offline messages.
Free sharing software instant messages in networks Microsoft Windows. High speed delivering messages to a large number of recipients (1000+)
Team MSG existed back in Windows 2000/XP and was intended for exchanging messages between users logged in locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows family operating systems, the MSG command became the main standard messaging tool because the command net send This OS is no longer supported.
Command line format:
MSG (user | session name | session ID | @filename | *) [message]
Description of command line parameters:
user- Username.
session name- Session name.
Session ID- Session ID.
@file name- A file containing a list of usernames, sessions, or session IDs to which the message is sent.
*
- Send a message to all sessions on the specified server.
/SERVER:server- Server (default - current).
/TIME:seconds- Waiting interval for confirmation from the recipient.
/V- Display information about completed actions.
/W- Waiting for a response from the user, useful together with /V.
message- The message being sent. If not specified, a prompt is issued or input from STDIN is accepted.
Important!
The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some default security settings in Windows Vista, 7 and later operating systems later
With standard settings, messages are not sent to users of remote computers and are accompanied by the following message:
Error 1722 when retrieving session names
This means that the computer where the message is to be received cannot obtain information about the logged-in users. The reason may be that the firewall is blocking incoming connections, the user's rights in relation to the remote system are insufficient, or remote procedure calls are prohibited in the terminal server service parameters. At a minimum, for messaging using the command msg between computers, you must have a user account valid for the remote system and make the following settings:
on each computer to which messages will be sent, add to the registry key HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server parameter AllowRemoteRPC type REG_DWORD and equal 1 To change the settings, you can use the .reg file with the following content:
Windows Registry Editor Version 5.00
"AllowRemoteRPC"=dword:00000001
In Windows Vista, Windows 7, 8, 10 registry key AllowRemoteRPC exists, but has the same value 0 what needs to be fixed. A reboot is required for changes to take effect.
because the messaging utility msg.exe uses the SMB (Server Message Block) protocol; a TCP port must be open on each computer to which messages will be sent 445
Examples of using MSG:
msg * /server:Server "Test message"- send a test message to all computer users Server
msg * /server:192.168.0.1 "Test message"- send a test message to all users of a computer with an IP address 192.168.0.1
msg RDP-Tcp#0 /server:TSServer "Test message"- send a test message to a terminal session user named RDP-Tcp#0 on the computer TSServer
msg console /server:Windows7 "Test message"- send a test message to the current local computer user Windows7
msg console "Test message"- sending a test message from an RDP session user to a local user. If this command is not executed by a terminal session user, then the message will be sent by the local user to himself.
To execute a command msg You can use the utility on behalf of another user PSExec from the package PSTools or standard means runas.exe
psexec -u otheruser -p otherpass msg * /server:win10 TEST message
runas /user:otheruser "msg * /server:win10 Test message"
Messages sent by the team msg to a local user of a computer running the Windows XP operating system who is not present (has not yet logged into Windows) are displayed in a window with an invitation to register in the system and may be accessible to others.
It existed in Windows 2000/XP and was intended for exchanging messages between users logged in locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows family operating systems, the MSG command became the main standard messaging tool because the command net send This OS is no longer supported.
Command line format:
MSG (<пользователь> | <имя сеанса> | | @<имя файла> | *} [<сообщение>]
Description of command line parameters:
<пользователь>
Username. <имя сеанса>
Session name. Session ID. @<имя файла>
A file containing a list of usernames, sessions, or session IDs to which the message is sent. *
Send a message to all sessions on the specified server. /SERVER:<сервер>
Server (default - current). /TIME:<секунд>
The interval for waiting for confirmation from the recipient. /V Display information about completed actions. /W Waiting for a response from the user, useful together with /V. <сообщение>
The message being sent. If not specified, a prompt is issued or input from STDIN is accepted.
Important!
The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some default security settings in the Windows Vista, 7 and 8 operating systems .
Usually, with standard settings, sending a message to remote computer, is not executed and is accompanied by the message
Error 1722 when retrieving session names
This means that the computer where the message is to be received cannot obtain information about the logged-in users. The reason may be that the firewall is blocking incoming connections, the user's rights in relation to the remote system are insufficient, or remote procedure calls are prohibited in the terminal server service parameters. At a minimum, for messaging using the command msg between computers, you must have a user account valid for the remote system and make the following settings:
|
Windows Registry Editor Version 5.00 "AllowRemoteRPC"=dword:00000001 In Windows Vista, Windows 7, 8, 10Technical Preview registry key AllowRemoteRPC exists, but has the same value 0 what needs to be fixed. A reboot is required for changes to take effect. Examples of using MSG: msg * /server:Server "Test message"- send a test message to all computer users Server msg * /server:192.168.0.1 "Test message"- send a test message to all users of a computer with an IP address 192.168.0.1 msg RDP-Tcp#0 /server:TSServer "Test message"- send a test message to a terminal session user named RDP-Tcp#0 on the computer TSServer msg console /server:Windows7 "Test message"- send a test message to the current local computer user Windows7 msg console "Test message"- sending a test message from an RDP session user to a local user. If this command is not executed by a terminal session user, then the message will be sent by the local user to himself. To execute a command msg You can use the utility on behalf of another user PSExec from the package PSTools or standard means runas.exe psexec -u otheruser -p otherpass msg * /server:win10 TEST message runas /user:otheruser "msg * /server:win10 Test message" Messages sent by the team msg to a local user of a computer running the Windows XP operating system who is not present (has not yet logged into Windows) are displayed in a window with an invitation to register in the system and may be accessible to others. |
Check if your system supports the msg command. The functionality of this command is much the same as the unused net send command. But this command only works in professional and enterprise versions of Windows. If you work in Windows Home, upgrade to Professional or Enterprise to be able to use the msg command.
- To find out your Windows version, click ⊞ Win + Pause or click right click Click on "Computer" and select "Properties". The Windows version will appear under Windows Edition.
Open a command prompt. Like net send, the msg command is run from the command line. Command line starts different ways(depending on your Windows version), or just click ⊞Win and enter cmd.
- Windows Vista/7: Open Command Prompt from the Start menu.
- Windows 8.1/10: Right-click the Start button and select Command Prompt.
- Windows 8: Click ⊞ Win + X and select Command Prompt.
Enter the command. Type msg and press Space. Next, you need to enter information that contains the text and direction of the message.
Identify the recipient of the message. Compared to net send, the msg command has additional options.
- msg username – enter the name of a specific user.
- msg session – Enter the name of the specific session.
- msg Session ID – Enter the specific session ID.
- msg@filename - Enter the name of a file that contains a list of usernames, sessions, and/or session IDs. Useful for sending messages to department employees.
- msg * – the message will be sent to all users connected to the server.
Specify the server whose users you want to send the message to (if you wish). If you want to send a message to a user who is connected to another server, enter the server information after the recipient information. If no server is specified, the message will be sent to the current server.
- msg * /server: server name
Set a time limit (if you wish). You can set a time limit to specify how long to wait for confirmation from the recipient. The time modifier is entered after the server information (if any).
- msg * /time: seconds (for example, 300 seconds for a five-minute interval)
Enter your message text. After entering the various parameters, enter your message text. Or click ↵Enter, and the system will prompt you to enter the text of the message in a separate line.
- For example: msg @salesteam /server:EASTBRANCH /time:600 Congratulations on increasing your sales this quarter!
Send a message. To do this, click ↵Enter. The recipient will receive it immediately.
- The msg command is intended to send messages to terminal users, not just different computers connected to the same network.
Troubleshoot. When working with msg you may encounter the following errors:
- "msg" is not recognized as an internal or external command, operable program or batch file. (msg is not recognized as internal or external team, executable program or batch file). In this case Windows version does not support msg . Upgrade Windows to Professional version.
- Error 5 getting session names or Error 1825 getting session names. Error when communicating with the recipient. You can try to resolve this problem by opening the registry editor on the recipient computer (to do this, run the regedit command), going to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server and changing the AllowRemoteRPC setting from 0 to 1.
I was faced with the problem of informing users, the most common reason is a 1C update, which requires all my users (and there are more than 160 of them) to log out of 1C and not log in for some time. It would seem that there’s nothing complicated about it, you can send a message via e-mail, as I did before when I had Office 365, but Yandex mail has its limitations: no more than 50 users on the mailing list. If you send it to more users, then the letter will simply not reach some. Sending 50 users separately is not convenient. The second problem with Yandex mail is the need to enter a captcha; in some cases, the system perceives mass mailing as spam, but the letters are necessary, if you do not warn the user, they will not be saved in time and there may be problems...
In general, it has become terribly inconvenient to send messages to all users. I started thinking about possible solutions.
The first thing that came to mind was: , but several inconveniences emerged:
- Messages arrive within approximately 30 minutes to 160 workstations, which is a very long time.
- The message appears only on the taskbar; if the user works via a remote desktop, he will not see the message immediately.
- It is necessary to maintain the functionality of Kaspersky agents on the user’s working machines, otherwise the message will not arrive at all.
The second option is to install some kind of messenger, but here there are also several inconveniences.
- There are a lot of messengers, they are not universal, you cannot send messages to each other between messengers.
- Good messengers are paid.
- Messages do not pop up on top of all windows, and if you need to communicate something urgent and important, then this is a useful property of the message.
- It requires installation and configuration of these instant messengers, as well as user training in new software.
As a result, I'm on the team Windows line, there are net send and msg commands to send messages to all computers on the local network. It all works very simply, you open the command line, write a command, a message is sent to the computer whose name you specified in the command text. Moreover, the message pops up on top of all windows, no registration is required, and everything is completely free.
The command for sending messages to one computer on the local network looks like this:
msg * /server:computername “Test message, click OK”
I made a list of computers, then a little tedious work on creating the same type of commands in one txt file, but it’s done quickly via copy-paste. The main thing is to make a list of computers. In a domain, this is done quite simply through the “Users and Computers” snap-in, right-click under the list of computers, then “Export list” directly to a TXT file. Since I have about 160 computers in the domain, I approached the issue a little more creatively, I didn’t do “copy-paste”, but in the already existing list of computers I auto-replaced the first letter in the computer name with msg * /server: + The first letter in the name of the computers, luckily for me, it was the same for everyone. Similarly for the second part, but only with the last letter of the computer name (the last letter in the computer name + "Test message, click OK"), as a result I received a TXT file with a list of commands. I changed the file extension from txt to bat and launched it for execution. As a result, all computers in the domain received a “test message, click OK.”
Unfortunately, such a command does not work outside the domain, and since I completed the task, it was simply not rational to experiment further. I was unable to send messages to computers in the workgroup, but I have only a few such computers. You can send them a message by mail, or in Kaspersky, or through some messenger. Let this be a topic for one of the following entries.
As a result, what I received: 1 file in which you can quickly change the text of the message and with which I can send any message for free to everyone in the domain. It seems great, but there are still a couple of disadvantages:
- It is necessary to keep the file up to date, add new ones, delete non-existent computers.
- No prompt feedback.
- The file turned out to be ugly, I think you can load the computer name values from the file into this command, but there was no time to figure it out completely.
However, the pros outweigh all the cons:
- Quick to implement, requires virtually no preparation for the next shipment.
- It works reliably, the user will definitely see this message.
- For free.
- Very, very simple, you just need to know one command and computer names.
I will be glad to receive any comments, suggestions)
Loading...
