"Updated on" filed on the Software installation record.<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Software installation records will never get updated by discovery or any other sources, rather when re-discovering the same record will update the "Last scanned" field on the installation record. So, "Last Scanned" is the filed will need to checking is need information when the installation record is discovered instead of updated_on.Process:=> When the information of software installations for a server are brought we just compare is the matching software installation record exists, if exist we update the Last scanned field. If record doesn't exist we create a new record and the rest all old data of the software installation are deleted. [-] Cause of the update on the "Updated on" filed: => The "Updated on" filed can be updated by different job like Reconciliation, Normalization or Software install Deduplication job.