So
came the Windows Management Framework for all operating systems, even for XP.
For me there, besides actually PowerShell 2.0, the main one is WinRM. Attached to PowerShell is just a way to execute commands on a remote computer.
Here's how to do it:
0. Put the Windows Management Framework Core
')
1. To configure winrm, on the machine that will be the server:
1.1 go to cmd.exe (I tried to do it from under ISE, but it does not work with interactive console programs)
1.2 run winrm qc
1.3 answer Y to the question about changes
2. Now, in PowerShell ISE on the client machine, click the icon with the terminal image, type the server name and account, then enter the password and work with the usual ISE on the remote machine.
And with the help of the * -PSSession command set, such a script is possible. Log in to the remote machine, perform a lengthy operation there, return and
inform the user that everything has been done.
PS
Boomburum sent a message from the anonymus:
"Hello! Help is needed because he himself did not find a solution;)). In general, the problem is this - I do not know how to contact the author of one of the topics. (specifically - habrahabr.ru/post/73613/). This article pushed me to get acquainted with the powershell networking capabilities. When configuring this feature on a PC with Windows XP SP3, a problem arose - an error popped up as follows:
************************************************** ********************
PS C: \ Documents and Settings \ Administrator> winrm qc
WinRM is not set up to receive requests on this machine.
The following changes must be made:
Start the WinRM service.
Make these changes [y / n]? y
WinRM has been updated to receive requests.
WinRM service started.
WSManFault
Message = Access is denied.
Error number: -2147024891 0x80070005
Access is denied.
PS C: \ Documents and Settings \ Administrator>
************************************************** ********************
For a long time I was looking for ways to solve this problem on the Internet, but I could not find anything worthwhile. Generally,
To solve this problem, go to Start-> Administration -> Local Security Policy (Local Security Settings - secpol.msc) -> Security Options -> We are looking for "Network Access: Sharing and Security Model for Local Accounts" (Network Access: Sharing and security model for local accounts) -> change the policy to “Normal -...” (Classic -...) -> Reboot and that's it — end the problem!
Huge request, send this message to the author of this topic, because I can't do this on my own. Let him post it, because the Russian-speaking part of the Internet population will greatly simplify the search for a solution to this problem. The problem is quite widespread! But I only noticed on Windows XP. (Everything was checked on a virtual machine with a clean system). Thank you very much in advance! ”