Lobbying for a dedicated web server

[Andrew Darby]

Hello, all.  I'm at a smallish academic library, and currently we have a
little folder on the university's web server, without access to
goodies/basic human necessities like PHP and MySQL.  As such, we are
about to lobby for our own web server, presumably to be hosted by campus 
in their climate controlled room.

My question, then, is:  What sort of resistance should I expect?  What
sorts of concerns are likely to be voiced (and what are reasonable
countering arguments)?

Perhaps I am wrong, but if the IT folks

1. do the initial setup of a LAMP (Linux/Apache/MySQL/PHP) environment,
with the security to their liking

and 2. integrate this box into their backup routine (i believe they do a
middle of the night chron job)

there should be little or no overhead on their part.  By gum, it would
be one less thing for them to worry about! My recollection from a
previous incarnation, is that Apache servers are pretty stable, and
don't require much (if any) maintenance . . .

And as a bonus, in the unlikely event we do something stupid and crash
the server, the campus at large is insulated.  (We currently have full
access to the library folder on the existing server.)

Any thoughts, suggestions, etc.?

Thanks,

Andrew Darby