1) Yes
2) No
You will need to either mount the USB drive so that it can be accessed using the same Destination string (path, etc), or change the Destination path (etc) to point at it in its new location/mounting. Sounds like you'd need to use a drive letter to start with, then a UNC path that represents how it is mounted/shared remotely.
Note that we occasionally get reports of issues whereby using a UNC path to point to a share that is actually a USB drive 'hanging off' a remote server can be problematic (drive 'flickering', etc). But others seem to use that method OK, so you'll need to try it and see. Nothing we can do if it's not do-able for you, sorry (except to suggest maybe try mounting the bare drive from the USB enclosure as an extra disk inside Server-B case)
2) No
You will need to either mount the USB drive so that it can be accessed using the same Destination string (path, etc), or change the Destination path (etc) to point at it in its new location/mounting. Sounds like you'd need to use a drive letter to start with, then a UNC path that represents how it is mounted/shared remotely.
Note that we occasionally get reports of issues whereby using a UNC path to point to a share that is actually a USB drive 'hanging off' a remote server can be problematic (drive 'flickering', etc). But others seem to use that method OK, so you'll need to try it and see. Nothing we can do if it's not do-able for you, sorry (except to suggest maybe try mounting the bare drive from the USB enclosure as an extra disk inside Server-B case)