Today I ran into a problem after updating Exchange 2010. After a reboot (which took ages!) I noticed that all the services were disabled. After some troubleshooting I found out that the problem had something to do with an installed update. My resolution (and was planned) was to install the latest servicepack (SP3). There is one drawback, the services are disabled and Exchange SP3 setup is unable to stop/start them.
I used this powershell command to set the service to manual :
During the install I had to execute this command 2 times, the SP3 setup worked fine and after that the services were automatically started.
I ran into this great wiki article from Microsoft from where you can find and download (!) all the Exchange 2003/2007/2010/2013 servicepack’s and fixes. You can also check all the build versions.
You can find the link here.
Update : a co-worker attended me of the continued list of the link above here
Some time ago I ran into an error while installing Exchange. It seems this problem also occurs when upgrading/installing an Exchange Server service pack. This is how to fix this problem :
First go to the (root) domain controller and register the schema extension :
Now load the plugin by starting mmc and adding the extension
Now right-click the Active Directory Schema en select Change Active Directory Domain Controller. (Choose the domain controller you wish to transfer the schema role to)
Hit ok when you receive the read-only warning.
Now select Change Schema Master and hit Change.
For a customer I ran into a strange problem. While doing a cross forest mailbox migration I noticed that mails were queuing up and were not delivered. It took some troubleshooting untill I found the solution. First I noticed that newly created users received email for several domains without any problems. Migrated users didn’t receive any external email.
I opened the user’s properties with ADSIEDIT and I noticed the old email addresses on the targetaddress field. I decided to delete the values and re-register those email addresses using the Exchange console. The user concerned received external email immediately .
Because it’s a cross forest migration we are using ADMT for the user migration. It’s possible to exclude this value and doing so will prohibit to these old values being migrated to the new domain.
Today I tried to move a database to a different drive and I ran into the following problem :
After some investigation I noticed a large amount of log files. After enabling circular logging and dismount and mounting the database everything went fine! Disable circular logging afterwards and make sure your backup solution is running working and flushes the logfiles correctly.
This is how to create a split SMTP domain using Exchange 2003 and another SMTP program like Exchange, Zimbra or something like that.
Step 1. Make sure you’re MX-record is already point to your Exchange 2003 mailserver and that part is working.
Step 2. Add the new domain name to the Recipient Policies:
Make sure the “This Exchange…” is not selected! (That’s important)
Now create a new SMTP connector :
Fill the IP-adres in brackets  and select an Exchange 2003 server using Add.
Goto Address space, add the new split SMTP domain and select the Allow Messages to be relayed option.
At this point the mail which can’t be delivered at the Exchange 2003 is being forwarded to the IP adres specified. At this point you have to make a receive connector (Exchange 2010 for example) or something else.
A follower of my blog asked me how to publish Activesync using TMG. I thought I already write a blogpost about it, but couldn’t find it. So I wrote another post. See the screendumps for some explanation.
In my case I had to adjust (enable) basic authentication :
We all now there are lots of ANTI SPAM/Virus appliances, software solutions etc. out there. But somehow in my production & test environment it was too expensive or too much hazzle. All the products I thought were interesting were too expensive or didn’t work like they suppose to. Because I didn’t want to spent thousands of dollars for hardware/software and licenses I started looking for a solution.
I ran into mailcleaner.org. They have a community driven antispam & antivirus solution with some a nice feature pack :
- fully compatible with any SMTP server
- routes mail on a per-domain basis
- per recipient/host whitelist and blacklist
- SMTP and LDAP/Active Directory callout for e-mail address validation
- temporary storage with retries in case of final server failure
- outgoing load balacing and/or failover
- SpamAssassin base ruleset and additional rules
- Bayesian controls, with auto-learn
- RBL checks
- Checksum protocols such as Razor/DCC/Pyzor
- URL RBLs
- SPF checks
Administration Web Gui
- Complete configuration of filtered domains, with forwarding and preferences
- configuration of the base system (network, proxy,…)
- access to all users’ configurations and quarantine
- full real-time spam quarantine access
- full real-time blocked content protection policy configuration
- advanced administration access list, so you can delegate light administrative access to other people, such as a hotline for example
- monitoring of the whole mailcleaner filter farm
- access to all logs
- mail queue access and control
User Web Gui
- Authenticator connectors so your users won’t have to remember another credential
- Full access to their quarantine, with message release and analysis options
- per e-mail address configuration options, such as delivery mode (tag, quarantine, drop) and periodic summaries
- support for almost any x86 compatible hardware
- automatic software raid genertion
and much more…
For your impression watch the screendumps :
Some details I left behind because of security purposes. But it took me about 10 minutes to install it, another 10 to configure it and I totally forgot I was running it for some time untill now. Just check it out at : http://www.mailcleaner.org
In my previous post you can read how easily it is to use the EMC to administer your Office365 account. Now you can imagine how easily it could be to migrate Exchange mailboxes from your on premises Exchange Server to Office365 or the other way around! This is how you can do that :
First open the console and select New Remote Move Request
Choose the user you wish to migrate :
Now specify the target domain and the remote database and hit next.
Hit next and watch your mailbox fly to the cloud!
Nowadays more and more people are migrating from Exchange to Office365/Exchange Online or are using a Hybrid solution. Many people don’t know that they can use the Exchange 2010 Management Console to control their Office365 settings and users. This is how you can link your Office365 environment to the EMC.
First download and install EMC, this is straight forward. Now open the EMC and select add Exchange forest :
Enter a friendly name and choose the option “Exchange Online”.
Enter your credentials and hit ok!
Notice that you have the possibility to administer your on premises Exchange and Office 365.