Hallo everyone.
I've started gradual SEP transition from v12.1 to v14. Got a new server, installed SEPM 14, performed DR then deleted all the clients from it. The idea was to redefine client groups, especially installation packages. As I will have to keep couple of Win 2003 servers (using 12.1 RU6 MP6 clients) and Win XP workstations (using 12.1 RU5 clients due to shutdown issue with later SEP client versions) I thought making sub-groups which would inherit all the group policies but have different installation packages will do the trick.
After that I've exported all of the new sylinks and started adding test clients. Everything seemed ok. Clients in groups with v14 installation packages succesfully upgraded, communicated with SEPM, clients with v12 kept all of the settings, communication looked fine. Tested for a couple of days then continued transfering clients from v12 SEPM to the new one.
Issue 1: stuck 32bit 12.1 virus definitions
End of the last work week, first couple of transferred clients changed status to "Out-of-date", although everything seemed ok. They were online, SEPM updated policies regularily, green dot was there. Tried to push content update from SEPM, nothing. Local 'Live Update...' did the job, but when left alone clients wouldn't DL new definitions. Re-checked Live Update policy, swapped to default, nothing.
And then I noticed SEPM's 32bit virus definitions are stuck on 11/02/2016 r20 (see attached 'LU content' screen).
No matter what I try:
- manual SEPM content update (as you can see from attached 'SEPM LiveUpdate status log.txt' -> "Symantec Endpoint Protection Manager could not update Virus and Spyware definitions Win32 12.1 RU6"),
- stopping SEPM/deleting content folder/restarting SEPM,
- even copying 32bit definitions from v12 SEPM,...
definitions are stuck at this revision. And only these (full Win32 12.1 RU6 definitions) everything else is upgrading ok.
As most of my workstations/mobiles and half of my servers are on Win 32 bit, this is a problem.
For now, I've changed Live Update policy from 'Use the default manager server' to 'Use a LiveUpdate server', but this is not a solution.
Issue 2: Scheduled Reports
When email server is configured to 'Require the specified email server to use a secure connection', wheather TLS or SSL, scheduled reports are not being sent. Test emails work correctly, but reports are not sent. If secure connection is not required reports go out as configured.
Anyone else seing these issues?
Any ideas?