powershell script to get the file size of files in multiple locations

You can run a simple PowerShell script to get the file size of files saved in various locations on a network.

Get-Childitem -file "C:\foofolder\2022.05.31 Fedex Ground.pdf" | select length

Get-Childitem -file "C:\foofolder\Citation\test\XYZ 000400.pdf" | select length

Get-Childitem -file "U:\O'Shea Documents\personal\port st. lucie.heic" | select length

Simply enter the file path in one column of an Excel spreadsheet, with the Get-Childitem -file command in the column to the left, and the | select length operator in the column to the right. Copy the three columns to NotePad and remove the tabs. Enter the script in Windows PowerShell ISE:

It will output the number of bytes in each file. [1924588 equals 1.9 MB]. You can copy the file sizes back into the Excel spreadsheet so they line up with file paths:

Recently, I used this script to get the length of hundreds of Excel files linked to on a spreadsheet for a trial exhibit list that were saved in dozens of different directories, when requested to find if a file was saved on the list under a different Bates number. The closest in size file proved to be a match.

checking for bad sectors with chkdsk

If you want to find out if a drive on a device running Windows has any bad sectors that you will not be able to copy files from, or copy files to, you can run the chkdsk command. chkdsk will locate bad sectors, and can also be used to fix errors in the file system. If you enter: chkdsk /r in Command Prompt, the system will locate bad sectors, and try to recover data from them.

chkdsk will generate a list of how many files are on a drive, and how many sectors are bad.

If you search in Windows for 'Event Viewer', and open it, in the Windows Logs folder you'll see the application log. Searching for 'chkdsk' in this log will find the results of any past chkdsk reviews run on the system.

Right click on the entries in the Application pane in which this search finds hits, and you'll be able to copy out the information to NotePad.

Zoom CRC - Connecting a Cisco or Polycom Video Conferencing System to a Zoom Meeting

When you get a Zoom invite you’ll see a long list of possible ways to get connected - in addition to the url on the host network, there will be a long list of numbers for different area codes and toll free numbers. Towards the end of the invite you should see a reference to an option to join by SIP, session initiation protocol - a 10 or 9 digit number, which matches the Meeting ID, followed by the @zoomcrc.com domain.

Zoom Conference Room Connector, or Cloud Room Connector, allows a Zoom meeting run on a desktop or smartphone to connect with the Cisco, LifeSize, and Polycom video conferencing systems, or anyone with SIP or H.323 VoIP communication protocols.

If you start a Zoom meeting on a laptop, you can connect to the meeting with a Cisco or Polycom system. An example of a videoconferencing system which is compatible with Zoom are the Polycom Group series systems:

Another example are the Cisco Tandberg TelePresence systems:

To enter the Zoom meeting from the video conferencing system you would enter the @zoomcrc.com address on a panel like this:

You may also be prompted for the meeting passcode.

For each CRC connection there will be a monthly fee of $49.