Parsec has become a go-to remote desktop tool for game developers, 3D graphics artists, designers, and video editors. As more and more people access their office workstations through Parsec, companies have asked Parsec to develop administrative tools to add, revoke, and manage accounts with access to machines. Parsec for Teams is a new product from Parsec that gives organizations and administrators that level of control, so they can feel comfortable letting their team work from home on a low bandwidth, 60 FPS, UHD remote desktop tool that doesn't get in the way of their work.
You can download Parsec and try it on your computer at work before you buy it. The consumer version of Parsec is not licensed for commercial use, and it does not include key security features included in Parsec for Teams. That being said, you can use the consumer version for your personal testing to make sure Parsec will work for your setup before you subscribe.
Parsec for Teams is priced based on the number of accounts you have on your team. You set the total number of accounts and then invite people or remove people based on need. You can install Parsec for Teams on any number of computers, but you will always be charged based on the total accounts you subscribe to.
Your designated administrator should sign up for Parsec for Teams and choose the number of seats your company will need. Add a corporate credit card and save the details before creating your team.
Use the Parsec for Teams admin page to invite people through their email, and they will receive an email asking them to join. They need to sign in to Parsec and/or create an account with the exact email address you invited.
Once people join your team, on the Parsec for Teams admin page you can search for users based on email and click the three white dots next to their name to add them as an admin. Only the owner of the account (the original creator of the Team) can add people as admins, change seat count, and change billing details.
Once people join your team, on the Parsec for Teams admin page you can search for users based on email and click the three white dots next to their name to add tags. Any admin can do this.
It's simple. Just go back to the administrator panel and revoke their access. They will lose the ability to connect to the company's PCs. Any admin can do this.
Installing Parsec for Teams on your office workstations can be done via the installation GUI or command line.
If you're installing via the installation GUI, you need to install Parsec for Windows on the workstation and download and run the ParsecSetTeamID.exe on the workstation. The ParsecSetTeamID.exe file will only properly run if you run the application as administrator. The ParsecSetTeamID program locks the workstation to your team, so only your team members can connect to it. After installing Parsec for Windows, run the ParsecSetTeamID.exe file and input your Team ID from the Teams Administration page.
If you're deploying via the command line, SCCM, or another packaging tool, you only need to download Parsec for Windows. The installer comes with both the Teams ID setting and Parsec in one bundle, so with your command line, run
parsec-windows.exe /norun /S /teamID:YOUR_TEAM_ID
(this is case sensitive). The flag
/norun tells Parsec that it should not run after installing. The flag
/S tells Parsec to install silently
/teamID: sets the Team ID on the workstation, locking the machine to the team.
If your team is onboarding while employees do not have access to their workstations, you will need to ask people to log into Parsec for the first time after installing the software using RDP.
- Ask your user connect to their PC via RDP
- If Parsec is not running, ask the user to then launch Parsec from the Start Menu or Program Files
- Tell the user to log in to Parsec with the account you invited to the team
- Disconnect the RDP session
- Open Parsec on your computer at home, and connect to the Teams PC. If the user did everything right, they'll see a PC in their Parsec app listed as a Teams PC.
You can apply settings configuration policies to the Parsec app via the Windows Registry. Configuration settings policy applied via the Registry will override any user configuration done in the Parsec settings UX, or in the configuration file (config.txt).
Create a String Value named "Configuration" in the HKEY_LOCAL_MACHINE\SOFTWARE\Parsec Registry Key.
This is the same location as the TeamID is stored.
The value data will be based on the configuration options you select, the configuration values should be colon(:) separated.
An example sets the connection to use a maximum of 15Mbps, and default to using H265 video codec when possible. It also hides the Parsec Arcade and Friends List from the Parsec App. Just note that setting this does not disable the Arcade or Friends list functionality at an account level, but rather just hides those features from the Parsec UI on the computer the policy was configured on.
In order for the configuration policy to apply, the Parsec app must be restarted. You can validate the policy by viewing the settings section of the Parsec app. Your users will also be able to see which settings are applied by policy and cannot be changed.
You can also add these Windows Registry settings by creating a .reg file, with the contents like this.
Windows Registry Editor Version 5.00
You can apply additional settings to hide app functionality such as the Parsec Arcade and Friends.
You can view advanced configuration settings here.
To make your life easier, here are some settings you may be interested in.
Hide the Parsec Arcade:
Hide the Parsec Friends list:
Set the connection bandwidth limit to 15Mbps:
Disable hosting on a computer:
Set the Parsec computer name:
Set the first UDP port the Parsec app will try use when a connection is initialized to this computer:
The Parsec application communicates with our backend via TCP, with our STUN server via UDP, and peer-to-peer with other Parsec hosts via UDP. All TCP traffic is encrypted and uses port 443, STUN UDP traffic uses port 3478, and the encrypted peer-to-peer UDP traffic uses port ranges specified in Parsec Settings or the configuration file. A value of 0 for the port settings will cause Parsec to use psuedo-random defaults based on the computer's hostname. Parsec will use one port, incremented from the Host Start Port, per client connection. If you want to allow for collaboration, you should reserve 2 or 3 ports (for 2 or 3 people to connect at once) to each workstation. If your organization's firewall allows for UDP hole punching, Parsec will work without any additional configuration. If not, choose whatever works best with your security model to allow the peer-to-peer UDP traffic to the Parsec application. If whitelisting by domain name or IP is necessary, here is the full list:
|Domain / IP address||Purpose||Protocol and Port|
|kessel-ws.parsecgaming.com||Websocket API||TCP 443|
|builds.parsecgaming.com||Automatic Updates||TCP 443|
|parsec.imgix.net||Image CDN||TCP 443|
|IPv4 18.104.22.168||STUN Server||UDP 3478|
|IPv6 2600:1f18:63d9:c506:1337:1337:1337:1337||STUN Server||UDP 3478|
Parsec will not start on a Windows workstation until a Windows User is logged in. If your Teams computer disappears from the list, please use RDP to connect to your workstation and log in to your Windows User. Disconnect from RDP, and Parsec will be running as long as Parsec is set to "Run when my computer Starts" in the task tray. If at any time, Parsec is not running on the workstation, you can RDP into the computer and start Parsec from Program Files or the Start Menu.
In the settings area of Parsec, you can add Approved Applications. This is valuable when you plan on inviting people to play test a game or view just one application. The person joining still needs to be a member of your team, but when they connect, they'd only be able to see and interact with the applications approved in settings. Please read more about Approved Applications here.