

Select the Tamper Protection Tab and disable.Go to Change Settings and select Client Management.Turn off Tamper Protection by opening the client.I am able to fix it manually by the following steps: All of the clients I have tested so far are able to communicate with our server as they have updated definitions, and report having successful connections, but no information can be read from SEPM. I did some research into this and it seems like it is a problem with the hardware ids on the clients being incorrect.

The machines show up as we have our AD structure imported into SEPM, however the fields just say "client version unavailable," or something similiar. Recently we have finished upgrading all of our managed machines to SEP 12, and now that the upgrade is complete, I noticed that a large number of our clients in SEPM are not reporting client versions, definition versions, etc.
