• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 95 subscribers
  • Views 4108 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Configuring Hybrid Exchange 2013 with IDM 6.1.x

ndahms
over 8 years ago

I was hoping someone could provide some insight in how to accomplish setting up Exchange 2013 Hybrid with IDM 6.1.x.

I thought it was as simple as modifying EX2K10_ADSAccount_ENABLE_Mailjobject but that wasn't the case, I can change very little in there. This is unfortunately stopping the project of migrating to Office 365. If anyone has done this or could give any insight in do how I'd accomplish this I'd greatly appreciate it.

Parents
  • 0 over 8 years ago
    ndahms,

    In my case, PersonHasRessourceTotal_AutoCreate_O365 is to enable an ADS account to be the MailObject of Mail User (not mailbox) if an employee has Office365 resource assigned. This process fires the process “VI_EX2K10_ADSAccount_ENABLE_Mailobject” which provisions the Mail User object to Exchange on-premises with OOTB Active Directory attributes. Usually there would be a delay to wait for DirSync to federate and synchronize the Mail User to Office365 (which of tasks is on the customer side). I not only modified “VI_EX2K10_ADSAccount_ENABLE_Mailobject” to populate additional attributes to Exchange on-premises, also added a conditional process step of PowerShellComponent to execute script for individual user license attribute (set/get/remove) as needed.
    HTH.
Reply
  • 0 over 8 years ago
    ndahms,

    In my case, PersonHasRessourceTotal_AutoCreate_O365 is to enable an ADS account to be the MailObject of Mail User (not mailbox) if an employee has Office365 resource assigned. This process fires the process “VI_EX2K10_ADSAccount_ENABLE_Mailobject” which provisions the Mail User object to Exchange on-premises with OOTB Active Directory attributes. Usually there would be a delay to wait for DirSync to federate and synchronize the Mail User to Office365 (which of tasks is on the customer side). I not only modified “VI_EX2K10_ADSAccount_ENABLE_Mailobject” to populate additional attributes to Exchange on-premises, also added a conditional process step of PowerShellComponent to execute script for individual user license attribute (set/get/remove) as needed.
    HTH.
Children
No Data