Endpoint Protection

 View Only
  • 1.  Wrong NIC again while upgrading to SEPM 12.1.5337.5000

    Posted Feb 25, 2015 03:15 PM

    Deja vu....

    http://www.symantec.com/connect/forums/sepm-1213-using-wrong-nics-servers

     

    Updated from 12.1.4 to 12.1.5 this morning.  Took forever.  A lot of cleaning and optimizing databases apparently.  The databases (we keep two) dropped 30GB.  Must be optimized now.

     

    Super slow for logging in, but we can eventually log in.  Nearly all the client machines were yellow, but they're coming back.  Manually checking for updates and updating the policies worked from the client machines.

     

    SEPM listed the wrong NIC again.  Went into Policies -- opened up Policy Components -- Can't change the default Manager Server List policy which had the wrong NIC listed (although it was listed second/after the correct NIC), so we made a copy of that policy, changed the policy, and applied that to all the clients.

     

    Now we're waiting for everything to filter through.  Fingers crossed.  I see last time it took a few days before everything was correct.

     

    Login time is about 5 seconds, down from 20 seconds earlier which was done from 10+ minutes the very first time we logged into SEPM after the 12.1.5 upgrade.

     

     

     



  • 2.  RE: Wrong NIC again while upgrading to SEPM 12.1.5337.5000

    Posted Feb 25, 2015 03:20 PM

    Is this NIC that it's showing even in use?



  • 3.  RE: Wrong NIC again while upgrading to SEPM 12.1.5337.5000

    Posted Feb 25, 2015 03:52 PM

    Yes, in use, but it's a backup network.  SEPM goes over the main NIC.  Backup process on the backup NIC.

     

    I don't know why it picked that up again.  Or, it lost the modified policy we made.  We can't edit the default MSL that includes this backup NIC.  So we made a copy, removed the backup NIC on the copy, and applied that copied policy to everything.  So far so good.

     

    This 12.1.5 update has just been super slow for the upgrade process and then we ran into this deja vu NIC issue.  At least it's a quicker fix this time around since we recognized it.