Help converting LDAP to OPATH
I have almost 450 QBDL's from Exchange 2003 that I need to convert to OPATH in Exchange 2010 SP1. Our Exchange 2003 mailbox server is currently turned off but 2003 hasn't been removed from the environment yet. I'm trying to follow these links: http://gallery.technet.microsoft.com/scriptcenter/7c04b866-f83d-4b34-98ec-f944811dd48d http://technet.microsoft.com/en-us/library/cc164375(EXCHG.80).aspx I have a sample QBDL named 'Woodlake Club 5045'. It's LDAP filter is "(|(objectCategory=group)(objectCategory=user))". [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\ConvertFrom-LdapFilter.ps1 "(|(objectCategory=group)(objectCategory=user))" ( ( ObjectCategory -like 'group' ) -or ( ObjectCategory -like 'user' ) ) When I try to set the new OPATH filter on that list, I get this error: [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Set-AddressList "Woodlake Club 5045" -RecipientFilter " ( ( ObjectCategory -like 'group' ) -or ( ObjectCategory -like 'user' ) )" -forceupgrade The operation couldn't be performed because object 'Woodlake Club 5045' couldn't be found on 'fl2000-dc003.ced-concord. com'. + CategoryInfo : NotSpecified: (0:Int32) [Set-AddressList], ManagementObjectNotFoundException + FullyQualifiedErrorId : 7C5EDE54,Microsoft.Exchange.Management.SystemConfigurationTasks.SetAddressList This list does show up in the Distribution Group container in EMC. What am I doing wrong?
September 14th, 2011 12:32pm

Hi, 1. Please turn on exchange 2003, then run the following command from exchange 2010 EMS: Get-AddressList 'Woodlake Club 5045' If no addresslist returns, please run Get-AddressList|fl, does it return all your 450 QBDL's ? If the 'Woodlake Club 5045' returns, please run the command to convert the LDAP to OPATH . .\ConvertFrom-LdapFilter (Get-AddressList 'Woodlake Club 5045' ).LdapRecipientFilter Then try to set new OPATH filter . Gen Lin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
September 15th, 2011 5:54am

I turned the Exchange 2003 server back on. It is only seeing the default lists it appears... [PS] C:\Windows\system32>Get-AddressList 'Woodlake Club 5045' The operation couldn't be performed because object 'Woodlake Club 5045' couldn't be found on 'fl2000-dc002.ced-concord.com'. + CategoryInfo : NotSpecified: (:) [Get-AddressList], ManagementObjectNotFoundException + FullyQualifiedErrorId : 461BDCFC,Microsoft.Exchange.Management.SystemConfigurationTasks.GetAddressList [PS] C:\Windows\system32>Get-AddressList Name DisplayName ---- ----------- All Users All Users All Groups All Groups All Contacts All Contacts Public Folders Public Folders Properties Properties All Rooms All Rooms test test
September 15th, 2011 9:41am

If I use the get-dynamicdistributiongroup command, then I see the lists. Changing the syntax to set-dynamicdistributiongroup -identity "Woodlake Club 5045" -RecipientFilter "( ( ObjectCategory -like 'group' ) -or ( ObjectCategory -like 'user' ) )" -forceupgrade seems to fix the problem for most of the DDG's, but there were still 122 DDG's which gave illegal syntax errors; It seems most of the errors are one of the two listed below. --- Invoke-Command : Cannot bind parameter 'RecipientFilter' to the target. Exception setting "RecipientFilter": "Invalid filter syntax. For a description of the filter parameter syntax see the command h elp. " ( -not ( CommonName -like 'SystemMailbox{*}' ) -and ( ( Alias -ne ) -and ( ( ( ObjectCategory -like 'person' ) -and ( ObjectClass -eq 'user' ) -and -not ( Database -ne ) -and -not ( ServerLega cyDN -ne ) ) -or ( ( ObjectCategory -like 'person' ) -and ( ObjectClass -eq 'user' ) -and ( recipientType -eq 'UserMailbox' ) ) -or ( ( ObjectCategory -like 'person' ) -and ( ObjectClass -eq 'contac t' ) ) -or ( ObjectCategory -like 'group' ) -or ( ObjectCategory -like 'publicFolder' ) ) ) )" at position 70." At C:\Users\jmueller.ORLANDO\AppData\Roaming\Microsoft\Exchange\RemotePowerShell\fl2000-excas001.ced-concord.com\fl2000-excas001.ced-concord.com.psm1:46856 char:29 + $scriptCmd = { & <<<< $script:InvokeCommand ` + CategoryInfo : WriteError: (:) [Set-DynamicDistributionGroup], ParameterBindingException + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.SetDynamicDistributionGroup --- Invoke-Command : Cannot bind parameter 'RecipientFilter' to the target. Exception setting "RecipientFilter": "Invalid filter syntax. For a description of the filter parameter syntax see the command h elp. " ( -not ( CommonName -like 'SystemMailbox{*}' ) -and ( ( Alias -ne ) -and ( ( ObjectCategory -like 'person' ) -and ( ObjectClass -eq 'user' ) -and ( recipientType -eq 'UserMailbox' ) ) ) )" at pos ition 70." At C:\Users\jmueller.ORLANDO\AppData\Roaming\Microsoft\Exchange\RemotePowerShell\fl2000-excas001.ced-concord.com\fl2000-excas001.ced-concord.com.psm1:46856 char:29 + $scriptCmd = { & <<<< $script:InvokeCommand ` + CategoryInfo : WriteError: (:) [Set-DynamicDistributionGroup], ParameterBindingException + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.SetDynamicDistributionGroup --- Outside of the DDG's, I still have 6 manually created e-mail address policies. Two of which I've migrated successfully, two of which contain mailbox manager settings to clear out the Inbox of two specific mailboxes after X number of days, and the last two have a broken filter. How do I convert the mailbox manager settings to Exchange 2010? The first failing legacy policy filter is: --- (&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(homeMDB=CN=Information Technology,CN=First Storage Group,CN=InformationStore,CN=FL2000-EXCH002,CN=Servers,CN=orlando,CN=Administrative Groups,CN=ced-concord,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ced-concord,DC=com)) )))) --- The second failing legacy filter is: --- (&(&(&(|(&(objectCategory=person)(objectSid=*)(!samAccountType:1.2.840.113556.1.4.804:=3))(&(objectCategory=person)(!objectSid=*))(&(objectCategory=group)(groupType:1.2.840.113556.1.4.804:=14)))(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*))) )))(objectCategory=user)(!memberOf=CN=AHG Group,CN=recipients,CN=users,DC=ced-concord,DC=com))) ---
Free Windows Admin Tool Kit Click here and download it now
September 15th, 2011 12:47pm

