Overview

The Intuiface Share and Deploy console enables the deployment of any published experience to any licensed Player, located anywhere in the world, on any supported operating system, assuming the underlying device has Internet access and the Player license is part of the experience owner's Intuiface account. With a simple mouse click in a web browser, any Internet-accessible device running Intuiface Player will download and then play published work. (For information about how to publish an experience, see this article.)

In Intuiface, the act of deployment is comprised of two mutually exclusive steps:

1. pushing the latest version of an experience to a Player device
2. running the version of an experience found on a Player device.

For example, deployment could consist solely of copying the latest version of an experience over to a Player device in anticipation of a play sometime in the future. Conversely, deployment could consist solely of a play request, ignoring whether or not the version of the experience on the Player device is the latest. As detailed below, push and play can be combined in a single deployment job.

NOTE: Remote deployment is a feature exclusive to those with an Enterprise-level account or running the 28-day Trial. Essential and Premier-level accounts can publish and share (with an account or via Windows self-installer) their experiences but can only deploy manually. For information about manual experience deployment, see this article.

Deploying experiences immediately

Prepare the device running Player

To deploy an experience, you must first prepare the target device. First, install and license Intuiface Player on each device. Then:

• Player on Windows: There is no need to run Player itself.
• Player on all other platforms: Simply run Player.

Now open the Share and Deploy console in any web browser and follow either of the two procedures outlined below.

Option One: Select the experience first

In the My Experiences view, select the experience you wish to deploy. This opens the Experience information panel.

Next, on the "Deploy in-venue" tab of the information panel, select the Players on which you wish to deploy this experience. You can filter this list by name, tag, and platform.

Finally, choose one or both of the following options and then click the Deploy button.

• Push   Copy the latest version of the selected experience over to each selected device if it's not already on it. If the experience you're deploying was never previously copied, the push could take time as you wait for the copy action to complete. If the experience was already pushed once before, then on all Player platforms other than Samsung SSP, a differential download will only copy the changes, speeding up the push process significantly.
• Play   Plays the version of the specified experience currently on each selected device. The act of playing does not take into account whether the version of the experience on the device matches that of the published experience in the cloud.

Clicking the Deploy button initiates the options you've selected. If both Push and Play are selected, the push always happens first.

Option Two: Select the Players first

In the My Players view, select the Players on which you wish to deploy your experience. To select more than one Player

• Filter by name/tag/platform.
• Select the triangle in the lower-left corner of each Player you'll be targeting (or, to select all filtered Players, click the checkbox in the upper left named "0 selected device").
• Click the "All selected devices" button to open the Player information panel.
  
  

NOTE: If you don't see Player for Windows in the "My Players" view, refer to our article about troubleshooting the absence of Player on Windows.

Next, on the "Deploy" tab of the information panel, choose the experience you wish to deploy. This list of experiences can be filtered by name.

Finally, choose one or both of the following options and then click the Deploy button.

• Push   Copy the latest version of the selected experience over to each selected device if it's not already on it. If the experience you're deploying was never previously copied, the push could take time as you wait for the copy action to complete. If the experience was already pushed once before, then on all Player platforms other than Samsung SSP, a differential download will only copy the changes, speeding up the push process significantly.
• Play   Plays the version of the specified experience currently on each selected device. The act of playing does not take into account whether the version of the experience on the device matches that of the published experience in the cloud.

Clicking the Deploy button initiates the options you've selected. If both Push and Play are selected, the push always happens first.

Deploying experiences on a schedule

Why schedule deployment?

There are a variety of scenarios in which deployment should not - or cannot - occur immediately. Such scenarios include

• Avoiding content updates during work hours
• Repeating deployments at regular intervals to ensure the latest content is always on each device
• Knowing personnel will be unavailable at the required deployment hour
• Pushing content to devices currently offline

How to schedule experience deployment

For the specifics of deployment scheduling, see our article Scheduling remote deployment and other Player services.

Working with secondary accounts

If you have a primary account in possession of secondary accounts, you can deploy to secondary account Players by selecting the appropriate secondary account from the dropdown list at the top of either the Experiences view or the Players view.

Consider selecting the secondary account in that dropdown as equivalent to logging in as the secondary account.

Location of a deployed experience

Experiences deployed to a Windows PC - whether using the Share and Deploy console or downloaded manually via Player - are saved in the folder: C:\Users\Public\Intuiface. The folder name for your project will be the first few characters of the Experience ID - e.g. 1-3f08d610-630a - which can be located on the experience's information panel:

Auto-Play experiences after crash or reboot on Windows PCs

On Windows devices, there are two circumstances under which Player will automatically restart itself and play the last run experience.

1. Player crashes
   If Player crashes, it will attempt to auto-recover itself. If successful, it will automatically open and run the experience it had in memory at the time of the crash.
2. Windows Device Reboot
   If the Windows PC is rebooted - e.g. to recover from a PC crash - Player can auto-start itself after PC reboot and login, then play the last run experience. This ability is turned on via the Share and Deploy console and is described in detail here.