PGP Universal Server Patch
Created: 05 Dec 2012 | Updated: 16 Jan 2013 | 7 comments
This issue has been solved. See solution.
So we have PGP Universal Server 3.1.0 and we needed to put the 3.2.1 patch on to fix the BSODs were were getting on Windows 7 machines at boot.
On the test laptop I've setup, it's a clone of our PGP Server. I've added the PUP file to the server and done the install. Everything appears to have worked and I've managed to update the two test clients on it etc.
However, I note, when you reboot the PGP Server the load up screen still displays it as being version 3.1.0 and in the console it also says on the Systems\General Settings that it's 3.1.0 yet the patch is installed and everything seems fine. Even the desktop client appears to be up to date.
Is this normal?
Discussion Filed Under:
Comments 7 Comments • Jump to latest comment
There are often two different pup files available. One updates PGP Universal itself (which will also update PGP Desktop, since the Desktop packages are included inside Universal). The other only includes updates to the Desktop packages. Perhaps you installed the second version of the update?
--------
David Finkelstein
Symantec R&D
According to this it's the 1st update you mentioned.
And as you can see, still says 3.1.0
What was the actual size of the pup file you uploaded?
--------
David Finkelstein
Symantec R&D
370mb
HI,
I think you need to log a support case with symantec for the same.
https://my.symantec.com/
Thanks In Advance...
Syed Saied
If the suggestion has helped to solve your problem, please mark the post as a solution
370MB or so is the size of the "pup lite" file, the file that only updates the copies of PGP Desktop. The actual server pup will be about 850MB.
--------
David Finkelstein
Symantec R&D
Ah right, that explains that then :)
I couldn't seem to find an option in the downloads for the actual server pup. We seemed to only have the full server install to download so you can setup a brand new server or, as you've now mentioned, the "pup lite".
But I think it was the Desktop client that mainly needed installing as I think that is what is causing are bluescreens on Windows 7. I def know it's PGP causing the bluescreens so we needed an updated version.
Would you like to reply?
Login or Register to post your comment.