Packaging Tulip Player for Enterprise Deployment

Looking for guidance on packaging Tulip player for deployment via SCCM.

  1. How do we disable automatic updates? We would like to push updates ourselves as needed

  2. Is there a method to create a custom device upon installation (or afterward via script executed upon install)? We have a standard barcode scanner and know the Device ID/Vendor ID information

1 Like

hello @Dan, great questions!!

I heard that @EddyA has been working with you directly on this topic, let us know if you have any follow up questions.

I’m interested in the outcome of this conversation. Thanks.

There is a mechanism to disable automatic updates:

“To disable auto updates please perform the following steps:

  1. Open Player

  2. In the menu select “Developer” → “Toggle Developer Tools ( Browser )” → Select the “Console" tab

  3. Locate the “>” chevron/command prompt at the bottom of the console output

  4. Paste " window.tulipDevTools.setDisableAutoUpdate(true) ” at the command prompt and hit enter.

  5. Confirm that you are seeing "Saved new value. Restart to take effect.”

We don’t yet have a streamlined approach to update management via SCCM, would be interested on proposals for that from Tulip.