When this applies

Each month, Vestis submits a support ticket requesting that the QL display images be updated - either the Random rotating set, the Monthly slide, or both.

Vestis contact: Dulce Pardo

If anything about the submitted files is unclear (naming, which plants should receive them, missing content), reach out to Dulce Pardo for clarification before proceeding.

What to expect in the ticket

Vestis will typically attach one or more of the following:

• A Random zip (e.g. August Spindle Images English.zip, August SLides French.zip) - general rotating image set
• A Monthly slide for that month, as a raw image or small zip (e.g. Slide8.jpg, 8-English.zip, 8-French.zip) - one image representing that calendar month

Content is usually provided in both English and French. French content goes only to the QL plant group; English goes to all other plants (CL and US).

Steps (L1/L2)

1. Confirm the ticket contents - check that filenames follow the expected pattern:
   • Monthly files must have the month's number somewhere in the filename (e.g. Slide8, 8-French). No number = the system can't route it, and it will be quarantined for review rather than applied.
   • Random files should NOT contain a number in the name (a stray number, like a year, will cause it to be misrouted to a Monthly folder instead of Random).
   • If naming looks off, follow up with Dulce Pardo before proceeding rather than guessing.

2. Update the Ninja distribution task(s) with the new files:

   • English content -> RK - Vestis | Distribute Random Images - All US and CL except QL
   • French content -> RK - Vestis | Distribute Random Images - All QL

   Replace/attach the new files to the appropriate task(s). Only update the task(s) relevant to what was actually sent (e.g. if only a Monthly slide was sent, you only need to update the file used by that push - Random stays as-is).

3. Push the files to plants using the bulk device-run method (this is more reliable than resaving the distribution task - resaving does not reliably re-trigger delivery to devices that already received a prior push):

   For English content (all plants except QL):

   1. Go to Devices in NinjaOne
   2. Filter to the "All US and CL except QL" group
   3. Select all matching devices via the checkboxes
   4. Use the Run menu at the top of the filtered list -> Automation -> Script
   5. Pick the English distribution script and run it against all selected devices at once

   For French content (QL only):

   1. Go to Devices in NinjaOne
   2. Filter to the QL group
   3. Select all matching devices via the checkboxes
   4. Use the Run menu at the top of the filtered list -> Automation -> Script
   5. Pick the French distribution script and run it against all selected devices at once

   Do both each month, even if only one language's content changed that month, since each group only receives its own language's files.

4. No further action needed. Each plant's nightly processing task runs automatically at 12:01 AM, picks up whatever was pushed, and applies it to the display. You do not need to log into individual plant servers.
5. Confirm completion (optional but recommended for larger content changes): check back the next day that the relevant plant(s) show updated content, or check that plant's process-log.txt if you have reason to verify.

If something goes wrong

Refer to the troubleshooting article for how to check the processing log and the Skipped folder, and how to identify common issues (naming mismatches, duplicate files, misrouted content).

Closing the ticket

Once distribution has been run and you've confirmed (or have reasonable confidence) that the update applied successfully, close the ticket back to Vestis / Dulce Pardo.