Many alerts of “The client computer has been renamed”

I need a solution

Hi everybody.

I need your help. The SEPM send many alerts of “The client computer has been changed”. What could be causing this?

I don´t find any information about this

This the email alert:

01/30/2019 14:28:44

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:28:33

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:28:24

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:23:44

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:23:33

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:23:24

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:43

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:33

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:24

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:14

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:28:44

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:28:33

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:28:24

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:23:44

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:23:33

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:23:24

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:43

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:33

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:24

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

01/30/2019 14:18:14

Default
symantec
My CompanyMH UsersUsuarios HabilitadosVice-AlcaldiaIgualdad y Género

Computo_6

J_Monge

Computer

No

DOMAIN.LOCAL

The client computer has been renamed

0

Related:

  • No Related Posts

Is smtpmail distributed as standard with Networker? (specifically 7.6.2.1)

Bit of an odd scenario, so apologies in advance!

I’m investigating one of our servers which has a few scheduled tasks running on it, attempting to make use of a ‘smtpmail.exe’. The only reference to any smtpmail executable I could find with the same argument syntax, is the one in EMC networker (as seen in this thread), and there just happens to be an installation of EMC networker on this particular server, with the ‘Legato/nsr/bin’ directory in the PATH. Which seems a pretty good indicator that the intention was for these tasks to be using smtpmail from networker.

However, there is no smtpmail executable in the bin directory, and never having heard of EMC networker until today, I don’t know if it’s something that is actually part of EMC networker and has somehow been removed from this particular installation, or it’s something non-standard and the above thread is just a bit of a red-herring.

Thanks in advance for any insights!

Related:

  • No Related Posts

Black Screens

I need a solution

I have a Windows Server 2016 Server that was upgraded (in-place) from Windows 2012 R2. It is a physical server that will randomly lock up with a black screen.   When the lock up occurs the server will still be responsive, you can ping the server, services continue to function (for awhile) but you cannot connect with RDP/console.  When we uninstall Symantec the issue goes away.  We have tried all the latest Symantec version and the issues continues to happen.

I found this forum post referencing the same issue: https://www.symantec.com/connect/forums/black-screens

And this article

https://support.symantec.com/en_US/article.TECH236543.html

However, these articles say the problem has been fixed in the latest Symantec update. I am using Endpoint 14.2 which is several versions newer then the ones referenced in the article and am still experiencing this issue.

0

Related:

Cannot use BBB for CIFS share backup

Hello folks,

I need to backup a CIFS share which I have manually mounted as drive Z: to my NetWorker server (Windows Server 2012 R2, v18.1.0.2).

In the documentation is mentioned that mount points can be backed up with the block-based backup feature:

Volume mount points—Specify volume mount points as save sets. For

example:

D:mount_point_name (for a single mount point)

D:mount_point_name1mount_point_name2mount_point_name3

(for nested mount points)

So I created a straight forward client resource with the BBB flag set to yes and “Z:” in the save set field.

But I get the message:

“\<unc-path>:No such file or directory”

Can anyone help?

Related:

  • No Related Posts

Symantec Diagnostic Tool – Service ccSet_NIS not installed

I need a solution

I’ve installed Symantec Diagnostic Tool onto a PC which has a fresh copy of Symantec Cloud.

As far as I know, Symantec on this PC is operating normally with green ticks on the status screen, and liveupdate and scan work OK.

But the diagnostic tool shows everything OK except: Service “ccSet_NIS” is not configured and operating properly.

And if I click for details, it says “Service is not installed”

What is this ccSet_NIS service and does it matter that it is not installed? If it does matter, how do I install it?
 

0

Related:

  • No Related Posts