3 ms·
Victoria University of Wellington accidentally nukes files on all desktop PCs
- olliej 6y agoLet's hope they have automated backup systems for managed systems. I'm guessing not.
- legerdemain 6y agoOh, IT did that to us once, when I worked at a lab in a SCIF. Nuked all research files that we hadn't yet uploaded to... shudder... SharePoint.
- Scoundreller 6y agoI mean, I know what an SCIF is, of course, but for everyone else: Sensitive compartmented information facility https://en.m.wikipedia.org/wiki/Sensitive_compartmented_information_facility https://en.m.wikipedia.org/wiki/Sensitive_compartmented_info...
- j_walter 6y agoThis is why you make backups...and backups of backups (or at least duplicate backups)
- Scoundreller 6y agoI’m surprised it’s even permitted to have files on the local drive and not stored on the network drive, especially for a fixed PC.
- hyperman1 6y agoMy company had something like this: In 1 or 2 months, a bunch of laptops of only one specific type+revision erased all user profiles spontaneously. Other laptops from that same vendor did no such thing. We ended up writing them off and donating all (20? 30?) of them for COVID remote schooling after one swallowed the data of a high impact manager. Data loss was minimal (thank god for backups) ,but a lot of people were angry . It never became 100% clear what happened, my vague recollection of the partial reconstruction was: * For some reason, this type of laptops decided to add 10 000 to the year in the RTC clock. The number was so high the bios couldn't even represent it, giving up at 9999. * Security policy dictates removal of profiles older than, I think, a year. So in the year 12019, all user profiles should be deleted. * The computer takes about an hour to boot, slowly deleting each profile. * After all profiles are deleted, the now blank laptop installs a patch to the timezone files and returns to the year 2019, then proudly declares itself ready for user logon. * The windows event logs did weird things in the date column, it just could not represent the date. Had to export the files to XML before it would show what year it was in. * If you interrupted the delete by rebooting the thing, then unplugging the network so no time servers would be available, then correcting the year in the bios, it would at the next reboot do a prompt forward time travel to 10 000 years in the future, then continue slowly removing profiles. As is usual in this kind of situation, HP support pointed to Microsoft, Microsoft to HP, and both of them to us doing some (unspecified) kind of misconfiguration.
- afarviral 6y agoThe article lacks a bit of clarity. It talks about computers as though they are assigned to students, but they have computers in the library (and other communal study areas) that are available for anyone, not individually dedicated to students (from experience, I went to Vic and regularly walk through the campass). Did they wipe the %userprofile% directories stored on these computers? That would be diabolical given how few lay people would understand how Windows directories/user profiles are managed en masse (you should know any local data on a shared machine could be deleted and that only certain roaming data would be retained after a fresh wipe.. For instance if there is a separate mapped drive which has your Documents folder mapped to it etc). This all could have been avoided with a simple message on the shared logon screen stating what folders are vulnerable to being deleted or accessed by other users.