exchange-2010powershell
We are working on Exchange through Exchange Management Shell and also PowerShell (snap-in Exchange 2010 added).
My point here is that we have two different series of answers.
EMS and PowerShell have two different behaviors.
Can you help to understand the differences between those two ?
I'm not talking about running scripts, but the way they work, they call Exchange for having such different answers.
Runspace ? Pipeline ? Permissions ?
Thanks in advance for the help you can provide.
I'd spin up an instance of an older version of Windows, install the Exchange 2003 management tools, and continue with the decommissioning procedure just to be safe. I'm assuming this is a production environment, and I don't think I'd toy around with deleting records via ADSIEdit.
I've finally fixed this.
Interestingly Send-As is an AD permission - not an exchange permission as you might have expected.
Anyway, these are the steps:
Make the target mailbox "shareable" using this command in Powershell on your Exchange Server:
Set-Mailbox user1 -type:shared
If you get this error (same as in my first post):
You will need to find that user in AD and go to the properties >> Security >> Advanced:
You need to ENABLE the option to "Include inheritable permissions from this object's parent":
Once that is done you should be able to complete the folder share script.
Then actually grant the rights using this command:
Add-ADPermission user1 -User Ourdomain\User2 -ExtendedRights "Send As"
Hope that helps others who have the same problem.
Kieran
Best Answer
I'd never given this much thought, but it appears you're right -- they're different.
Please take a look at this blog post for some more detail. The list doesn't look exhaustive by any means, but it might be a good place to start. The two most interesting points are quoted below --