Skip to main content

List Directories Using robocopy

Robocopy command below will lists directories and subdirectories on the path specified.

It will lists folders and sub folders regardless whether the file path is too long.

Path can be a network path or a path on a local drive.

But Robocopy should be present on the system, for Windows 7 and Windows 8 users it should be included already.

For previous versions of Windows or for whatever reason that Robocopy is not on your system.

Download Robocopy on this link below:
http://www.microsoft.com/en-sg/download/details.aspx?id=17657

It's a resource kit for Windows 2003, and it includes Robocopy tool.

Robocopy command lists directories and subdirectories on the given path:

Robocopy /L /E "c:\MyFiles\Project_Notes" null *.* /log:d:\FolderList.txt

Robocopy  /L /E "\\ServerProj\SharedFolder\LongUserFolders" null *.* /log:d:\NetworkFolderList.txt


Robocopy  Source   Destination   Files to copy or use wildcards (*.*)

  /L :: List only - don't copy, timestamp or delete any files
  /E :: copy subdirectories, including Empty ones.

Check out this link for Robocopy syntax on Technet site:
http://technet.microsoft.com/en-us/library/cc733145.aspx

Syntax can also be shown on the command prompt, type: robocopy /?

In copying source and destination should not be interchanged, or else it will be a disaster.

Null - means basically means empty or nothing. It will discard  all data send to null.

In order not to waste space on the drive, send the copy to null.


To check folders which has long path or exceeds 260 characters from the text file log.

Let PowerShell do the task in getting the folder length and create a file which lists the folder path which exceeds 260 characters.

The text file created by PowerShell will only contain paths that are too long.

Paths that are not long will not be included on the lists.

Here's the PowerShell code to check paths that are too long:

=====================================
$pathToFile = "d:\NetworkFolderList.txt"
 

$xLines = Get-Content $pathToFile

ForEach ($Line In $xLines)

{

$xLength = $Line.Length
#write-host $xLength

   If ($xLength -eq 260)

    {

    #$Line is the folder path
    #$xLength is the length of the path
    $Line, $xLength | out-file -append d:\xpathLine.txt

    }

 }

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

Output will look like this:
\\NetworkPath\Folders\ThatareTooLong
270
\\NetworkPath\Folders01\SubFolders\ThatareTooLong
290

The number below the path will correspond to the length above the path.

Cheers..Hope it helps..

click labels below for more PowerShell on this blog...

================================
Linux Android App cheat sheet:
https://play.google.com/store/apps/details?id=com.LinuxMobileKit

Free Android App with No Ads.

Heaven's Dew Fall
https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer


Android Catholic Rosary App - Guide


Educational App for Android Kids:

https://play.google.com/store/apps/details?id=com.letsmultiply

Android Divine Mercy Chaplet Guide  
https://play.google.com/store/apps/details?id=com.dmercyapp 

Comments

  1. hello
    you can use long path tool.

    ReplyDelete
    Replies
    1. hi getlinkz pit, thanks for the comment..yes long path tool can do the job also.. above method is just a simple script without any third party tools..

      Delete
    2. yeah Longpathtool can be used here..

      Delete
  2. Long path tool is very popular software! When cleaning files from a Windows Operating System (OS), you are halted with errors relating to the filename or the file path being too long.
    This is due to a 255/260 character limit on Windows Operating Systems preventing the files in a directory from being removed.
    You can used Long path tool?

    ReplyDelete

Post a Comment

Popular posts from this blog

Notepad++ convert multiple lines to a single line and vice versa

Notepad++ is an awesome text editing tool, it can accept regex to process the text data. If the data is in a “.csv” format or comma separated values which is basically just a text file that can either be opened using a text editor, excel or even word. Notepad++ can process the contents of the file using regex. Example if the data has multiple rows or lines, and what is needed is to convert the whole lines of data into a single line. Notepad++ can easily do it using regex. However, if the data is on a single line and it needs to be converted into multiple lines or rows then regex can also be used for this case. Here’s an example on how to convert multiple rows or lines into a single line. Example data: Multiple rows, just a sample data. Press Ctrl+H, and  on "Find what" type: [\r\n]+ and on "Replace with" type with: , (white space) --white space is needed if need to have a space in between the data. See image below, "Regular Expression" must be se

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

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 Outpu