\nFor this scenario we have a large file transfer that is occurring, one that was kicked off with Start-BitsTransfer. It is a large transfer as well. Because the file being ‘transferred’ is large, we can use the Get-BitsTransfer cmdlet to review it’s progress:
\n[sourcecode language=”powershell”]
\nGet-BitsTransfer
\n[\/sourcecode]
\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2020\/12\/Other-BitsTransfer-01.jpg?ssl=1\"){kind=spacer}
<\/a>\n[sourcecode language=”powershell”]
\nGet-BitsTransfer | Fl
\n[\/sourcecode]
\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2020\/12\/Other-BitsTransfer-02.jpg?ssl=1\"){kind=spacer}
<\/a>\nNow, remember that the transfer is occurring in the other PowerShell Window. When we suspend the transfer, we can seee the suspension in both Windows:
\n(Initiated Shell)
\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2020\/12\/Other-BitsTransfer-03.jpg?ssl=1\"){kind=spacer}
<\/a>\n(Shell where the transfer was suspended)
\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2020\/12\/Other-BitsTransfer-04.jpg?ssl=1\"){kind=spacer}
<\/a>\n
** NOTE ** If managing a large amount of Bits Transfers is necessary, it might be a good practice to provide a good Display Name to help differentiate between each transfer being managed. The file or files being downloaded are not listed when running the Get-BitsTransfer cmdlet.<\/em>
\nFrom here we can decided to Resume the Bits Transfer or remove the Bits Transfer as well. Once suspended, we can deterine the next action for the Bits Transfer, like Resume, Complete and Remove. If we decide the fileis no longer needed, we can use the Remove-BitsTransfer cmdlet like so:
\n[sourcecode language=”powershell”]
\n$BitsJob = Get-BitsTransfer -Name 'Bits Transfer'
\nRemove-BitsTransfer -BitsJob $BitsJob
\n[\/sourcecode]
\nWhich shows no feedback when run:
\n
<\/a>\nIf we want to cancel all jobs, we can run this:
\n[sourcecode language=”powershell”]
\nGet-BitsTransfer | Remove-BitsTransfer
\n[\/sourcecode]
\nIf we want to either Resume or Complete the transfer, we can do this:
\n[sourcecode language=”powershell”]
\n$BitsJob = Get-BitsTransfer -Name 'Bits Transfer'
\nResume-BitsTransfer -BitsJob $BitsJob
\n[\/sourcecode]
\nOR
\n[sourcecode language=”powershell”]
\n$BitsJob = Get-BitsTransfer -Name 'Bits Transfer'
\nComplete-BitsTransfer -BitsJob $BitsJob
\n[\/sourcecode]
\nThen the job will run to completion and your files can be accessed.<\/p>\n
Additional Options<\/h3>\n
When creating a job, we have other options:
\nAsynchronous: Runs the job in the background and the PowerShell command prompt is available again.
\nAuthentication: Specify an authentication type for the Source [Basic, Digest, NTLM, Negotiate or Passport]
\nCredential: Used to authenticate to a source that requires credentials
\nDescription: Helpful information for us to determine what the job is for.
\nDisplayName: A name we can use to visually distinguish between jobs.
\nProxy Parameters: Allows us to use a Proxy to download files in case one is in place.
\n\tProxyAuthentication, ProxyBypass, ProxyCredential, ProxyList and ProxyUsage
\nRetryInterval: When a job is retried if a connection is not made. Minimum value is 60 seconds, default is 600
\nRetryTimeout: If the job is not completed in this time, then job will fail. Default is 14 days.
\nTransferPolicy: Used if there needs to be a cost assigned to the download due to congestion, data caps, etc.
\n\tAccepted Values: None, Unrestricted, Capped, BelowCap, NearCap, OverCapCharged, OverCapThrottled, UsageBased, Roaming, IgnoreCongestion, PolicyUnrestricted, Standard, NoSurcharge, NotRoaming, Always
\nTransferType: Specify the type of download whether it is a download, upload or a uploadreply:
\n\tDownload (the default): File is being downloaded
\n\tUpload: Job is uploading a file to a server
\n\tUploadReply: Job will upload a file and download a reply file
\nUseStoredCredential: Only use this if Proxy Credentials are needed, and then specify Proxy as the value for this parameter. If Proxy is used, then the ProxyCredential parameter must also be used.<\/p>\n
CONCLUSION<\/h3>\n
As we can see, the Bits Transfer cmdlets provide some interesting capabilities. As a script author, I have used this script for downloading files needed to perform certain tasks. These tasks range from a Prerequisite installer script, to a health script to a script that downloaded needed files or moved needed files to a desired location. Bits Transfer makes this easy to manage and handle multiple source and destination targets.<\/p>\n
FURTHER READING<\/h3>\n
I cover this and many more topics in this book:<\/p>\n