I encountered this strange bug when testing Update Rollup 4 for Exchange Server 2007 SP3. Originally I was checking to see whether the same bug that surfaced with UR4 for Exchange Server 2010 SP1 would also occur with the Exchange 2007 update. Instead I found this other bug which I’d never seen before.
So far I’ve only tested this with Exchange Server 2007 SP3 (both with and without UR4) and Outlook 2007.
The bug occurs when copying a parent public folder into one of it’s own sub-folders. For example here if I copy the “Branch Office” folder into the “Sales Team” sub-folder.
To begin with I right-click the “Branch Office” folder and choose Copy “Branch Office”.
The copy dialog box opens and I select the “Sales Team” sub-folder.
After the copy has finished an extra instance of the parent folder has been created in the resulting folder tree.
Now granted this is not likely to be a common scenario, possibly not even a supported one, especially when performing the same copy via Outlook Web Access results in this message:
Between this and the problems seen with UR4 for Exchange Server 2010 SP1 I wonder if there should be a best practice to perform public folder structural administration (eg copying/moving folders) only via Outlook Web Access.
What is your opinion on this?
