The
dbatools module is becoming a popular tool to use. [Caveat as I'm a major contributor to that module.]
Your need to script out things for a reinstall would also apply to keeping a "backup" of those objects and information as well. Claudio (another contributor) actually published an article today on using dbatools to backup the logins on a given instance.
There is also the Export-DbaSpConfigure to export the sys.configurations data. Some commands at this time I think support piping to "Export-DbaScript" but not all yet. This command just takes the output of a command, that outputs the SMO object, and will just script it to a file. Think along the lines of using the Script Database functionality in SSMS, but with other objects like Logins or Linked Servers. Obviously some objects cannot be fully scripts, like linked servers as they contain a password. So those you would have to treat appropriately on how you back them up.
If you find items that would be beneficial to add into dbatools, by all means, submit an issue to request it or contribute a new function.
Shawn,
Thank you for the reply. I'm actually very familiar with dbatools and I've seen a lot of the discussion in the slack channel. My main holdup with dbatools right at this second is that the module isn't digitally signed yet. Once it is, it should adhere to my organization's execution policy and will make a lot of administrative tasks easier--so I'm looking forward to that.
Again, thanks for the suggestion!
Mike
Mike Scalise, PMP
https://www.michaelscalise.com