Skip to main content

Listing Public Folders in Exchange Server

By

This weekend I built an entirely new virtual environment for my PowerShell classes moving forward.  Essentially I did this to add in some SQL, Exchange and DSC scenarios.  Just in time to.  I have two Exchange administrators in my PowerShell class this week here in Fort Wayne so I am using my new setup to enhance the class.  Here is the first one.

How do I let all of the public folders, including sub folders?

The Get-PublicFolder cmdlet can be used for this.  Here is the public folder structure that I created using the New-PublicFolder cmdlet.

Level 1 Level 2 Level 3
Folder1    
Folder2    
  FolderA  
    Folder1A
    Folder2A
  FolderB  

This command will recover all the public folders and their parents.

PS C:> Get-PublicFolder -Recurse | Select -Property name,parentpath

 

Name        ParentPath     

----        ----------     

IPM_SUBTREE                

Folder1     \              

Folder2     \              

FolderA     \Folder2       

Folder1A    \Folder2\FolderA

Folder2A    \Folder2\FolderA

FolderB     \Folder2

 

The second question is how to filter for public folders within a parent folder?

PS C:\> Get-PublicFolder -Recurse |

    Where-Object {$_.ParentPath -like "*Folder2*"} |

    Select -Property name,parentpath

 

Name     ParentPath     

----     ----------     

FolderA  \Folder2       

Folder1A \Folder2\FolderA

Folder2A \Folder2\FolderA

FolderB  \Folder2  

 

Here we are using The Where-Object cmdlet to filter the ParentPath property.  The Value of ParentPath is a string.  In this example, we are looking for any folder inside of Folder2.

Another option utilizes the FolderPath property.  The FolderPath property is an array of strings. 

PS C:\> Get-PublicFolder -Recurse |

    Select-Object -Property Name, FolderPath |

    Where-Object {$_.FolderPath -contains "Folder2"}

 

Name     FolderPath                 

----     ----------                 

Folder2  {Folder2}                  

FolderA  {Folder2, FolderA}         

Folder1A {Folder2, FolderA, Folder1A}

Folder2A {Folder2, FolderA, Folder2A}

FolderB  {Folder2, FolderB

 

This output also contains the root folder in the query, Folder2. 

More to come as we continue this week.

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more