[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1277
  • Last Modified:

Lost access to Exchange public folder

Hi,

On monday I upgraded to Office 2010 on our terminal server.

We are running Exchange 2007 on a 2008 Small Business Server.

After this upgrade, I cannot access public folders anymore.
We have only used one public folder, and that was an email public folder for the leader of the company.

This folder is now unavailable, both from outlook 2010, outlook 2007 on a older installation, and also from the outlook web access!...

I do now know if the 2010 upgrade has anything to do with this happening, but I thought I would bring it up as an element just in case.

Now, the folder has been used every day, and stopped suddenly after the upgrade.

Anyone have an idea what could have happened?

As you can see from the image, the public folders tree is not showing any content, allthough there is a folder there.

 image showing the public folder with no content
0
Ring1
Asked:
Ring1
  • 3
  • 2
2 Solutions
 
abhijitmdpCommented:
Have you checked on your servers, whather the folders are visible there. Open exchange management shell and run below command and post the result.

Get-PublicFolder
Get-PublicFolderDatabase

Also check the public folder visibility from Exchange Management Console> Tool...>Public Folders
 and reply.
0
 
Ring1Author Commented:
Hi,

the folders are visible in Exchange management console, so that is affirmative.

However, I think I have tracked the problem now.

When the users got their new outlook, the first thing that one user was missing was the favorites folder, where the public folder was published, so what he did (that naughty user) was just simply move the physical folder fra puclic folders, over to his own exchange folder, and voila, the public folder as set up is still present, but the content is moved away.

I just re-created the folder after backing up the content and now it is okay....

cry wolf.....
0
 
Ring1Author Commented:
Fine
0
 
abhijitmdpCommented:
Its a good idea but are you still getting the error after this change.
0
 
Ring1Author Commented:
Solved this by performing some serious hearings with the users, and one of them admitted that he had abused the system "just a tad"....
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now