Keeping track of how many times a network app gets installed

[guru533]

Is there a program out there that will let me track and control how many times a network application gets installed. I would also like the application to recognize only unique (users) installs, but I know that might be asking for too much.

 

[chriseubank]

The best thing to do is write a batch file to write a "lockfile" to a temporary directory under the same folder structure, then use an "if exist" test to see if it's already been installed... then you can append the output to a logfile using environment veriables (%username%) .. i've done this a few times and it works like a charm! The only thing is, you need to have the users run the batch file and not the executable. The only other way around this is to have the batch file constantly rename the executable's extension back and forth to something that the users don't recognise as an application

Good luck,

 

[MikeKap]

One program that would help you is SysTrack. Among many other things, SysTrack monitors changes to inventory and writes all changes to a log. Every time the application gets installed, upgraded or removed you would see this activity. These actions can be set up to alert you (or your help desk) via page, pop-up, e-mail, SNMP alert, etc. You could also generate a report of this activity, online or batch, and have it exported to HTML and posted to a website. As mention, SysTrack does much more than this and runs on any Windows machine (desktop, server or terminal server).

Mike
Kapski@yahoo.com

 

[DanMc]

Both the above answers are good. There are two approaches. 1: control who can install. 2: detect who has installed afterwards.

2 is easier, but never secure and foolproof.
1 can be easy, but is hard if you want to make it secure and foolproof. Some people do a combination of both approaches.

I use a form of 1. We have WinXP clients that are members of a Win2k domain. We use Group Policy to assign STARTUP, LOGON, LOGOFF, and SHUTDOWN scripts. The STARTUP and SHUTDOWN scripts run as the computer SYSTEM account, which means they have a different set of rights (basically admin). The LOGON and LOGOFF scripts run as whoever is logging on to the PC at the time. On the Win2k server, you can create a share with the setup files, and grant the computer rights to the share. Users who log on to that computer won't have access.

Win2k server = SERVER
Share \\SERVER\AppInstall
Give READ access to "Domain Computers" or each PC account individually

Create a startup script batch file similar to the following:

@ECHO OFF
IF EXIST "C:\Program Files\App1\App1.exe" GOTO LOG
:INSTALL
\\SERVER\AppInstall\SETUP.EXE
:LOG
IF EXIST "C:\Program Files\App1\AUTHORIZED.LICENSE" GOTO END
NET SEND SERVER "%COMPUTERNAME% has App1 installed, but does not yet have an AUTHORIZED.LICENSE file in for the app. Please install a license file, or uninstall the app"
REM Uncomment the following line to enable automatic install of an AUTHORIZED.LICENSE
REM ECHO This PC is Licensed for App1 > "C:\Program Files\App1\AUTHORIZED.LICENSE"
:END