Updated US from 2.12 to 3.2.1 Cannot install Desktop Email
Created: 07 Nov 2012 | 8 comments
Hi, we have upgraded our Universal, i've downloaded the client install file from the Universal server and tried to install the client on a number of PCs but keep getting the same thing.
After installing the client, restarting the PC and logging on as a user this is what I find.
- It asks to accept a certificate which I say to allow always
- it prompts for an email address, I enter the users email address
- it says an email will be sent to this person
- I open the email
At this stage usually the email dissapears, and I can click on next and continue with the assistant. But it doesnt dissapear and i can go no further.
please could somebody help?
Many thanks
Discussion Filed Under:
Comments 8 Comments • Jump to latest comment
What do you mean by the email disappears? What mail client are you using?
http://www.cstl.com
We use Outlook 2007.
Before the upgrade of our Universal server, we would:
- download the client from the universal server
- install it as admin
- restart the pc and log in as the user
- the enrollment assistant would appear and we would fill in the email address
- it would say an email would be sent to the user
- we would open up Outlook, open up the message.
- straight after opening the message, the message would close on its own and dissapear. It would switch to the enorllment assistant and we could click next and generate a key.
The problem since the upgrade is now that, when we open up the message in Outlook which is sent by the enrollment assistant. The message doesnt dissapear when it is opened, it just stays in the inbox, and we cannot get to the next stage of the enrollment assistant
thanks
Ahh I understand now.
Have you tried it via silent enrollment?
http://www.cstl.com
Thanks for the advice, how could I do this?
Would it get past the enrollment stage, this is where it seems to be getting stuck.
Thanks
Yes, there would be no wizard at all when a new user logs on, it will automatically do it all for you, and (really) is the preferred method of deployment.
http://www.symantec.com/docs/TECH183325
Enjoy :)
http://www.cstl.com
Thanks, i've spoken to symantec and they've advised we go from 2.12 to 3.2.1 another way...
2.12 SP4 Build 1128 >>> 3.0.2 SP2 Build 129 Via backup of 2.12 recovery on clean install of 3.0.2 from ISO
3.0.2 SP2 Build 129 >>> 3.1.2 SP3 Build 50 Via PUP update
3.1.2 SP3 Build 50 >>> 3.2 MP5 Build 2599 Via PUP update
3.2.0 MP5 Build 2599 >>> 3.2.1 MP3 Build 4940 Via schema repair and PUP update
We will try this upgrade path
in otherwords, a very complicated upgrade path :)
http://www.cstl.com
i know...
I'll report back when we have, it might help someone save the many hours i've spent on it!
Would you like to reply?
Login or Register to post your comment.