I have just taken an exchange 2010 install (two nodes dag, two CAS/Hub transport servers) from 2010 RTM to 2010 SP1 Rollup 3v3 released on 27th of June 2011 I think.
The updates took way longer than anticipated. When SP1 is applied without any preparation will highlight a lot of pre-reqs. In practice I found the following were required:
– apply all Windows high priority updates
– install the filterpack64bit.exe
applying the service pack itself, happened without any problems on the non-mailbox server.
On the DAG it is important to:
– make sure that there are no mounted copies on the server on which the SP is applied.
the CAS servers may go into a frenzy, processing the queues accumulated in the process, no need to panick, things will go back to normal fairly quickly.
————–
exporting mailboxes to pst’s. Exchange 2010 SP1 has a nice allows export of mailboxes to pst files, without the need for an outlook installation on the server, as it was the case on Exchange 2010 RTM.
the following steps will accomplish this:
– set the permissions:
New-ManagementRoleAssignment -Name “[name of the role assignment]” -SecurityGroup “[security group in AD]” -Role “Mailbox Import Export”
the AD security group needs to be universal; at least that was my case
– set a network path – make sure that “Exchange Trusted Subsystem” is given appropriate permission on the share
-the actual export of the mailbox to pst:
New-MailboxExportRequest -Mailbox [mailbox name] -FilePath “[the path to the desired pst file on the storage]”
get-MailboxExportRequest will display the status of the current exports
you can do this in bulk in two steps:
first identify the users (disabled users for example)
$mailboxname = get-mailbox -Server [Server Name] | where { &_.ExchangeUserAccountControl -match “AccountDisabled” }
then operate the export request on the variable:
$mailboxname | foreach-object {New-MailboxExportRequest -Mailbox $_ -filepath [the path to the pst storage]