Thin Client hardware and BESClient (Duplicate computer)

Usage and Config Platform
1

(imported topic written by mxc0bbn)

I have HP Thin clients with the BESClient installed in my environment. The clients have an enhanced “write lock” so they can’t be messed with by normal users; however, whenever you have to make a change to them you can disable the write lock, reboot, make the change and then re-enable the write lock.

For some reason though, every time I disable the write lock it resets the “
ReportSequenceNumber
” and the “
ComputerId
” field in the “HKLM\Software\BigFix\EnterpriseClient\GlobalOptions” key.

The “ComputerId” field remains the same for a short time after it boots back up but eventually it does change.

What is it about disabling the write lock that resets this key? The newer thin-clients use “File-based” write lock which can be set to ignore write lock on the BESClient directory, but I think the older “Enhanced” write lock is all or nothing.

Can anyone shed any light on why this might be happening or how I can set it to ignore write-lock on the BESClient folder?

Thanks,

M.

2

Hi Did you find any solution for the same ?

I am also facing the similar kind of issue, where whenever user login into the system we are able to see multiple entries of the system.

Thanks and regards,
KK