even if you did connect to "\\b\wherever\script.vbs", and execute the file, it would still execute on cpu A, after dragging off the disk shared by B.
The only method I know of to get CPU B, to execute the script is to put waders on and get inside the windows internals, you'll need to...