My-Technet

From the Exchange Blog

So I just installed RU1 on my brand new Exchange 2010 server and then I issue a Get-Exchangeserver -Identity MyExchangeServer and get the following output for AdminsDisplayVersion and ExchangeVersion:

Ok that looks a little familiar for some reason. I go to my Exchange 2010 RTM server and issue the same CMDlet and get:

…The same result! But one server has RU1 installed and the other is RTM. Shouldn’t I get a different version number back?

Well… no. Exchange 2007 and forward do not reflect the version number either in the value for AdminDisplayVersion, ExchangeVersion, or at this registry key HKLM\SOFTWARE\Microsoft\v8.0\<Role>\ConfiguredVersion as influenced by roll ups. This is a common misconception.

The most conclusive way to get the version of your exchange server, rollup and all, is to check the file version of ExSetup.exe in the BIN folder.

Here is Exchange 2010 RU1 version:

And here is Exchange 2010 RTM:

Another way of getting this information is to run the following PowerShell one-liner:

GCM exsetup |%{$_.Fileversioninfo}

The below output is from an exchange 2010 server running RU1:

Here is an exchange 2010 RTM server:

You can then correlate the version number you find with those listed here, here or on the actual rollup update download pages.

A storage status of “NoChecking” means they do not have a mailbox limit.

To schedule the script. Through Windows Scheduler “PowerShell.exe -PSConsoleFile "C:\Program Files\Microsoft\Exchange Server\Bin\ExShell.psc1" -Command “C:\Script.ps1"

Save as a .ps1 file

________________________________________________

$FromAddress=MailboxReport@domain.com

$ToAddress=ExampleUser@domain.com

$MessageSubject="Mailbox Report"

$MessageBody="User Mailbox Storage Limit Status"

$SendingServer="emailserver.domain.com"

$file="C:\Mailboxes.txt"

Get-MailboxStatistics | Sort-Object StorageLimitStatus | ft DisplayName, StorageLimitStatus, ItemCount > $file

$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody

$Attachment = new-object System.Net.Mail.Attachment $file

$SMTPMessage.Attachments.Add($Attachment)

$SMTPClient=New-Object System.Net.Mail.SMTPClient $SendingServer

$SMTPClient.Send($SMTPMessage)

Solution:

1. Enable Encryption in the Outlook 2003 Profile.

2. Create a GPO to enable Encryption for Outlook 2003 clients.

http://support.microsoft.com/kb/2006508

3. Disable the Encryption requirement on the Exchange 2010 server.

From PowerShell on the Exchange server: Set-RpcClientAccess -Server:ExchangeServerName -EncryptionRequired:$False

MS KB for this issue – http://support.microsoft.com/kb/2009942

Prerequisites:

• Existing Exchange 2007 Servers must have SP2 installed.
• Existing Exchange 2003 Servers must have SP2 installed.
• Exchange Organization is set to Native Mode.
• At least one Global Catalog in each AD site must be Server 2003 with SP2.
• Active Directory Forest Functionality must be at least Windows Server 2003.
• Exchange 2010 cannot be installed on a RODC.
• Verify the existing Exchange 2003 Server does not have a SMTP Smart Host configured.
• Verify network with Exchange Pre-Deployment Analyzer.
• Possible Got Ya’s: Exchange 2010 requires client encryption and Outlook 2003 slow to delete email messages.

Required Software:

• From PowerShell on the server where Exchange will be installed.
• Set-ExecutionPolicy RemoteSigned – This will allow PowerShell scripts created on the server to be run on the server.
• Import-Module servermanager
• Save the command below to a .PS1 file extension. (Command below needs to be on a single line)
• add-WindowsFeature Net-Framework,RSAT-ADDS,Web-Server,WEB-ISAPI-Ext,Web-Metabase,Web-Lgcy-Mgmt-Console,Web-Basic-Auth,Web-Digest-Auth,Web-Windows-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-over-HTTP-Proxy -Restart
• Change to the directory of the PowerShell script you just created.
• Enter .\SriptName.ps1
• After the Reboot, configure Net.TCP port sharing service.  Enter – Set-Service NetTcpPortSharing -StartupType Automatic

(continue reading…)

Migrate Mailboxes to Exchange 2010 Server.

Move SSL Certificates to Exchange 2010 Server. Process is the same as Exchange 2007.

Migrate Public Folders. Process is the same as Exchange 2007.

Configure Offline Address Book on Exchange 2010 Server:

(continue reading…)

Prerequisites:

• Existing Exchange 2007 Servers must have SP2 installed.
• Existing Exchange 2003 Servers must have SP2 installed.
• At least one Global Catalog in each AD site must be Server 2003 with SP2.
• Active Directory Forest Functionality must be at least Windows Server 2003.
• Exchange 2010 cannot be installed on a RODC.

Required Software:

