...disdain for the receiver, wether intentional or not.
Whether. Or was that intentional?
Don't get me started on "preexisting"
According to Merriam-Webster it's first known use is 1585: http://mw1.merriam-webster.com/dictionary/preexisting
So it has been around for a while unlike most buzzwords.
Music lobby group, the BPI, welcomed the move, saying music creators 'deserve to be paid for their work just like everyone else'
I agree. It's just unfortunate that when you buy mainstream music only a very tiny percentage goes to the music creators. Most of it goes to record label fat cats and towards lobbying for shit like this ban.
If the server is suitable to be used for more than one purpose then each purpose should be in its own virtualised environment which will have its own purpose defined name.
With how easy virtualisation is these days there is no need to go mixing different functions within the same os environment which can cause all sorts of random problems as different software reacts with each other. Separate them out using virtualisation making it easy to move to new hardware, easy to retire old things no longer needed, easy to re-image if some software plays up.
(...example? Clicking "cancel" when Task Scheduler demands a password in Server 2k8 will lock out an AD account in a hurry. Neat little bug, but one of the zillions of subtle things a sysadmin would know, but an MCSA would not.)
My sysadmin experience says that would lock out the account because you have set up a task to run as an account but not provided a password for that account. Therefore when the task tries to run the password the task scheduler provides (null) does not match the account password. Or do you mean there is actually some bug that causes the account to get locked simply by clicking cancel?
No problem is insoluble in all conceivable circumstances.
