Business products v7 release

[lukas.hasik]

Hi,
the avast7 wasn't tuned up for the Itanium... The best option for now will be to manage the servers with "old" 4.8 ADNM and leave the 4.8 clients on it. The rest of network can be anaged with new EA and client of v7.
We will have to start up our old Itanium server and tune up the v7 clients.

Thank you

[jvasic]

Thank you for your quick response. We already uninstalled old database and old ADNM console because we couldn't make it work together with new database on the same pc. But it won't be a problem, we will install standalone old clients on our five servers and make them update directly through internet from Avast servers until you come to a working version of v7 clients on Itanium servers. Thanks again!

[jvasic]

We have another problem with deploying EPS to our client computers with old agents. When we started deployment task from new AEA Console everything went ok only on 35 from 105 clients. On 90 clients we have errors reported and when we try to deploy new client application from console separately on any of those Windows XP computers same error occurs - access denied. We had similar error on first install several years ago but we solved them by deploying .msi installation package via windows server group policies. Problem is that now from AEA Console when we generate setup package we get only .exe file and we can't use it for deploying via GPO's. Is there a way to create or download from somewhere .msi installation package for EPS managed client application?

[wpn]

maybe you can look into login scripts (batch files? vbs files?) which can start running executables at computer startup?  its an awkward way but u could look into it to test.  Having it run with administrative rights ofcourse

[nannunannu]

maybe you can look into login scripts (batch files? vbs files?) which can start running executables at computer startup?  its an awkward way but u could look into it to test.  Having it run with administrative rights ofcourse

This was actually my preferred way to deploy...  Modified a batch file to uninstall components from the previous AV software before launching the .exe installer for Avast!  Used DesktopAuthority to launch the batch file as administrator - worked like a champ.