samba - Apr 2002 - Checking installed software on Windows boxes

On Tuesday 16 April 2002 13:39, you wrote:
> At 12:34 16/04/2002, you wrote:
> >    The main thing we're getting out of the PDC is the ability to
run a
> >     script upon login to track installed software on PC's.
>
> Good Idea to check the installed software on PC's with a script logon.
>
> Could you give me more information on this script? Is it working? How it
> get info from the PC's?
   Unfortunately the script itself is not what is doing the real work.
   When someone logs onto the NT machine, a drive is mapped the startup 
script runs a commercial package (Track-It! 4.0) on the client, which then 
pushes the information onto the NT PDC.
   This solution has a few problems:

   The script only runs when users log into the PDC.  Some users never turn 
off their computers, so the script never gets run.  Also, some users have not 
been set up to log into the PDC, and instead they log into their own PC's.
   A better solution would be to allow an update of installed software upon 
demand, but that solution was much more costly ($4000 as opposed to about 
$400).

   I wouldn't recommend the current solution we're using, since
there's no
way of guaranteeing that the information required gets gathered in a timely 
manner.

        - Chris

Chris Knadle
cknadle@aeroflex.com

Thank You

It will help. In my network, all users logs into the samba PDC every day. I
think it could work.

I will search for (Track-It! 4.0)

Roberto 

At 16:30 16/04/2002, you wrote:
>On Tuesday 16 April 2002 13:39, you wrote:
>> At 12:34 16/04/2002, you wrote:
>> >    The main thing we're getting out of the PDC is the ability
to run a
>> >     script upon login to track installed software on PC's.
>>
>> Good Idea to check the installed software on PC's with a script
logon.
>>
>> Could you give me more information on this script? Is it working? How
it
>> get info from the PC's?
>
>   Unfortunately the script itself is not what is doing the real work.
>   When someone logs onto the NT machine, a drive is mapped the startup 
>script runs a commercial package (Track-It! 4.0) on the client, which then 
>pushes the information onto the NT PDC.
>   This solution has a few problems:
>
>   The script only runs when users log into the PDC.  Some users never turn 
>off their computers, so the script never gets run.  Also, some users have
not
>been set up to log into the PDC, and instead they log into their own
PC's.
>   A better solution would be to allow an update of installed software upon 
>demand, but that solution was much more costly ($4000 as opposed to about 
>$400).
>
>   I wouldn't recommend the current solution we're using, since
there's no
>way of guaranteeing that the information required gets gathered in a timely 
>manner.
>
>        - Chris
>
>Chris Knadle
>cknadle@aeroflex.com
>
>-- 
>To unsubscribe from this list go to the following URL and read the
>instructions:  http://lists.samba.org/mailman/listinfo/samba

> -----Original Message-----
> From: Chris Knadle [mailto:cknadle@aeroflex.com]
> Sent: Tuesday, April 16, 2002 12:30 PM
> To: samba@lists.samba.org
> Subject: [Samba] Checking installed software on Windows boxes
> 
> 
> On Tuesday 16 April 2002 13:39, you wrote:
> > At 12:34 16/04/2002, you wrote:
> > >    The main thing we're getting out of the PDC is the 
> ability to run a
> > >     script upon login to track installed software on PC's.
> >
> > Good Idea to check the installed software on PC's with a 
> script logon.
> >
> > Could you give me more information on this script? Is it 
> working? How it
> > get info from the PC's?
> 
>    Unfortunately the script itself is not what is doing the real work.
>    When someone logs onto the NT machine, a drive is mapped 
> the startup 
> script runs a commercial package (Track-It! 4.0) on the 
> client, which then 
> pushes the information onto the NT PDC.
>    This solution has a few problems:
> 
>    The script only runs when users log into the PDC.  Some 
> users never turn 
> off their computers, so the script never gets run.  Also, 
> some users have not 
> been set up to log into the PDC, and instead they log into 
> their own PC's.
We have the same issues-what about using the Windows Sheduler
on the Win9x PCs, NT's at, and Win2k's Task Scheduler on the
PCs to run the script instead?  As long as they're
authenticated to the samba server (logged in, wkstn locked?)
it might work for you.  Watch out for running the script
against a mapped drive-I found out Win2k's backup won't
run if the user is logged out, due to the un-mapping on
logout.  Setting the backup location to the UNC works fine.
e.g. u:\\-backup-\diff.bkf fails, unless logged in;
\\server\user\-backup-\diff.bkf works logged in/not logged in.

Jim
>    A better solution would be to allow an update of installed 
> software upon 
> demand, but that solution was much more costly ($4000 as 
> opposed to about 
> $400).
> 
>    I wouldn't recommend the current solution we're using, 
> since there's no 
> way of guaranteeing that the information required gets 
> gathered in a timely 
> manner.
> 
>         - Chris
> 
> Chris Knadle
> cknadle@aeroflex.com
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>