We are installing PGP on a number of servers, (all Windows Server 2003 Enterprise, SP2) some of which have an internet connection and some don't (security reasons).
I have been able to authorize one server that's connected to the internet, using the following command, and it works near instantly:
pgp --license-authorize --license-name "<removed>" --license-organization "<removed>" --license-number "<removed>" --license-email "<removed>"
However, when I try this against a similar server, again with an internet connection, the cmd window just stops and won't close normally. There is a static cursor beneath the command, and it will stay like that until I kill the process via tskmgr (which also stops the service) at which point there is an 'insufficient random bits' message, which I assume is the result of the process being ended prematurely.
This freezing also happens when I try any command which requires a license. There is nothing in the event viewer. No CPU/load problems. procmon/filemon don't show anything at the exact time of execution.
Does anybody know what would cause the process to hang completely like this? (it remains like this for several days - I left it over the weekend to see)
Also, I've read conflicting info about whether an internet connection is actually needed for authorizing this version? If it is, and we need to use an authorization text file, does this need to be obtained from Symantec (I found no options within our account), or do we need to use the one at the bottom of this page: http://www.symantec.com/business/support/index?page=content&id=HOWTO42089 ?
Many thanks,
Richard Penna.