Nope, you've not been seeing things! They really pushed out a noddy (botched) home product and labelled it as "business" -
and it gets worse!
If you had been using the AVG 3.6.4 client, and upgraded to Avast 4.0.0 client (via the Scheduled Component Update policy setting) rather then install 4.0.0 from a new Avast install package, you are (to put it bluntly) buggered!
In that scenario you'll find, in addition to those I've already listed :
1. Old policy settings are NOT carried across/migrated.
2. The "new" policy settings are never applied and DO NOT WORK, leaving all your endpoint totally out of control.
3. Remote control, while functional if not great before, is knackered. Utterly unusable. "Premium Remote Control"? What a joke.
For me the best, the ONLY option, was to rip out Avast 4.0.0 and re-install AVG 3.6.4. That is when it really hit the fan!
First before doing anything, assuming you have created a custom policy (you can't modify the Master), go into your policy and DISABLE Scheduled Component Update. If you do not, as soon as you've finished rolling back to 3.6.4 (which you have to do largely manually) it will upgrade it straight back to 4.0.0.
Also, PREY that you still have an install package for AVG 3.6.4. If you DO NOT you are really stuffed - you can't create it. You only have the option of creating the garbage Avast 4.0.0.
If you DO still have your AVG 3.6.4 install package, PREY that when you created it you selected your custom policy as the the default for it. If not, yet more pain because you can't disable Scheduled Component Updates in the default master policy, and that will be the one applied!
Now comes the real pain in the backside.
In the portal you can look at the status and properties of each "device" (endpoint) and click on "Uninstall". This is utter crap.
Yes it will uninstall it from the selected endpoint BUT, 15 mins after you've finished re-installing AVG 3.6.4 it UNINSTALLS IT again!!!
I'd used the "uninstall" button in the portal on the first 5 endpoints then wondered why, after re-installing, they suddenly disappeared from the portal device list. That's when I found they had all uninstalled again. For some reason, and I don't know why, doing it from the portal seem to work fine (at first) but doesn't clear the Uninstall Request. So as soon as you've re-installed it and it completes any database updates, it sees the uninstalled request and euthanizes itself!
Very helpful NOT.
The main thing I've noticed is that no restart is done at the end of the uninstall, if done via the portal. However, even doing a manual restart afterwards doesn't clear the Uninstall Request. It still waits patiently until you've re-installed it, then rips it back out.
So you have to go round and uninstall Avast 4.0.0 from every single endpoint manually, one by one.
Here's the final, real pain in the backside.
If you have an AVG 3.6.4 install package to re-install, but it doesn't apply your custom policy by default (as mine didn't as I hadn't yet played around with policies when I created it), you have to do the following:
This has to be done on each and every machine, one by one! (I at least could do it via Microsoft's own Remote Desktop client MSTSC.EXE rather than physically have to go each one)
1. Manually uninstall Avast 4.0.0 and restart the machine.
2. When restarted, manually start the install of AVG 3.6.4.
3. As soon as you've started it, keep refreshing the Device List in the portal until it appears, usually quite quickly
4. As soon it appears click on it to view it's status and properties. Note: It will still be greyed at this point and say "Installing"
5. In the properties change the policy from the default master policy to your custom policy which has Scheduled Component Update disabled. Even though it says it has been applied, I click on Save anyway. If you don't do this BEFORE restarting the machine it will almost certainly upgrade itself back to Avast 4.0.0. I know 3 of mine did!!!
6. Once the install has completed on the machine, restart it
Now continue on to the next machine, and the next, and the next, and the next.......
George
To think, we switched to this because I was utterly fed up to the back teeth with the sheer amount being taken up keeping damned Kaspersky Endpoint Protection 10 working because of all the bugs in it (and it has become bloatware). The AVG version was lightweight but ok. Compared to Avast 4.0.0 and the trashed portal, Kaspersky was a dream!!!!
