Microsoft Windows Module Installer invoked by every 15 seconds from the ITCM agent

Products

• CA Client Automation - Asset Management
• CA Client Automation - IT Client Manager
• CA Client Automation
• CA Client Automation - Software Delivery

Issue/Introduction

Microsoft Windows Module Installer appears to be invoked by a repeating (every 15-20 seconds or so) check from the ITCM agents on those servers, causing a high-CPU state almost constantly, both high CPU for the installer and high CPU for a few CA ITCM processes.

Environment

Client Automation 14.0 and above

 

Resolution

CAF Service logs show continuous IP address changes like the two following ones:

Notifier: System reports 6 addresses
Notifier: IP address( 172.x.y.z )
Notifier: IP address( fe80::xxxx:xxxx:xxxx:17d8%4 )
Notifier: IP address( 169.a.b.c )
Notifier: IP address( ::1 )
Notifier: IP address( 127.0.0.1 )
Notifier: IP address( fe80::xxxx:xxxx:xxxx:fff4%6 )
Notifier:CheckIPAdresses: Old/New size 5/6; Old/new checksum: 32382/56641; rc: 1
Notifier: System reports 7 addresses
Notifier: IP address( 172.x.y.z )
Notifier: IP address( fe80::xxxx:xxxx:xxxx:17d8%4 )

Notifier: IP address( 169.a.b.c )
Notifier: IP address( ::1 )
Notifier: IP address( 127.0.0.1 )
Notifier: IP address( 2001:0:xxxx:xxxx:xxxx:xxxx:53ea:fff4 )
Notifier: IP address( fe80::xxxx:xxxx:xxxx:fff4%6 )


And the registration agent running continuously to report the new IP addresses.

The Microsoft Teredo Service on these machines is interacting in some way with IPv6 Routing Requests, even though not using IPv6. This seemed to constantly update server IP tables, causing the knock-on effect of the CA Agents attempting to re-discover what they saw as a server networking change.


Disable the Teredo service on the server to avoid caf executing caf register every 15 seconds.

This could be done in command line with :

netsh interface teredo set state disabled

 

This could also be done with an Asset Job of type Command :

 

1- Create an Asset Job of Type Command :

 

 

 

Click Next

 

2- In Job Name put a name like "Disable Teredo". Click Next

 

3- In Text put the command line :

netsh interface teredo set state disabled

 

4- Click Next and Set Scheduling button.

 

Set "Run only once" in Scheduling Tab

And make sure that “This job is allowed to run unattended” is checked under Miscellaneous tab

 

 

 

5- Click OK and FINISH and assign this job to the machines.