Re: installing client side proxies

Thanks Andrew.  Your option 3 is my original plan.  I will take a look at=

deploying them using Active Directory and GPOs.  I do not have much knowl=
edge
of either, so it is time to learn!


>-- Original Message --
>Date:         Thu, 17 Oct 2002 14:07:36 +0100
>Reply-To:     Technical discussion of VBCOM <[email protected]>
>From:         Andrew Gayter <[email protected]>
>Subject: Re: [VBCOM] installing client side proxies
>To:           [email protected]
>
>
>We use .MSI packages and deploy them using Active Directory and GPOs
>This kind of deployment will result each Windows Installer on each
>client invoking the .MSI file from a shared directory on the server.
>
>Other techniques rely on ghosting, or taking images of OSs that have the=

>package installed. You can then push out the configuration onto client
>machines.
>You could configure your client's logon scripts to run the install, but
>you will need to make sure it only runs once.
>
>-----Original Message-----
>From: Technical discussion of VBCOM [mailto:[email protected]]
>On Behalf Of Greg Robinson
>Sent: 17 October 2002 12:05
>To: [email protected]
>Subject: Re: [VBCOM] installing client side proxies
>
>I am using Windows Installer.  I create a MSI file and then run the
>SetUp.
>
>
>Maybe I do not fully understand what else it can do for me though as I
>do
>not have much expierence in the Installer world.  I do not want to have
>to deploy a setup file that all my clients need to run.
>
>
>>-- Original Message --
>>Date:         Thu, 17 Oct 2002 09:02:16 +0100
>>Reply-To:     Technical discussion of VBCOM <[email protected]>=

>>From:         Andrew Gayter <[email protected]>
>>Subject: Re: [VBCOM] installing client side proxies
>>To:           [email protected]
>>
>>
>>Windows Installer and Active Directory/SMS will do what you want.
>>
>>-----Original Message-----
>>From: Technical discussion of VBCOM [mailto:[email protected]]
>>On Behalf Of Greg Robinson
>>Sent: 16 October 2002 14:07
>>To: [email protected]
>>Subject: [VBCOM] installing client side proxies
>>
>>I have always had control over my clients (usually just another server)=

>>when using DCOM.  On my current project, I do not.  We developed a DCOM=

>>Object that will run on a server that hundreds of clients will remote
>>to.
>> I exported a client side proxy that we run locally for testing.  I
>>would
>>rather not have to ask hundreds of clients to run the setup file on
>>their
>>workstations.  I would like this to be invisible to them.
>>
>>Is there a way I can 'hide' this or 'install this for them' without
>>their
>>knowledge?  Our exe also runs on their workstations and we do monthly
>>updates.
>> I was thinking of adding some script that shells out to the set up
>>program
>>and runs it for them.
>>
>>
>>
>>
>>
>>
>>Greg Robinson
>>Director of Training and .NET Technologies
>>Scribble Software and Training
>>www.scribblesoftware.com
>>www.scribbletraining.com
>>
>>You can read messages from the VBCOM archive, unsubscribe from VBCOM,
>or
>>subscribe to other DevelopMentor lists at http://discuss.develop.com.
>>
>>You can read messages from the VBCOM archive, unsubscribe from VBCOM,
>or
>>subscribe to other DevelopMentor lists at http://discuss.develop.com.
>
>
>
>Greg Robinson
>Director of Training and .NET Technologies
>Scribble Software and Training
>www.scribblesoftware.com
>www.scribbletraining.com
>
>You can read messages from the VBCOM archive, unsubscribe from VBCOM, or=

>subscribe to other DevelopMentor lists at http://discuss.develop.com.
>
>You can read messages from the VBCOM archive, unsubscribe from VBCOM, or=

>subscribe to other DevelopMentor lists at http://discuss.develop.com.



Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.