logon scripts

There is a small reward if someone provide the right solution.

If the w/s is already loaded with the antivirus s/w or update then it shouldn't run.

There was a server based solution for deployment of Dr.Solomon's/Mcafee called Total Virus Defence Management Edition. It worked pretty well and allowed you to 'push' the software on to your PCs. However I think it's been superceded by a new technology called VirusScan ASaP. You can try it free here: http://www.mcafeeasap.com/content/virusscan_asap/default.asp

Hope this helps.

We are users of MaCfee ASAP and Netshield.
MaCfee ASAP is used on all client workstaions and works great. Check it out rorycarlin@hotmail.com is listing the download.

Well, here is my thought:
YOu could copy the entire installation CD for your virus software into the Netlogon share of your PDC. I would have the root of the CD in the Netlogon share itself, so the path to Setup.exe would be \\PDCSERVER\NETLOGON\Setup.exe
Ok, next, add these lines to the logon scripts used by your Administrators:

IF EXIST "c:\program files\VIRUS_SOFTWARE_NAME\PROGRAM.EXE" goto VIRUSFOUND
ECHO Virus software NOT installed. Installation will proceed.
CALL Setup.exe

EXIT

:VIRUSFOUND
echo Virus software already installed. Quitting.
pause
EXIT

See? In the IF EXIST line, you will scan the local computer for a file that is only installed in the directory that is created by the virus software. If that file does NOT exist, then you call a routine that will CALL the Setup.exe program for the virus software (or Install.exe or whatever program starts the installation for the virus software).
For example, I use McAfee Netshield. So, I would run IF EXIST "c:d:\program files\network associates\netshield nt\mcconsol.exe"
For you, put in whatever directory and main EXE that your virus software has.
Now, a word about the quotation marks. Since the directory Program Files is NOT in the old fashioned 8.3 namingconvention, a logon script would have problems reading it. So, put the whole line between quotes, and then it will run fine.

Last thing: NT/2000 will not allow a normal user to install something like a virus software. Most of them check for userrights to install programs on the local machine. So, to avoid changing your users rights just to do this, set up the logon scripts your Admins use. Have them go to each workstation, log in, and the install will start if it is needed.

Hope this helps.

Hi Charles.
The latest version of Total Virus Defence is called Active Virus Defence and has a tool called ePolicy Orchestrator. This replaces Management Edition and allows you to roll out installs and updates to your users, The setup can be run Silently or Overtly. For NT\2000 the RunAs commands can be used to avoid the permissions problems.
If you want to control your own updating, What you need to do is create a user called !AVService and give this user 'Log on as service rights' with Domain Admin privileges then create a hidden share called AVUPDATE$ on a server then set the permissions to 'Full Control' to Domain Admins and the !AVService and 'Change' to the user group(s) your users are in, Remove the Everyone permission. At each WSor on install give the Anti-Virus services this user name as the log-on name.
Then use the Dats & Superdat from NAI,s website, These are downloaded daily (01:00 GMT) using a scheduled batch file and a ftp script to the hidden network share, Which is also available on our inhouse FTP server (IIS) for the automatic updating ( from the AV console). The batch file deletes previous versions and renames the new Sdatnnnn.exe but leaves the Sdatlog intact. Every WS is set to update either at service start up (NT\2000) or at middday (Win 9x). Then weekly (Fri pm) a scheduled task is set on each WS to run the Superdat (renamed to dat.exe) in silent mode, (\\SERVER\avupdate$\dat.exe /s) this ensures that the scan engine is updated at least weekly. If your mail server is using Groupshield then run the dat.exe daily on the mail server as this ensures that the GS files are updated ( the dat,s do not update Groupshield).

Chris Hirst

This question was auto closed due to inactivity