Endpoint Encryption

Hi all,
I am setting up a test server for Endpoint Encryption 7, we are still running 6 for the company. I have an issue whereby when trying to create the first client Framework MSI I get an error saying invalid server location when it tries to check the web server.  Does anyone have a few troubleshooting ideas I can go through to try and resolve this?

Setup as follows:
Windows Server 2003 R2 Standard
IIS V6.0
ASP.net v2.0 50727 - Allowed in IIS
Webserver  - Symantec Endpoint Encryption service is showing as started
Endpoint Encryption 7.02 installed
Sql Server 2005
SQL server and Enpoint Server and IIS are installed on the same test server.
I have set up 3 domain accounts for this call SEEIIS, SEETEST and SEESQL.

When trying to create the package it asks for the communication information, it sets the server to the local webserver so I use account SEEIIS
At the moment when I try to create the first Framework Client install it fails to find / validate the server - http://UKGUISEE7TST01:590/GECommunicationWS.asmx  - which is the local server.
I have tried to use the SEEIIS account as well as my own domain admin account for this but still have not got passed the invalid server location message that comes up when it tries to connect.

If I use the http://UKGUISEE7TST01:590/GECommunicationWS.asmx address in an IE7 browser I can access the page fine.

I cannot see any error messages in the Event Viewer to help me.

Regards
Ian

Hi Ian,
A few things to check first;
- Have you run the configuration manager program to setup the web server?
- Check the IIS logs (C:\Windows\System32\LogFiles) for any codes other than 200 just in case anything strange is happening, though it sounds like IIS is OK.
- You might want to use the latest version of SEE (7.0.5) rather than 7.0.2.
David

Hi David,
Thank you for your response.
Which part of the SEE management server install would have done the webserver? I thought it was where I set the port number (590), webservername and protocol ( http)

under IIS I can see the website set up called Symantec Endpoint Encryption services - This site status is running.
I have just looked through the log files. There are several files there but non contain anything of use I dont believe.

I have just checked the event viewer again after a restart and the ADsync / SQL / ASP.Net 2.05.... services all started successfully.

We would go straight to version 7.05 if we go ahead and upgrade, this is just a proof of concept on our new Dell laptop hardware as in Version 6, after encrypting the hard drives in AHCI mode, the machine never boots again.

Regards
Ian

Was simple really. The test server would not validat it's dns name, so to get it to work we changed the server name to http://localhost::590/GECommunicationWS.asmx

This worked fine. Created the Framework and SEE installers fine.

And those installers, pointing at localhost, work on other client installs?!

Hi David,
No the clients would never find the server with 'localhost' in the MSI config. This server build was simply a proof to see if SEE7 would work on our new Dell laptops in AHCI mode. In version6 when the hdd is encryted in AHCI the machine never boots again. I created the SEE7 deployments ( with almost no security) simply as a test to see if SEE7 would work.

Sadly we have exactly the same scenario. Once the C: is encrypted, after a restart the machine never boots again.

By running a recovery /d I think it was and waiting for it to decrypt for nearly a whole day, the laptop booted again......once! then it was back to a flashing cursor in the topleft of the screen before SEE loads.

I have not done any further work on this as yet

delete

Just got off the phone to support.  This may help some people....

Make sure you have the following Windows Components installed first:

- Application Server\ASP.NET
- Application Server.IIS.Front Page 2002 Extensions

If you still get the error message

- Open IIS Manager
- Expand Web Service Exntesions
- CHECK ASP.NET 2.0.5...is set to ALLOW  -mine was set to PROHIBITED
- If you need to, right click and choose Allow
- Restart IIS
- Recresate your package

Hope this works for anyone else out there - did for me :)