Have about 100 endpoints. Performed a migration of Console and DB from Windows 2003 to Windows 2008R2 and Sql 2005 to Sql 2008R2.
While not perfect, the migration took and the console on the new machine looks just like the old machine with all exclusions in place.
Got the dreaded 1326 error and knew it was some combination of sophosupd username and password issues and proper sharing. Took about a day and a half to resolve that.
The good: I have gone into the console and chosen 2 servers and 2 workstations and performed a "protect computers" on them. The endpoints properly update and can attach to the new primary server and receive files.
The bad: All of the endpoints in the console have red x's on them, except for the update server itself which is green. If I run "protect" on them, they show up with a brown down arrow icon for about 15 minutes. The endpoints do receive the new package, but it appears to that do not report back to the console. Ultimately, the endpoint icons go from brown back to red. And while the endpoint update policy does show the proper primary server, it doesn't show "Sophos" as the secondary location - which is how it's set in the main policy.
***If I look at the properties of the endpoints on the console, the details still report that the primary update server is the old 2003 server, not the new 2008R2 server - even though the endpoints are finally talking to the new 2008R2 server.
I feel that if I can just get the endpoints to properly talk to the new console location, I can push out the protect command to the company.
Suggestions?
Adam in DC
This thread was automatically locked due to age.
