File Based Discovery & Sodtware Asset Management Normalization Summary<!-- /*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: block; max-width: ; width: auto; height: auto; } } How FBD and normalization work? File based discovery will only collect file information from the target if the file has the potential to match the software product in samp_file_name tablethis table contains the list of filenames that will be scanned.If SAMP is active on the instance, File-based Discovery creates or updates identified software products in the Software Installation [cmdb_sam_sw_install] table and updates the licenses of matched software packages. Without SAMP, no software records are created and only the file information goes into the File Information [cmdb_file_information] table.If any file matches a software product, Discovery populates the Product and Publisher information for that fileThe normalization process compares the discovered publisher, discovered product, and discovered version values against the ServiceNow repository of normalized equivalents. Matches are added to the corresponding normalized fields (publisher, product, and version) of the Discovery Model table.The normalization process compares the discovered publisher, discovered product, and discovered version values against the ServiceNow repository of normalized equivalents. Matches are added to the corresponding normalized fields (publisher, product, and version) of the Discovery Model table. The normalized fields are then used to match up entitlements purchased, and to compute license positions.For example, the discovered publisher Microsoft Corp could be normalized to Microsoft for the normalized publisher field.The second part of the normalization process looks for pattern matches between discovered fields and normalized values, and updates the normalized fields accordingly. This scheduled job runs daily by default but the frequency can be changed. When there are changes to a normalization rule, applicable normalized and partially normalized Discovery models are renormalized with the updated values.Both normalization processes must be completed for normalization be to be effective. Since the scheduled job for normalization does not run in conjunction with additions to the Software Installations table, View job results to verify that the job ran successfully if normalization results do not look accurate.The scheduled job for the normalization process runs daily but it can be changed. Whenever a new discovery model is created, the normalization process is also run. If SAMP is active on the instance, File-based Discovery creates or updates identified software products in the Software Installation [cmdb_sam_sw_install] table and updates the licenses of matched software packages. Without SAMP, no software records are created and only the file information goes into the File Information [cmdb_file_information] table.