• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7416
  • Last Modified:

EdgeSync Error 1024 and "The supplied credential is invalid"

Hello Everyone,

I have a problem and I am pulling my teeth out trying to get this one to work!

I have a new Exchange 2010 CAS/HUB Server and New TMG Server that will server as my Edge Server.

I am trying to enable EdgeSync between the Hub and TMG and I am getting the error 1024 on the Hub and when I run Test-EdgeSyncronization it returns the error "The supplied credential is invaild". After all my research I have atleast fiqured out it is a problem with the cert.

I currently have a 3rd party cert that is mail.xxx.com that is installed on the CAS and enabled for SMTP, IIS, IMAP, and POP services.

I know that I can't move the 3rd party cert onto the edge and enable it for SMTP and attempt to get the EdgeSync service to work b/c when I try to import the Sync File that was generated on the Edge to the Hub is fails and says you can't have the cert in both locations.

What is one to do, I am supposed to have the same internal cert on both machines? I can't see to fiqure this one out on my own.

Thanks for you help!

-Mike
0
BAYCCS
Asked:
BAYCCS
1 Solution
 
Viral RathodConsultantCommented:
The problem  that you are having is not because of certs, its an issue with credentials. EdgeSync uses ADAM credentials to connect to the edge server, and those are periodically changed by the "Edge Credential Service" running on the edge server. I would guess that service might not be running on your edge box, or a sync didn't happen for whatever reason within the initial 4 hours after you created the subscription. What you'll need to do is

1. Make sure the credential service is up and running on the edge.
2. Create a new subscription file by calling new-edgesubscription again.
3. Reimport the subscription.
4. Call start-edgesynchronization immediately after you subscribe.

the CN is expected to be different between the file and what start-edgesynchronization is telling you. The CN in the file is the CN of the ADAM user account Edge Sync will connect with initially, and the CN in start-edgesynchronization is the CN of the representatino of the Edge server in AD (how we keep track of it basically) so they will be different.  

Let me know if the above works.
0
 
BAYCCSAuthor Commented:
The Credential service wasn't running... WOW I can't believe it was that simple...

Thanks you!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now