Data Firmware

Exchange Calendar Permissions Using PowerShell

With Exchange 2010 and now extended into Exchange 2013 and 2016, Microsoft added the ability to manage permissions on folders in a users email account through PowerShell.

The most common is managing calendar permissions.  Heres an example of some commands:

To get the permission on a mailbox:

Get-MailboxPermission -Identity "Boss Hog"

To get the permissions of a subfolder:

Get-MailBoxFolderPermission -Identity "Boss Hog:Calendar"

To change permissions on a subfolder:

Add-MailboxFolderPermission -Identity "Boss Hog:Calendar" -user "Roscoe" -AccessRights Reviewer

To remove permissions on a subfolder:

Remove-MailboxFolderPermission -Identity "Boss Hog:Calendar" -user "Roscoe"


Heres also a list of all of the permissions you can assign.  HERE is a link to Office support with some details on what each of these permission levels can do.

• None
• Free/Busy
• Free/Busy, Subject, Location
• Contributor
• Reviewer
• Nonediting Author
• Author
• Publishing Author
• Editor
• Publishing Editor
• Owner

Get

Export Emails within a Date Range from Exchange 2010

Today I had to do this to assist with an email audit for a government agency.  Below are the steps you need to follow to make this happen.  The TechNet article leaves out a very important step that I have included for you below.


1. Open up the Exchange Management Shell and enter the following command:  New-ManagementRoleAssignment –Role “Mailbox Import Export” –User "DOMAINUSERACCOUNT"

**NOTE:  Now close the EMS and reopen it.  You have to do this because the roles for the user logged in are loaded when the EMS is started.

2. Use this command to export your email date range and the location where you want to save it: New-MailboxExportRequest -Mailbox "SAMPLE USER" -ContentFilter {(Received -lt 01/01/2012) -and (Received -gt 03/31/2012)}  -FilePath "SERVEREXPORTSSAMPLE_USER.pst"

Depending on the size of the users email you may get a file rather quickly or you may get a message from the EMC that the job is queued and will be filled when it is completed the search and export process.

What lead me here was the error "The Term New-MailboxExportRequest is not recognized as the name of a cmdlet, function, script file, or operable program".

The steps above will avoid this error and get you exactly what you need from the email box.

If you just want to dump the entire mailbox use this:  New-MailboxExportRequest -Mailbox "SAMPLE USER" -FilePath "SERVEREXPORTSSAMPLE_USER.pst"

Get

Exchange SP2 Install Error This Server Role Cant Be Installed Because the Following Roles

Mailbox role

Get

Adjust Exchange 2013 Send Receive Message Size Limits

After setting up and Exchange 2013 SP1 server on Server 2012 R2 I ran into this small issue with a customer.  Even though I had all of the send/receive connectors in the ECP set at 100M, I was still hitting the default 10M attachment size limits.

Heres how to fix that by changing the Global Transport Settings: (short answer)

Check to see what the size limits currently are -
Get-TransportConfig | ft MaxSendSize, MaxReceiveSize

Once you know those sizes then heres the command to change them to what you need -
Set-TransportConfig –MaxSendSize 100MB –MaxReceiveSize 100MB

I know these sizes are a little large but just using them as an example.  Go ahead and bounce the Transport service just to be sure the settings take effect and youll be good to go.

All of the other size limits can be set using the ECP under Mailflow and then Send Connectors and Receive Connectors.

Update:  Ive just completed reading almost all of Mastering Microsoft Exchange Server 2013.  This is an excellent read that will give you tons of insight into installing, maintaining, and mastering all there is to Exchange 2013.  I highly recommend you give the book a read.

Get

Exchange 2010 Error A reboot from a previous installation is pending

If you are seeing this error while trying to apply an Exchange SP or RU and you have restarted heres a quick fix for it:

Get

Certificate Not Showing After Importing Into Exchange 2013

I ran into this one today with two servers in a DAG.  This is caused by the certificate youre using not having the private key.  Heres how I fixed it:

Go to the 1st server -> Start -> Run -> MMC -> File -> Add/Remove Snap Ins -> Certificates -> Computer Certificates -> Local Computer

Browse to the personal certificate store, right click on the correct certificate, select All Tasks, and then Export.  Make sure here you choose "Export Private Key" and assign a password.  Click Next and then name the file and where you want to save it.  The file will have a .pfx extension.

From there on the 1st server inside ECP you can go to Servers -> Certificates -> Choose the server you want and then import the certificate.

Once this process is done just assign the services to the certificate (SMTP, POP, etc) and then restart the server if possible.  If not some say you can do an IISRESET from the command prompt and then youll be good.

Good luck!

Get