Jump to content

tbma

Member
  • Posts

    18
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About tbma

Contact Methods

  • Website URL
    http://

tbma's Achievements

0

Reputation

  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. There is a very nice version of the 7zip SFX module, and a tiny utility (by the same author) to hide command window. I don't know why the author is so shy to show it to the ppl, but some of us are using it for a long time already. http://unattended.solta.ru/
  3. You can also escape it using \" Something like
  4. 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: How about even simplier resolution? Just use long names? DOS is officially dead at least 5 years now
  5. 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
  6. Huh?? How to automatically update Symantec AntiVirus Corporate Edition definitions without using LiveUpdate... with the batch files.
  7. 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.
  8. 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.
  9. 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. 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.
  10. 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`
  11. 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? <{POST_SNAPBACK}> 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).
  12. 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
  13. 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
  14. 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.
×
×
  • Create New...