I created a batch file ‘nvspbind.cmd’ with the exact contents that you posted, only modified for my target computer’s network connections, which does not include a wireless connection. On my target computer I used the GUI to set my the binding order out of sequence (1,3,2,4).
Contents of my ‘nvspbind.cmd’:
nvspbind /++ "Local Area Connection 4" ms_tcpip
nvspbind /++ "Local Area Connection 3" ms_tcpip
nvspbind /++ "Local Area Connection 2" ms_tcpip
nvspbind /++ "Local Area Connection" ms_tcpip
I then put a copy of nvspbind.exe in C:Windows on the target computer.
I then executed a BatchPatch deployment (using the same method as described here, but instead of deploying a .MSU I deployed the .cmd remotely-deploy-a-standalone-msu-update-to-multiple-computers ) to deploy nvspbind.cmd to the target computer. It ran successfully with Exit Code 0. I then verified in the GUI on the target computer that the bindings had been re-ordered successfully.
Another option that also works is if you don’t want to put a copy of nvspbind.exe on the target computers, instead you can put it in the same directory as your nvspbind.cmd file with just those two files (nvspbind.cmd and nvspbind.exe) in that directory. Then in your deployment settings you’ll still deploy the .cmd file, but then you’ll also tick the box that says ‘Copy entire directory…’ so that both the .cmd and the .exe get copied to the target. Then the batch file is executed, and the files are removed from the target after completion.
All that said, I don’t see any reason why you should not be able to do exactly what I just did.
-Doug