Currently uncategorized posts. This is a rather temporary holding place for posts that are not yet in the appropriate category. If I post new articles on the move, they may end up in here for a while until I am able to categorise.
I have noted there are quite a few folk who would like to use the user principle name for the Outlook Web Access login with Exchange 2007 / 2010. Some people would like to add the external domain name and use this as the UPN and login
The rights for public folders can be explicit rights such as “ReadItems” or “CreateItems” or ‘roles’ such as Owner, Contributor etc, which have a set of rights.
Add-PublicFolderClientPermission -Identity “Company Contacts” -AccessRights PublishingEditor -User Steve
This will add the PublishingEditor ‘role’ to Steve, so he is able to create and delete all items that he creates, and can delete all content items regardless of ownership (but cannot delete folders he does not own). He cannot change permissions on folders that he has not created.
There is also a Remove-PublicFolderClientPermissions that will remove any permissions you wish in the same manner as above.
This is fine on a folder by folder basis but what if we want to give permissions to All users or permissions for a specific user but recursively for a whole bunch of public folders. Well, that is where the AddUsersToPFRecursive.ps1 script comes in!
So, with this we specify the -TopPublicFolder and specify the username and we can add the specified rights recursivley to all public folders beneath. Useful if want the same permission structure on all public folders.
** Note, if the Top level PF has a space, you must place the name in ‘ ‘ inside the ” “. So -TopPublicFolder “‘\My Computer'” **
** Note, that you need to put the \ at the beginning of the path to represent the beginning of the public folder structure **
Recently a friend asked me why he cannot simply use the VSS capability of NTBackup on his 2003 64bit server to backup the Exchange system.
The answer lies in the generic nature of the VSS capability of NTBackup. It is not exchange-aware and requires that you make sure that all disks with exchange information are also backed up to ensure a successful backup.
There are no time advantages, because using the generic VSS streams the data, instead of a quick ‘snapshot’ of the data as a Fully exchange aware VSS based backup solution would offer.
This msexchangeteam article runs through this subject:
Many people sort incoming mail into folders, perhaps so they are not interrupted with email being delivered directly to their Inbox, and to prioritise the mail they wish to see now / those that they can review later.
The problem is with Distribution lists, it is not possible to see that the email has been sent to the DL address. So how can this be resolved?
There is a great little custom Transport Agent designed by the Microsoft Exchange Team that does just this: