By default, an Exchange server will try and send emails to a smart host using port 25. Unfortunately, there is no option to change the port number within the Exchange Management Console. This howto guide will show you how to change this to a different port number. This will be done using the Exchange Management Shell. Continue Reading…
- 64 bit edition of Windows 2008 Server (if not using 2008 R2)
- You must have a copy of Exchange 2010.
This can be downloaded from:- Exchange 2010 with SP1 – http://www.microsoft.com/download/en/details.aspx?id=21570
or
- Exchange 2010 with SP2 – http://www.microsoft.com/download/en/details.aspx?id=28190
This guide outlines the installation for Exchange 2010 with SP1, but SP2 should be very similar, if not the same.
Both can be installed as trial copies, which last 120 days. If you want to continue using it after the 120 days, you will need to purchase a Exchange 2010 license. - Exchange 2010 with SP1 – http://www.microsoft.com/download/en/details.aspx?id=21570
- The server must be joined to a domain (or be the domain controller, however this is not Microsoft’s recommended approach).
- Microsoft .Net Framework 3.5
- Windows PowerShell v2
- Latest updates from Windows Update.
The “Get-Service” PowerShell command can be used to display the status of all services on a machine. To make this easier to read, and to narrow down the results to specific services, you can pipe the output to “Where” and filter the results.
The following command displays a list of Microsoft Exchange related services, and their statuses.
Get-Service | Where {$_.DisplayName -Like "*Exchange*"} | ft DisplayName, Name, Status
Example output:
This command can be modified easily to filter for another service name if required.
The “Get-MailboxStatistics” PowerShell command can be used to view statistics for a specified mailbox/user account.
The only required parameter is the mailbox name, or the user identity.
For example:
Get-MailboxStatistics -Identity Administrator"
Simply running the Get-MailboxStatistics as per the example above, you will only see a few of the columns that get returned (DisplayName, ItemCount, StorageLimitStatus, and LastLogonTime).
To view all the available columns/values, you can pipe the Get-MailboxStatistics command to “fl”, which outputs the data in a Formatted List arrangement, which fits on the screen nicely.
Get-MailboxStatistics -Identity Administrator | fl
You can also limit this output to only display the data that you want to display.
The below example displays the display name, item count, total item size, and the last logon time.
Get-MailboxStatistics -Identity Administrator | fl DisplayName, ItemCount, TotalItemSize, LastLogonTime
For more information on the “Get-MailboxStatistics” command, issue the “help Get-MailboxStatistics” command from the PowerShell.
Installing Microsoft Exchange 2010 on Windows Server 2008 R2
April 11, 2012 Exchange Server, MicrosoftExchange Server 2010 is currently (at the time of writing) the latest version of Microsoft’s email server software. Its main features consists of email, calendaring, contacts, and tasks.
This how to article will outline the steps required to install Microsoft Exchange Server 2010 on a Windows Server 2008 R2 machine. The steps should remain the same for a standard Windows Server 2008 (64-bit required) machine, as long as it is up to date with all the latest updates.
Prerequisites
You need to ensure the following prerequisites are met before beginning the installation of Exchange 2010:
You may find that you need to install some additional updates when the installation does the readiness checks. It will tell you what its missing, and where to download the updates from.
For full details on what the requirements are, you can find more info at:
http://technet.microsoft.com/en-us/library/bb691354%28EXCHG.141%29.aspx
Installing Exchange 2010
Start the Exchange 2010 setup that you downloaded. The first time you run this, it will simply extract the setup files. You then need to go to the folder they were extracted to, and run the setup.exe file.
You should be presented with the following screen:
There will be 5 installation steps to go through as part of the installation. The main one being step 4, which is actually installing Exchange 2010.
If steps 1 or 2 aren’t greyed out, make sure you close the installer, and install the required programs.
Click Step 3, and select your language option. I used “Install only languages from the DVD”.
Click Step 4, and the Exchange 2010 installation will start.
The Exchange Server 2010 introduction screen should come up first.
Simply click “Next” on this screen.
Next comes the license agreement. Read through this if you need to.
Select the “I Accept” option, and click the “Next” button to proceed with the installation.
You will now get a page inviting you to participate in sending error reports back to Microsoft.
If you have no need to send/receive error reports, select the “No” option, and hit “Next”. If you would like to participate, by all means select “Yes” to this.
You should now be presented with the installation type options.
Exchange Server 2010 has a number of different roles. These can be split out onto multiple servers, or it can all be installed on the one server. For this guide, we are simply going with the “Typical Exchange Server Installation”, which installs every role required onto the one server.
Select the “Typical Exchange Server Installation” button so it is highlighted.
Change the installation path if you want to install it to a location that is not the default.
Also, tick the “Automatically install Windows Server roles and features required for Exchange Server” option. If you don’t have a required feature installed already, it will get installed automatically (For example, IIS).
Click “Next” after selecting the above options.
You will now be asked questions about the installation.
You must enter in a name for the Exchange organization.
I will be leaving this as “First Organization”, but you can change it to be your company name if you wish.
Click the “Next” button to proceed to the “Client Settings” screen.
If you have any workstations that will be using Microsoft Outlook 2003 to connect to this server, you will need to select “Yes” on this page. Otherwise you can select “No”. Outlook 2003 requires a public folder database. Setting this to “Yes” simply creates the public folder database.
Click “Next” to continue to the “Configure Client Access server external domain” screen.
If you want to be able to connect into exchange from external sources (Outlook web app, Outlook anywhere, Exchange ActiveSync) you will need to tick the “The Client Access server role will be internet-facing.” option. The server can be behind a NAT router/firewall, but some port forwards would need to be set up for external clients to be able to connect in.
Enter in the domain name that will be used to access the server remotely. For this example, I am using “mail.networkinghowtos.com”. Make sure the domain name you select points back to your own server for things to work correctly. This domain name will get set for things such as the OWA External URL setting.
Click “Next” to continue.
You will now have a “Customer Experience Improvement Program” screen appear.
Have a read through this screen, and select the option that suits you. I chose “I don’t want to join the program at this time”.
Click “Next” to continue to the readiness checks.
This step simply goes through and checks to make sure all prerequisites are correct before proceeding to actually install the Exchange 2010 package.
This may take a few minutes to go through.
You may find that you get errors or warnings during this process, as per the screenshot below.
If you get any errors, the process will stop, and you will need to correct them before going any further. The errors generally have a link to a page on the Microsoft website explaining what the error is, and if a update is required, it will link to the update.
Warnings are just warnings, and you can still proceed with the installation. Its worth checking what the warnings are, just in case there is anything critical that you need to address before proceeding (eg. If you install Exchange 2010 on a domain, you cant install Exchange 2003 or Exchange 2007 on the domain at a later date).
Click “Install” to proceed with the installation of all the Exchange 2010 components/roles/tools/etc.
This process will take awhile, depending on the speed of the server.
Once that goes through, you should have all items with a green tick stating “Complete”, indicating that the items were installed successfully.
Click “Finish” to complete the Exchange Server 2010 installation.
You will get a popup stating that you should reboot before the putting Exchange Server 2010 into production. Reboot the server when you get a chance.
Conclusion
You should now have Microsoft Exchange Server 2010 installed on your machine, ready to be configured further using the Exchange Management Console.
By default, the installation will be set up to handle emails between users on the Domain. You will need to configure Exchange 2010 further if you want emails to be sent/received using a real domain name over the internet.
ActiveSync device not receiving new emails unless outlook is open
January 5, 2012 Exchange Server, MicrosoftHave you noticed that your ActiveSync device (iPhone, iPad, Blackberry, Windows Mobile, Android phone, or any other device that use ActiveSync) does not receive new email messages from your Exchange server unless Outlook, or Outlook Web Access (OWA) is open? This can sometimes be caused by the way antivirus software scans new emails. Some anti virus programs only scan new emails when they are accessed (either via Outlook, or OWA, but not by ActiveSync). The problem with this, is that the emails don’t get delivered to the user until they have been scanned. The easiest way to determine if this is the problem, is to open outlook, and see if you get emails straight away on your ActiveSync/mobile device. Then close outlook, and see if you still get new emails come in straight away. You might need to send a test email from another PC or different email provider to test this.
Thankfully there is an easy solution to fix this. A simple registry key change on the exchange server should fix this behavior. The setting is called Proactive Scanning. By default this setting is “0”, or off. Setting this setting to “1”, or on, means that all emails will be scanned as soon as they are received, instead of only on access. The second benefit of enabling proactive scanning, is that there may be an increase in speed when initially accessing new emails, as the server won’t have to scan it when you actually go to access it.
More details on proactive scanning can be found on the Microsoft website at the following address:
http://technet.microsoft.com/en-us/library/cc483040.aspx
The following steps detail how to enable proactive scanning.
Open the registry editor.
Browse through to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeIS\VirusScan
You should see the registry keys as per the image below.
Double click the “ProactiveScanning” key on the right. This will bring up the edit dialog.
Change the value from “0” to “1”, and hit the “OK” button.
The Proactive Scanning setting is now enabled, but it will not take effect until you restart the exchange services, or you set the ReloadNow key to “1”.
The ReloadNow key should generally always appear as “0”, as after it is changed to “1”, and the config is reloaded, it will automatically get reset back to “0”.
Double click the ReloadNow key to bring up the edit dialog.
Set the value to be “1”, and press the “OK” button.
The key should now appear with a value of “1”, or enabled.
Press the F5 key to refresh the registry, or go to the View -> Refresh menu option. If Exchange is currently running, it should have picked up the registry change, reloaded the config settings, and set the ReloadNow key back to “0”.
The value should now appear as “0” as per the image below.
The last thing to do is to test the mobile/ActiveSync device, to make sure this has fixed the issue.
You should now receive emails as they come into the Exchange server, without any delays.