Thank you, Bill. For anyone's reference who is reading this thread, the solution is that there was a key file in the MachineKey's file for the Agentry Server that, for whatever reason, had security that no one (or process) could access it. I took ownership of it, deleted it, then allowed it to be recreated (per the instructions above), the Agentry server then started up correctly without the crypto error.
-- Ed