As if the past few years of hell dealing with AVAST bugs and lack-of-support weren’t enough…
Someone decided to change the support system over the weekend…deleting my account and tickets. There’s so many words I want to use in describing how pathetic this is…but I’m trying to have restraint. The current ticket was because of a bug in your program that your team was having trouble figuring out. I know you don’t care, but we need it fixed or we cannot use your product.
Anyway bellow is a short reply to your problem :
Task name can be any windows string, even “This is My very first Custom scan” :o)
As for the ashCmd.exe:
when using named non-interactive scan (/@= “task name” parameter), all parameters should be defined in the particular task. It means that ashCmd will always ignore the last part of that command (/r=C:\AVTest.txt) and use report file settings defined in “test Scan”.
2.) if avast5.ini doesn’t contain a task named “Test Scan”, “Test scan”, “test Scan”, nor “test scan”, then the client, (not the console) will always report “Following task is not known” error. The task must be visible in avast5.ini and in the client ui.
3.) To copy a scanning task job configuration to the particular client, you have to specify that computer as a job target first. Creating a task in the console is simply not enough, you have to let the client know that it can (and it should) use it.
@Everyone - Thanks but I had to completely remake this account this morning. Never got new emails about my ticket and show none of my past tickets on this account. No links work to get there. I emailed a reply to my old response in hopes this can get pulled from an archive or something.
@Lukas - Thank you. #1&3 are not news, but I’ve only done the smallest amount of “messing with” the INI file (only changed the server during a migration).
On the server that hosts the Small Office Administration, we have a simple “Test Scan” job setup to target my workstation. The only point of this is to test the ashCMD functionality. On my workstations INI, it does have the test job added in (BUT that could be from when I first setup the job and clicked run to make sure it communicated). Now the server itself’s INI file doesn’t have the job, but it was never a target of this job so I think that’s normal.
I get the error that the job wasn’t found. I tried every variation of upper/lowercase on the T and S (all screenshotted and added to that lost ticket…) but no luck.
Can anyone think of something I’m missing here? Do I need to add it to the local .INI even though it’s not running on the local machine? The command does work with “Quick scan” just not with custom jobs.
I’d appreciate any further assistance if possible, as I’m not feeling too great about this ticket situation. I would assume I’m in the wrong forum area also, so if a moderator or someone wants to move this, I would appreciate it.
As much as I want to curse and scream out how dumb this is…
Thank you all regardless for assisting me on this matter.