Discovery of Nutanix system returns "Refer to prism" for Serial Number attributeDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Discovery of Nutanix system returns "Refer to prism" for Serial Number attribute While scanning Nutanix devices discovery returns "Refer to prism" for serial number thus keeps over riding same ESX server CI for each Nutanix device discovered. Release Any Release Cause This is because the serial number specified on the ESX host does not reside on the location discovery checks for it according to standard practice. Resolution As a work around NUTANIX has provided a script to run on the ESX server to copy the Serial Number at the correct location. Note: This script needs a restart. You can reach your NUTANIX support for that script. Additional Information https://community.servicenow.com/community?id=community_question&sys_id=213cfc46db1fe7409a64e15b8a961917&view_source=searchResult