Scheduling an exchange task on Exchange System Manager

I have an exchange 2003 server. I work for an Insurance underwriting company. Against my recommendations Management decided to use the Outlook public folders as part of processing new business, and renewals. End users would move related email correspondences with attachments to public folders. New subfolders are being created every day. I have been running a wizard in Exchange System Manager forcing permissions to propagate to the subfolders. Is there a way to schedule this as a task.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

First, I would highly recommend that you show the business value for not letting users create public folders.  If they need new folders, have them submit a request.

Second, everything can be scripted, and the key is using PFDAVAdmin and SETACL.

Again, this is putting a small bandaid on a big wound.  Stop the hemorraging and design a PF business process that uses existing folders.  No users should have rights above Editor so they cannot create subfolders or repermission folders.

It may sound draconian, but you will thank me when you finally transition to a newer version of Exchange and have to deal with improperly named PFs or worse, want to move to Hosted Exchange and have this business dependency using public folders as barrier.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mario716Author Commented:
I actually need to find a better application to woo management away from using public folder this way. I should had mentioned that I am planning to migrate to Exchange 2010 in a couple of weeks. Will the PF be a problem?
With Microsoft announcing that Public Folders have reached end of life but were put back into 2007 and 2010 I reallly don't think they will be in the next version of Exchange.  They are NOT in the online version.

The replacement for this is either SharePoint or some other product that integrates with Exchange.  By the way, scripting the permissions on these folders is really easy in PowerShell on 2010.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.