Agree with witch. After supporting staff laptops across 3 sites most faults are fixed with a reimage Also if you manage to get a rolling replacement going its helps reduce the burn.
We used to use TPM but don't anymore because the laptops I wanted didn't have it in them. We ensure our staff policy says no personal details to be held on the laptops instead. Saying that, TPM will be something I will be looking to reintroduce in the next batch.
No encryption here
As someone asked later, we are also planning to used Windows Enterprise's Bitlocker full drive encryption for security, and try to get Microsoft Direct Access running.
If we go ahead with this, it's going to be a busy summer. Thanks for the input so far, everyone; the negative and the positive!
Also other non-technical tips that have helped us along the way :
Label the chargers with the laptop computer name. Yes, some staff will accidentally swap them with colleagues, but most will keep hold of their own and when they leave them lying around the owner will be easier to trace. Also if you have several different model's of laptops (we do now, as the fleet has got bigger) you'll know what model the charger belongs to.
Obviously get some spare chargers to loan out and a few spare laptops as well and then keep a log of who has borrowed what. Quite often the chargers won't make their way back, so you'll have to chase them. If someone keeps doing this over a course of time you'll have a recorded history that you can past up to SLT and say "this person is losing chargers and costing us money"
Help guide. Put some sort of help guide on their desktop. Keep it short and concise (although they probably won't read it anyway) and make it read only. Then when you hand them out you don't have to blurt out random things out that you remember at the time. Just say sign this form and remember to read the help guide. (They won't, but you can throw it back at them later)
Software. I had to install various software for different departments on the same image. To simplify it, I put a "teachers software" folder on their desktop and this contained everything they needed (shortcuts etc.) and then make it read only. They can then drag their favourite icons on to the desktop if they wish.
Also make sure you have extra spare laptops at this time of year. If anywhere else is like this place, you'll find new staff want to start before the old staff have left, leaving you with a shortfall of laptops :-p and the ones on maternity also won't give up their laptops so that could be another reason for a shortfall.
we've had teacher laptops for years. there will always be:
certain teachers whose laptop always seems to fall apart
teachers that put (all) files on their desktop instead of their userarea
teachers that used their laptop with their personal digital camera and the pics somehow got in their userarea. GBs of them.
Same as above but with itunes
teachers that let their kids use their laptop and its full of games/junk
teachers who left their charge at home / lost it.
spyware/dodgy browser toolbars
I'd start off with the policy they replace their own charger if they loose it. I dread to think how much we've spent on those...
but let them install their own software.
Last edited by browolf; 17th June 2014 at 12:27 PM.
We have docking stations here and everything seems fine. I personally don't like them, but they work. Here are some Pro's and Con's:
PRO: Teachers can use their own laptop in each room.
CON: Supply staff have not this facility.
PRO: docking stations have their own power cable, so staff don't need to remember chargers.
CON: I've come to buy more spare 'dockable' laptops now (couple of years later) and they don't make any to fit the dock any more.
So a couple of pointers... buy a good few spare docks and laptops, because before you know it, they will be end of life and you will need new everything!
We have Toshiba's here and they seem sturdy and well built. The laptops are i5 Tecras, more business PC, but then you need something good that'll last.
There are currently 1 users browsing this thread. (0 members and 1 guests)