I need help enforcing all users to share their calendar. We have a company policy for sharing calendar of users, however we only set this up on first install of users, and some users turn this off later on. This is how we set up calendar sharing for our users: In Outlook: Click all folders view (on the menu to the left), then right click calendar and set permissons. We give a comany group named Company_Users read access to calendar. Then everybody in Company_Users can open and read calendar of other users. Is this possible to script somehow? Either at login as the user, or in Exchange PowerShell? E.g. create a task that run every night that override users that hide their calendar?

Not in Powershell but in PFDAVAdmin. Here's one of many tutorials on the Internet: FAQ: Give Calendar Read Permission on all Mailboxes – PFDavAdminJesper Bernle | Blog: http://xchangeserver.wordpress.com

Not directly via powershell, have to use EWS, examples below. Exchange 2007 - default-calendar-permission-powershell http://gsexdev.blogspot.com/2008/03/default-calendar-permission-powershell.html Exchange 2010 - default-calendar-permission-powershell http://gsexdev.blogspot.com/2011/01/default-calendar-permission-powershell.html James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

thanks. i need it scriptet, so im not sure if pfdavadmin will help... unless i can override this permanently.. the exchange 2007 seem to only do a default setup. what happens when a user modifies it afterwards? doesnt seem to help.. seems like there is an add-permission in the 2010-powershell however i dont run 2010..

Take a look at this one. Class library helper for setting Calendar Permission via Powershell and Exchange 2007 http://gsexdev.blogspot.com/2008/03/class-library-helper-for-setting.htmlJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

The PFDAVAdmin solution needs to be rerun to include new mailboxes from last run, so I guess it really isn't all that convenient. Go for the cooler ;-) solution suggested by James.Jesper Bernle | Blog: http://xchangeserver.wordpress.com

"The code itself is very untested and I don’t consider it stable and or safe for use in a production environment I can only recommend that you use it in a test/dev environment and as a guide to building your own applications. I’ve include a complied DLL as well as the full source so you can look/debug as you please. If you do spot any major bugs and things I’ve done wrong or that could be done better please let me know so I can update the source." well this doesnt look very promising...