We just moved both our database and server to a new single piece of hardware, and almost everything seems to work. Clients show up as online and their last update time updates fine, but actions never report and new clients don’t show up. The fillDB.log shows lots of the following line (computer number obviously varies)
Unexpected exception encountered parsing file C:\Program Files (x86)\BigFix Enterprise\BES Server\FillDBData\bufferdir\000000000000010e; discarding: Client report has no verified signer. Discarding message from computer 2244898
I’ve turned off report encryption, and the files are definitely coming in as plaintext (I can view them in notepad), but for whatever reason the FillDB service refuses to parse them. The client logs seem like everything is OK - they see pending actions, and they show that they send their reports in successfully.
Is there some setting on the server that says to ignore the verified signer, or some way for the client to regenerate whatever signature is being referenced?
I was able to get most old clients to report by making encryption optional, but if I install the client on a new machine, the new machine never shows up in the console, and the client log shows entries similar to the following:
At 08:41:16 -0700 -
RegisterOnce: Attempting secure registration with Unrestricted mode
Scheduling client reset; Computer id changed to 4788178
Configuring listener without wake-on-lan
Registered with url
Registration Server version 9.0.835.0 , Relay version 9.0.835.0
Relay does not require authentication.
At 08:41:17 -0700 -
Failed automatic client authentication key exchange with server message: class X509VerifyError<7>
Relay selected: tem.quiznos.com. at: IPADDRESS:52311 on: IPV4
If old clients are working but new client logs are showing something like “Failed automatic client authentication key exchange with server message: class X509VerifyError<7>”, this is what we wound up doing to fix (with help from support)
Stop the TEM Server Services
Rename the EncryptedClientCAKey in C:\Program Files (x86)\BigFix Enterprise\BES Server
Run BESAdmin, which will recreate that file
Restart all services
After that, new clients were able to register. If your client logs aren’t showing that X509VerifyError then this probably won’t help…