• From PowerShell on the server where Exchange will be installed.
• Set-ExecutionPolicy RemoteSigned – This will allow PowerShell scripts created on the server to be run on the server.
• Import-Module servermanager
• Save the command below to a .PS1 file extension. (Command below needs to be on a single line)
• add-WindowsFeature Net-Framework,RSAT-ADDS,Web-Server,WEB-ISAPI-Ext,Web-Metabase,Web-Lgcy-Mgmt-Console,Web-Basic-Auth,Web-Digest-Auth,Web-Windows-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-over-HTTP-Proxy -Restart
• Change to the directory of the PowerShell script you just created.
• Enter .\SriptName.ps1
• After the Reboot, configure Net.TCP port sharing service.  Enter – Set-Service NetTcpPortSharing -StartupType Automatic

(continue reading…)

Follow the steps below if an SSL cert exists already on another server.

Export Existing SSL Cert/Private Key

1. Click on OK (in the Add/Remove Snap-in window)
2. Select Computer Account
3. Select Local Computer
4. Click the + to Expand the Certificates Console Tree
5. Look for the Personal directory/folder and expand Certificates.
6. Right Click on the Certificate you would like to backup and choose > ALL TASKS > Export
7. Follow the Certificate Export Wizard to backup your certificate to a .pfx file
8. Choose to ‘Yes, export the private key’
9. Choose to include all certificates in certificate path if possible. (do NOT select the delete Private Key option)
10. Leave default settings > Enter Password (if required)
11. Choose to save file on a set location
12. Finish

Importing your Certificate/Private Key (from .pfx file format)

1. Start > Run
2. Type in MMC and click OK
3. Go into the File Tab (or Console) > select Add/Remove Snap-in
4. Click on Add > Click on Certificates and click on Add, then close (to close the Add Standalone Snap-in window)
5. Click on OK (in the Add/Remove Snap-in window)
6. Select Computer Account
7. Select Local Computer
8. Click the + to Expand the Certificates Consol Tree
9. Right click on the Personal Certificates Store (folder)
10. Choose > ALL TASKS > Import
11. Follow the Certificate Import Wizard to import your Primary Certificate from the .pfx file. When prompted, choose to automatically place the certificates in the certificate stores based on the type of the certificate.

Follow the steps below to generate a CSR request for a new SSL Cert.

From the Exchange 2007 Shell –

New-ExchangeCertificate –GenerateRequest:$True -Path c:\mail.domain.org.csr -KeySize 2048 -SubjectName “C=US, S=State, L=City, O=Company Name, OU=Org Unit Name, CN=mail.domain.org” -DomainName mail.domain.org -PrivateKeyExportable $True

Import the SSL Cert into Exchange 2007 Server – From the Exchange 2007 Shell – “Import-ExchangeCertificate –path C:\mail.domain.org.csr”

From the Exchange 2010 Shell -

New-ExchangeCertificate –GenerateRequest:$True -KeySize 2048 -SubjectName “C=US, S=State, L=City, O=Company Name, OU=Org Unit Name, CN=mail.domain.org” -DomainName mail.domain.org -PrivateKeyExportable $True > C:\SSLName.txt

Import the SSL Cert into Exchange 2010 Server – From the Exchange 2010 Shell – “Import-ExchangeCertificate -FileData ([Byte[]]$(Get-Content -Path C:\CertName.cer -Encoding byte -ReadCount 0))”

Follow the steps below to enable the Standard SSL Cert on the Exchange 2007/Exchange 2010 Server.

From the Exchange Shell enable the Cert for Exchange with the “Enable-ExchangeCertificate –Services “SMTP,POP,IMAP,IIS” –thumbprint “thumbprint”

From the Exchange 2007/Exchange 2010 Management Console:

Change the “Client Receive Connector” FQDN to mail.domain.org instead of Exchange01.domain.local

From the Exchange 2007 Management Console: Server Configuration – Client Access

From Outlook Web Access Tab – “OWA (Default Web Site)” – Change Internal and External URL to https://mail.domain.org/owa

From Exchange ActiveSync Tab – “Microsoft-Server-ActiveSync” – Change Internal and External URL to https://mail.domain.org/Microsoft-Server-ActiveSync

From Offline Address Book Distribution Tab – “OAB (Default Web Site)” –  Change Internal and External URL to https://mail.domain.org/oab

For Exchange 2010 Only: From the Exchange Control Panel Tab -  “ecp (Default Web Site)” – Change Internal and External URL to https://mail.domain.org/ecp

From the Exchange 2007/Exchange 2010 Shell –
Change Autodiscover URL – “Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.domain.org/autodiscover/autodiscover.xml”
Change Web Services URL – “Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory –InternalUrl https://mail.domain.org/ews/exchange.asmx –ExternalUrl https://mail.domain.org/ews/exchange.asmx”