Firewall Status Mix Up 12.1RU4

Dear community

I recently noticed that the clients on our network seem to have a total mix up in means of firewall status:
 

All the clients and the back end are running on version 12.1.4013.4013.
This seems strange to me due to several reasons:

1. Since all of the clients are on the same network and actually do not have any firewall policy attached to their locations.
2. In another environment, where the clients and back end are running on version 12.1.1101.401, the firewall status of each client is shown as "Enabled".
3. Both environments are set up identically in terms of Locations, communication settings and policy assignments.
4. All of the clients affected have been set up from scratch, no migrations.

I have seen various other posts on this already:

• http://www.symantec.com/connect/forums/firewall-status-disabled-or-disabled-policy-strange-behaviour
• http://www.symantec.com/business/support/index?page=content&id=TECH200415
• http://www.symantec.com/connect/forums/121-ru2-disabling-windows-firewall
• http://www.symantec.com/business/support/index?page=content&id=TECH204587

But none of them has been concerning the version 12.1.4013.4013.
In other words, is there anything that can be done except searching and hoping? Or am I just missing something?

At least it looks like there has been some other community member with a similar behaviour:
https://www-secure.symantec.com/connect/forums/sep...

I see that a support case has been his marked solution. Is there any knowledge for the public on this one?

Any assistance is welcome :)

Cheers