?
Solved

Outlook 2007 SP3 client, Office 365 Post-Upgrade, free/busy and calendar problems

Posted on 2013-06-03
9
Medium Priority
?
1,130 Views
Last Modified: 2013-06-07
I'm running Outlook 2007 clients, updated to SP3, on Windows 7 Professional.  Connecting to Office 365 POST UPGRADE.

I have verified that auto discover is running properly (although it was a long battle to make that happen...)

On some clients, clicking on ANY calendar keeps popping up a free/busy error.  Also when selecting the user's own calendar and clicking "NEW" generates a free/busy information error.

Some posts I've read point to the powershell commands to reset the default permissions, however I've found that they are pre-upgrade, and the commands are not part of the MSOL cmdlet package for powershell.

Any ideas would be greatly appreciated.
0
Comment
Question by:MarketingDrive
  • 5
  • 4
9 Comments
 
LVL 45

Expert Comment

by:Vasil Michev (MVP)
ID: 39219539
Can you provide some more information? What is the exact error message? Do you have a local AD, have you ever had local Exchange server? Does the issue happen for clients outside of your company environment, such as home PCs? What are the results from test E-mail Autoconnectivity (or ExRCA: http://aka.ms/rca, Office 365 tab, Outlook Autodiscover)

If you suspect the issue is with Calendar permissions, you can view/reset them using Exchange Online PowerShell:

http://help.outlook.com/140/cc952755.aspx

Once connected, use the Remove-MailboxFolderPermission command:

http://technet.microsoft.com/en-us/library/dd351181(v=exchg.150).aspx

(it might be easier to use Outlook to remove them)
0
 
LVL 1

Author Comment

by:MarketingDrive
ID: 39219644
Error when you click on a shared calendar is "folder already exists," and error when you click on "new meeting" on your own calendar is "cannot open free/busy information."

We have local AD running on Windows Server 2008 R2.

We used to have an on premises Exchange 2010 server which has been UNINSTALLED.

Seems its only affecting domain machines, as home machines and MAC's are fine.

ExRCA passes the autodiscover test, as does CTRL+Clicking on the outlook system tray icon and performing the autodiscover test from there.

As for the powershell commands, the Remove-MailboxFolderPermission command does not appear to be a valid O365 POST UPGRADE cmdlet.  

Thanks, Dave
0
 
LVL 45

Expert Comment

by:Vasil Michev (MVP)
ID: 39219734
It's not about just passing the test, but getting the correct EWS URL.

If it's only an issue with domain machines, it might be due to the way Outlook searches for the endpoints. In a local domain environment, it will always use the SCP first. You can review the following article about more information:

http://support.microsoft.com/kb/2212902

My suggestion is to try bypassing the SCP lookup and see if that changes things.


And i can assure you that the Remove-MailboxFolderPermission cmdlet is present in the new version as well, you are either not connected to Exchange Online or using account with limited access:


PS > Get-Command Remove-MailboxFolderPermission

CommandType     Name                                               ModuleName
-----------     ----                                               ----------
Function        Remove-MailboxFolderPermission                     tmp_hsvufl1e.vma


PS > Get-OrganizationConfig | Fl AdminDisplayVersion


AdminDisplayVersion : 0.20 (15.0.651.16)


Anyway, you can use Outlook when it comes to folder/calendar permissions, just verify them from the Properties dialog. But first lets make sure its trying to connect to the correct EWS
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
LVL 1

Author Comment

by:MarketingDrive
ID: 39219893
Thank you for your reply-  I have already removed any outlook autodiscover entries in the registry, that is how i was able to get autodiscover to work again.

As for the Remove-MailboxFolderPermission command, I've tried it in Azure AD Powershell and in regular Powershell with the following error:

Get-Command : The term 'Remove-MailboxFolderPermission' is not recognized as the name of a cmdlet, function
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path
and try again.
At line:1 char:1
+ Get-Command Remove-MailboxFolderPermission
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Remove-MailboxFolderPermission:String) [Get-Command], Comman
   ception
    + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand



That being said, I'd love to use outlook to manage permissions, but I get the error in outlook...

The EWS address that the autodiscover address uses is:  https://outlook.office365.com/EWS/Exchange.asmx.
0
 
LVL 45

Accepted Solution

by:
Vasil Michev (MVP) earned 2000 total points
ID: 39220078
The EWS url looks good. Did you obtain in from the local client or the ExRCA test (just to make sure that indeed the Outlook client is seeing the correct URL)?

If the EWS isn't the problem, we should look at the permissions I guess. Please use the instructions in this article to connect PowerShell to Exchange Online:

http://help.outlook.com/140/cc952755.aspx

It will work with either regular PowerShell or the Azure one. Then, please run the following command on one of the affected mailboxes:

Get-MailboxFolderPermission -identity user@domain.com:\calendar

We can examine the output and see if there is anything wrong with the permissions.

Also, try to narrow down the issue. Does it affect all users or only specific ones? Can you reproduce it on another machine with one of these users, preferably outside of your company network? Use a different version of Outlook as well, you can just get the free Office 2013 trial one. Were the users migrated from on-prem or? Does it affect users created in the cloud?
0
 
LVL 1

Author Comment

by:MarketingDrive
ID: 39230220
Output from Get-MailboxFolderPermission -identity user@domain.com:\calendar for a user who cant create an appointment on their own calendar:

FolderName           User                 AccessRights                                                                
----------           ----                 ------------                                                                
Calendar             Default              {AvailabilityOnly}                                                          
Calendar             Anonymous            {None}
0
 
LVL 45

Expert Comment

by:Vasil Michev (MVP)
ID: 39230267
Nothing unusual here as well. We missed one obvious test however, what happens when the user tries to make an appointment using OWA? As there is nothing wrong with the permissions and autodiscover, we are left with a client issue. So just ask one of the users to login to the Outlook Web App and test from there.

Lastly, perform the Synchronization, Notification, Availability, and Automatic Replies test from ExRCA: https://www.testexchangeconnectivity.com/. Among other things, it creates calendar appointments and check for free/busy information.
0
 
LVL 1

Author Comment

by:MarketingDrive
ID: 39230479
I created a security group and then used the powershell command Add-MailboxFolderPermission to add that security group to the shared calendar and it worked just fine.

I think now that I can assign as a group, i just have to examine the remaining users' folders who are having sharing issues and assign with the same command, or using the Set version.

Thank you for working through this problem with me, it led me down the correct path.
0
 
LVL 1

Author Closing Comment

by:MarketingDrive
ID: 39230480
Excellent troubleshooting and very helpful recommendations.
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As a Microsoft Exchange user, you must have known the importance of an Offline storage table (OST) file. It is nothing new for an Outlook user to be dependent on a .ost file during a server break down or a problematic Internet connection. In such a…
The Exchange database may sometimes fail to mount owing to various technical reasons. A dismounted EDB file can be the source of many Exchange errors including mailbox inaccessibility for users. Resolving the root cause of mounting problems becomes …
The video provides a quick and easy steps to migrate MBOX file to well known Outlook PST and Office 365. Besides this, it also supports and migrates more than 20 email clients of MBOX which include AppleMail, Opera, Thunderbird and SeaMonkey effortl…
The video will let you know the exact process to import OST/PST files to the cloud based Office 365 mailboxes. Using Kernel Import PST to Office 365 tool, one can quickly import numerous OST/PST files to Office 365. Besides this, the tool also comes…
Suggested Courses

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question