Hi

I am trying to apply the following setting

Set-CalendarNotification -Identity "username" -CalendarUpdateNotification $true

The error I get back is

The operation couldn't be performed because object "username" couldn't be found on 'DC.local.domain'

Ive checked the DC that it reports and the user exisits, aslo if I run the get-mailbox command it locates that user.

I have tried using set-AdServerSettings -ViewEntireForest $True and also Set-AdServerSettings -RecipientViewRoot "contoso.com/Marketing Users" (obvisoluly subsituating our domain dn OU etc :)

Im at a bit of a loss to why the system cant find this users. I tried some other users but they have the same problem.

Any ideas?

Hello

exchang prowershell start remotely over http://cas/proweshell or install exchange management shell localy?

Hi,

I am running the exchange management shell directly on the Exchange server. We actually have two servers in a DAG. Both have the same issue, each of them use a different DC, so doesn't look like a problem isolated to a single DC either

Is it s single forest, single domain or is it more complex than this? 

I have an empty root with 3 tree-root domains (exchange is installed in one of these) and a child domain.  I usually use set-adserversettings -viewentireforest $true before I run a command. 

Thanks,

Jason

Hi Jason

We have two forests with a trust. Single domain in both. Ive tried the viewentierforest command but no joy unfortunately. Also specifying the OU the user is located in didn't seem to help.

Anything else I can try?

Hi aqualityplace,

Thank you for your question.

We could refer to the following link to use Set-CalendarNotification:

http://technet.microsoft.com/en-us/library/dd351284.aspx 

The assigned permission to run the cmdlet is Recipient Management Role Group.

But if we run the cmdlet Get-ManagementRoleEntry "*\Set-CalendarNotification" , we will find the cmdlet is only included in the "MyTextMessaging" End user Role.

So we suggest the feature only be set by oneself (we can set it in ECP: See All Options->Phone->Text Messaging).

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Thank you for the suggestion. Turns out I had miss understood the requirement. Customer just reported they had a problem running that cmdlet.

I didn't check the behaviour they were expecting. They don't actually use any unified messaging so have no phone or text functionality other than active sync. So this wouldn't work for them anyway....

Your suggestion will still be helpful for anyone who may require this though :)

Thanks again