powdarrmonkey

Ok, here: 1. set yourself up a Hotfix folder in your netlogon share, and in there a folder for each hotfix (I suggest you use the hotfix number, so \\domain\netlogon\hotfix\958058 for this one). You can use some other share if you want, but in netlogon you don't have to think about permissions. Pop the hotfix executable in there. 2. Script attached to put alongside the exectuable, just change the variables inside it to match your environment and the hotfix you're deploying. Remove the .txt extension. 3. Call from the startup scripts of your favourite group policy object, sacrifice a goat and make some coffee. Edit: and whoever neg-repped... helpful enough now? hotfix-template.cmd.txt

Sorry, it hasn't appeared since (probably a bonus )

The module you're compiling is trying to link to the video4linux headers, make sure you've got them installed. Looks like version incompatibility though It's a package from a Ubuntu Personal Package Archive and has a different signing key from the official respositories; you can install the key (if you trust the author) from https://launchpad.net/~intuitivenipple/+archive/ppa That one's a patch for the kernel source itself. Unless you're familiar with building your own kernels and modules (and all the other dangers that entails, like a non-booting system) you probably want to avoid that one if you can. I think the Ubuntu PPA is probably your best bet to try first.

Poke me on Monday and I'll send you the scripts.

Convince me otherwise then. (and good luck with the OS...)

I have some black magic for this; do you want it?

You want 'Our Suppliers'.

Welcome to three years ago...

Since when was the GPL classed non-free? Damn, that scuppers our entire distribution... Security by obscurity. Meet the cluestick.

There are plenty of schools around here. Not one of ours though, smoothwall takes care of that

Well, they're both sock puppets - look at their profiles. :spam:

Not very keen on this one either:

Genius. BBC strikes again

That's an awful lot of admin overhead unlocking accounts for people all the time..

If they are logging in with a domain account and cached credentials, you could reduce the cache time to a month, then they won't be able to log in until they have shaken hands with the domain again. Edit: you could also write, or have written, a small tray app that after a month bugs them in an annoying way to handshake bring the machine on site... if you ask nicely, I might be persuaded for some kind of return favour.

Set your proxy in environment variables, or pass them directly to wget: Wget - ArchWiki

No, the dollar indicates that it's a hidden share, it just happens that administrative shares are also hidden.

One set of our machines does this, because for some reason the BIOS thinks it can boot off the smartboard. Obviously it fails majestically and coredumps.

OP: you need a PRS license, and you need to take advice from them and not us who are not copyright experts.

*shrug* I didn't write it...

Here's how we do it in Debian-land, which should be practically the same for Ubuntu (the gdm package is imported with almost no changes): Giving your Xen instances a working X setup Edit: I think it's what you mean - just like Remote Desktop does for Windows?

You can't distribute a static key with group policy - the Wireless Network Setup Wizard is your friend here, create yourself a USB disk, label and keep handy.

When the rush is over I'll happily visit Dorset, but sadly not on a weekday - sorry.

RADIUS-based or a static WPA2 key?

Staff will have to manage their own files - I've found a cheap, school-issued USB disk makes a good carrot. This is where "your files aren't back up if they're not on the network" really starts to matter.