Distributing Across A Network 1

[boggg1]

I have many users using many PC's (and no one to one correlation of users with PC's). The IT department will distribute my installation script (which installs a Visual Basic program) across the big corporate network (using SMS). The components are stored on a server (so no file copying to individual PC's is necessary).

1) Should the script be run once per PC or once per user and why ?

2) Does your answer to 1) mean that is the only way to do it or does it mean that is the preferred way to do it ?

Thanks.

Boggg1

 

[CasperTFG]

1) If you are using an installation script (i.e. vbs) that you made then once per PC. If it is using Install Sheild or some other installer, then you can set it to be installed per user or per PC.

2) There are many ways to do this...

How does your program interact with the server? DCOM? If so you need to set up DCOM security to allow users to interact with the application.

Casper

There is room for all of gods creatures, "Right Beside the Mashed Potatoes".

 

[boggg1]

Thanks Casper

I have been using Inno Setup and my installation works if I simply run the setup on one PC. Every user who uses that PC can use the program (and therefore must be using the components). In this case the .exe (where I can update it easily) is on the network but the (unchanging) components are on the PC. I have been asked to put the components on the network and I am far from being convinced this is a good idea - but I will try.

I cannot yet see in Inno Setup how to determine whether the installation is per user or per PC. Surely the two methods register the components in a different part of the registry as components are available under different conditions - either on certain PC's or to certain users ?. So how does Inno Setup determine where the registration occurs ?

DCOM - well beyond me at the moment. Is this COM but across a network ? I guess I need the IT department to sort this do I ? Are components on the network a big issue ? I don't want to become a network expert at this time but I will do what I have to do, of course.

If DCOM is a big issue would it be simpler for me to go back to IT and say leave the .exe on the network but put the components on every PC ?

Boggg1

 

[CasperTFG]

As far as install per user and per computer... the only difference is where you put shortcuts and if you keep settings in the registry where they are kept, but that again is program level so not to be concerned with.

Basically what I am saying is. Once you register a DLL on a system it is registered for all users. The install user/computer option only makes a difference for where shortcuts to the application are placed.

Casper

There is room for all of gods creatures, "Right Beside the Mashed Potatoes".

 

[boggg1]

Thank you, that's a key thing to know. I will contemplate the consequences early next week. Have a star or two and a good weekend.

Boggg1