This increases script execution time - but also results in potentially loosing effective permissions or group memberships on premises. When this switch is utilized as FALSE - if the migrated group was set on any other disrtibution list on premises with permissions or is the member of another distribution group Purpose/Change: In this version we are implementing a switch that allows administrators to bypass retaining on premsies settings for the group. For example, we update the AD calls to utilize calls that work assuming a non-alias is utilized for the group.Īdditionally new functions have been created to log information regaridng the items created. Purpose/Change: In this version we correct some of operations. It's now broken down into triggering inbound replication and outbound replication from local domain controllers within the site.
Redefined the replicate domain controllers function. In the ad connect invocation function split the importation of the module from the delta sync so that individual errors could be trapped. Updated the move to ou to function to utilize the powershell session and static domain controller specified. We now only refresh if the array type is greater than 1000 objects.Ĭreated a remote powershell session to the domain controller specified / now required. This added time and was not necessary if the individual array items were less that 1000 objects. In the build array logic the powershell session was rebuilt for each iteration. Customers desiring to retain the group on premises must now specify -convertToContact:$FALSE. This resulted in the migration being undone - and old information from on premises now overwriting new information in the cloud. In doing so - the groups softmatched from on prmeises to the migrated cloud only distribution lists. In recent weeks a customer performing conversions accidentally rebuilt their ad connect box, and selected the OU contacining converted groups. This would leave the distribution group on premises. In versions prior to 1.4 convert to contact was not mandatory as true. Purpose/Change: In receiving customer feedback an interesting scenario was presented.
Provisioning the contact which corrected this issue.
0 kommentar(er)
