Jump to content

tbma

Member
  • Posts

    18
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by tbma

  1. I am using 2 very simple tiny wrappers by Oleg_Sch.

    hidcon.exe (2kb) - runs command line apps or cmd scripts hidden. Command line is the name of the application or script and it's parameters. For example "hidcon.exe adduser.cmd username password".

    msistub.exe (2.5kb) - runs msiexec.exe with specified .msi file. eq. "msistub MyApp.msi /qb!-" = "msiexec /i MyaApp.msi /qb!-".

    Both programs have only one command line switch - "-nw", That means NO WAIT. By default they are waiting for lauched programs/scripts to finish.

  2. OK, You can use quotes when adding registry but for everything inside the the main set of quotes (the first and last quote) you have to add two " instead of the one. Ancient programming trick from the Spectrum coming in use again :D

    You can also escape it using \"

    Something like

    REG ADD %KEY%\015 /V 1 /D "%CDROM%\INSTALL\WSFTP\WS_FTP.exe -s -f1\"%CDROM%\INSTALL\WSFTP\wsftp.iss\""
  3. In any case, resolution is simple: Install MS Antispyware BEFORE you install those other apps. Setting the install to kick off earlier in the RunOnceEx.cmd is a 30 second job.

    Jason

    It creates short name every time it creates a file, not dynamically. So they will be named in order of creation.

    On my machine for example:

    MICROS~3    Microsoft ActiveSync

    MICROS~4    Microsoft AntiSpyware

    MICROS~1    microsoft frontpage

    MICROS~2    Microsoft Office

    How about even simplier resolution? Just use long names? DOS is officially dead at least 5 years now ;)

  4. I don't tend to quote myself, but this, my friend, works perfectly for me *every* time. I have the absolute newest, truest, bluest version of MSAS and the same setup that worked 6 months ago works fine today.

    Jason

    This will work, unless somebody have folders named "Microsoft blah-blah etc." in "Program Files" already (i.e some other Microsoft products installed).

    In that case "Progra~1\Micros~1" will point to some other place, and this installation will fail... with error 101.

    /offtopic on

    Is anybody experimented with MsAS command line switches?

    I have found -LaunchMode N (where N is a number), as well as known switches -scan -withui -withreultui,

    but but I haven't figured out -schedule yet.

    /offtopic off

  5. Starting with version 10.0.1 processing of the Auto-Created Scans can be disabled by setting DWORD value "StartupScansEnabled" in "HKLM\Software\Intel\LanDesk\VirusProtect6\CurrentVersion\AdministratorOnly\General" to 0.

    Scans still will be created, but will be disabled.

    reg add HKLM\Software\Intel\LanDesk\VirusProtect6\CurrentVersion\AdministratorOnly\General /v StartupScansEnabled /t REG_DWORD /d 0 /f

    p.s. all this is for the unmanaged clients, - with managed clients same parameter can be set from the Server Console.

  6. The most significant new feature in 10.0 that differs from the 9.0 is "Tamper Protection", where AV will fight any programs (viruses) that are trying to damage it's registry or files.

    After I've seen some viruses, that eat AV's from the inside and leave happy "pretend that I'm working" shell - any question for me about migrating to 10.0 disappeared.

  7. Not certain, but that key looks like it pertains to the new built-in MS Security Center. I kdon't know if the mesagge box that pops up is from the security center or from Symantec! If it is MS, then that would work also.

    Message pops up from the Symantec AV itself, when filedate of the virus definitions in the installation differs from current date for more than 30 days.

    You can disable it either

    • setting date back before installation, and returning it back after LiveUpdate.
    • Or constantly updating definitions inside the installation.
    • Or using a method I described here.

    Fist do the test install.

    Then run

    reg query "HKLM\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion" /v PatternFileDate

    it will display something like

    ! REG.EXE VERSION 3.0

    HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion
       PatternFileDate     REG_BINARY      2305160000000000

    Grab that long number (it's a filedate of the definitions installed) and insert it into your installation script.

    Something like

    reg add "HKLM\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion" /v NoWarnPattern /t REG_BINARY /d 2305160000000000 /f

    Running this before installation will supress the warning.

    In either case it requires running and cmd file before and after, which is a bit of a kluge and inelegant, even if it works.

    p.s. With this method there is no need to mess with the system dates, and remake your install every month (which looks very elegant to me;)). And since you will need to run cmd commands anyway if you want to get rid of the "AutoCreated Scan", - I see no problem adding some more.

    Just hide the black ugly cmd windows (there is plenty of tools available) and it will look very elegant. ;)

    I am running all this from the 7zip SFX using StartX

    ;!@Install@!UTF-8!
    RunProgram="StartX.exe /B /WAIT \"install.cmd\""
    ;!@InstallEnd@!

    and cmd window never shows up.

  8. If the values dont exist either add them or ensure that they exist

    running

    setlocal enableextensions

    will enable them from the .bat file

    p.s. try `dir "%ProgramFiles%\a*" /b/s` or even better `dir "%ProgramFiles%\a*.exe" /b/s` ;)

  9. Unfortunately they will not, if we are talking about just applying the keys to HKCU.

    Well, in some cases HKCU tweaks may not "stick" when applied at T-12. Are you saying this is the case with doscan.exe prevention? Have you tried importing at T-12?

    Honestly I haven't tried it with cmdlines.txt.

    I am interested in one unified way to install the app not only at T-12, but also on already installed boxes (XP and w2k workstations that is).

  10. here it is

    call :ReadReg ProfilesDirectory
    for /f "usebackq delims==" %%i in (`echo %TMP1%`) do set TMP2=%%i
    call :ReadReg DefaultUserProfile
    set TMP1=%TMP2%\%TMP1%

    if exist "%TMP1%" (
      reg load HKU\default "%TMP1%\NTUSER.DAT"
      reg add "HKU\default\Software\Intel\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks" /v CreatedUserQuickScan /t REG_DWORD /d 0x1 /f
      reg add "HKU\default\Software\Intel\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks" /v CopiedDefaultScanOptions /t REG_DWORD /d 0x1 /f
      reg unload HKU\default
      )
    set TMP1=
    set TMP2=
    goto :eof

    :ReadReg
    rem *** single tab here between == and "
    for /f "usebackq tokens=3,3* delims== " %%i in (`reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" /v %1 ^| find "%1"`) do set TMP1=%%i
    goto :eof

  11. sleepnmojo is correct. No need to mess with HKU.

    Either way the settings will apply to all users.

    Unfortunately they will not, if we are talking about just applying the keys to HKCU.

    Try to create a new user and he will get the auto generated scan as soon as he logs in.

    Universal automated way of determining the "Default Profile" folder is not trivial, but I have a solution as you may know :hello:

  12. I tried adding the CreatedUserQuickScan to HKU\.DEFAULT\Software...etc but it didn't affect new users logging in on the machine - they got the auto generated scan for their first logins until the login script command I set up deleted it from their HKCU....

    You need to add 2 keys, imho.

    reg add "HKU\.DEFAULT\Software\Intel\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks" /v CreatedUserQuickScan /t REG_DWORD /d 0x1 /f
    reg add "HKU\.DEFAULT\Software\Intel\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks" /v CopiedDefaultScanOptions /t REG_DWORD /d 0x1 /f

    adding those 2 in installation script to HKCU, before running MSIEXEC, would disable autocreation alltogether.

  13. This is only a temporary solution.  You need to add the key I specified in post 43 of this thread.  When SAV doesn't see it, it will create the startup scan.  The Symantec solution is similar, but adds an extra key, which isn't really needed.

    Many Thanks!! I've added the line below following your recommedtations as the last line and it dit the trick. :)

    reg add "HKCU\Software\Intel\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks" /v CreatedUserQuickScan /t REG_DWORD /d 0x1 /f

  14. My version of install.cmd ;)

    rem * Supress annoying warning about outdated virus definitions until nex update. Number is a definitions date, and depends 
    rem on you current installation. Can be taken from HKLM\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion\PatternFileDate
    rem after test install.
    reg add HKLM\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion /v NoWarnPattern /t REG_BINARY /d 23030C0000000000 /f

    rem * Installing all components except LotusNotus Auto-Protect. Enabling "Tamper Protection".
    start /WAIT msiexec /i "Symantec AntiVirus.msi" /QB!- RUNLIVEUPDATE=0 SYMPROTECTDISABLED=0 ADDLOCAL=SAVMain,SAVUI,SAVHelp,EMailTools,OutlookSnapin,Pop3Smtp,QClient

    rem * Launch silent LiveUpdate for virus definitions.
    start /WAIT "" "%programfiles%\Symantec Antivirus\VPDN_LU.EXE" /s

    rem * Removing auto-created startup scan to avoid high CPU usage.
    reg delete "HKCU\Software\Intel\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks" /f

×
×
  • Create New...