Mail-Enabled Security Groups after migration from Exchang 2003 to Exchange 2010
After we have migrated all users from Exchange 2003 to Exchange 2010, users are now unable to manage mail-enabled security groups they have permissions to manage. When viewing the groups, a lot of them have invalid Alias's (a space or other character), and when this is corrected manually we get a message advising that to save the changes the object must be upgraded to the current Exchange version. We have 200+ groups that need to be changed. Is there any way to perform both these steps (correct the Alias and upgrade the exchange version) using powershell? Thanks Dan
January 5th, 2011 9:41pm

Not easily. You'd need a script, like the following. $Lists = Get-DistributionGroup | Where-Object { $_.Alias -like "* *" } ForEach ($List In $Lists) { $Alias = $List.Alias -Replace (" ", "") $Identity = $List.Identity Set-DistributionGroup -Identity $Identity -Alias $Alias -WhatIf:$True } Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
January 5th, 2011 10:51pm

Thanks Ed...that's what I thought :-) What about the object upgrade to the latest Exchange version? Dan
January 5th, 2011 10:57pm

Try this: Get-DistributionGroup –ResultSize Unlimited | Set-DistributionGroup –ForceUpdateTim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
Free Windows Admin Tool Kit Click here and download it now
January 5th, 2011 11:05pm

I am getting a lot of warning errors that the group may be corrupt or an inconsisten state. This may be due to invaluid characters. I receive "Cannot bind argument to parameter 'Identity' because it is a null." The reason I need this is because my groups are in this state. Any thought. I am also extremely green with using Power Shell. Thanks PaulPaul Glickenhaus
March 23rd, 2011 3:39pm

You have to figure out what the conditions are and fix them. They might not all be spaces, and there may be spaces at the beginning or end of the line. Try these to get rid of leading and trailing spaces. Run each a couple of times along with the one I gave you before to make sure you get rid of all the spaces. Even after doing this, there may be other bad characters like at symbols. $Lists = Get-DistributionGroup | Where-Object { $_.Alias -like " *" } ForEach ($List In $Lists) { $Alias = $List.Alias -Replace (" ", "") $Identity = $List.Identity Set-DistributionGroup -Identity $Identity -Alias $Alias -WhatIf:$True } ************* and ************* $Lists = Get-DistributionGroup | Where-Object { $_.Alias -like "* " } ForEach ($List In $Lists) { $Alias = $List.Alias -Replace (" ", "") $Identity = $List.Identity Set-DistributionGroup -Identity $Identity -Alias $Alias -WhatIf:$True } Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2011 3:45pm

Not usre if this is because we have not finished our migration yet.Paul Glickenhaus
March 23rd, 2011 3:55pm

You can fix these at any time. You don't actually migrate the distribution groups; they appear because they're already in Active Directory.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2011 4:27pm

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

Other recent topics Other recent topics