Last week I installed the BES client on three HP Think client computers, model HP T620 Plus Quad Core (Thin client)
This week I have found that all three clients have ghosted (greyed out) entries in the BES console where it looks like they re-registered themselves with the console.
The Thin clients use Flash storage and are running WIndows 7 6.1.7601
Any thoughts on how I can keep these ghost entries from showing up or having the clients re-register themselves?
So these sound like Embedded OS endpoints? If so did you change the write mode? By default embedded computers will lose all state when they are restarted (including the registry)
Unfortunately the answer will vary a lot depending on the hardware. Some embedded cash registers for example are basically large computers with regular hard drives. Some like yours are flash and designed to be reset when they restart (they are write protected) and when you install software you need to turn off the write protect.
The issue with the BigFix software is there are a few things that can change on the server end that the client will see those changes and think it has changed deployments so it resets, even if you turn off the write protect for the initial run of the client. So it depends on your tolerance for the duplicates in the type of environment you use and how often the boxes restart.
The same problem happens for users of VM’s where they roll back their VMs regularly or using software like DeepFreeze for example.
The fix for this was to set the Thin clients to File Based Write Filter (FBWF) and put the following in the “exclusions” setting meaning that they will be in RAM and persisted at reboot instead of just being read/only.