Centralization is a common approach covering more than IT support. Software development, QA, CM, QC/IV&V, and project management are heading in this direction as well.
Centralization can reduce staffing size because it is easier to share people and avoiding the "half-person" problem (Site A needs 1 1/2 people, site B needs 1 1/2 people, etc). Centralization also allows for much more technical specialization. Having IT support distributed requires generalization; someone who can handle any type of problem.
The efficiency for IT support achieved through centralization, however, creates a bottleneck. Remember, almost every IT support call is an indication that a business function is on hold. Instead of having IT staff idle while waiting for problems to occur, we have business staff idle waiting for problems to be resolved.
When IT staff are valued based on specialized technical knowledge, they are at risk when technnology turns over every 5 - 10 years. In this environment, one's skill set is periodically reset from expert to amature status and if one is valued based on technical expertise, it is hard to justify paying that level for the same person to learn the ropes in a new technology.
Lastly, I feel IT service quality suffers when done remotely. A vast majority of the "stupid user" issues described in various places in TechRepublic and other sources are really communications failings by trying to do the work over the telephone or by e-mail. What might be resolved in less than a minute by someone present can degrade into an excercise of frustration and embarrassment when done remotely.
Centralization values technical specialization and business knowledge generalization while decentralization values technical generalization and business knowledge specialization.