Over the past number of years Cheddon Limited has specialised in IT migration projects primarily to Microsoft technologies. Source environments include Novell NDS/eDirectory, ZEN, GroupWise and IBM Lotus Domino which are typically migrated to Active Directory, Exchange Server and System Center Configuration Manager.
Active Directory forms the core of any Microsoft Enterprise, and provides a central location for network and resource administration and security. Migrating to Active Directory is often a pre-requisite for other technology, such as Microsoft Exchange 2010, but can also be a standalone project it it's own right.
Migration from other messaging technologies to Microsoft Exchange Server can be a complex logistical and technical undertaking in terms of new infrastructure design, co-existence and integration with legacy systems, and migration activities that bring minimal business disruption. Very often, simply knowing what to expect in advance can be half the battle.
We not only provide "new build" or migration services. We can also undertake reviews of existing systems and infrastructure. We can help you to ensure that the services involved in the running of your business are being delivered in a secure, reliable and effective way to give you the best possible return on your investment.
At Cheddon Limited we understand that technology itself can only ever account for part of the solution. We understand that not all of the migration challenges will be technical. That’s why we have a commitment to help deliver every solution using a winning combination of technology, real life experience, common sense, and industry best practice.
Our web site gives an overview of the most popular services we currently provide, along with many enhancements. We are also able to provide services ranging from consultancy to design and implementation of a range of other technologies so please contact us if you have any questions regarding areas not covered on our web pages.
The scenario I set out to handle was intended to be the simplest one you could encounter, it’s the simplest set up in a lab (uses the fewest VM’s), and so probably in the real world also for a small business.
The starting point is a business that is using Domino integrated with AD.
I have single domain single forest Active Directory with Domino installed as a member server. Users are created in AD, and then migrated to Domino, registered in the Domino Directory and given mail files.
At some point the business decides to move from Domino to Exchange for it’s e-mail.
Exchange 2013 is now available and there is no pre-existing Exchange in the organisation, so Exchange 2013 has been installed in the same AD as Domino.
It’s been a while!
Exchange 2013 was RTM on October 11 2012.
Exchange 2007 SP3 RU10 came out February 11th with Exchange 2010 SP3 coming out the next day February 12th.
Exchange 2013 Cu1 was out April 02nd
And on May 14th, the sizing tool has been made available.
Finally, we can design an Exchange 2013 infrastructure to co-exist in an Exchange 2007 or 2010 org, and move mailboxes.
You can grab the tool here.
I’m using NME 4.6.1 to do a migration from Domino 8.5.3 to Exchange, and we needed to check something in the Domino Directory.
I download Domino Designer because I needed Domino Administrator, and the only version I can find to download is V9.0
Turns out NME doesn’t work with 9.0, it doesn’t even find the client.
Slightly tedious, I need to use Administrator from a separate workstation, and it’s back to Notes 8.5.3 on the NME server!
I’ve seen this happen a few times over the past few years, most recently just this weekend.
The initial symptoms that alert you to this issue vary, databases are offline, transaction log volumes are full, transaction logging is out of control or mailboxes are full of NDR’s, but by and large the issue is the same.
In my recent customers case transaction log disk space was being consumed at upwards of 1Mbyte per second, and a 30GByte log volume that should last a week is filling up in just over 8 hours, between backups, and databases are being dismounted.
The most recent case is on Exchange 2003, but I’ve also seen it with Exchange 2007 and Exchange 2010.