Questions
Opened this issue · 2 comments
Hello,
I am writing to you today because I have just discovered your solution and whaaaouuu but I have two small concerns:
- Unfortunately when the app runs the Enable-Remote Mailbox command it fails
- Another small bug is that the created account always fails to go in correct OU – always ends up in the default user OU
- since it does not complete the enable-remote I have the impression that the adsync run never takes place.
Thanks a lot for your job.
Thomas
Hi Thomas,
i've found out that the Remote Forwarding Address is not filled out automatically, the prefix is missing. When i add the prefix manually the command looks good, but unfortunately, we have 2 DCs and the sync is too slow. User is created on DC1 but Exchange looks up for the user on DC2, so the command fails. A workaround would be, to execute the tool on DC2. A solution would be, if we could select the target DC for user creation or mailbox creation. In PowerShell it would be -DomainController dc.domain.local
Right OU is working for me
ADSync takes place, just take a look on your AADConnect Server -> Synchronisation Service
what should the remote forwarding address be for a given O365 user?
"company.onmicrosoft.com"?
also, thoughts about a section on here to create a "welcome" email for the new user?