How do I use PowerShell to uncheck the folder visible property on a Public Folder?

I am creating several public folders and have the cmdlet to change default permissions to "None".  Once this is run, the permissions change to default, however the folder visible property is still checked so I am looking for a way to uncheck it so that the only folders that show are ones that the user has actual permissions to view.
2015-08-03-11-46-55.pdf
D BInfo Sys Engineer SrAsked:
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.

Will SzymkowskiSenior Solution ArchitectCommented:
All you need to use to remove this permissions is Remove-PublicFolderClientPermission. See below for example...

Remove-PublicFolderClientPermission -Identity \PublicFolder1 -User Default -AccessRights None

Open in new window


Will.
0

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
D BInfo Sys Engineer SrAuthor Commented:
That changes the permissions to none but unfortunately it does not uncheck folder visible.
0
Will SzymkowskiSenior Solution ArchitectCommented:
Ok so i have tested this in my lab and i have the following scenario...

Default was assigned to Author on a public folder

I then ran the following command...

Remove-PublicFolderClientPermission -Identity \PublicFolder1 -User Default -AccessRights None

Open in new window


When I ran that command it automatically removed the FolderVisible checkmark as well.

Will.
0
D BInfo Sys Engineer SrAuthor Commented:
Will,

What version of Exchange are you using?  I am wondering if this is an Exchange 2013 "feature".


Thanks,

D
0
Will SzymkowskiSenior Solution ArchitectCommented:
I have tested this on Exchange 2010 SP3, and it works without any issues. However in Exchange 2013 there is no different the cmdlet is the same. so it should work.
https://technet.microsoft.com/en-us/library/bb124573(v=exchg.150).aspx

Will.
0
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
Powershell

From novice to tech pro — start learning today.