{"id":52093,"date":"2009-11-04T00:01:00","date_gmt":"2009-11-04T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2009\/11\/04\/hey-scripting-guy-can-i-format-a-portable-drive-when-it-is-inserted-into-a-computer\/"},"modified":"2009-11-04T00:01:00","modified_gmt":"2009-11-04T00:01:00","slug":"hey-scripting-guy-can-i-format-a-portable-drive-when-it-is-inserted-into-a-computer","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-can-i-format-a-portable-drive-when-it-is-inserted-into-a-computer\/","title":{"rendered":"Hey, Scripting Guy! Can I Format a Portable Drive When It Is Inserted Into a Computer?"},"content":{"rendered":"

\"Bookmark<\/a><\/p>\n

 <\/p>\n

\"Hey,<\/font><\/p>\n

Hey, Scripting Guy! I work with portable USB drives all the time. These are used for backup purposes, for temporary storage, for Sneakernet<\/font><\/a>, and as a means to work with extremely large files that I do not want cluttering up the small hard disk drive on my corporate standard desktop. The problem is that I now have more than a dozen portable USB drives, some of which are continually connected, and others that I shuttle in and out of my computer on an hourly basis to transfer files from one computer to another. (Our IT department has disabled file sharing on our computers, and therefore I cannot simply copy one file from one computer to another. In addition, all file attachments get stripped out of e-mail and so I cannot use e-mail to transfer files either. I am therefore left with sneaker net.) <\/p>\n

The problem is that, once I have used a portable drive to transfer a file from one computer to another, I do not always delete the file to clean up the drive. As a result some of these drives tend to fill up with useless information. Here is what I currently do: I plug the portable USB drive into my computer, and then navigate to the drive in Windows Explorer to check for files on the drive. If the drive has files, I do a quick format to clean it up. I would love to automate this process. Do you know of a script that will automatically format a portable drive when it is inserted into a computer?<\/p>\n

— JM<\/p>\n

\"Hey,Hello JM, Microsoft Scripting Guy Ed Wilson here. Well this afternoon, the Scripting Wife made me a nice pot of Earl Grey tea<\/font><\/a> in my little blue tea pot, and even shared one of her Tim Tams<\/a> with me. I guess she is still excited about her new flat panel monitor for her Windows 7 Ultimate computer. I am listening to “Zapatos de Tacon Alto” (High-Heeled Shoes) by Jose Feliciano on my Zune. I bought the CD-ROM a couple years ago while I was teaching a VBScript class in Monterrey, Mexico. Anyway, I am reviewing the e-mail in the scripter@microsoft.com<\/font><\/span><\/a> mail box (we receive several hundred e-mails a week to this alias, and it takes a decent amount of time to go through them all). All in all, it is a terrific afternoon in Charlotte, North Carolina, in the United States—a fine scripting day! <\/p>\n

JM, I wrote the MonitorDiskFormatDrive.ps1 script for you. It will detect when a new drive has been added to your system. After the new drive has initialized, the contents of the drive are displayed on your Windows PowerShell console. If there are any files on the portable drive, you will be prompted to format the drive. If no files exist on the drive, it will automatically be formatted. The complete MonitorDiskFormatDrive.ps1 script is seen here. <\/p>\n

MonitorDiskFormatDrive.ps1<\/strong><\/p>\n

#Requires -version 2.0<\/p>\n

function Test-IsAdministrator
{
    <\/span><#
    <\/span>.Synopsis
        <\/span>Tests if the user is an administrator
    <\/span>.Description
        <\/span>Returns true if a user is an administrator, false if the user is not an administrator        <\/span>
    <\/span>.Example
        <\/span>Test-IsAdministrator
    <\/span>#>   <\/span>
    <\/span>param()
    <\/span>$currentUser = [Security.Principal.WindowsIdentity]::GetCurrent()
    <\/span>(New-Object Security.Principal.WindowsPrincipal $currentUser).IsInRole([Security.Principal.WindowsBuiltinRole]::Administrator)
} #end function Test-IsAdministrator
 <\/span>
Function Get-IsWindowsXP
 <\/span>{
   <\/span>if( (Get-WmiObject -Class win32_operatingsystem).version  <\/span>-gt “6.1.2600” )
     <\/span>{ $false }
   <\/span>else { $true }
 <\/span>} #end function Get-IsWindowsXP<\/p>\n

Function Get-DriveEvent
 <\/span>{
  <\/span>Register-WmiEvent -Class win32_VolumeChangeEvent -SourceIdentifier volumeChange
  <\/span>$newEvent = Wait-Event -SourceIdentifier volumeChange
  <\/span>Get-DriveContents -path $newEvent.SourceEventArgs.NewEvent.DriveName
 <\/span>} #end function Get-DriveEvent <\/p>\n

Function Get-DriveContents ($path)
 <\/span>{
  <\/span>If( (Get-ChildItem -Path $path).count -gt 0)
    <\/span>{  <\/span>
      <\/span>Get-ChildItem -Path $path
     <\/span>$in = Read-Host -Prompt “Drive contains files. Format anyway? y \/ n”
 <\/span>    <\/span>if ($in -match “y”) { Set-DriveFormat -path $path }
     <\/span>if ($in -match “n”) { “Drive will not be formatted. Exiting” ; exit }
    <\/span>}
   <\/span>Else { Set-DriveFormat -path $path }<\/p>\n

 <\/span>} #end function Get-DriveContents
 <\/span>
Function Set-DriveFormat($path)
 <\/span>{
  <\/span>“Formatting drive $path this can take some time …”
  <\/span>$drive = Get-WmiObject -Class win32_volume -Filter “DriveLetter = ‘$path'”
  <\/span>$drive.Format(“FAT32″,$true,4096,”testFormat”,$false)
 <\/span>} #end function Set-DriveFormat
 <\/span>
# *** Entry Point to Script ***
if( -not (Test-IsAdministrator)) { “This script requires admin rights.” ; exit }
if(Get-IsWindowsXP) { “This script requires Windows Server 2003 or newer.” ; exit }
“Watching for new Drive …”
Get-DriveEvent<\/p>\n

<\/font><\/font><\/span><\/p>\n

If you want to format a disk drive, it requires administrator rights. There is no point in running the MonitorDiskFormatDrive.ps1 script if the user does not have administrator rights. To check for these rights, use a function I wrote for the Windows 7 Resource Kit<\/font><\/a> called Test-IsAdministrator<\/b>. The Test-IsAdministrator<\/b> function uses the GetCurrent static method<\/font><\/a> from the Security.Principal.WindowsIdentity<\/font><\/a> .NET Framework class to determine the current user. After the current user identity is established, the IsInRole method<\/font><\/a> from the Security.Principal.WindowsPrincipal<\/font><\/a> .NET Framework class is used to determine if the current user is an administrator. The Test-IsAdministrator<\/b> function is seen here:<\/p>\n

function Test-IsAdministrator
{
    <\/span><#
    <\/span>.Synopsis
        <\/span>Tests if the user is an administrator
    <\/span>.Description
        <\/span>Returns true if a user is an administrator, false if the user is not an administrator        <\/span>
    <\/span>.Example
        <\/span>Test-IsAdministrator
    <\/span>#>   <\/span>
    <\/span>param()
    <\/span>$currentUser = [Security.Principal.WindowsIdentity]::GetCurrent()
    <\/span>(New-Object Security.Principal.WindowsPrincipal $currentUser).IsInRole([Security.Principal.WindowsBuiltinRole]::Administrator)
} #end function Test-IsAdministrator<\/p>\n

<\/font><\/span><\/p>\n

Because the MonitorDiskFormatDrive.ps1 script relies on the Win32_Volume<\/b> WMI class, the first thing the script does is to determine the version of the operating system (OS) the script is running on. This is because the Win32_Volume<\/b> WMI class does not exist on Windows XP. The OS check is performed in the Get-IsWindowsXP<\/b> function. The Win32_OperatingSystem<\/b> WMI class is used to determine the version of the OS. If the version of the OS is higher than 6.1.2600 (which was the OS version of Windows XP), the script returns false<\/b> to the calling code. If the version of the OS is not greater than 6.1.2600, the function returns true<\/b> to the calling code. The complete Get-IsWindowsXP<\/b> function is seen here:<\/p>\n

Function Get-IsWindowsXP
 <\/span>{
   <\/span>if( (Get-WmiObject -Class win32_operatingsystem).version  <\/span>-gt “6.1.2600” )
     <\/span>{ $false }
   <\/span>else { $true }
 <\/span>} #end function Get-IsWindowsXP<\/p>\n

<\/font><\/span><\/p>\n

The Get-DriveEvent<\/b> function is used to create the WMI event that will monitor for a volume change. To do this, the Win32_VolumeChangeEvent<\/a> WMI class is used. This WMI class is designed to detect when a volume change event occurs. The event could be a new drive or a drive that was removed from the system. Because of the way the MonitorDiskFormatDrive.ps1 script will be used, it is safe to assume the volume change event that will occur will be a drive-added event. The Register-WmiEvent<\/b> Windows PowerShell cmdlet is used to create the WMI event. The Wait-Event<\/b> Windows PowerShell cmdlet will pause the Windows PowerShell console until an event occurs. This is great for halting the execution of your script when you know that something is about to occur, such as if you are getting ready to insert a USB drive into your computer. When the event occurs, the script will continue and will retrieve the DriveName<\/b> property from the instance of the Win32_VolumeChangeEvent<\/b> WMI class. This is important because when a removable drive is added to my system, a drive letter is assigned to it. The letter is not always the next available drive letter, nor is it always the same drive letter. This is seen here: <\/p>\n

\"Image<\/p>\n


The complete Get-DriveEvent<\/b> function is seen here:<\/p>\n

Function Get-DriveEvent<\/p>\n

<\/font><\/span><\/p>\n

 <\/span>{<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>Register-WmiEvent -Class win32_VolumeChangeEvent -SourceIdentifier volumeChange<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>$newEvent = Wait-Event -SourceIdentifier volumeChange<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>Get-DriveContents -path $newEvent.SourceEventArgs.NewEvent.DriveName <\/p>\n

<\/font><\/span><\/p>\n

 <\/span>} #end function Get-DriveEvent<\/p>\n

<\/font><\/span><\/p>\n

The Get-DriveContents<\/b> cmdlet uses the Get-ChildItem<\/b> Windows PowerShell cmdlet to retrieve the contents of the newly added drive. If the drive has files (in other words, if the count is greater than zero), the Read-Host<\/b> cmdlet is used to prompt the user for permission to format the drive. If the user types “y”, the Set-DriveFormat<\/b> function is called. If the user types “n”, the script exits without making any changes. If the drive contains no files, the Set-DriveFormat<\/b> function is called and the drive is formatted. The Get-DriveContents<\/b> function is seen here:<\/p>\n

Function Get-DriveContents ($path)<\/p>\n

<\/font><\/span><\/p>\n

 <\/span>{<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>If( (Get-ChildItem -Path $path).count -gt 0) <\/p>\n

<\/font><\/span><\/p>\n

    <\/span>{  <\/span><\/p>\n

<\/font><\/span><\/p>\n

      <\/span>Get-ChildItem -Path $path<\/p>\n

<\/font><\/span><\/p>\n

     <\/span>$in = Read-Host -Prompt “Drive contains files. Format anyway? y \/ n”<\/p>\n

<\/font><\/span><\/p>\n

     <\/span>if ($in -match “y”) { Set-DriveFormat -path $path }<\/p>\n

<\/font><\/span><\/p>\n

     <\/span>if ($in -match “n”) { “Drive will not be formatted. Exiting” ; exit }<\/p>\n

<\/font><\/span><\/p>\n

    <\/span>}<\/p>\n

<\/font><\/span><\/p>\n

   <\/span>Else { Set-DriveFormat -path $path }<\/p>\n

<\/font><\/span><\/p>\n

 <\/font><\/p>\n

<\/span><\/p>\n

 <\/span>} #end function Get-DriveContents<\/p>\n

<\/font><\/span><\/p>\n

The Set-DriveFormat<\/b> function uses the Win32_Volume<\/b> WMI class, which is documented on MSDN<\/font><\/a>. When the script is run, it must be run with administrator rights to format the drive. If it is not run with administrator rights, the script will display a message that indicates administrator rights are required. This is shown here:<\/p>\n

\"Image<\/p>\n


The complete Set-DriveFormat<\/b> function is seen here:<\/p>\n

Function Set-DriveFormat($path)<\/p>\n

<\/font><\/span><\/p>\n

 <\/span>{<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>“Formatting drive $path this can take some time …”<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>$drive = Get-WmiObject -Class win32_volume -Filter “DriveLetter = ‘$path'”<\/p>\n

<\/font><\/span><\/p>\n

  <\/span>$drive.Format(“FAT32″,$true,4096,”testFormat”,$false)<\/p>\n

<\/font><\/span><\/p>\n

 <\/span>} #end function Set-DriveFormat<\/p>\n

<\/font><\/span><\/p>\n

When the MonitorDiskFormatDrive.ps1 script is run, the script first uses the WMI event to monitor for a new drive event. When the drive event is detected, the drive letter is captured, and the contents of the drive are displayed. If contents are present on the drive, a prompt is used to ask if you wish to format the drive. If you type “y” for yes, the drive will be formatted. If you type “n” for no, the script will exit. If the drive is to be formatted, a message that states the drive is being formatted is displayed. The return code from the format method of the Win32_Volume<\/b> WMI class is displayed when the format job is complete. This is shown here:<\/p>\n

\"Image<\/p>\n

 <\/p>\n

JM, that is all there is to using a WMI event class to monitor for the insertion of a new drive on your computer. WMI Event Week will continue tomorrow when we will talk about… <\/p>\n

If you want to know exactly what we will be looking at tomorrow, follow us on Twitter<\/font><\/a> or Facebook<\/font><\/a>. If you have any questions, send e-mail to us at scripter@microsoft.com<\/font><\/a> or post them on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.
 <\/p>\n

Ed Wilson and Craig Liebendorfer, Scripting Guys<\/span><\/b><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

  Hey, Scripting Guy! I work with portable USB drives all the time. These are used for backup purposes, for temporary storage, for Sneakernet, and as a means to work with extremely large files that I do not want cluttering up the small hard disk drive on my corporate standard desktop. The problem is that […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[42,3,4,45,6],"class_list":["post-52093","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-events-and-monitoring","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

  Hey, Scripting Guy! I work with portable USB drives all the time. These are used for backup purposes, for temporary storage, for Sneakernet, and as a means to work with extremely large files that I do not want cluttering up the small hard disk drive on my corporate standard desktop. The problem is that […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52093","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=52093"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52093\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=52093"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=52093"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=52093"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}