cmdlet: Reporting
Hi Exchange wizards,
Kindly help me in developing a cmdlet to report the Exchange attributes (Mailbox size etc..) of the members of a security group as a csv file.
Exchange Server: 2007
Many Thanks in advance
Regards from www.windowsadmin.info
March 14th, 2011 10:45am
I recommend that you post this in the Exchange Server Development forum.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 14th, 2011 1:58pm
Hi ManU,
Will this cmdlet be helpful?
Get-DistributionGroupMember "SG" | foreach {Get-MailboxStatistics $_.Name} | select DisplayName,TotalItemSize | export-csv
c:\test.csv
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.
March 15th, 2011 4:13am
Hi Frank,
Thank you very much for your solution. Unfortunately, I need it for a Security group. That group has some users and I have to generate a report on the users presented in that group. Couild you please help on this?
Cheers,
Manu
Regards from www.windowsadmin.info
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2011 4:44am
you can try something like this:
get-adgroupmember groupName | foreach {Get-MailboxStatistics $_.Name} | select DisplayName,TotalItemSize | export-csv
c:\test.csv-join("74686979616775313440686F746D61696C2E636F6D"-split"(?<=\G.{2})",21|%{[char][int]"0x$_"}) www.myExchangeWorld.com This posting is provided "AS IS" with no warranties, and confers no rights.
March 15th, 2011 8:54am
Oh, I thought he was asking to develop a cmdlet, not come up with a command!Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2011 11:26am
Hi Thiyagu,
Thank you for your contribution. But it gives me an error:
The term 'get-adgroupmember' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.
I think, it is because the powershell is not supporting the cmdlet (may be because of the reason that I am using WIN2K3)
Do you have a suggestion on this?
Thanks,
ManuRegards from www.windowsadmin.info
March 15th, 2011 11:37pm
Will this cmdlet be helpful?
Get-DistributionGroupMember "SG" | foreach {Get-MailboxStatistics $_.Name} | select DisplayName,TotalItemSize | export-csv
c:\test.csv
Hi ManU,
If possible, maybe you can temp mail enable the Security Group, after you get the report, disable it.
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.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 3:14am
Hi Frank,
That's very good.
If we are going for this solution, we may include the cmdlets “Enable-DistributionGroup -Identity "LargeMailboxUsers” and Diable-DistributionGroup
-Identity "LargeMailboxUsers” also in the ps1.
Many Thanks
Regards from www.windowsadmin.info
March 16th, 2011 5:13am
The cmdlet is Get-QADGroupMember, but it is part of the Quest ActiveRoles product. I believe that there's a free download of it here:
http://www.quest.com/powershell/activeroles-server.aspx.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 9:49am
The cmdlet is Get-QADGroupMember, but it is part of the Quest ActiveRoles product. I believe that there's a free download of it here:
http://www.quest.com/powershell/activeroles-server.aspx.
There's also the standard Get-Group.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
March 16th, 2011 9:49am