Fat client hell - put files on file server?

[Nananana]

Hi.
I have a Client/Server solution installed on a customer's site.
Some of the client SW is an ISV's product.
Some additional files are provided by us (another ISV).
It's mainly some EXEs and XML files.
I hate the thought of updating 40+ PCs with every change in the SW.
I'm not sure it's feasible, so I ask -
What would be the implications of placing the EXE and XML files on a
shared file server?
Performance - would the file copied to the local PC before execution?
Any other thoughts?
TIA

 

[Haggis]

Hi.
I have a Client/Server solution installed on a customer's site.
Some of the client SW is an ISV's product.
Some additional files are provided by us (another ISV).
It's mainly some EXEs and XML files.
I hate the thought of updating 40+ PCs with every change in the SW.
I'm not sure it's feasible, so I ask -
What would be the implications of placing the EXE and XML files on a
shared file server?
Performance - would the file copied to the local PC before execution?
Any other thoughts?
TIA

at our company , we made a small program for the local computers that looks
to see if certain files were updated (and copies them from the server)
before running the program.

then you just place the updated file on the server and the next time the
program is run , it will grab the new files

 

[Nananana]

at our company , we made a small program for the local computers that looks
to see if certain files were updated (and copies them from the server)
before running the program.

then you just place the updated file on the server and the next time the
program is run , it will grab the new files

Thanks.
I like your concept.
Another concern is minimum changes in the applications, so -
1. It's a general solution
2. It will not bother the very busy programmer.
Please note - there are 2 apps already installed on all the client PCs.

How about this:
1. Current situation: The applications are on each client under
c:\program files\<application>\bin
2. On a shared file server, whenever there are new files to install,
I'll put them in x:\update\program files\application\bin
1. For each client, Add an "update.cmd" to the startup folder
2. "update.cmd" will xcopy files from x:\update to c:
So whenever I have new files to distribute, all the user should do is
re-boot.

Problem: How would I know all the clients are updated, and I can remove
the files from the server?
(Even though no harm is done if the files are copied again)
TIA

 

[NoStop]

Thanks.
I like your concept.
Another concern is minimum changes in the applications, so -
1. It's a general solution
2. It will not bother the very busy programmer.
Please note - there are 2 apps already installed on all the client PCs.

How about this:
1. Current situation: The applications are on each client under
c:\program files\<application>\bin
2. On a shared file server, whenever there are new files to install,
I'll put them in x:\update\program files\application\bin
1. For each client, Add an "update.cmd" to the startup folder
2. "update.cmd" will xcopy files from x:\update to c:
So whenever I have new files to distribute, all the user should do is
re-boot.

Gawd, one has to reboot too often as it is with this toy operating system.
Now you want them to have to reboot before running an app? That's just
nuts.

Problem: How would I know all the clients are updated, and I can remove
the files from the server?
(Even though no harm is done if the files are copied again)
TIA

--
WGA is the best thing that has happened for Linux in a while.

The ULTIMATE Windoze Fanboy:

http://video.google.com/videoplay?docid=-2370205018226686613

Is this a modern day equivalent of a Nazi youth rally?:

http://www.ntk.net/media/developers.mpg

A 3D Linux Desktop (video) ...

View Some Common Linux Desktops ...
http://shots.osdir.com/

 

[Nananana]

Gawd, one has to reboot too often as it is with this toy operating system.
Now you want them to have to reboot before running an app? That's just
nuts.

No.
Only when update is required.
It can be every, say, 3 months.