Andy White's questions

Does anyone know of any more advanced/powerful replacements for the "Internet Information Services (IIS) Manager" for IIS 7? It might include things like selecting multiple items to update/delete/etc. at once, and more powerful features like that.

I'm hoping for something analogous to Sysinternals' Process Explorer replacement for Windows Task Manager. They both basically do the same thing, but the Sysinternals tool is more powerful/flexible.

We have some automated deployments that tend to leave virtual directories/apps and app pools lying around, and it can be a pain to go in an delete them all one-by-one in IIS manager. I was considering writing a script/utility to do automated cleanups, but was hoping something already exists.

When using Windows auto-update, it seems to save the install files on my large external hard-drive, rather than my Windows c: drive. I'd rather not have all that stuff on my external drive - is there any way to force it to only use c: for windows update files?

I inherited a laptop with Windows XP installed. I think the user account I'm using originally had a different username. Some of the enviroment variables (APPDATA and HOMEPATH) are still referencing the former username, rather than my new username. The variables aren't set in the normal env var section of System settings, but I see them in the registry in HKEY_CURRENT_USER/Volatile Environment. I read that these are generated dynamically at login, so I'm wondering what is the appropriate way to modify these to use a different username in the path.

I currently have a machine with SQL Server 2005 SP3 installed. I would like to add a SQL Server 2008 instance, but I'm not sure if I should upgrade the 2005 or try to install a separate instance of 2008.

If I upgrade the 2005, will I run into any issues with backwards compatibility? (Probably a dumb question).

Is it possible to run separate, stand-alone instances of 2005 and 2008 on the same machine?

Can anyone recommend a package management tool like apt-get or yum for Mac OS X? I've seen that Fink has ported apt-get to Mac OS X, is this a good way to go, or are there other/better options out there?

In my .vimrc, I want to check if I'm in MacVim vs. regular vim so I can optionally set some MacVim-specific settings, which should not be applied to regular vim.

How do I do this?

Of the major Unix shells (bash, ksh, tcsh, zsh, others?), are there any compelling reasons to use one over another?

• Which is the most interactive/command-line friendly?
• Which is the most conducive/intuitive for writing scripts?
• Are there any major built-in features that one shell offers that others don't?
• Are any of these shells really good for one type of function, but not another? Or are they all pretty well-rounded/flexible?
• Is it just a matter of personal preference?

I can make this community wiki if anyone prefers.

I have a Mac Mini that I would like to login remotely from a Windows XP laptop. Is this possible? What types of things do I need to do to allow remote connections from the Mac, and what type of interface will I be able to have? (Command-line interface? Or full GUI interface?)