Hi Nick,
It looks like you're having a few different issues so I'll try and split them up. We could do with some more information in a few parts so if you'd like to send it in to our support e-mail we can look at it further for you.
If a machine is re-imaged and subsequently re-deployed, then it is possible that the agent will create a new asset within the system. The agent itself uses a unique id (UUID) to match a computer up to the correct asset within Parago, and re-imaging may change this as it cannot generate the same id. It is possible to disconnect the old duplicate PC and then merge the new asset, which will keep all of your historical data.
The information that the agent pulls back is directly tied to the information that Windows has available. We have encountered several different models of PC that have the serial number of 'to be provided be OEM'. This means that at the time of the PC creation, the manufacturers themselves didn't set a serial number on the machine, and as a result Windows gets that message which in turn is passed on to us.
With regards to the agent not uploading, we tend to ask that you identify at least one problem machine and look at the log file for that. Any changes to your network or the agent may result in your networks security stopping the upload. If you can identify the problem for one machine it tends to follow suit that most if not all of the other machines are also having this issue. Once they start uploading properly you shouldn't have to look at any logfiles again. 99% of the time we find it is related to the organizations proxy blocking access to our servers.
If you'd like some more information or help regarding your issues, please feel free to contact us again.
Regards,
Colin
Suplicate entries and lots of info missing
Moderator: Colin Nocetti
-
- Parago Software Staff
- Posts: 11
- Joined: Tue Aug 04, 2009 8:57 am