Over the last couple of years the UNT community has been steadily migrating to Drupal; we recently selected Drupal as the official campus CMS, and are currently running several hundred Drupal sites in production.

The university Central Web Support office (where I work) is tasked with managing the Drupal instances we give to folks around campus, along with applying security updates, end-user documentation, and other general support services. We face a number of unique challenges in this capacity:

1. How do we maintain a consistent look and feel throughout the enterprise?
2. How do we ensure a reasonably simple user experience, especially when many of our users are non-technical folks saddled with web responsibilities on top of their usual jobs?

This is a snippet from our current distribution's install profile. The password is set later with another helper function.

/**
 * Implementation of hook_form_alter().
 *
 * Allows the profile to alter the site-configuration form.

This presentation was delivered by Adrian Rollett and I at DrupalCamp Austin 2009. It discusses the potential of the Drupal features module, installation profiles, and drush_make in building polished, custom Drupal distributions.