Migration to Exchange 2013: Calendar Permissions get lost using Outlook 2007

1. What was before

User or administrators in the Exchange 2007/2010 world are providing access rights to their calendar, resources, etc. – i.e. ‘reviewer’ on a Room-Resource for user or AD groups.

2. Now you migrate all mailboxes to Exchange 2013

3. What happens?

Outlook 2007 clients will receive a permission error while opening shared calenders, resources, etc.

“An error occurred when setting schedule permissions”

4. Solution

You can follow this long-winded MS Solution: http://support.microsoft.com/kb/2836889/en-us

5. Or

Remove and Add all permissions again per Powershell:

 

 

Conclusion

Take care with your migration if your enterprise office standard is related  to Outlook 2007

 

 

 

 

Migration of Distribution Groups from Exchange 2007 / 2010 to 2013

What are you doing?

After migrating all of your groups to Exchange 2013 with

you try to change the membership either in PS oder EAC.

What happens?

Error

You don’t have sufficient permissions. This operation can only be performed by a manager of the group.

The Reason / The Solution

2007 and 2010 did not required the AD Attribute managedby (owner). Today, for Exchange 2013 this is a requirement. Just set the managedBy Attribute with set-distributiongroup to an Admin Group like “Organization Management”

 

have fun, Alex

Exchange 2013: Dude where is my Exchange-Server?

As you now, Exchange 2013 does not use the CAS Array Name itself for connecting to Exchange, instead it uses the MailboxGUID (which is equal to the ExchangeGUID Attribute)

Connection Status of Outlook:

 

With the following command we can figure out to which server the Mailbox belongs to:

Or just have a look to the “Proxy Server” in your Connection Status ;-) = right mouse + CTRL key on the Outlook Symbol in your taskbar.

have fun, Jimmy

Exchange 2013 EAC opens Exchange 2010 ECP – How to prevent it

In Coexistence to Ex2010, Ex2013 will proxy your Exchange Admin Center (EAC) Logon to the legacy Exchange Control Panel (ECP) of Exchange 2010 if your adminstrator account is still on Exchange 2010. You can move administrators mailbox to Ex2013 or you can add the extension ‘/?ExchClientVer=15’ to your ECP-URL. I always prefer adding this extension :-)

https://localhost/ecp/?ExchClientVer=15

have fun, Alex

Get-LogonStatistics not showing RPC Sessions

Last time I tried to troubleshoot some Throttling-Policy Limitations at customers side with Exchange 2010 and Outlook 2007. OK, what to do first? Yes, you will try to count the open active RPC / MAPI Session with following PS command:

So, what was the outcome? There was no open Session even the Outlook Account was active and working on the Exchange CAS Server. What was the solution? Yeah, quite simple – Remove / Replace the Outlook Profile :-)

 

Ex2013: Where is my OWA SSO to legacy Exchange 2007

Yes you red right and that is something I learned at customers field.

After setting your legacy URL:

and pointing your DNS Namespace to Exchange 2013, the new 2013 FBA will authenticate you. So far so good. Exchange now checks your location of mailbox and if you are still on Ex2007 it will “redirect”. As we learned, a hidden-formular with my credentials should be transfered to the legacy server where FBA (Forms Based Auth) is also active.

So what is the Clue? In Ex2007 you will have to authenticate a second time – Oh my God, who will tell this the customers?

have fun, Jimmy