The Network Administrator

To get current user status

PS] C:>Get-MailboxAutoReplyConfiguration Joe.blow

To disable out of office for a user

[PS] C:>Set-MailboxAutoReplyConfiguration joe.blow -AutoReplyState Disabled

I know that with the release of Service pack 1 for Exchange you may not need the PowerShell commands for permissions, here is a great reference.

http://technet.microsoft.com/en-us/library/bb310789.aspx

With Exchange 2010, I remember writing an article on using the PowerShell commands to export a user mailbox to a pst file before SP1. After applying SP 1 to my Exchange 2010 server, these steps have again changed!

You need to use an account that’s a member of the organizational management groups, and have the “Mailbox Import Export” role assignment assigned to you or a role group you’re a member of.  You must specify a UNC path to a network share that the “Exchange Trusted Subsystem” group has read/write access to.

Step One
Create a share on a server, and grant Exchange Trusted Subsystem read/write permission. In this example I’m using “\\servernamehere\c$\ArchivedEmails”

Step Two
Next, you’ll need to grant a user, or group, the Mailbox Import Export role assignment. You can do this using the Exchange Management shell.

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User DomainName\UserName, close and re-open the Exchange Management shell, and you’re ready to go!

Exporting a Mailbox
New-MailboxExportRequest command with the –Mailbox parameter, to specify the mailbox to export along with the –FilePath “\\ExchangeServerName\c$\ArchivedEmails\EmailAlias.pst”

Check the mailbox export progress

Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

Head to your EMC (Exchange management shell) and fire off this command


Remove-MailboxPermission -Identity 'username' -User 'domain\username' -AccessRight FullAccess -InheritanceType All


“Operation could not be completed because something changed in the remote forest.”

If you see this error, the most common cause is an Exchange rollout update http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a371fa96-e85b-4a4f-8242-15d56595d0ec&displaylang=en was installed on the workstation, but not yet installed on the server itself. Once this update is on the server and on the workstation you should be all set.

In Exchange 2010 SP1, ISInteg is no longer a standalone program.

The functionality provided by the ISInteg tool has been rolled into two new Exchange Management Shell cmdlets:

New-MailboxRepairRequest
New-PublicFolderDatabaseRepairRequest

These new ISInteg cmdlets come with some cool new functionality!
The cmdlets work with the database mounted. It’s no longer required to unmount the database to perform an integrity check or fix database errors.
You can repair logical corruption at the mailbox level.
You can fix corrupt search folders.
You can fix the Provisional Fid.
You can fix Aggregate Counts.

More info….

http://msexchangeteam.com/archive/2010/08/23/455899.aspx

Open Your Exchange Management Shell and issue the script below


Get-MailboxStatistics -Server SERVERNAMEGOESHERE | Sort-Object -Property TotalItemSize | `
Format-Table DisplayName,TotalItemSize


Or descending


Get-MailboxStatistics -Server SERVERNAMEGOESHERE | Sort-Object -Property TotalItemSize -Descending | `
Format-Table DisplayName,TotalItemSize


While trying to Export a user mailboxes to pst file i am getting an error message. Also it fails with the Error “Error was found for username (UserNameEmailAddress) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219”.

***Updated***

***Must have Outlook 2010 64bit installed on the server.

It looks the work around for this was to logon to the exchange server as  administrator, launch the windows power shell modules as Administrator,

Then type Export-Mailbox –Identity EmailAlias@domainname  –PSTFolderPath C:\EmailAlias.pst


Goodbye PFDAVAdmin and hello Exfolders. I recently used this tool to recover a public folder that was deleted by an end user.

You can download the tool here:
http://msexchangeteam.com/files/12/attachments/entry453398.aspx

ExFolders must be run from an Exchange 2010 server – it cannot be run from a workstation as PFDAVAdmin could.

It can connect to Exchange 2010 or Exchange 2007, but not older versions.

Remove Item-Level Permissions is gone, because there are no item-level permissions in Exchange 2007 or 2010.
DACL fix functionality is gone.

There are also a few new features:

Folder property imports are now supported. You were able to do folder property exports with PFDAVAdmin, but not imports.

Item property exports are supported – that is, you can export a set of properties from all items in a folder. This feature request has come up again and again for troubleshooting purposes. Item property imports are not supported.

ExFolders supports the new free/busy permissions that were introduced in Exchange 2007 and Outlook 2007.

You can now connect to multiple mailbox stores at the same time, so you can run a batch operation against several mailbox stores or all mailboxes in the org if you need to.

http://msexchangeteam.com/archive/2009/12/04/453399.aspx

So after we had Exchange 2010 installed, and verifying all activeSync settings were correct. I kept getting cannot connect to server when setting up ActiveSync on my iPhone…This is was solved the issue…

This issue occurs if the AD user object of the Exchange 2010 user doesn’t have “Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with entries explicitly defined here.”

Once this setting is checked, Exchange ActiveSync works again.