Jump to content
billb@yearone.com

Security Center 10/Endpoint 10.1

Recommended Posts

We have been using Agent version 9.2.69 and protection version 8.1.0.831. We had version 9 on the security center. I upgraded to security Center version 10.0.3361. My problem is upgrading all the clients. I upgrade their agents to 10 but security center still shows 9.2.69. I could not get any systems to upgrade to endpoint version 10.0 by using the security center. I upgrade a number of server by the manual method but the version does not show up in the security center. It is still showing the older version. Am I doing something wrong?

 

I have not called support yet.

Thanks.

Bill

Share this post


Link to post

Please check the version of the agent locally.

 

Open a command window and run klnagchk.exe.

 

Which version was displayed?

Share this post


Link to post
Please check the version of the agent locally.

 

Open a command window and run klnagchk.exe.

 

Which version was displayed?

Run addtionally execute the klcsngtgui.exe utililty from the NetworkAgent folder, "Send heartbeat" and keep us up2date.

 

Br,

dawinci

Share this post


Link to post
Run addtionally execute the klcsngtgui.exe utililty from the NetworkAgent folder, "Send heartbeat" and keep us up2date.

 

Br,

dawinci

 

I ran the program. It shows the correct agent but the Administrator Server address is wrong. How can I change it to the right server?

It was working before the upgrade.

Thanks.

Bill

 

Starting utility 'klnagchk'...

Checking command line options...OK

Initializing basic libraries...OK

Current computer is 'YEARONE\ACCOUNTING'

Network Agent version is '10.0.3361'

 

 

Reading the settings...OK

Settings verification...OK

Network Agent settings:

Administration Server address: 'WSUS.yearone.com'

Use SSL connection: 1

Compress traffic: 1

Numbers of the Administration Server SSL ports: '13000'

Numbers of the Administration Server ports: '14000'

Use proxy server: 0

Administration Server certificate: not installed

Open UDP port: 1

Numbers of UDP ports: '15000'

 

Synchronization interval (min): 15

Connection timeout (sec): 30

Send/receive timeout (sec): 180

Host ID: 6b3768fe-80f5-41dc-b4ce-2e1169ac8dce

 

 

Attempt to connect to the Administration Server...Transport level error while connecting to http://WSUS.yearone.com:13000: general error 0x4E7.

 

An attempt to send ICMP packet to the Administration Server

Sending ICMP packet WSUS.yearone.com [192.168.24.18]...OK

Sent = 1, Received = 1

 

 

Attempt to connect to the Network Agent...OK

Network Agent is running

Receiving the Network Agent's statistical data...OK

Network Agent's statistical data:

Total number of synchronization requests: 0

The number of successful synchronization requests: 0

Total number of synchronizations: 0

The number of successful synchronizations: 0

Date/time of the last request for synchronization:

 

 

Deinitializing basic libraries...OK

Edited by BillBowling

Share this post


Link to post

Use the tool klmover to change the address.

 

klmover.exe -address xxx.xxx.xxx.xxx

Share this post


Link to post
Do I run this on the Security Center Server?

 

Thanks.

Bill

No. Locally on the client side from the command line. Tool is located in the Network Agent installation folder.

Share this post


Link to post
No. Locally on the client side from the command line. Tool is located in the Network Agent installation folder.

 

There has got to be a better way. I have over 100 clients. This was working before the upgrade.

I did it on one server. System Center does see it now. So this is the problem.

It looks like it pushed the agent out to everyone. Did pushing the agent out cause this?

 

Thanks.

Bill

Edited by BillBowling

Share this post


Link to post
There has got to be a better way. I have over 100 clients. This was working before the upgrade.

I did it on one server. System Center does see it now. So this is the problem.

It looks like it pushed the agent out to everyone. Did pushing the agent out cause this?

 

Thanks.

Bill

 

make a .cmd or .bat file that runs the command line, make an installation package for just that little file, then deploy it as a 'task for specific computers' to all the clients. works when I have to do command line stuff on all the clients, since we don't have a typical windows domain setup for stuff like that.

Share this post


Link to post

in your package repository configuration do not use the name of the server (WSUS.yearone.com). Use the IP address.

 

That´s why you got the error: general error 0x4E7.

Share this post


Link to post
in your package repository configuration do not use the name of the server (WSUS.yearone.com). Use the IP address.

 

That´s why you got the error: general error 0x4E7.

 

Where is this configuration located? I cannot seem to find it.

 

Thanks.

Bill

 

Share this post


Link to post

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.