Default Scope and Search Root cannot be set at the same time
Hello,
I am trying to add resource delegates for a resource mailbox in Exchange 2010, and it fails with the below error:
[PS] C:\Windows\system32>set-Ca
WARNING: An unexpected error has occurred and a Watson dump is being generated: Default Scope and Search Root cannot be set at the same time.
Default Scope and Search Root cannot be set at the same time.
+ CategoryInfo : NotSpecified: (:) [Set-CalendarProcessing], NotSupportedException
+ FullyQualifiedErrorId : System.NotSupportedExcepti
Can you please advise what is the reason, and how to view/change default scope/search root for mailbox(es)?
I am trying to add resource delegates for a resource mailbox in Exchange 2010, and it fails with the below error:
[PS] C:\Windows\system32>set-Ca
WARNING: An unexpected error has occurred and a Watson dump is being generated: Default Scope and Search Root cannot be set at the same time.
Default Scope and Search Root cannot be set at the same time.
+ CategoryInfo : NotSpecified: (:) [Set-CalendarProcessing], NotSupportedException
+ FullyQualifiedErrorId : System.NotSupportedExcepti
Can you please advise what is the reason, and how to view/change default scope/search root for mailbox(es)?
ASKER
As far as I know, it does not matter which format to use here:
http://technet.microsoft.com/en-us/library/dd335046.aspx
This parameter can take the following values:
DN
Canonical name
GUID
Name
Display name
Alias
Exchange DN
Primary SMTP e-mail address
http://technet.microsoft.com/en-us/library/dd335046.aspx
This parameter can take the following values:
DN
Canonical name
GUID
Name
Display name
Alias
Exchange DN
Primary SMTP e-mail address
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
failing cmdlet started working without any changes after delegates were added in Exchange Management Shell. Issue resolved.
Please describe in details your steps to resolve this issue.
ASKER
delegates have been added via EMC instead of EMS. After that, EMS cmdlet also worked. Root cause is unclear though.
set-CalendarProcessing -Identity NskRoom238 -ResourceDelegates:a.zimme
If this works, you can repeat the step for the other users.
Another good discussion here on this topic.
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/03c49126-942c-4d12-b92a-9c719fba3e26/