ZES and Windows 7

Thanks so much for the reply, but still no-go.

Reinstalled the client and the server.

Verified the name being used in both is the same and resolves to the
correct IP.

The name on the cert is the name being used in the client.

IE gives me no cert errors at all when I surf to any URLS
(https://endserver.domain.com/PolicyS...eldClient.asmx works fine
in the broswer). IE is completely fine with the cert now, but the ZES
client sure doesn't like something at all.

I can't figure out what it is, bummer. I'm just going to have to
roll-out Win7 without ZES I guess, until it works anyway. It's really a
shame too, ZCM supports Win7 from a testing standpoint.

Don

SimonMag wrote:
> I had a similar issue when I was testing, what I found was that you have
> to make sure that the name of the Endpoint server you type in during the
> client installation matches exactly to what you named the server during
> the server install process:
>
> endserver.domain.com - would have to be entered during the client
> install. You will have to make sure that you are not getting any
> certificate errors in IE.
>
> Try:
> https://endserver.domain.com/PolicyS...eldClient.asmx
>
> This checks your distribution service us up and running.
>
> Hope it helps.
>
> Simon.
>
>
>
> Don Duval;1851865 Wrote:
>> Now, I know this isn't supported in any way, shape or form. But there
>> really isn't any where else for me to take this so...
>>
>> I have thrown the ZES client on some Win7 test machines as a part of
>> my
>> rounds of testing and have run into problems. The big one is on the
>> client, when trying to Check-in with the server, get's a ...
>>
>> "The underlying connection was closed: Could not establish trust
>> relationship for the SSL/TLS secure channel"
>>
>> error. OK, Cert error probably eh? No problem, import the cert into
>> IE(8
>> of course). Browser no longer barks about an invalid cert. Reboot for
>> good measure, log on to the machine again and... same thing.
>>
>> Any ideas? Thanks for your time.
>
>