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

book

Article ID: 141953

calendar_today

Updated On:

Products

CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Software Delivery CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

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

 

Resolution

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

Notifier: System reports 6 addresses
Notifier: IP address( 172.21.0.11 )
Notifier: IP address( fe80::2546:f031:cddf:17d8%4 )
Notifier: IP address( 169.254.23.216 )
Notifier: IP address( ::1 )
Notifier: IP address( 127.0.0.1 )
Notifier: IP address( fe80::38a2:32d2:53ea: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.21.0.11 )
Notifier: IP address( fe80::2546:f031:cddf:17d8%4 )
Notifier: IP address( 169.254.23.216 )
Notifier: IP address( ::1 )
Notifier: IP address( 127.0.0.1 )
Notifier: IP address( 2001:0:2851:782c:38a2:32d2:53ea:fff4 )
Notifier: IP address( fe80::38a2:32d2:53ea: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.