Why is it that my server upgraded to the version 7 client since it is not even a full release and just RC???
Also I just spent half a day debugging a Microsoft Exchange problem and found out that the new version 7 client was causing all my problems.
This is a production environment and my client was without email for half a day. Can someone explain me what went wrong?
Thanks.
The version 7 client has been released. The version 7 management console has not. So your server is acting correctly in upgrading you to the latest released client software.
Can the management console manage client version 7?
The version 7 client has been released. The version 7 management console has not
That hasn’t sense!
All day talking with customers. Clients updated to avast! 7 and SBC saying that the licenses are not valid.
It’s crazy!
If you have problems with the console try to update it using: http://files.avast.com/iavs5x/setup_console_epsp.exe
This updates your console to ASOA 1.2.2.8 and you ABP/ABPP licenses file is valid.
Yes just saw that my license was expired and now no client detected. I reinstall the license, service crash, had to stop with task manager. But still no client detected.
I actually had this problem last week with one specific person. Today, MY computer upgraded to v7 when I told it to “Update Program” in the client interface. And now I have the same problem–NO LICENSE!
So do I have to install the RC admin panel to distribute licenses to v7?
Will clients start auto-upgrading to v7 and then not protect the computers because of this license issue?
This seems very, very bad.
Re-running the deployment from the SBC console at least gives me “trial mode”, so I guess that is the answer for people who get auto-updated for now until we resolve what the next step needs to be.
I would hope that if I’m expected to upgrade to pre-release software because of this issue that it is reasonable stable and will upgrade itself going forward. A lot of times, pre-release software won’t upgrade to the released version because there is “no upgrade path”. If you’re going to force people to install pre-release, there needs to be an upgrade path…
in this case I suggest to everyone to go under Group Policy and set Program update to manual until the console is officially out
You can reapply your license.
I just open an emergency ticket and waiting for an answer.
I think Avast just mess up real good on this one. I hope they fix it ASAP or else I will start looking for an alternative.
So far I was very please with this product but if they start to drop the ball left and right then we will see.
If you have problems with the console try to update it using: http://files.avast.com/iavs5x/setup_console_epsp.exe
This updates your console to ASOA 1.2.2.8 and you ABP/ABPP licenses file is valid.
This is not a solution, they need to fix the problem NOW. I have 10 unmanage clients right now that are suppose to be manage.
This is unacceptable.
So we go with a Beta product to solve a problem they created?
I think this is not a beta, this is the solutions that AVAST Software give me for my customers, and it works!
Yep the RC was 1.2.2.5…
@ phoenixsecure
Yes you’re right, but I think (but I hope more) in a few hours there’s the officialy introduction of ASOA…
What version of ASOA do you install? There are 4 version. I have BPP now. Also will we have to uninstall and install the enterprise version after?
http://files.avast.com/iavs5x/setup_console_epsp.exe
Endpoint Protection Suite Plus - extended protection of workstations & servers
I think this is correct for you
This is getting better. Upgraded my console and now it installed the client on my server automatically without asking and there is no uninstall.
Problem description:
When the customer is using “old” SBC console and the new v7 client on the same computer then after computer restart the SBC console refuses license. It then affect also the client who receives license from the console.
This issue appears only for customers with new console and old client on the same computer. It doesn’t affect old client+old console, new console+new client.
Problem analyses:
It’s caused by the incompatibility of license utility interface in the new client.
Problem solution:
The problem has been fixed in client and the updated client will be released soon (tomorrow morning).
The problem can be also fixed by upgrading of the SBC console itself to v7 version. http://files.avast.com/iavs5x/setup_console_epsp.exe
I just hung up the phone with a reseller. He has a client using avast! Pro 7, and 2 of the computers auto upgraded to Endpoint Protection. The license file was now expired. We reinserted the license file, and it showed licensed. Then 1/2 hour later, it is expired again. Removed, reinstalled 7 Pro, and installation auto upgrades to Endpoint again, reinsertred license file, and good for 1/2 hour.
Does anyone understand what is going on here? Why would avast! 7 Pro upgrade to endpoint? This issue is breaking functioning systems.
J.R. Guthrie
@edj - yes, the update of the console v7 fixes the problem.
@all - the link provided by edj is the final build of the console. We are sorry for inconvenience caused by this licensing issue. We’ll roll out client update that fixes it completely.
@JR - avast pro can’t update to Endpoint (or at least shouldn’t). Could you sent me more details in email (screenshots and setup.log welcomed)