Get-PublicFolder -recurse does not work with Exchange 2010
This simple PowerShell command works as expected in Exchange 2007 get-publicfolder "\test" -recurse it returns the public folder named test and all the folders under it. The command does not work in Exchange 2010; it simply returns the public folder named test with no subfolders. Having read and re-read the syntax for the get-publicfolder command in Exchange 2010 it seems as if it should still work. i have tried many variations of the \test ID ( '\test', \'test', \test, \"test", "\test", \"test\", \test\) and none works in Exchange 2010. Is there a trick to getting the -recurse option to work, or is is simply non-funcational in Exchange 2010? Thanks TBrennan
February 19th, 2013 4:04am
It is my experience that it works; I've certainly used it a lot.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
February 19th, 2013 9:33am
Einstein has been quoted as saying the definition of insanity is doing the same thing over and over and expecting different results. He died before the advent of modern computers or he would never had said that. I copied and pasted the command in my original post from an EMS window on an Exchange 2010 server; it would report only the top level folder named test with no subfolders whatsoever. This morning I copied the same command out of my original post and pasted it into the EMS window on the same Exchange 2010 server and it reported the top level folder and all the subfolders.TBrennan
February 19th, 2013 11:13am
Einstein never had to work with public folder replication. What probably happened in your case was that the public folder hierarchy hadn't yet replicated to the server on which you ran the command.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
February 19th, 2013 4:13pm