Go to the Exchange Client Access Server and turn on EXTRA tracing. To do so, take these actions:

1) Go to Start, Run… Type EXTRA

2) Once EXTRA opens, at the Update and Customer Feedback screen, Choose “Check for Updates on Startup” and “I do not want to join the program at this time”

3) Check for Updates Now…

4) Once the updates have been applied, Go to the Welcome Screen…

5) Choose Select a Task…

6) Choose Trace Control… Click OK on the Informational Message

7) Verify that you have plenty of hard drive space on the server. Change the location of the trace file to the location with the larger amount of hard drive space available. Change the Maximum log file size from 100MB to 500MB. (Circular Logging should be enabled by default).

8) Then choose Set Manual Trace Tags…

10) Under Set Trace Tags Manually, select all the Trace Types…

11) Under Components to Trace section, Select OWA and ensure all Components should also be selected.

12) Apply the Mailbox filter for the User Mailbox who you can reproduce the issue with.

13) Start Tracing and reproduce the problem.

14) Stop the Tracing, The default location for the .ETL (EXTRA file) will be in the Root of the Current User directory if it hasn’t been changed previously in step 7.

Traces will be viewable by an Exchange Support Engineer.

Note1: He'll use a tool while extrace.exe –c –v ExchangeDebugTrace.ETL > output.csv

Note 2: Version Microsoft.Exchange.Diagnostics.dll must match the one corresponding to the server we took traces from...

Note 3: Exchange admins: don't take into account the above previous notes for your daily operations/troubleshooting, it's a reminder for me and a FYI so that you guys have an idea of things MS Support can do behind the scene...

Using ADSIEDIT :

go into configuration>services>microsoft exchange>administrative groups>... and navigate to any public folder database/store and check the properties

Find a msExchOwningPFTree attribute:

this should equal the distinguished name of the public folder hierarchy. In my example :

CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SSC-SPC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAINA,DC=CONTOSO,DC=CA

We should see a Folder Hierachies container holding the Public Folders container:

=> that key (CN=Public Folders) links each public folder datase/store to the public folder hierarchy so that they can be seen/added/removed etc

If you have issues with your PF hierarchy or issues accessing your PF using OWA or Outlook or both, check that you have these attribute and AD Object correctly provisionned (msExchOwningPFTree attribute on database which DN should be equal to the one on the “CN=Public Folders” object under the  “CN=Folder Hierarchies” AD container)

This is one check among others for PF issues.

Sam

I’m a red fish, so I wrote the Powershell’s Job commands here so I’ll have a repository.

An other way to list the Job commands is to type get-command *-job or get-command –Noun job

• Start-Job :

Start-Job -ScriptBlock {dir –path c:\windows –rec}

Start-Job -Filepath c:\scripts\sample.ps1

Invoke-Command -computername s1 `

-scriptblock {get-eventlog system} –asjob

• Get-Job
• Receive Job [-keep]
• Wait-Job
• Stop-Job

Get-Job –name n*| Stop-Job

Stop-Job *

• Remove-Job