Advertisement
Guest User

Remote Parsec Launch

a guest
Mar 2nd, 2018
243
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Batch 2.53 KB | None | 0 0
  1. Until proper support is implemented, here is a workaround. This only works reliably if you are on the same network as the computer you are connecting to. I've had mixed results when leaving the local network so I won't post instructions to do so here. Google is your friend.
  2.  
  3. 1. Download SysInternal's PsExec from http://live.sysinternals.com/tools/psexec.exe and place it in your C:\Windows\System32 folder. Do this for all clients. It's not necessary to store in this folder, but it lets us run psexec without including the path to it.
  4. 2. Open Notepad, click File > Save As, set Save as type to "All Files (*.*)". Name it the app you want to launch on the remote system with the file extension .cmd. So for example, Dota 2.cmd
  5. 3. Copy paste this code below into your notepad, replace any values surrounded by < > and then File > Save.
  6.  
  7. ======================================================================================
  8.  
  9. Echo off
  10. cls
  11.  
  12. Set Computer=<Your Computer Name/IP>
  13. Set User=<Remote Username>
  14. Set Pass=<Remote Password>
  15. Set LaunchExe=<Your launch parameters>
  16. Set PsExecPath=C:\Windows\System32
  17. Set ParsecPath=%AppData%\Parsec\electron
  18. Set ParsecID=<Your Parsec Server ID>
  19.  
  20. %PsExecPath%\psexec \\%Computer% -u %User% -p %Pass% cmd /c start "" %LaunchExe%
  21. start "" %ParsecPath%\parsec.exe server_id=%ParsecID%
  22.  
  23. ======================================================================================
  24.  
  25. 4. Double click on the file you just saved and it will remotely launch your LaunchExe and connect to your remote computer via Parsec.
  26.  
  27. Use this template to create as many game launchers as you need, for as many computers as you need.
  28.  
  29. Notes:
  30. The Computer name can be found by pressing the Windows key and the Pause key together. The IP address can be found by using command prompt on the remote computer and typing "ipconfig" and finding your ethernet's IPv4 Address.
  31. The User and Pass should be for the currently logged in user on the remote computer.
  32. The LaunchExe is the path to the exe on the remote server, not the computer you are connecting from.
  33. The LaunchExe can be either a file path or a URI. For example, "C:\Program Files (x86)\Steam\Steam.exe -applaunch 570" and "Steam://run/570" are both valid.
  34. The LaunchExe may need to be surrounded by quotes if there is a space in the path.
  35. The ParsecID can be found by following the instructions at https://support.parsecgaming.com/hc/en-us/articles/115003035491-Finding-Your-Server-ID
  36. The PsExecPath and ParsecPath are set to their default paths. Change if you installed in a different location.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement