theriver

The most important thing you can do is patch. If a security vulnerability is found in the application then it won't be long before people are trying to use it to break into vulnerable sites. If the components you use have a mailing list, subscribe so you get notified of new releases and can update asap. The other most important thing you can do is backup :-)

Are you getting any errors at the DHCP end (e.g. scope full)?

Never noticed this particularly, but I once accidentally bridged the wireless card on my laptop and not the ethernet card which slowed things up somewhat . . . .

Sorry, I should expand on that - if this is an addition to your existing register system for the other years, you've got to ensure the procedures around it are 'fireproof'.

Hello I am also sure that you could write a code for that - e.g. a script in the user's startup that writes to somewhere. Depending on your requirements and how complicated you want it you could write an entry to a database, or even simply write a batch file that writes a file to a share with the username and computername in the filename. This does seem like a flawed solution to me though, because you'd be relying on every student to log into a computer for every lesson - do all of your teaching rooms have computers? If you've got a room with 2 PCs and 30 kids in it, how useful is this solution going to be? And what do you do if there's a fire? How do you know who is in? This seems to me to be trying to find an unnecessary complicated solution to a simple problem. Isn't it easier for the tutor to just take a register?

DBAN, overwrites your disk with junk: Darik's Boot And Nuke | Hard Drive Disk Wipe and Data Clearing. Can take a while, but is easy (and free). If you can't get the disk into a PC to do this, you can physically destroy the disks - I think some round here recommend drilling into the case and into the platters, though I've personally never tried this (mainly as I know I'd drill into my own leg in the process).

Honestly, you people. Pencils contain LEAD, and LEAD is like, a METAL, right, so obviously they will stick to magnets.

So, as qcomer says, this means that the database already exists. Often you will find that running a script twice will break something (e.g. insert duplicate system data or lookup data into some table), so in general if the script doesn't work first time out, instead of re-running it's safer to roll back to your previous state. In this case it looks like you can delete the 'helpdesk' database you've just created and try again. The 'invalid object name' and 'DDL' stuff makes me wonder if you're inadvertantly running the script this subsequent time against the wrong database - have a look at the dropdown that's underneath 'New Query' and to the left of "!Execute" - that's the database your current query window is going to run stuff in. In any case, I'd say: drop the database and try running the script again, once only. If it fails, post the errors up here.

Hmm. So I've just seen a trailer for a TV show called 'Dirk Gently'. I don't watch TV much and didn't realise an adaptation had been done. The question is: will it be worth watching, or a huge disappointment? I have asked this table leg, but its answer didn't make any sense.

The thought of having to do this for a server room . . . . . What Cable Wrangling Technique Kept Wires Tidy During NASA’s Moon Missions? - How-To Geek

Worth taking the setup app out of the equation? Try setting up an ODBC alias to the SQL Server using the credentials you're plugging into the setup, show you whether you can connect to the database server in the first place.

Not sure if this is the best way, but in the past I've done similar things with 7-zip, setting the compression to 'store' (no compression, fast), and split to volume set to DVD. Have to manually burn to DVD of course, but it eliminates the guesswork. And, because I'm a kind person, I've supplied the command line app and a bat file that unpacks it all HDD :-)

I was sent this link recently: danah boyd | apophenia » How Parents Normalized Teen Password Sharing which claims data to show that 1 in 3 US teenagers share their passwords. If this really is normalised, as is claimed, then clearly telling people "don't tell anyone your password" doesn't work, and this is an issue that has to be acknowledged.

Which model, and do you mean the lid part or the bezel?

Listen, I am not even sure YOU people exist, let alone another universes. To be honest, I thought the error was calling the esteemed Prof. Cox 'Dr'. I do love Brian Cox though: given that he has a music career most people couldn't tell you much about and went on to be a massively famous scientist, he's pretty much the opposite of Dr Brian May. Brian and anti-Brian, if you will.

Perfectly clear. Yes. The RDP session maps the local printer, and for that the Terminal Server requires the correct printer drivers. I have attempted to run a system like this in the past and it can be horrendous, as you are at the mercies of whatever printer the user happens to have! If it turns out to not be possible (i.e. either through a lack of available drivers or an unwillingness to go down this route), you could press to get a PDF writer installed on the TS box, and copy the PDF's down the wire. May be a pain though, depending on how much printing they do....

.... and here just now.

I'm more of a Quote Unquote man myself . . . .

You can install the SQL Management tools on another box and connect to the database server to figure out what's going on (assuming the DB server accepts remote connections).

Sorry, me too. I assumed you were joking with that first post :-)

You don't HAVE to upgrade from Windows Me, in the same way that you don't HAVE to walk upright or use cutlery.

Have a look at: Windows lifecycle fact sheet - Microsoft Windows

Umm, misguided attempt at virus protection?

I'm old enough to remember floppy drives, which used to accumulate all kinds of things - including on one memorable occasion the top portion of a print out of a child's CV. You know, the bit with the name on.

That's a nice post . . . . but a troubling image.