Inetersting points raised
One thing I did not see is how to deal with a highly diverse user base. What is suitable for our secretarial staff is totally unsuitable for researchers and developers, and what is suitable for a researcher in software engineering is not suitable for somebody doing image processing or CUDA development. There is a tendency towards "one architecture to rule them all" in many IT departments, which would either deliver a complete overkill system for the low end users (leading to cost overruns for which IT is famous), or frustrate the hell out of power users. All to often, the latter is chosen.
There is of course a tension between keeping things simple for the IT staff and at the same time keeping a highly diverse and constantly changing customer base happy.