per my previous comment in the original thread, VSS is NOT a configuration management tool. It is a version control tool. Very different animals. VSS lacks many of the components and features required to make it a true configuration management tool.
Version control is a sub-topic within configuration management. It is very similar to "testing" being one aspect of QA.
More than just version control, configuration management includes all the administrative controls and processes that are in place to identify, evaluate, control and track change. And it it is not limited to just code. Configuration management, in addition to source code control, also covers things like requirements, documents, test scripts, etc. That includes even the SDLC processes themselves.
Stripped down to it's essentials, configuration management is about what you are going to do when a change is suggested. Who evaluates the change? Who approves the change? Who tracks the change? How is the change implemented?