I used to work somewhere where I was tasked with upgrading a rather old version to the newest, and I did actually get it working perfectly with Exchange and SQL! Yes I'm awesome. But it did make me age about 5 years and become very bitter :((

Speaking of which, what would you recommend for backing up a mixture of Linux and Windows boxes? Still using clever rsync and a bit of Backup Exec, works fine so far..

Haven't got a clue - I'm fortunate enough to never ever have to backup Linux :D The only Linux stuff we ever use is appliance based, so doesn't need backing up as it's quicker to just rebuild than restore.

I really do like DPM for backup Microsoft stuff. Been very impressed with it.

This might show my lack of Linux knowledge, but could you do a backup to an MS File Server and then back it up as normal files?

This'd take some work. but you could configure multiple IP's (or NICs) and do quasi out-of-band management.

So, each server has two IP's - a 'public' one (The current one, registered in DNS etc) and a 'management' IP which isn't registered in DNS (This is important!!). When you want to do maintenance just disable the public IP.

The ideal would be two NIC's running on two different VLANs, but it'd still work on a flat network.

Other than that I don't know of a generic way to disable logons, unless you can do something application specific (I.e., disable a share, or disable terminal services if it's a terminal server etc)

Problem is, it kind of makes no sense. Try and "define" what you mean - do you mean that the computer shouldn't provide any services - what about websites, etc? Do you mean non-admins shouldn't log on at the console? Remotely? Do you mean file shares should be inadmissible?

I don't see how it'd be feasible for MS to provide a switch to do what you need as it's so dependent on individual use cases.