Thanks. So You could code an EAP-TLS with proprietary functionality as long as this proprietary "stuff" did not interfere with the EAP-TLS standard.
When we coded the drivers they would register a class root and then a class id for the device in the registry.
So I think the only way to delete such entries would be if you could determine the class id for the "wrong" device" and delete it from Class Root.
When we coded the drivers they would register a class root and then a class id for the device in the registry.
So I think the only way to delete such entries would be if you could determine the class id for the "wrong" device" and delete it from Class Root.