But for the thousands of SMB IT techs that don't know the first command for how to make their switches backup to a TFTP server, we feel we made the right choice. Sadly, it means that some of you won't get what you are looking for with our TFTP server. So you can see that are tradeoffs in our decision to build more than a TFTP server tool. Two, not having a TFTP server as a tool means it's not readily obvious how you would (or whether it's even possible to) do some of the things you can do with the TFTP server tools. Included with TFTP-based backup and restore are alerts for when switches aren't getting backed up, alerts for when the running configuration and startup configuration mismatch, and alerts for when the configurations change over time. One, we chose to solve the most common problem for why people want a TFTP server, and we strove to solve it well. It sounds subtle, but the distinction is kind of important for two reasons: This is different than saying we have a built-in TFTP server, and you can use it to backup your switch configurations. Please follow the more recent link that Nic posted for exact details, but the summary version is that Spiceworks backs up switch configurations as part of its regular network scan by using a built-in TFTP server. So, where's a How-To for installing and using? Took a break from searching to post this but, looking some more!

And the link Nic posted just wants to take me to the SW Download. I, for one, did not know SW had an integrated TFTP server.

Open tftp server