In a very old post, I explained how to set up your own Subversion server to benefit from storing your scripts in a versioning repository. Certainly when you are working with multiple administrators on one environment, you want to be sure you are using the latest version of a certain script, and be able to roll back to a working version if you or one of your colleagues manage to wreck it.
New environment, and while setting up a new Subversion for our small group of admins, I found out about VisualSVN. Same functionality, but easier to use!
VisualSVN’s main payware product is a plugin for your Visual Studio setup to store your source files in a Subversion repository.
What attracted my attention, though, is their free available VisualSVN Server. This package includes Apache and Subversion, but comes in an easy to use Microsoft Management Console plugin to create, maintain and administer your repositories and supports out of the box AD authentication.
So if you’re running a small group of Windows admins, and never worked with CVS or Subversion, I’d strongly suggest installing VirtualSVN Server on a fileserver-like machine and TortoiseSVN on your workstations to protect your code from any mishaps.