Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -AllowedFileTypes '.rpmsg','.xlsx','.xlsm','.xlsb','.tiff','.pptx','.pptm','.ppsx','.ppsm','.docx','.docm','.zip','.xls','.wmv','.wma','.wav','.vsd','.txt','.tif','.rtf','.pub','.ppt','.png','.pdf','.one','.mp3','.jpg','.gif','.doc','.bmp','.avi','.xml'

With that in mind, I spent about 30 minutes to whip up a script to generate and email the server reports. Here is how you do it:

1. Download the latest version of the server kit, copy the script to a directory. I use a Win2k8 R2 VM host to manage my Exchange servers with EMC and execute remote commands. That said, I copied the files there. You'll need to follow the instructions to set the execution policy to allow "RemoteSigned".
2. I ran the discover command to find the servers in my domain, and then I used the DiscoverCSV switch to specify my CAS/HUB hosts:

   .\FPSSK.ps1 -Report -DiscoverCSV 'C:\[DIRECTORY]\FPSSK-[FILE].csv' -Log 'C:\[DESTIONATION]'

3. With the steps above out of the way, set up your email PowerShell script:

   $smtpServer = "[FQDN]"
   $msg = new-object Net.Mail.MailMessage
   $smtp = new-object Net.Mail.SmtpClient($smtpServer)
   $msg.From = "[SENDER]"
   $msg.To.Add(”[RECIPIENT]")
   $msg.Subject = "[SUBJECT]"
   # Piping the output from the summary report into the body of the message
   $msg.body = (gc "C:\[DESTINATION]\[SUMMARY-TEXT-FILE" | out-string)
   # Loop through the destination and attach only the individual server reports
   foreach ($file in gci "C:\[DESTINATION]\FPSSK-Report-[SERVER]*.txt"){
       $att = New-Object Net.Mail.Attachment($file.fullname)
       $msg.Attachments.Add($att)
   }
   $smtp.Send($msg)
   $att.Dispose()
   
   

4. Create a second script for your cron job commands (I named my file cron.ps1):

   powershell -command "C:\[DIRECTORY]\FPSSK.ps1 -Report -DiscoverCSV C:\[DIRECTORY]\FPSSK-[FILE].csv -Log C:\[DESTINATION] | C:\[DIRECTORY]\[EMAIL SCRIPT].ps1"
    

5. Create a new schedule task to run a program/script, and under the actions tab point it to "%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe" with the following arguments: "-NoLogo -File "C:\[DIRECTORY]\[CRON].ps1"
6. Once you have done this, be sure to test the command file command before executing your cron task.

Note: FPSSK will create a report file each time you run the script so, it would be wise to add a few more switches to remove the previous report files before running your new report.

Enjoy!

netsh advfirewall firewall add rule name="Allow DPM Remote Agent Push" dir=in action=allow service=any enable=yes profile=any remoteip=[IP]

After a lot of research and trial and error, I was able to pinpoint the issue. To import PST files using import-mailbox, you have to make sure that you meet the following requirements:

• Created a Windows 2008R2 VM
• Install Exchange with the mailbox role only.
  • Create a new database, name is IMPORT.
• Install Microsoft Outlook 2010 x64. As of SP1 you don't need Outlook!
• Before you begin, make sure that you point your IMPORT database to one of the internal CAS hosts:
  • Set-MailboxDatabase [DATABASE] -RpcClientAccessServer [INTERNAL RPCACCESS HOST]
  • Trust but, verify: Get-MailboxDatabase [DATABASE] | fl RpcClientAccessServer
• Once you've done this, create the new mailbox, and then move it to the the IMPORT database.
• From there, you can run in your mailbox-import command, which should be successful.

You should also make sure that your databases have the correct permissions. You can do this through ADSI under CN=Databases,CN=Exchange Administrative Group (ID),CN=Administrative Groups,CN=US,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[FQDN],DC=[TLD]:

• Read
• Administer information store
• Allow impersonations to personal Exchange Information
• Create named properties in the information store
• Open mail send queue
• Send as
• Receive as
• View information store status

Simple conclusion: Make sure that your CAS array is not causing the issue…

That said, I decided to axe public folders from my Exchange deployment because I don’t want to trouble myself with a legacy features that might hinder on my operation. With that in mind, here is how you would remove a public folder/database from Exchange 2010:

• Start EMS
• [PS] get-OfflineAddressBook -Server Exchange02 | remove-OfflineAddressBook
• [PS] Get-PublicFolder “\” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Recurse -ErrorAction:SilentlyContinue
• [PS] Get-PublicFolder “\Non_Ipm_Subtree” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Recurse -ErrorAction:SilentlyContinue

You are done. Now you just have to re-create your OAB, and you are set!

Cannot process argument transformation on parameter 'DC'. Cannot convert value "SERVER\ecp (default Web site)" to type "Microsoft.Exchange.Data.Fqdn".

The solution is rather simple:

New-EcpVirtualDirectory -externalurl "https://fqdn.tld/ecp" -internalurl "https://SERVER/ecp" -Server "exch01.xxx.local"

Once you've done this, be sure to close down EMC and re-open it. You should also verify by running GET-ECPVirtualDirectory.

Upgrade to SP1 and use the reset virtual directory feature!

When I started EMC (logged-in as Domain Admin), I would see an Access denied error. To correct the issue, I simply ran the following from Exchange Management Shell:

Then again, I could use Parallels/VMWare Fusion in coherence mode and get the same results…