You have it wrong, I’m simply quoting fact. SOA has problems with Windows Server 2012 R2.
I shouldn’t have to provide log files, service conditions, or firewall activity. This is what I pay Avast! to workout with their beta testing before they release a product to the public.
Miracle workers? No I just want a working product. I have another year of license or I would move to another Endpoint AV product.
Server Operating Systems:
Microsoft Windows Server 2003 and 2003 R2 (any edition with latest Service Pack, 32-bit or 64-bit, incl. Small Business Server)
Microsoft Windows Server 2008 and 2008 R2 (any edition with latest Service Pack, 32-bit or 64-bit, incl. Small Business Server, except Server Core)
Microsoft Windows Small Business Server 2011 (any edition with latest Service Pack, x64bit)
Microsoft Windows Server 2012 and Server 2012 R2 (any edition with latest Service Pack, x64bit, incl. Small Business Server/Essentials, except Server Core)
Microsoft SharePoint Server 2003/2007/2010/2013
I believe there are three Avast! Services listed and running on the server.
I can access the Avast! SOA website remotely (from a laptop within the local Domain) but can not access the Avast! SOA website from the Windows Server 2012 R2 Essentials.
The server SOA installation appears to be working properly and communicates with the computers on the local network. I can remotely manage the EPSS software on all my networked computers but can not directly access the SOA on the server.
The SOA or EAC should be configured to work as part of the server’s Dashboard rather than a website.
And you still cannot access the management console? What web browser do you use to access the console?
Can you provide us with the management console logs?
I use MS IE on all equipment. I can not access the management console using the WS2012R2 built-in browser. However I can access the management console using W8.1 and W8.0 IE browsers remotely using client machines. I even opened-up protection on the WS2012R2 browser and dropped all firewalls. The management console can not be accessed locally on the server.
Has this new SOA software been tested on a WS2012R2 system or are you simply waiting for your paying customers to help troubleshoot its’ problems?
If the customer is going to depend for support on the reseller then, why you guys are running this forum (especially the busniess section)??
I started a new thread more than 24 hours back for a very simple issue but non of the mods replied.
today morning (before 8 hours) I sent the same issue to AVAST through built-in support functionlity but again no reply.
instead of reminding us about the benefits of buying from local reseller, please invest that time on solving our issues without making jokes like WPN did.
That defeats the need to have Avast! actually fix the problem. Windows Server 2012 R2 Essentials installs with a locked-down version of IE. Avast! needs to fix the Small Office Administrator program to work with IE on the Server. Even the latest version of SOA (1.3.3.42) doesn’t work with the Server IE.
However from a client machine, the SOA on the Server works fine, using the client’s IE.
Honestly, coming from someone who is seriously in the “don’t point fingers at the other guy, just fix your stuff” camp with respect to software vendors, I think in this case you may be asking for more than you should.
If I understand correctly, you are complaining about IE Enhanced security mode, which has been on by default for … a while… It is also trivial to turn it off for administrators, while leaving it on for non-privileged users (should you have any with local login rights for your server)… No direct experience with the Essentials flavor, but it appears to be the same as other versions of server 2012 and 2012R2 according to a quick search:
When you look at what IE ESC is, it makes sense that some web applications will not run while it is enabled… I’m still glad that it is the shipping default from Microsoft, but I also understand that it isn’t a magic bullet.
So disable IE ESC, or as you’ve pointed out, there is no reason why you need to run it from the console of the server. Any admin workstation can open the URL just fine. So… Why are we having this conversation?