Is there any cmdlet available to convert a Distribution Group's Scope to Global from Universal? Thanks in advanceRegards from www.windowsadmin.info

Not sure, I've used admodify in the past to do this. Active Directory: Convert Global Groups to Universal Groups Bulk http://msexchangetips.blogspot.com/2007/11/active-directory-convert-global-groups.htmlJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi ManU, Will this cmdlet be helpful? Get-DistributionGroup | where { $_.grouptype -Like "global*" } | Set-Group -Universal Frank Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Frank's cmdlet should work.Gulab | MCTS-MCITP Messaging: 2010 | MCTS-MCITP Messaging: 2007 | MCC 2011 | Skype: Gulab.Mallah

Hi Frak, Thank you very much for your support. As I have mentioned in my question, I am actually trying to convert a Universal group to Global group and I think you guys answered for the reverse operation. Could you please support me on this? Regards from www.windowsadmin.info

With Exchange 2007 there's no cmdlet to change the scope to anything except universal. For what reason do you want to change the scope of the group to anything other than universal?--- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Thanks for your support. The reason for my question is like this: I have to audit the mailboxes of an AD Group, which is a Global-Security group . For that, I wrote a script to convert first, the group in to Universal-Distribution and I can generate the CSV file required. Again through script, I can modify the group to Security. To complete the task, I need to have a script again to set the group as Global as previous. Do you have any other solution?Regards from www.windowsadmin.info

Why not just use the get-group cmdlet if all you want is the membertship of the group? There's no need to worry about the scope of the group. All you need to worry about is whether the group exists in a multi-domain forest. If it does, then "Global" is probably the wrong scope if it's used for sending e-mail. (get-group <name>).members--- Rich Matheisen MCSE+I, Exchange MVP