Hi, I tried to find a topic related to this, but I was unable to. I want to use a product called PDQ to push out the client to over 2,000 workstations and use the screen saver feature of Xibo to display in-house slides. Is there a way to do this?
I’m not familiar with PDQ I’m afraid. There’s no silent install option to just install the screensaver, but it should be possible to extract the scr file and any dependencies, and a valid configuration and drop that on to Windows PCs with tools like Group Policy.
We don’t have a guide on that but if someone were to author one on here we’ll gladly include it in the Guides section.
Thank you Alex.
If I just push the scr file and the dependencies out to the workstations, would it still be able to be updated by the server for campaign changes? If not, then I don’t think that will work.
However, I believe I can push out the player package to all PCs, and then do a second deployment that would do the screen saver install and populate the necessary options that register it with the server, but I’m having problem locating the files. Would they be in the system32 folder or somewhere else?
If you configure the screensaver correctly to talk to your CMS then yes it will update when you make changes in the CMS.
Alex,
When you say “extract the scr file and any dependencies, and a valid configuration,” would the dependencies be the actually files that are in the scr file? For example, I have 5 slides in my screen saver, which consists of 5 full screen photos. Would I need to drop those 5 photos plus the scr file with the configuration to every computer? If so, is that something that could just be put on a share and point the configurations to the share? Thanks for all of your help!
No Melody.
You just need the Xibo client installed on the machine (which you can do via the MSI) and then to drop the configuration for the Xibo Player Screensaver on to the machine for each user who will run the screensaver.
The actual content for the screensaver is delivered from the CMS to the screensaver via XMDS (in the same way as content is delivered on a normal Xibo Player installation).