I have had issues with logs of Exchange getting 100GB and more, or the backup application not clearing the logs. So, there is a way to keep the logs from getting large and you running out of diskspace. It’s a simple solution which you can undo it in 5 minutes with no repurcusions.
:: Open Exchange Management Console
:: Navigate to Organization Configuration/Mailbox
:: Right click on the Mailbox Database Store in question and select Properties
:: Click on the Maintenance tab and tick the option Enable Circular Logging
:: Click Apply
:: Dismount and Re-Mount Store
Downside to this? You can’t restore with current data. You can only restore from your last backup. Old log files are overwritten during this procedure and not enabled by default for a reason. I enabled circular logging, backed up the server, and disabled circular logging and scheduled more frequent backups in order to keep the log files under control.
There seem to be an issue with Windows SBS Small Business Server 2011 or Windows Server 2008/ R2 running both Exchange 2010 SP1 Rollup 3 or 4. This has happened many times and gone through the Exchange and router configuration many times with no success. Here is the simple workaround to this teething issue. The issue seems to be a bug from Microsoft where if you have IPV4 along with IPV6 enabled. The IPV6 will be used to resolve the DNS when sending an email. This will fail and the user will either get a delivery report or a delay report.
To solve the issue, simple do the following:
– Open the ‘Exchange Management Console’
– Expand the ‘Server Configuration’ node
– Right Click and select ‘Properties’ on teh server in the content window (This will popup the server’s property window)
– Click on the ‘External DNS Lookups’
– Select ‘Use These DNS Servers’ radio button and add the external DNS IP addresses of your ISP
– Click on the ‘OK’ button to save the configuration
– Expand the ‘Organization Configuration’ node and click on the ‘Send Connectors’ tab
– Right click on your send connector and select ‘Properties’
– Click on the ‘Network’ tab
– Tick the option to ‘Use domain name system (DNS) MX records to route mail automatically’ and make sure to tick the ‘Use the External DNS Lookup settings on the transport server
This should solve the problem and it will process all the mail in the queue of Exchange. Of course depending if you have the right configuration and ports open from the router.
Whe opening the Exhange 2010 management console i.e. EMC once may see the below error:
Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available.
This seems to be an issue with the IIS port 80 bindings. On my server I managed to fix it by removing any bindings of port 80 and do them again.
Open IIS, and then right-click on tye Default Web Site.
Click Edit Bindings.
Remove the bindings with port 80 and set the value of All Unassigned for the IP address.
In my case this solved the problem. Also I found the below just in case you have multiple sites.
You are running multiple websites.
You try to set up a redirect, for example, to https://mail.contoso.com/owa by requiring Secure Sockets Layer (SSL) on the Default Web Site.
You create another website to do the redirect back to the SSL-enabled website.
Windows Remote PowerShell requires port 80 to be available on the Default Web Site. If you want to set up an automatic redirect to /owa and redirect http requests to https, follow the instructions in the section, “For a Configuration in Which SSL is Required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0” on the following Microsoft website:
The new FREE application from Microsoft will let you import any PST file into an Exchange 2010 mailbox. This is fairly easy to use and if you want a quick way to import a PST file into an Exchange mailbox here’s how.
First of all download the PST Capture from here.
Secondly you have to have the followin pre-requisits before installing and using this product, which are:
– Outlook 2010 64bit version installed *
– Logged-in user being in the Active Directory group “Organization Management” group
– Logged-in user being in the Active Directory group “Administrators”
– Logged-in user being in the local administrators group
Once you install the product see the list below for the possible problems/solutions:
Error: RPC error from Exchange
You possible have mailbox size restriction and it exceeded during import
Error Openinng Mailbox
You don’t have the Outlook 64bit installed and possible have the 32bit
Error: Outlook installation not found
You Haven’t installed Outlook
Open the Exchange Powershell and type the following to view the language of the mailbox.
Get-Mailbox -Identity "Noel Pulis" | fl name, languages
Now, to change the language of the mailbox use the below, for example the code below will change my mailbox to English.
Set-Mailbox -Identity "Noel Pulis" -Languages "en-GB"