Release/Deployment/Packaging tools for multi-application systems -

in our company have following situation: have several (hardware) systems, each several software applications. however, since hardware different, software different in cases. furthermore, out in field there lots of different version combinations of software.

for example, consider following (simplified) situation:

systems: sys1, sys2, sys3
applications: app1, app2, app3, app4, each different versions

sys1 uses app1 v1, no app2, app3 v3, , app4 v2, while
sys2 uses app1 v1, app2 v2, app3 v2, , no app4, and
sys3 uses no app1, app2 v3, no app3, , app4 v3.

that is, every system uses different set of applications, , different versions of each application. different combination of versions, e.g. app1 v1 used app3 v2 , app3 v3.

currently, manage set of valid software sets manually copying respective releases "internally public" folder accessed field service , production department. however, of time have latest versions available, , hard them of older version sets system.

we change process sort of automated system. there software tools out there can process? thinking of software can set different systems , different software components, create different versions of each, , assign specific software versions specific system versions.

does know software that? or should consider change our packaging/deployment management? btw: how process called "officially"?

to clarify things: use source control, build server, , like. not point, missing step combination of several software components complete package can used service , production. since not use build server software components (yet), think might hard let build server take on job, open suggestions.

edit:
operating system windows (2000, xp, vista, 7, , 7 embedded).
applications written in different languages, c++ , c#, our solution should independent of language, if possible.

i work in large company (thousands employees) , have same version everybody, lot of applications. have pre-production environment, developement environment, , final releases. of course, work java , of our applications webapps, don't have problems our hardware.

i think best environment. same release.