I have upgraded my EEM version from 5.1.9 to 5.2.5 version, while testing the new verson it was observed that the duplicate entry was not generated if the EEPC client is re-installed & mahcine object still existed in the Database; however post migration we find this is not the case & the duplicate machine entry still created. Is there any way that this can be fixed ????
There are two portions to it. First is "Boot protection" requested status (Enable, Disable, Remove, Remove and Reboot), then there is the last seen status. What are both?
When was the last time you have rebuilt index (cache)?
Que :There are two portions to it. First is "Boot protection" requested status (Enable, Disable, Remove, Remove and Reboot), then there is the last seen status. What are both?
Ans. The Boot Protection in General Tab is in "Enabled" state with the currunt version "5.2.5".
Que : When was the last time you have rebuilt index (cache)?
Ans. No, we haven't rebuild the Index cache....
Ohh I think its Index rebuild was done before , below is the file content...
LockTimeout=30000 ; the time we wait for the lock on the index file to become available in 100ths of a second
; (default is 30 seconds).
LockSleep=10 ; the time we wait before re-trying locking of the index file in 1000th of a second.
HashCount=160 ; the number of "buckets" into which the hash of the name is split
LifeTime=86400 ; = 24 hours -> the time (in seconds) for which the index will be used before it is
; automatically re-created (default is 30 minutes). A value of zero means
; that it never expires.
Thanks lot for you information, I will apply it & share you the result, but have doubt that with this cache rebuild, how duplicate entry generation will be disabled...