Clients are unable to connect to SEPM after adding a replication server, or new SEPM to the environment.
ersecreg-a.log example:
08/10 05:02:43 [461336:466208] 4 Bad format.
08/10 05:02:43 [461336:466208] xxx.xxx.xxx.xxx--FAILED
08/10 05:08:10 [461336:457880] <CHttpReg::ProcessReq> [xxx.xxx.xxx.xxx] Processing Reg request from Client,TotalRegistrationsProcessed: 1
08/10 05:08:10 [461336:457880] <CHttpReg::ProcessReq> Post Data ContentLength = 2272, Configured MaxPostDataLength = 8192.
08/10 05:08:10 [461336:457880] <CHttpReg::ParseData> Data invalid - Unable to parse decrypted data: ¾[email protected]<ý¹ˆ®$"ÖÙ]){t«=ƒô"C”ÐÍZø¥kÃ`e’›œ0nŒ¿óӘ쑒T(w+h€|«OÊôýòvß§Å`ÙF yò‡•iz¯â¹â¼—92§âõ„°Ÿ“Œéày6äK@ÒÇMf¸» C*×ÁDpåÉò-[:G* oͧ*«Ld‘1
Secars,hello test on clients fail.
New server replicated incorrect KCS values.
Verify server KCS values. If it is found that the client's sylink, and the sylink found in %Program Files%\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent are the same, however the KCS value in the conf.properties are incorrect, follow the resolution in this article.