Thanks Howard.. I didn't have time to look over the script too closely, but it makes more sense now. I didn't see it, but do you check to see if VirusScan is disabled? I've found many users have found tricks to run programs in such a way that it causes VirusScan to be disabled. Occasionally, it will never work again, so even if it's installed, it's dead in the water...

I notice a lot of hard work done in scripting for VirusScan... as for my sitution, these are the parameters I have to work with:

1. VirusScan 4.5 SP1 is deployed.. 4.5.1 SP1 causes problems with running autoupdate in the runonce or during the logon script (I still haven't figure out why)

2. DAT updates are done daily (random) via internal ftp.

3. SDAT updates are done monthly.. also, using this method, we can deploy ANY setup.exe file that I can create.. this is kind of a strange way to do it, but it can be used to install programs without the user having admin rights in NT/2000.

4. Lots of other things happen in the logon script. Here are some:
a. checking drive space
b. running software auditting tools
c. doing IE updates
d. special dial-up section
e. updating McAfee settings/file extensions
f. copy kixtart files to windows 95

Anyway, I'm still working on it.. bound to figure it out sometime.

Brian