how to run commands in command prompt in remote computer and save output in local file
-
I want to run a command in remote computer command prompt and fetch command output of the remote computer and save the output in local system. i don't want to use WMI for this as wmi is not enabled in the remote computer.
WMI should help you achieve this task quite easily provided you have access to the remote machine. Try Create a Remote Process using WMI in C#[^] as a good sample.
Apps - Color Analyzer | Arctic | XKCD | Sound Meter | Speed Dial
-
WMI should help you achieve this task quite easily provided you have access to the remote machine. Try Create a Remote Process using WMI in C#[^] as a good sample.
Apps - Color Analyzer | Arctic | XKCD | Sound Meter | Speed Dial
i have already mentioned wmi is not an option.
-
I want to run a command in remote computer command prompt and fetch command output of the remote computer and save the output in local system. i don't want to use WMI for this as wmi is not enabled in the remote computer.
-
i have already mentioned wmi is not an option.
If firewalls settings can be configured, try Running Any Command Line exe Remotely Using the Process Class[^].
Apps - Color Analyzer | Arctic | XKCD | Sound Meter | Speed Dial
-
i have already mentioned wmi is not an option.
If firewalls settings can be configured, try Running Any Command Line exe Remotely Using the Process Class[^]
Apps - Color Analyzer | Arctic | XKCD | Sound Meter | Speed Dial
-
can psexec work for machines not in domain.
-
I want to run a command in remote computer command prompt and fetch command output of the remote computer and save the output in local system. i don't want to use WMI for this as wmi is not enabled in the remote computer.
Do you think of a tool similar to Java's Web Start used by e.g. Continuous Integration tools like Hudson and Jenkins? Well, I do not know of such a component in the .Net world...
-
Do you think of a tool similar to Java's Web Start used by e.g. Continuous Integration tools like Hudson and Jenkins? Well, I do not know of such a component in the .Net world...
can i execute command in a windows box remotely over internet and get its output provided i have full details of credential required to connect to the remote machine. Through PSexec i am able excute command in remote machine in the LAN /intranet and get output in my local machine in a text file but will it be possible to get the same details if the remote machine is connected in Internet.
-
can i execute command in a windows box remotely over internet and get its output provided i have full details of credential required to connect to the remote machine. Through PSexec i am able excute command in remote machine in the LAN /intranet and get output in my local machine in a text file but will it be possible to get the same details if the remote machine is connected in Internet.
Assuming you have the credentials and legal approval then the pc must be directly connected to the internet, meaning it must have an ip directly on the internet, or have port forwarding enabled on the router it sits behind. Normally you are not going to find pc's directly attached to the internet. Best practice is a firewall in between, which means you need to manually set up port forwarding at the pc's location.
-
I want to run a command in remote computer command prompt and fetch command output of the remote computer and save the output in local system. i don't want to use WMI for this as wmi is not enabled in the remote computer.
Lets start with the basics first. To execute a 'command' on a remote machine then the remote machine MUST have a server application running which will execute those commands. (Note that starting an application is also considered executing a command so you cannot expect to remotely start the application.) And that server application MUST be remotely accessible. That is an absolute. There is no other possibility. There are many applications that can do this - including writing your own. The FIRST step to implementing a solution is to determine what that server application will be. Because that will determine what the client application can do and what it can't do.