Question: I'm wondering what you do as a programmer that's not programming but necessary for your task (eg: local setup, server setup, deployment, etc). I'm curious to know how many non-programming related tasks people are performing. 

For example, when on web development projects I often:

* Install servers
* Manage user right/access to servers
* Perform backups
* Configure IIS/Apache
* Setup FTP sites

On non-web projects I often:

* Write build scripts
* Setup source code management tools/procedures
* Probably more stuff I'm not thinking of

Some tasks are more related to programming than others (such as writing build scripts) but others fall outside of my area of expertise (domain setup comes to mind). Just interested to know how many people perform tasks in their jobs that are not programming related.

Answer: 
Well, since a programmer's primary tool is his computer, I think it's fair to assume some expertise with it. Most of those sorts of things you've described are difficult for someone unfamiliar with computers, but pretty easy (even with little prior experience) for someone who understands the domain and knows how to find and read documentation.

In a big, well-organized business or project, I'd expect someone who was more specifically familiar with those sort of administrative things to take care of them. However, if there's not enough of them to warrant a full-time job, then I don't think it's unreasonable to have anyone competent work on it; and programmers are probably at the head of the queue in that regard.
My job title is "Senior Software Engineer". In point of fact, for most of the past several years, I did fairly little software development, but did do a lot of:

Systems & web administration

Static web page development with HTML (I don't consider that programming, although I have done PHP, CGI, and JavaScript).

As others have said, help desk sorts of stuff, although not as much as in the past.

As a "task leader", I'm expected to have some people/management skills, although that usually devolves to writing monthly reports. I also get sucked into CMMi stuff from time to time, which in an ideal world might be somewhat relevant, but is usually just record keeping so the employer can bid on new contracts which require it.

Working in science lab, there's a need to know some of the science, especially if you want/need to work on the code doing the scientific calculations.

Working in a (U.S.) government facility, there's lots of paperwork and a need to know lots of government regulation (e.g. Freedom of Information Act)

Fortunately, I've recently made an internal transfer where I'm doing more development work and less of this other stuff!