• My last round of deployments, I set up a command line install script.  Tweaked the locations for the databases, logs, etc, set the service accounts and the first SA account, then ran with it.  Remove any services not required on a particular server before the install, and the nice part is, all my servers have the same basic setup from the git-go.

    Then tweak the various settings like Max Mem after the install, and start adding logins.  We've got a fair number of SQL Logins, sometime back I found a script from someone (don't recall who) that is able to pull the login and password and create a "create login" script, that also duplicates the SID for those accounts (so I don't have a mass of orphan logins to fix on the new server.)  The various Windows logins are easier to recreate / script out on the old server.

    I suspect when we do our next migration sometime in the future, I'll be able to just tweak my current command line install and use it again.