The console selector occupies the left side of the main window. The console selector displays consoles and console groups.
Xbox One Manager maintains a list of the consoles you work with, so that you can quickly choose which console to work with. You can hide or show the list using the show/hide button on the bar between the console list and the details panel on the right side of the window.



Clicking the address or name of a console causes additional tabs to be shown, allowing you to get additional information on the console or perform actions on the console.
Console groups are a user defined collection of consoles. Console groups allow actions, such as installing an application, to be performed on all of the consoles in the group at once. Console groups are created using the Create Group button.
Consoles can be added to a user created console group using either of the following methods:

The Group Details tab lists the consoles in a group and allows you to add and remove consoles from a group. The Group Details tab also allows you to perform the following actions:
the Groups feature does not optimize the recovery or app deployment mechanism. For example, using a Group to install a new recovery on 10 consoles is the same as running 10 simultaneous recovery commands. This means that the performance of recovery or game deployment is dependent on your hardware and network setup, particularly the performance of the network card in the PC running the command and the network bandwidth between that PC and the consoles you are targeting. The more consoles you have in a group, the more the command you execute is going to bottleneck on your PC’s network performance. Please take this into account when using the Groups feature. For example it might make more sense to deploy a game to 32 consoles from 2 different PCs, than from a single PC. In that case you would want to set up 2 groups each containing 16 consoles rather than a single group containing 32 consoles.
We have successfully tested recovering and deploying to groups with up to 16 consoles in them (for example running recovery against a group with 16 consoles in it, push deploying a 40GB game to a group with 16 consoles in it). The optimal size of groups for your studio will depend on your hardware and network setup and your experience may vary from ours. Please give us your feedback on what does and does not work well for you.
If you are using Groups to run recovery for a set of consoles or to push deploy a game, we recommend that you copy all of the assets to the PC that is performing the command. For example copy the recovery files to the PC running the recovery command, rather than leaving those files on a file server. This avoids having repeatedly to copy the files from the file server to your local PC and then to the console.
These guidelines around scalability do not apply to installing a packaged game (“install app package”) from a web server – in that case the package is streamed directly from the web server to the target console. If you wish to simultaneously deploy to a large number of consoles, this is the most efficient solution.
You can hide the console list by clicking the Hide button, and show the list by clicking the Show button.
Figure 1. The Hide button

Right clicking on a console displays a list of commands mirroring the menubar commands, plus commands to specify a default console for the PC or remove a console from the selector.

Right clicking on a group displays a list of commands that can be performed on all consoles in the group.

Xbox One Manager allows you to set a default console using the context menus in the console list. Specifying a default console displays an asterisk next to the console icon in the console list, and sets the default console for use by other tools such as the command line tools, Visual Studio, and PIX.
Note that if you have previously set a default console by using xbconnect.exe, the default console you specified will automatically be added to the list of consoles and marked as the default console the next time you launch Xbox One Manager.
Xbox One Manager allows you to export your console and group data to an XML file and import that data on another computer running Xbox One Manager.

Your console and group data will be saved in an XML file that contains a list of your current consoles and console groups. For example:
<?xml version="1.0" encoding="utf-8"?>
<ConsoleCollection xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Version="1">
<Consoles>
<Console Address="10.120.195.186" />
<Console Address="10.137.125.26" />
</Consoles>
<Groups>
<Group Name="MyGroup">
<ConsoleReferences>
<ConsoleReference Address="10.120.195.186" />
<ConsoleReference Address="10.137.125.26" />
</ConsoleReferences>
</Group>
</Groups>
</ConsoleCollection>
After importing the XML file, the CONSOLE SELECTOR will be updated to include the consoles and console groups in the XML file.
You can remove all registered consoles and custom console groups from Xbox One Manager using the Remove All Consoles and Groups command.

You can remove all consoles in a custom group from Xbox One Manager when you remove the group using the Remove Group command.
In cases where Xbox One Manager can’t connect to a console check the following common issues first:
The console is using WiFi instead of wired networking. The transport used by xbconnect and Xbox One Manager do not get a valid Host IP address when connected via WiFi.
The ability to get IP addresses is sometimes controlled by an allow list of MAC addresses. The Host IP address is coming from a different MAC address on the console, so if your studio has an allow list, you need to make sure that the Host MAC is also added to the allow list. You can find the network MAC addresses for a console by going to the retail Settings app, then Network -> Network Settings -> Advanced Settings.
Note: Xbox One Manager cannot connect to a console if xbconnect shows the following:
HOST: Unreachable.