[se7engreen]

I'm stuck on this one.
I am trying to help a small company with a number of projects and one of those projects is deploying a custom written program to about 35 windows pc's (2K, XPpro). The only domain controller is a Win2K server and I could assign this MSI through group policy, but the company programmer produces a new MSI package weekly with slight changes. I guess I'm looking for any way to automate the weekly update without having to re-assign the new package in group policy.
Any advice is much appreciated.
Thanks

[Phurious]

Quite possibly a dumb question...have you considered using a log-in script to call the package from a share on the server? In this case you could just swap the msi out week to week as the different builds are developed.

[se7engreen]

I have considered that but the problem with that is the newer MSI will not overwrite the older one. The way the MSI's are currently, the older version needs to be uninstalled before the new one can be installed. The work-around for this right now is a logon script copies the new executable and all needed *.dll's to the users drive. They would like to handle this differently because of some performance issues related to the program.
Not a dumb question at all, you're just being logical
If the programmer could create MSI's that would upgrade the previous versions that would be a great solution, but I don't know what is involved in that process because I don't do programming.
Thanks for your response!