USCYBERCOM plans, coordinates, integrates, synchronizes and conducts activities to: direct the operations and defense of specified Department of Defense information networks and; prepare to, and when directed, conduct full spectrum military cyberspace operations in order to enable actions in all domains, ensure US/Allied freedom of action in cyberspace and deny the same to our adversaries.

That's purely speculative. Also one would assume that setting Location Services to 'off' will infact turn off location services.

Settings > General > Location Services

Now you can choose which apps are able to access your location information, or disable this feature altogether. Was that really so hard?

...research that will be presented (PDF)...

I wish that I had Hypersafe installed so I could open Acrobat on a virtual machine instead.

I am not even on the electoral roll but am considering signing up to give Labor my last preference.

You might have had more luck if you were Googling "Kepler's Laws".

Does anyone actually use Modchips on their Wii any more?

Of course Microsoft offer support. I'm not sure exactly what you mean by 'mission critical documents' but they offer a high level of support for all of their products.

They will create patches for you if you discover a bug which is effecting your systems and, in most cases, this graduates to a KB once they have tested it fully. The turnaround for this type of thing is usually as long as it takes them - in the order of days (not months, and sometimes less) - and in the meantime they will devise a workaround suitable to your environment. I couldn't comment on cost, though it is obviously worth whatever they charge considering how many large companies are onboard.

Microsoft's definition of EOL is that they will no longer patch bugs found in the product, nor will you be able to obtain support either online, via email or telephone. It doesn't begin shutting down servers, though I suspect if you are running any 10 year old hardware it may be well past the due time for you, as the administrator, to begin a hardware refresh cycle. With an Enterprise-level agreement you will not be paying for the copy of 'Windows 2000' or 'Windows 2003" but rather 'x copies of Windows Server OS' so it makes sense that in order to get the full benefit of your licensing you upgrade your operating system and software whenever possible.

I also don't buy your comment that you can only have first-level support for a proprietary product. Using MS as the example we have been, I think you'll find that the majority of people supporting Microsoft systems are Levels 2,3,4+ (whatever 4+ may be).

My experience comes from working in a range of large corporations, both consulting and in-house, where Microsoft was the ONLY option due to the quality of the overall product and support provided on their enterprise products.

FWIW I use Mac at home.

> practices

practises

Speaking from experience, having two machines with the same SID on a single Domain you will have issues related to the computer account in Active Directory. Remove one of these computers from the Domain and the others will experience Netlogon errors and various other issues as a result. Although NewSID may no longer be relevant due to lack of Vista/2008/7/2008R2 support, you should always sysprep /generalize to prevent these issues from occuring. Not too sure why an MS blogger would have this stance, I've seen it numerous times (10+) with my own eyes. The fix is to either perform an offline workgroup join and generate new SID's on all but 1 affected machine, or to remove machines, NewSID all but one, and rejoin the Domain.

Do you remember when the only thing you could get on copper was an analogue dialup signal? It's much easier to achieve higher speeds with the infrastructure already in place than without it....or you could just move 100m away from your telephone exchange and use as much of your beloved gigabit ethernet as you like.

That's not true. For clustering of front-end services (ie, IIS) you use NLB which is fully configurable load balancing and fault tolerance.

I would think that this would also largely depend upon what you are using to serve the pages people are going to be accessing. If you are using IIS as a web server (I'm assuming this is not the case) then the NLB component of Windows is already there ready to be turned on. This will provide fault-tolerance and load balancing for the front-end but if you have databases then these will also need redundancy for your service to be HA (MS have failover clusters for this purpose). I've found MS implementations of load-balancing / HA to be simple and effective if they are implemented properly.

http://lmgtfy.com/?q=windows+xp+vs+windows+7

Follow the first link. There we go, that wasn't so hard.