The WS-Management Service cannot process the request

Exchange 2010 sp2 try to run PowerSheel:
fix:
Recycle MSExchangePowerShellAppPool in IIS.

Powershell script to enumerate SMTP addreses and alieses

I used the script to collect the information from Exchange 2003 for migration to Exchange 2010, but it can be used for collecting the information from Exchange 2010 (but it can be easy done with Poweshell snapin for Exchange). For setup PowerShell environment for Exchange 2010 you can try my blog page powershell-ms-exchange-part1. 
To view the script click on "Read More"

Users on specific mailbox server could not access Public folders from Outlook

Exchange 2010 sp2 environment was upgraded from Exchange 2003. Users on specific mailbox server cannot access Public Folders through Outlook but can with OWA.
Check those setting on the mailbox database where users with the problem belongs:
I

It should point to a mailbox database on a Exchange 2010 MBX server instead Exchange 2003.

RESOLVED: The WS-Management service cannot process the request.

From: http://jasonshave.blogspot.com/2011/01/resolved-ws-management-service-cannot.html

RESOLVED: The WS-Management service cannot process the request. The user load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least Z milliseconds.

I did some digging around for this one and found a few crafty articles about adjusting throttling policies using PowerShell and making changes through ADSIEdit (http://reidablog.blogspot.com/). However, none of these seemed to fix my issue.

We had a newly built Exchange 2010 SP1 server which was ready to go into production but kept throwing the error when attempting to use PowerShell. Two other servers appeared to be running fine.

The server had recently received a new SSL certificate using the Exchange 2010 certificate provisioning and assignment process in the GUI. Unfortunately the IIS service hadn't been restarted yet and the URL used for remote PowerShell was using a certificate which wasn't trusted or valid anymore.

A quick "IISRESET" on the server resulted in my fix.

Exchange 2003 Powershell - Mailbox size

Really good script:

#      Author:  Steven Peck   - #">www.blkmtn.org

#        Date:  06/15/2007

# Description:  Exchange 2003 output to file

#        Display Name, Store, Storage group, MB Size, and Date Absent in DS

# Changed by Boris Sirotin 3/4/2012 to include external parameters for possible 3 exchange servers

#The syntax will be: .\thescriptname server01 server02 server03

# Get date for file name

param ($server01,$server02,$server03)

$day = Get-Date -UFormat "%Y%m%d"

# Gets data through WMI from specified Exchange mailbox servers

$computers = $server01, $server02, $server03

#

foreach ($computer in $computers) {

Get-Wmiobject -namespace root\MicrosoftExchangeV2 -class Exchange_Mailbox -computer $server01 | sort-object -desc MailboxDisplayName `

   | select-object MailboxDisplayName,StorageGroupName,StoreName,Size,DateDiscoveredAbsentInDS | Export-Csv -Path c:\temp\$computer-$day.csv

}

PowerShell Exchange 2010 prerequisite script

Very good script for Exchange 2010 features installation:
http://www.ehloworld.com/152

Setup secure TSL communication

Setup secure (TSL) communication with an external company (Exchange 2003 server)

Task list:
Collect information about the external company
Acquire public certificate for the Exchange server (we can use same as we using for OWA access – but it should be public)
Setup firewall to permit SMTP access to the Exchange server.
Setup a dedicated Virtual SMTP server for communication with the external company.
Setup a SMTP connector to the external company
Test the communication.

Collect information about the external company

We need to collect next information for the task:
The company SMTP Domains (all info and IP addresses here and below will be bogus – only for example): Nobody.com
Inbound IP addresses: mail1.nobody.com – 148.168.1.2; mail2.nobody.com – 148.168.2.2

Setup firewall to permit SMTP access to the Exchange server

It is straight forward thing, for example for PIX:
Create NAT mapping:
static (inside,outside) 146.82.131.230 192.168.1.5 netmask 255.255.255.255
0 0
Create firewall rules:
access-list outside_access_in permit tcp host 148.168.1.2 host 134.82.131.230
eq smtp
access-list outside_access_in permit tcp host 148.168.2.2 host 134.82.131.230
eq smtp

Where 134.82.131.230 public address of your SMTP server (We will create it by Exchange System Manager), and 192.168.1.5 is LAN address.

Setup a dedicated Virtual SMTP server for communication with the external company.





















We need to create just a standard SMTP server here on dedicated IP address (different for default SMTP).




















Here you need to enter your public certificate in, use the “Certificate” Tab.




















Here you can enter your exchange server public name (exactly like in your public certificate).



















Setup a SMTP connector to the external company
If we did not have connectors before, we will need to create two connectors first will pointed to default SMTP Virtual Server and second to Virtual Server (NOBODY) which we created during the project.


















Address space for MAIN connector should be “*” and cost should be higher then for NOBODY:


This connector will route all mail except for nobody.com domain.


















Second connector will looks like this:























And address space (in my case it was 5 different domain names):























Here how to set TLS for sending e-mail to this external domain:


















Test the communication

To test communication we need to be sure an e-mail message has TLS reference in the header, for example:

“Received: from source ([148.168.1.2]) (using TLSv1) by” – for mail from NOBODY company (inbound), and –
Received: from mail.mydomai.com ([146.82.131.230])
by gromsgia01i.nobody.com (8.13.8/8.13.8) with ESMTP id m3FG0WVe026377
(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)

Restore Exchange public folders from BackupExec backup.

Exchange 2003 public folders Backup Exec 12 (disk backup). Then try to restore a single Public folder Backup exec restore can not open Public Folders selection with message "You must install additional languages on this computer to see selection". Public folders have a folder with Japanese language. Solution was to install East Asian languages from - Control Panel - Regional and Language Option. Below is the screen:

Exchange Defragmentation

I always forget the command:
For example, the following command runs the standard defragmentation utility on the pub1.edb (and stm) and saves the copy in the user-defined file in remote location:
eseutil /d "e:\program files\exchsrvr\mdbdata\pub1.edb" /t\\rcm-dc1\temp\temppub.edb /p

OWA - can not be accessed

When try to access OWA (server OS 2000 sp4, Exchange 2003 sp2) have blank white screen. Rebuild all IIS Exchange directories:

1. Deleted all Exchange directories under Default web site.
   
2. Stop the web site
3. Restart Exchange Attendant service or just reboot the server.