Sr. IT Engineer

Gerwin Jansen

SAM2009

The More I know, the more I don't know

David Johnson, CD

<div>
What is weird is the Move-Item cmd with -force doesn't work in pipeline.<br><br><br>
</div>


What is weird is the Move-Item cmd with -force doesn't work in pipeline.




<div>
where are you adding the -force -destination ... as the first argument?
</div>


where are you adding the -force -destination ... as the first argument?

<div>
Like this:<br><br>Get-ChildItem -Path I:\IT-UsersToDisable -File | Move-Item -Destination I:\IT-UsersToDisable\OLD<strong>&nbsp;-Force</strong>
</div>


Like this:

Get-ChildItem -Path I:\IT-UsersToDisable -File | Move-Item -Destination I:\IT-UsersToDisable\OLD -Force

<div>
Did this work, or did not work?<br />
If did not, does including it at the begining change the behavior?<br />
Or in this case you have to pass foreach-item and then run move-item one at a time?
</div>


Did this work, or did not work?
If did not, does including it at the begining change the behavior?
Or in this case you have to pass foreach-item and then run move-item one at a time?

<div>
OLD is a folder, I assume?<br>The command should work. To make sure, I even tried with read-only files in both locations - no issue.<br>There might be an issue with system files or files with a particular security setting on files or folders.<br><br>BTW, the sequence of (named) options does not matter. The sequence of unnamed parameters does, of course ;-).
</div>


OLD is a folder, I assume?
The command should work. To make sure, I even tried with read-only files in both locations - no issue.
There might be an issue with system files or files with a particular security setting on files or folders.

BTW, the sequence of (named) options does not matter. The sequence of unnamed parameters does, of course ;-).

<div>
Does it work like in my suggested cmd? Like with <strong>Get-ChildItem</strong> first and add the end: "| Move-Item...-Force"?
</div>


Does it work like in my suggested cmd? Like with Get-ChildItem first and add the end: "| Move-Item...-Force"?

<div>
Yes. &nbsp;My test was something like<br><pre><code class="code-1 nolinks" id="code-20-43362526-1">gci *.txt | move-item -force -Destination Old &nbsp;&nbsp;</code></pre>
</div>


Yes.  My test was something like


gci *.txt | move-item -force -Destination Old   

<div>
Look what the get-childitem outputs <br />
<br />
I do not think you need to specify what is being moved when it is fed over pipe, is the issue where -force is added, at the beginig as the first argument or after the last.<br />
Are there spaces in the file names.
</div>


Look what the get-childitem outputs

I do not think you need to specify what is being moved when it is fed over pipe, is the issue where -force is added, at the beginig as the first argument or after the last.
Are there spaces in the file names.

<div>
Thank you. Finally after comparing files I realize there a NTFS security issue. Thanks for yoir help.
</div>


Thank you. Finally after comparing files I realize there a NTFS security issue. Thanks for yoir help.

<div>
<div class="content wysiwyg-content fr-view">
<p>Hi,</p><p><br></p><p>I use this PS cmd:</p><p><br></p><p>Get-ChildItem -Path I:\IT-UsersToDisable -File | Move-Item -Destination I:\IT-UsersToDisable\OLD</p><p><br></p><p>But got this error msg:<br id="isPasted">Move-Item : Cannot create a file when that file already exists.<br><br>I realized that file: users.csv is already existed in "E:\IT-UsersToDisable\OLD"<br><br>How can I force it to just move and overwrite it?</p>
</div>
</div>



Hi,
I use this PS cmd:
Get-ChildItem -Path I:\IT-UsersToDisable -File | Move-Item -Destination I:\IT-UsersToDisable\OLD
But got this error msg:
Move-Item : Cannot create a file when that file already exists.
I realized that file: users.csv is already existed in "E:\IT-UsersToDisable\OLD"
How can I force it to just move and overwrite it?

PS: Move-Item. How to force to overwrite an existing file?

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

A scripting language is a programming language that supports scripts, programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator. Scripting languages are often interpreted (rather than compiled). Primitives are usually the elementary tasks or API calls, and the language allows them to be combined into more complex programs. Environments that can be automated through scripting include software applications, web pages within a web browser, the shells of operating systems (OS), embedded systems, as well as numerous games. A scripting language can be viewed as a domain-specific language for a particular environment; in the case of scripting an application, this is also known as an extension language.

Scripting Languages

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.