Trying to write a report to show which PCs have been rebuilt or replaced
Good morning, I' trying to write a report that will show which machines were rebuilt, or replaced as our support vendor often replaces tills and office PCs across our estate and doesn't always inform us.
SELECT NAME, MAC, KUID, Created, Count(Name) As Num FROM ORG2.MACHINE GROUP BY NAME Having Num > 1
Shows which machines have either been replaced or rebuilt, is there a way to have a single query that will show Name (same), MAC (different if machine replaceD) and KUID (different if machine reimaged) ?
Thanks,
SELECT NAME, MAC, KUID, Created, Count(Name) As Num FROM ORG2.MACHINE GROUP BY NAME Having Num > 1
Shows which machines have either been replaced or rebuilt, is there a way to have a single query that will show Name (same), MAC (different if machine replaceD) and KUID (different if machine reimaged) ?
Thanks,
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
GillySpy
13 years ago
It looks like you are making an assumption that you will have a duplicate record. You may want to review this document: http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=673&artlang=en
Posted by:
nbs
13 years ago
Posted by:
GillySpy
13 years ago
The asset history is only updated if the current record is updated. If a new record is created then there are now 2 asset histories and 2 machine records.
Check out the FAQ and run the tests and follow the suggested remedies to nip it in the bud. For the existing "duplicates" there is a cleanup section. I'd call support if you run through it and still see issues.
Check out the FAQ and run the tests and follow the suggested remedies to nip it in the bud. For the existing "duplicates" there is a cleanup section. I'd call support if you run through it and still see issues.
Posted by:
nbs
13 years ago
OK, I am seeing PCs that have an asset history showing the MAC address has changed, since the NICs are on-board I assume this means the PC has been changed.
Ultimately though, what is the best process for identifying PCs that have been swapped out as it seems both my assumptions are not entirely accurate? Essentially I want to identify these swapped out PCs on a daily basis so I can report these to our support team highlighting PCs that they may need to check to ensure it's been configured properly and also get idea of how many PCs are being replaced / re-imaged on a weekly basis. The PCs in question are point of sale tills.
Part of the reason is if I can get this information, it should be possible to identify particular hardware types that get replaced more often / re-imaged, making it easier for us to identify hardware types that need to be removed from the system (so leading to lower calls logged / support costs).
Ultimately though, what is the best process for identifying PCs that have been swapped out as it seems both my assumptions are not entirely accurate? Essentially I want to identify these swapped out PCs on a daily basis so I can report these to our support team highlighting PCs that they may need to check to ensure it's been configured properly and also get idea of how many PCs are being replaced / re-imaged on a weekly basis. The PCs in question are point of sale tills.
Part of the reason is if I can get this information, it should be possible to identify particular hardware types that get replaced more often / re-imaged, making it easier for us to identify hardware types that need to be removed from the system (so leading to lower calls logged / support costs).
Posted by:
GillySpy
13 years ago
nbs, the faq has a couple of reports to run. A MAC change without other changes is often not a problem -- e.g. a machine switching from wireless to wired or to VPN. I can't think of a common reason for POS machines though. Swapping a NIC could be one. But Swapping a entire PC should not be one. If a PC was swapped out -- ie. machineA retired and replaced by machineB then in a healthy process you would now have two machines in inventory. MachineB should not overwrite MachineA as they are different objects and different assets. If you don't want to eat up licenses then you should retire machineA (delete or archive-and-delete) from inventory
If these machines are being deployed from the same image then you should make sure they do not have the agent installed (or enabled) until AFTER they have their final name, etc. Doing the agent as the FINAL post-installation task is recommended.
If these machines are being deployed from the same image then you should make sure they do not have the agent installed (or enabled) until AFTER they have their final name, etc. Doing the agent as the FINAL post-installation task is recommended.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.