Hi, Please try the following command to update the filter for dynamic distribution group: get-recipient -RecipientType DynamicDistributionGroup |update-recipient
September 16th, 2011 3:33am

That command completed without errors. How can I confirm that all the legacy DDG's have been updated? How do I migrate the mailbox manager functionality as well as convert the filter for the other two policies?
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2011 10:28am

How do I convert these filters to OPATH? --- (&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(homeMDB=CN=Information Technology,CN=First Storage Group,CN=InformationStore,CN=FL2000-EXCH002,CN=Servers,CN=orlando,CN=Administrative Groups,CN=ced-concord,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ced-concord,DC=com)) )))) --- The second failing legacy filter is: --- (&(&(&(|(&(objectCategory=person)(objectSid=*)(!samAccountType:1.2.840.113556.1.4.804:=3))(&(objectCategory=person)(!objectSid=*))(&(objectCategory=group)(groupType:1.2.840.113556.1.4.804:=14)))(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*))) )))(objectCategory=user)(!memberOf=CN=AHG Group,CN=recipients,CN=users,DC=ced-concord,DC=com))) --- How do I fix the invalid filter syntax generated by the script for the other 122 DDG's?
September 21st, 2011 11:45am

I fixed one of the former mailbox manager rules by creating a new retention tag, applying it to a new retention policy, and mapping that policy only to the mailbox in question. The second MM rule was for a public folder, not a mailbox. It doesn't appear you can apply a retention policy to a PF, what is/are the workaround(s)?
Free Windows Admin Tool Kit Click here and download it now
September 21st, 2011 12:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics