A co-worker is working with RIM Tech Support to correct a problem on our BES server. She's trying to run the following command in EMS: Get-mailboxcalendarsettings | set-mailboxcalendarsettings - removeforwardedmeetingnotifications $true. But she keeps getting an error "cannot save changes made to an item to store". She has Exchange Organization Level permissions. Can anyone help determine the problem?

Follow up: We were able to get the command to run using set-mailboxcalendarsettings . Could it be an issue with the pipe command?

Does this work?get-mailbox | set-mailboxcalendarsettings - removeforwardedmeetingnotifications $trueset-mailboxcalendarsettings requires an Identity parameter as pipeline input, but get-mailboxcalendarsettings doesn't provide one.

No same error ... Here's the whole thing:Cannot save changes made to an item to store.At line:1 char:1+ g <<<< et-mailbox | set-mailboxcalendarsettings -removeforwardedmeetingnotifications $true

Do you get this on every mailbox or only some of them?get-mailbox |% {Write-host $_.displayname set-mailboxcalendarsettings $_ -removeforwardedmeetingnotifications $true}

When I ran the command I only got one response, which was the error shown above.

You got that when you ran the script I posted?

No, sorry, I got that reponse to the original command I ran.When I ran your script, I got a response from each mailbox. Each one looked like this:Joe User set-mailboxcalendarsettings Joe User -removeforwardedmeetingnotifications TrueCan you explain why your script worked and the original command did not?

I'd have to do some testing. It doesn't appear to like that particular pipeline construction. Are you using Powershell V1 or V2? I seem to remember something about a change in V2 that disallowed changing the current piepline object within the pipeline.

PowerShell v1

Are you running the command from the server, or from a workstation with the management tools installed?If you're running it from a workstation, do the versions match between the management tools there and the Exchange version on the server?

command run from server

Weird. It may be version specific. I'm running V2 on my servers, and I cannot reproduce that.