A new piece of information...
Seems the client machines that are disappearing were all imaged using a machine that had SEP installed prior to running Microsoft sysprep. The original machine was joined to the domain, all software installed including SEP and then dis-joined. Then, the machine was sysprep'd and an image of the hard-drive was taken. This image was then used to deploy several other machines. Now every machine from this image exhibits the same behavior; that is, only one machine from the "clone" group shows up in the SEPM console at a time.
We have noted that it appears the last machine to "check in" is the one that appears in the client list in SEPM console. We took one machine in this group and ran Clean-Wipe from Symantec and then reinstalled SEP as a managed machine, but the same behavior results. We deleted the SEPM console and associated embedded database, then reinstalled it and waited for machines to check in. The same behavior resulted. It appears that SEPM is reading each of these machines as being the same machine.
The question then would be: What unique identifier was cloned to each of these machines that SEPM console reads and determine all these machines to be the same when they check in? Is it a registry key, or what?