Skip to main content

Building your own public display system

I've been meaning to document how we setup our own public display system for sometime and have finally got round to it. We have 5 large displays in public areas around the school that display information. These are independent and can display different info on each screen. So what do you need?


  • Obviously - some displays - big TV's or monitors - either will do. If TV's - remember to turn off any power management features! You can get 42" models for <£300 now.
  • Mounts to fit them to a wall - typically around £20-30 mark.
  • Mini PC - anything will do - something that can run Windows.
  • If you have WiFi you don't need cabling - but otherwise a network point near the mounting location.
  • Suitably located power socket.

You need to setup is a system where the PC will boot up, auto logon and then be able to be controlled remotely by someone elsewhere in the school who puts stuff onto the displays. So this is how to do it:

Step one - build the PC
Install Windows and domain join the device.
Install the software you want to use to display stuff - we use PowerPoint.
Install iTALC and a student machine (more later).

Step Two - configure policies for these machines
Create an OU for your display PCs in Active Directory, so you can apply some special policies to them. See below:
You need to set Power Management to never let the display or PC go to sleep. Thats what the bottom policy does.
The key one is 'Displaypcs' - this makes the machine auto logon with a 'display user'.

So these are just a series of registry setting to specify auto logon, the domain, the user and finally the password.

Step 3 - iTALC
On each display PC you need to install iTALC as a classroom PC (so not as a master). Now this software is a free classroom management application and allows teachers to control PCs - but this is another use. 

You will need to setup iTALC on a PC and configure the parameters for a student PC and a teacher PC and save the configs as two separate xml files. Keep these in a network share and load them up with all new installs. You will also need to setup a network share that iTALC needs to store screen grabs and so on. There are good setup guides for iTALC out there. 

The person managing the displays needs to have iTALC installed as a master and then you need to add the display PCs to it.

Step 4 - Put stuff on your displays
So sitting in your office, you can now fire up iTALC, login with your AD credentials and view your screens:


Double click on the screen you want to manage and take charge of the device. So our devices are connected to a network share, so the user simply opens up a PowerPoint and sets it to loop - thats it. The actual PowerPoint is created on the users local machine.

So thats it really. Setting up iTALC for the first time can be a bit fiddly - but once done with your settings saved it quick and easy to deploy. Lot cheaper than commercial setups!


Comments

Popular posts from this blog

Delete a specific email using GAM

If a user send an inappropriate email to a loads of people or get stung by some sort of email exploit you can quickly delete the email from all of the recipients using a GAM command. Step 1 - get the email header Go into Google Vault and search for the offending user or someone known to have got the message. Click show details and grab the email ID. This will be a long string of characters followed by @mail.gmail.com Step 2 - find out who has the email Go into Google Vault and find the original message sent by the offending user. Look at the details to see who got it. Copy the list and dump it into a spreadsheet. Clean up to just a list of emails with a column header 'mail'. Save as a csv file. Step 3 - delete messages with GAM Put your CSV file in your GAM folder - this e.g. assumes its called mail.csv Run: gam csv mail.csv gam user ~mail delete messages query rfc822msgid: MESSAGEIDHERE doit The alternative nuke option is: gam all users delete messages query rf

Adding subdomains to G Suite

This is how I add subdomains (so basically new schools) to out G suite setup. I've got these steps documented on a scruffy set of notes that I've now got in Keep - so time to document them - for myself as much as anyone else! Steps in order (roughly) Add the new domain Verify the new domain Add MX records to hosting Add SPF record for Google to hosting Turn on email authentication Add DMARC record to hosting Setup custom Directory and restrict students OU to this. Create an admin quarantine for the domain. Configure SPAM setting for the domain. Turn on and off services as appropriate. Map a blank Google Site to the naked domain - if required. Setup some basic groups - allstaff, allusers (for directory) and students with appropriate permissions. Deploy custom wallpapers. So the steps in a bit of detail: Add the new domain & Verify ownership Click on Domains in the admin console: Add/remove domains followed by "add a domain" At this

My favorite GAM commands - well a few of them at least!

Where would be without GAM? Paying for expensive syncing tools or doing tedious manual tasks in the admin console. GAM can automate most things you might want to do in G Suite. So these are a few of my favourite commands - one I use either as part of a batch file - or just standalone. There are loads more - but these are ones that are used daily. Classroom Create a spreadsheet of all your domains classes -  gam print courses todrive Create a spreadsheet of a teacher's classes:  gam print courses teacher fred@mydomain.com todrive Bulk create classes: gam csv classes.csv gam create course alias ~alias name ~alias section ~subject teacher ~teacher status ACTIVE where classes.csv is a list of classes you want to make. Add teachers: gam csv teachers.csv gam course ~alias add teacher ~teacher Add students: gam csv students.csv gam course ~alias add teacher ~student Sync Students (in this example to a group - but could be an ou/csv file) gam csv groups.csv gam course ~g