Guido Where I work we have a small/medium installation of about 1400 pcs. We use GP for installation of programs that are .msi
However this method work extremely well with a high success rate and 100% monitorised (unlike GP). We use it with success to update the antivirus signatures daily. We also use it to update service packs at weekends as we have many offices with low bandwidth. We have an inventory database of the PCs. There is a field that contains a random number that is generated daily. We use this to order the software installation. Basically what we do is the following run a script that 1.Loop through pcs 2. get the name of the targets from a database. 3. If software not installed then 4. if pc online (ping it) then 5. Install software 6. Write installation information to database 7.Next Regards Peter Jessop On 7/20/05, Grillenmeier, Guido <[EMAIL PROTECTED]> wrote: > well, I could think of many more drawbacks using this option... > > don't get me wrong - psexec is cool. But I don't really see it as an > option to deploy software to many clients of which usually a certain > percentage is remotely connected or offline. So you'd have to build > your own little framework to ensure availablity of the clients and > successfull install of the app etc. The success naturally depends on > your client landscape > > /Guido > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Peter Jessop > Sent: Dienstag, 19. Juli 2005 17:50 > To: ActiveDir@mail.activedir.org > Subject: Re: [ActiveDir] Logon script with Admin rights > > There is simple way of doing this that works if > a) the .exe has a quiet option (-q for example) with no gui output > b) it is not necessary to install the program from a logon script > > > Simply install the program from another machine using psexec.exe > i.e > logon remote machine with sufficient privileges and run > psexec -c \\remotemachine "install.exe -q" > where install.exe is the installation program > > This method has several advantages if you put it in a script > 1) It can easily be extended to install over a range of computers > 2) You can get feedback as to whether it has installed or not. > > As Rick points out preparing .msi files has it's drawbacks, not least > of which is access to a clean machine to prepare it on. > > > Regards > > Peter Jessop > List info : http://www.activedir.org/List.aspx > List FAQ : http://www.activedir.org/ListFAQ.aspx > List archive: > http://www.mail-archive.com/activedir%40mail.activedir.org/ > List info : http://www.activedir.org/List.aspx > List FAQ : http://www.activedir.org/ListFAQ.aspx > List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ > List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
