How to copy a file to remote machine(system is server 2003) using WMI

Question

1.00/5 (2 votes)

See more:

hi I want to copy my file to a remote machine which system is win server 2003 using WMI, but I don't know the exact code.

note: I have try to use the method, File.copy, but I am failed, because the remote machine need username and password, but in this method have no such information.

Please help me, and I don't need the MSDN, but some exact code or other idea all welcome.

--thank you

Posted 24-Mar-12 16:37pm

dirk.zhang

Add a Solution

Comments

[no name] 24-Mar-12 22:47pm

So you won't do any research but want us to write the code for you?

dirk.zhang 24-Mar-12 23:46pm

...Definite no, just I have many resource except some precise pseudocode and idea

3 solutions

Solution 1

WMI tasks for files and folders change file or folder properties through WMI, including creating a share or renaming a file. If you want to copy a file or read and write a file, the easiest way is to use the Windows Script Host FileSystemObject rather than WMI. For other examples, see the Files and Folders section of the TechNet ScriptCenter.

Posted 24-Mar-12 16:53pm

Wes Aday

Solution 2

Look at PowerShell. In verion 2 there is apparently cross computer capabilities. Can also do WMI from Powershell.

Posted 24-Mar-12 17:28pm

Clifford Nelson

Comments

dirk.zhang 27-Mar-12 22:45pm

can you give me more information about PowerShell, I want to learn it more

Clifford Nelson 28-Mar-12 3:56am

I used it in version 1. You would be surprised at how easy it is to use in place of cmd prompt. There are aliases for the dos commands so you can use them, then they have pipes, and work with objects, so that much more flexible. Can also easily add using C# or VB. PowerShell 2 added cross platform capability, which I have not used. One of the early Powershell books spent a fair amount of time on WMI, but you basically use the same commands as for WMI in DOS prompt. Many of the newer MS tools are actually built on PowerShell, so that you no longer have to do everything through a GUI. Books out there, look at them.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

dirk.zhang · Accepted Answer · 2012-03-27T16:44:00

Solution 3

I give up WMI, and use the method of ".net user" in C# to solve the problem.

Posted 27-Mar-12 16:44pm

dirk.zhang