re-imaged

They re-imaged a lot of the Guardians of the Galaxy to have a more proper spaced based origin.

System restore is hardly ever used by our IT guys, and machines are often sent back to be re-imaged.

Any minor Windows system problem usually results in sending the machine to be re-imaged.

If an SSL vulnerability is announced, what is the process for guaranteeing that you've updated all the master copies and re-imaged as necessary?

We accidentally re-imaged all of the Windows servers with Linux the other day.

We did this on a dedicated machine which could easily be wiped/re-imaged.

It had been over a year since I installed FileZilla, but I re-imaged one of my machines and needed it.

It's also costly because now I'm questioning server integrity, thinking about what should really be re-imaged.

At any time, the machine can be automatically re-imaged as needed.

I'm sure you're well aware but that server should not be trusted now for anything sensitive (or anything at all really) until it's been re-imaged.

The demo gets fiddled with, and the language changed (which is what happened here; language changed to something your system isn't equipped to deal with; we still have a number of non-Unicode translations which can make systems without that language/typeface look goofy), pretty regularly, so it gets re-imaged a couple times a day.

Out of the blue, Several machine would be "re-imaged" and that means it would delete all the logs, working directories etc.

If Canonical promises to pay 20c per CD they ship, and 10% of those CDs are imaged and torrented and downloaded and burnt and re-imaged and re-shared all over the web, nobody knows how many "units" are out there, and there's no reasonable way Canonical (or Mozilla, or any other prospective licensee) can comply with any patent license more complicated than "do whatever you want".