Replacing a server = One change
Reconfiguring some shared folders = One change
Replacing a whole bunch of printers = One change
There are a couple of advantages with a change process like this.. the first one is collective responsibility, so the poor sysadmin can pass at least some of the blame back to the CAB if it goes wrong. And then also there's the point that other people might have a legitimate input into the process, especially if there are things happening in the business on the same day as the proposed change that IT doesn't know about.
I was brought up on Star Trek. Surely someone out there in TV land must have the means of brining a decently plotted and good looking Space Opera back to our screens?
But there's a gotcha.. I upgrade to 8.1 via Windows 8. The first step from Windows XP to 8 ran pretty smoothly, all of my data from the XP installation was moved to a folder called windows.old where it could be recovered from by someone with a basic understanding of PCs. All well and good, but the obvious next step was to upgrade to Windows 8.1.. a bit trickier as you can't do that without installing KB2871389 first (either through Windows Update or manually). The Windows 8.1 download is enormous, 3GB+ but it installs smoothly enough.
The catch? Well, upgrading from Windows XP to Windows 8 creates the windows.old folder with the old data in. Upgrading from Windows 8 to Windows 8.1 DELETES that folder and creates a new one with the old Windows 8 settings.. obliterating your original data from the Windows XP installation.
Well, that wasn't a problem for me as I'd backed up everything onto another drive which I unplugged to be on the safe side. But it wasn't what I was expecting to happen *at all*.. and you can see that a less paranoid customer (or one without a suitable backup disk) could well lose everything if going from XP to 8 to 8.1. And I do notice that there doesn't seem to be a Windows 8.1 Upgrade version available anywhere, so this is the path that a lot of people would take..
Stop trying to infect me with malware and perhaps I'll stop blocking you from my browser.
And if it wasn't late.. it wasn't finished properly. Like the Storm. And then the PlayBook was both late *and* not finished properly.
Nokia found itself in the same dead end, but at least it had some sort of strategy when it jumped off the infamous "burning platform". I think that Apple is at risk of the same pitfalls.. they are a much more defensive, conservative company than they were six years ago. The only people who really seem to have a clue are Samsung, and they've got all the appeal of the Borg collective as far as I'm concerned..
So it's not clear if those addresses belong to the FBI, the CIA, NSA, or anyone else.
Is this even "legal" on the Internet? Perhaps those IP addresses should be reclaimed and reassigned by ARIN since "nobody" is using them and IPV4 addresses are now in short (nonexistent) supply.
Correct, the IP address block (220.127.116.11/29) was allocated to a Verizon Business customer probably located in the Washington DC or Virginia area. Some neighboring blocks in the same
As for "legality".. the block is allocated to Verizon who break it down into smaller chunks for customers who may or may not wish to identify themselves in the WHOIS records. It is just 8 IP addresses in any case.
Going into a 30 mph zone? Set the speed limiter for 30.. then you can watch the road, not your speedometer. 50 mph average speed cameras? No problem.. set the speed limiter to 50 and you won't go any faster. Going down a motorway in France? Set it to 80 mph. Taking it on a track? Leave it switched off. Bloody marvellous.. all cars with cruise control should have it fitted. But a surprising number of people who DO have it fitted don't know how to use it.
However, it is true that certain ad networks do very minimal checking or even seem to be in league with malware pushers. But publishers soon drop ad networks like this and they end up being relegated to the scummy tier of publishers only.
Oh.. it's hardly new anyway. Here's a report from 2004.