After SMA upgrade to 8.5, it doesn't read/establish persistent connection to NS if already received Communication profile with persistent enabled on 8.1 RU7.

book

Article ID: 172594

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

After on-box upgrade from 8.1 RU7 to 8.5: Already received Communication profile with persistent enabled on 8.1 RU7 managed client, after Symantec Management Agent (aka SMA) upgrade to 8.5 doesn't read/establish persistent connection to NS.

 

Steps to reproduce:

  1. Install ITMS 8.1 RU7 release and have some managed clients
  2. Perform on-box upgrade to ITMS 8.5
  3. Do not upgrade SMA and first go to notification server settings page -> enable persistent connection. Now open NS Communication profile and enable persistent connection there as well -> save changes.
  4. Now refresh policy on managed not yet upgraded 8.1 RU7 client computers.
  5. Enable SMA upgrade rollout policy -> receive it on clients -> make sure that clients are upgraded to 8.5 -> check persistent connection state in SMA UI -> see result -> it isn't established and SMA continue to communicate via HTTP(s).

Cause

Known issue    

Environment

Upgrade from ITMS 8.1 RU7 to 8.5

Resolution

A fix has been added to our ITMS 8.5 RU1 release (targeted to January 2019).

Current Workaround:

  1. Disable persistent setting in NS communication profile,
  2. refresh policy on already upgraded SMA client,
  3. then enable "Persistent" setting in NS communication profile and refresh policy on client side,

Now SMA will be able to read/establish persistent connection to NS