Skip to main content

PowerShell move files and change file name




PowerShell can easily move files to another folder.

Ever want to move files and change the filename or add date tags to the filename?

Well, it can be done automatically or manually.

Choice is always at the hands of the person doing the task.

Manual task is always practical if it is just a few numbers of files.

But if the task is repetitive or the files range from hundred to thousand, manual task could be daunting or probably not an option.

If the task is repetitive, automation should be a good if it not a best option.

If numbers of files are quite large automation is good as well, it saves time and effort.

PowerShell is always a friend when it comes to automation and saving time.

Here's the PowerShell code to move files without hassle.

This code below moves a single file to the folder location specified.

=======================
#Get the current date

$xdate = Get-Date -UFormat "%Y-%b-%d-%A"



#Write-Output $xdate



#specify the filename, date and filename extension

$str = "linuxrh_copy_" + $xdate + ".txt"





#write-output $str



#move the file to the specified folder location

Move-Item d:\linuxrh.txt D:\xlinux\$str

=======================

Why create a script when there is only one file to move?

Of course there is not much joy, if it is only one file.

But the script could come handy, if it the task has to be done on a daily basis or an interval of hour.

Just set a task scheduler and forget about it.

Well, if there is a need to move a hundred of files or more here's the PowerShell script:

=======================
 
$xdate = Get-Date -UFormat "%Y-%b-%d-%A"



$source_path = "D:\logs\"

$xbasename = Get-ChildItem $source_path -Name



$destination_path="D:\move_logs\"



#write-output $xbasename





ForEach ($xdata in $xbasename) {



#get the filename only

$xreplace = $xdata -replace '.txt','_'





#add the filename, date and filename extension

$final_filename = $xreplace + $xdate  + ".txt"





#write-output $destination_path$final_filename

#write-output $source_path$xdata $destination_path$final_filename



#do the action move the files

Move-Item $source_path$xdata $destination_path$final_filename



}

=======================


Cheers.. Hope it helps..


----------------------------------
Free Android app, download at Google play:
Android Divine Mercy Chaplet Guide  
https://play.google.com/store/apps/details?id=com.dmercyapp 

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more