Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

I deleted a Internal User on our PGP Universal Server by accident

Created: 24 Jul 2012 | 4 comments

How do I get them back?

We've tried importing the user, that fails...

Any help is appreciated!!

Comments 4 CommentsJump to latest comment

CB4's picture

You could have the user re-enroll. Assuming there is nothing wrong with their PGP Desktop they should be able to recover their WDRT and keys.

JasonMeyer501's picture

How would they do that?

Apologies, if this is documented somewhere I'm happy to read it, I just haven't been able to FIND it..

JasonMeyer501's picture

OK, found the process to re-enroll here:  https://www-secure.symantec.com/connect/forums/how-re-enroll-windows-clients

Did that but it did not re-add the user to the PGP Universal Server.   It hasn't added the PGP Corporation folder to the user/AppData/Roaming folder yet either.. 

Appreciate the input both past and future.  :)

stevenuk's picture

Don't know if this is best practise but works for me.

On XP I re-enroll manually if the tool doesn't seem to be doing it.

Some of these are hidden folders.  Go to Tools, Folder Options, View and Show hidden files

Stop the pgptray and go to

c:\documents and settings\username\application data

Get rid of pgp corporation folder

c:\documents and settings\username\local settings

Get rid of pgp corporation folder

And in My Docs

Get rid of PGP

Remove them from the User Access part of PGP Desktop.

Reboot and login with another PGP user setup with access on that laptop.

Then readd the user and it should re-enroll them when they login.

See if they then get added.  If not might need to call Symantec.

What version are you using?  I know this happened on our older version and we had a consultant in to do the upgrade.  And he sorted out the issue with the user not being readded when we had the same issue.