With the new DST changes, many customers are asking about how to identify all their public folder calendars and their owners. Fortunately, this is very easy to do using PFDAVAdmin. When you crea...
Published Feb 16, 2007
Version 1.0
Blog Post
Hi Harry,
I noticed on the blog post here you already answered your own question: http://msexchangeteam.com/archive/2007/02/21/435543.aspx.
One way you can save yourself the manual work is to use a Powershell one-liner like this:
get-content $homedesktoppermissionsexport.txt | foreach { "tzmove -Q \Public FoldersAll Public Folders" + $_.Split(@(9))[1].Substring(14) + "" } > $homedesktopmybatchfile.bat
That will produce a batch file with the tzmove commands for each folder. Note that there is one part of this one-liner that you may need to modify, and that's the [1]. In this case I'm using a permissions export where the folder path column is the second column in the tab-delimited file, so [1] refers to that column (because the first column is column 0). If you're using a Property Export where the folder path is in the first column, you'll need to change [1] to [0]. This one-liner also reformats the folder path so that it's in the format you mentioned in your comment on the other post.
You also might want to remove any lines from your file that don't contain folder paths (such as the comments at the top of a PFDAVAdmin permissions export). Otherwise the one-liner will spew errors for those lines.
I noticed on the blog post here you already answered your own question: http://msexchangeteam.com/archive/2007/02/21/435543.aspx.
One way you can save yourself the manual work is to use a Powershell one-liner like this:
get-content $homedesktoppermissionsexport.txt | foreach { "tzmove -Q \Public FoldersAll Public Folders" + $_.Split(@(9))[1].Substring(14) + "" } > $homedesktopmybatchfile.bat
That will produce a batch file with the tzmove commands for each folder. Note that there is one part of this one-liner that you may need to modify, and that's the [1]. In this case I'm using a permissions export where the folder path column is the second column in the tab-delimited file, so [1] refers to that column (because the first column is column 0). If you're using a Property Export where the folder path is in the first column, you'll need to change [1] to [0]. This one-liner also reformats the folder path so that it's in the format you mentioned in your comment on the other post.
You also might want to remove any lines from your file that don't contain folder paths (such as the comments at the top of a PFDAVAdmin permissions export). Otherwise the one-liner will spew errors for those lines.