Yes, that was also one I didn't know about right away as it appears in 2010 docs, but wasn't really showing in the 2013 stuff--wasn't hard to find though after the EAC/GUI was prompting me to upgrade groups.
While we're sharing, I recall the first error message I got when someone couldn't manage their delegated DLs (after "upgrading"), the errors led me to this kb, which I see still lists 2013 as not being able to use groups: http://support.microsoft.com/kb/2586832 The second resolution link is the post from the OP, but the first link is also something we had to do to limit the abilities of DL managers the way we wanted. -B From: [email protected] [mailto:[email protected]] On Behalf Of Rami SIK Sent: Wednesday, May 07, 2014 1:15 PM To: [email protected] Subject: [Exchange] RE: Managing DLs with Groups Take a look at here: http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx We also needed to run a PS script to upgrade our DLs during migrating from Exchange 2007 to 2013! That script is provided in the Exchange 2013 scripts folder - Manage-GroupManagementRole.ps1, you may need to use ForceUpgrade switch! Regards, Rami From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aakash Shah Sent: Wednesday, May 07, 2014 12:32 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Managing DLs with Groups I just learned that with Exchange 2010 and Exchange 2013, you can no longer manage DLs with groups as per http://blogs.technet.com/b/exchange/archive/2011/05/04/how-to-manage-groups-with-groups-in-exchange-2010.aspx. Besides the workarounds mentioned on the blog above, are there any other workarounds/solutions that people have used to address this problem? My goal primarily is to be able to quickly audit a user's permission to identify what access permissions they have, ideally through the Member Of tab along with the rest of the user's permissions. Thanks, -Aakash Shah ________________________________ If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
