Turns out this is due to crl.verisign.net validating the certificate. Since our MES terminals have internet access blocked the .Net Epicor client can't validate but keeps trying. The following has been added to the mfgsys.exe.config as the first line in the runtime section:
<generatePublisherEvidence enabled="false"/>
We've tested it on several machines and it appears to have solved our issue.
<generatePublisherEvidence enabled="false"/>
We've tested it on several machines and it appears to have solved our issue.
--- In vantage@yahoogroups.com, "Jennifer" <jlisser@...> wrote:
>
> We are using a GPO to force IE to use a bad proxy - only problem is, it's taking up to 2 minutes before MES comes up for a log in.
>
> If I take the user out of the container with the GPO or log in as myself, MES pops right up.
>
> I did notice in the config file there are https links . I removed those URLs, leaving "" for the path. No change.
>
> You mentioned in an earlier post to force the same GPO we are - curious if you enforced it... and if you did, were the users seeing long delays before MES launched afterwards?
>
> Jenn
>