I think you need to verify it and trust it BEFORE importing it into the Universal Server.
Regarding ADK do you know if the key was created with unbound client and upload to Universal ?
Did you try to create an ADK with managed client.
This issue usually happen when the ADK is not signed by organization key and thus not marked as
In certain situations when ADK is in CKM mode and client is bind to UN with key mode as SCKM or CKM then ADK client can remain 'unverified'
Is this tech note now out of date? It states that you must create the ADK with an unmanaged client
Yes that is right. You must create an ADK with unmanaged client as per KB.
Apoogise .. It was my typo as it should be unmanaged client as oposite to managed client where you can genereate a key and upload a key to PGP UN under AD section but ADK won't work.
Thnak you Adam & Alex,
I had generated the ADK & WDE admin keys on a managed client.
I followed this doc: http://www.symantec.com/business/support/index?page=content&id=TECH149500.
Neither the ADK-Guidelines nor the Admin guide state the usage of unmanaged client to generate ADK
Is there any way that e can mark these keys as verified now?
What are the effects of continuing with these keys marked as unverified?