• State Verified Answer
  • Replies 8 replies
  • Subscribers 62 subscribers
  • Views 2951 views
  • Users 0 members are here
Options
Related

Active Role Synchronization for GAL entries

lrigs
over 3 years ago

Hello,

I'm hoping someone can provide any information or experience on syncing a GAL between two Exchange environments.

Right now I am just creating a contact in the target domain using a user account info from the source and giving the contact the target address of the source domain account. I create the contact but still need to run a script on the target side to mail-enable the contact. Has anyone ever used the sync between two Exchange environments to create a mail contact that is mail enabled? Or anyone know a easy way to sync the GAL?

I've mostly worked with the domain sync between two domains. I just need to sync one way for the GAL to have entries from the Source domain to the Target.

FYI: I'm not an Exchange Admin and inexperienced with Exchange side of the house.

Thanks for any advice or guidance in advanced.

Thank you,

Lu

Parents
  • 0 over 3 years ago

    Are you using Quick Connect or the Synchronization Service to create the Contacts in the Target environment? Assuming the follow-up script the you are running on the Target side Contact is Enable-MailContact with the ExternalEmailAddress parameter? Within the Source->Target sync process, along with Firstname, Lastname... have your sync process also populate the TargetAddress attribute on the Target Contact with the Source object's email address. This should allow you to not have to run any follow-up scripts.

  • 0 over 3 years ago in reply to Richard.Lambert

    I missed the part in your post where you said you are already populating the TargetAddress attribute. Can you provide a little more info on how this GAL sync has been implemented and I can check how I've configured this previously and see what else may have been done.

  • 0 over 3 years ago in reply to Richard.Lambert

    Richard is on the right track here - the issue is likely the fact that the contacts are not actually being mail enabled in the target environment.  Populating the TargetAddress property alone is not enough.  You need to fire the Exchange cmdlet "Enable-MailContact" against each object.

    One way you could achieve this is to use a script activity contained in an Active Roles Change Workflow that is launched by the action of creating the contact.

    You can tell that a contact is "good" or "ready" by the fact that it has a LegacyExchangeDN property.

    Hope this helps.

Reply
  • 0 over 3 years ago in reply to Richard.Lambert

    Richard is on the right track here - the issue is likely the fact that the contacts are not actually being mail enabled in the target environment.  Populating the TargetAddress property alone is not enough.  You need to fire the Exchange cmdlet "Enable-MailContact" against each object.

    One way you could achieve this is to use a script activity contained in an Active Roles Change Workflow that is launched by the action of creating the contact.

    You can tell that a contact is "good" or "ready" by the fact that it has a LegacyExchangeDN property.

    Hope this helps.

Children
  • 0 over 3 years ago in reply to JohnnyQuest

    You are correct JohnnyQuest. In going over some configuration notes I have when setting this up previously and I had configured a Post-Sync script in Quick Connect/Synchronization Service to mail enable the newly created Contacts. And as JohnnyQuest said, configuring a Change Workflow in Active Roles would also accomplish the same results. Therefore Lu, running a post-creation script against the newly created Contacts needs to be done to mail enabled them. And as you can see, there are a few ways you can automate the running of said email enablement script.