How to find and remove Exchange 2003 refs from Exchange 2007/2010 org?
I've jut removed my last Exchange 2003 server, and am attempting to get my address lists sorted out. Attempting to create an address list using the new-addresslist cmdlet, and specifying a recipientcontainer, I get:
New-AddressList : You can't specify the recipient container because legacy servers are detected.
I'm assuming (perhaps incorrectly) that there's still some 2003 remnant left behind that's causing this.
Any suggestions on where to start looking, and how to get rid of?[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
July 14th, 2010 1:11am
This should help:
http://support.microsoft.com/kb/833396
Read the whole article.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.
"mjolinor" wrote in message
news:eccaf925-66b9-4bc1-8495-5e8005e035d9...
I've jut removed my last Exchange 2003 server, and am attempting to get my address lists sorted out. Attempting to create an address list using the new-addresslist cmdlet, and specifying a recipientcontainer, I get:
New-AddressList : You can't specify the recipient container because legacy servers are detected.
I'm assuming (perhaps incorrectly) that there's still some 2003 remnant left behind that's causing this.
Any suggestions on where to start looking, and how to get rid of?
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 6:08am
Thanks Ed. I've done that, but there appears to be some ghost of an old server lurking in AD somewhere that 2010 isn't happy about.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
July 14th, 2010 6:28am
Hi,
First I think we need to check if the default e-mail address policy has been upgraded.
Get-EmailAddressPolicy | Format-List Name,*RecipientFilter*,ExchangeVersion
You can try to use
Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients to upgrade.
After that, you can try the cmdlt to create address list again.
Address List and EAP filter upgrades with Exchange Server 2007
http://msexchangeteam.com/archive/2007/01/11/432158.aspx
Regards,
Xiu
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 8:44am
That was it! Thank you.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
July 15th, 2010 2:43am
Spoke too soon. I can set the parameters and preview the list membership, but it still won't actually create it.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2010 3:26am
Hi,
After you upgrade the default email address policy,please check the version of it.
Also please run update-emailaddresspolicy -identity "Default Policy".
Besides, I'd like to know the detail cmdlt that you use to create the address list.
Regards,
Xiu
July 15th, 2010 5:23am
[PS] C:\>(get-emailaddresspolicy "default policy").exchangeversion
NextMajorVersion : 1.0 (0.0.0.0)
NextMinorVersion : 0.2 (0.0.0.0)
Major : 0
Minor : 1
ExchangeBuild : 8.0.535.0
[PS] C:\>new-addresslist -name "Test" -Displayname "Test AL" -recipientcontainer "ou=bk006,ou=cbc users,dc=cbc,dc=cts" -
includedrecipients "allrecipients"
You can't specify the recipient container because legacy servers are detected.
+ CategoryInfo : InvalidArgument: (\Test:ADObjectId) [New-AddressList], InvalidOperationException
+ FullyQualifiedErrorId : 76EB9DD3,Microsoft.Exchange.Management.SystemConfigurationTasks.NewAddressList
[PS] C:\>[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2010 5:40am
Hi,
First I found that the cmdlt
new-addresslist do not have
recipientcontainer this parameter. So if you use this parameter in the mix environment that has exchange 2007, I think it will not process the cmldt. That should be the root cause of the
issue.
Besides, the use of the
RecipientContainer property inside the
RecipientFilter parameter is not supported/possible even though it is listed as valid. We can find that the OPATH property
RecipientFilter actually maps to the LDAP attribute
msExchDynamicDLBaseDN (http://technet.microsoft.com/en-us/library/bb430771(EXCHG.80).aspx)
Regards,
Xiu
July 15th, 2010 6:42am
Also I found a similar thread, Exchange users do have done the local test.
addresslist with filter for multiple OU´
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/6f9c0f4d-13ba-4d74-bd46-1d210ec5d830
Regards,
Xiu
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2010 6:44am
So specifying the recipient container when creating an adderss list through the New Address List Wizard in the GUI will not work, either, as long as I still have 2007 servers in the mix? I have a legacy application that runs on 2007, and I don't
expect the vendor to get it upgraded for 2010 any time soon.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
July 15th, 2010 6:48am
Yes, that could be the stick.
Regards,
Xiu
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2010 4:50am