Windows Server 2003 - Dev/Staging/Production environment

[dave2korg]

I have been tasked with creating an environment for the web developers at my company to effectively develop, stage and then push to production a few of our corporate websites. Currently we have a dev/staging server and we use a robocopy script to push to live. This process worked well when we only had 1 web programmer/developer, but now that we have multiple we are lacking accountability and flexability.

The development server is internal on the domain, the production webservers/webservices sit on an outside network and are not part of the domain but developers have credentials for the them.

What we would like to do:
Site goes to dev server for changes, developer pushes site to staging for testing (would like to be able to log who did this), after approval site gets pushed to live.
I would like to do this without having to code any username/password into the site code. Also, have login scripts that will map drives for the developers from their desktops to the staging and production servers.

I know its possible, I figured I would ask around here for the best way to do it with scalability in mind. Also, if this is not the right area for the topic please go ahead and move it.

Thanks!

David M.
A+, Net+, Security+, CCNA, CNE