Internet browsers are perhaps one of the most exploited applications because of all they are capable are doing with the internet. For 2012, Mozilla’s Thunderbird, SeaMonkey, and Firefox had the following security advisory bulletins:

Over the last 10 years, Hillsborough County Public Schools (HCPS) in Southwestern Florida saw an influx in the use of technology in schools. With over 267 school sites and more than 85,000 endpoints, it became imperative to select a solution that simplified and centralized management of its IT environment. To resolve this issue, HCPS selected a variety of solutions from Symantec. As a result all 85,000 endpoints are secure and can be remotely managed for convenience to faculty and staff. Risk posture was improved, but most of all management was simplified with automatic updates that deploy quickly and efficiently. To learn more about how Symantec solutions help simplify endpoint management and protection at HCPS, check out this link http://bit.ly/V676DD

Items completed:

3 SMP servers, 1 parent, 2 child with hierchy completed.

SQL maintenence plan created per Symantec recommendations.

AD import completed.

Subnets manually created(We are using the 8 scheme which would have been tough to import)

Tested PCAnywhere functions, decent product, not very good at screen aspect ratios for such a mature product. Very bare bones?

Only issues are: 1 server had to be respun in VM and rebuilt becuase of various strange errors with SMP agent. Also some Java oddities when importing OS files, which thankfully can be bypassed by simply pressing cancell to the credential challenge(This was on XP and 7 desktops with the Symantec's proposed GP configuration in palce. But that error still persisted, attached is the photo of the error, on an XP machine you can press cancell and continue with the file upload).

The design of the product still irks me a bit for the options on Site Servers. Even with fiber...

A few days in to the migration, have some questions came up. So lets go through it.

Our infrustructure is more like 1 huge building than 80 separate sites. The availability of having fiber connected to all the sattalite campuses means we can centrally manage as if they were in the same building. The problem is SMP isnt really designed for that kind of infrustructure. And the few issues we encountered are:

1. The technicians cannot manage the infrustructure in real time from 1 console. The amount of our clients meant we had to use hierchy, which means teh Parent server sees things later(Synch schedule). While all synched machines will be on the Parent server, any new clients will take 24 hours for the Parent console to see. Which means no OOB deployment from the parent Console.

2. Replication of packages maybe required as Task Servers, which means we would have to replicate our packages atleast 5 times(5 Task Servers). We dont need that as our San can handle the...