My new server will run Server 2008 with Exchange 2010.Just for a “worst case scenario” I’ve put in some public folders and I’ve got some Outlook 2003 clients. Make sure before you start, you have the Exchange 2010 media and unlock code, you don’t want to download the media on a site with a slow internet connection, (at time of writing the disk image is 1GB in size). If your existing domain controllers are all x32, and you are also upgrading domain controllers, during the process, Then you will be extending the domain schema (i.e. Transport\v4.0_15.0.847.30__31bf3856ad364e35\Microsoft. Update (3/5): Updated blog after official KB article got published. After running the script you should be able to start the Transport service or install 3rd party containing transport agents..it’s not 2003 R2 or 2008) then make sure you have x32 bit Windows media with you (Note: 20 R1 only, as 2008 R2 is all x64 bit). You domain and forest functional levels need to be (at least) Windows Server 2003, before you start the migration. Make sure any third party anti virus and/or mail scanning software is supported and will work on Exchange 2010, and you have the media and licences handy. You will need to install on a x64 bit server, make sure you have a server capable, and Windows x64 bit media with licences. Before you even think about going further make sure you have a good backup!If you are lucky enough to have VMware ESX, Hyper-V or another virtualisation platform, consider doing a P2V conversion on your Exchange 2007 server then simply turning the 2007 Server off, then if it all goes to hell in a hand cart simply turn the original server back on again. While your thinking about backups – does your backup software support Exchange 2010?13/07/11 I recently posted an article on Exchange 2003 to 2010 Transition, Only to be asked, “Can you do the same for Exchange 2007 to 2010?”, so here it is 🙂 Before we start, I’m aware “Migration”, “Swing Migration”, and “Transition” have three very different meanings, Depending on which KB, blog or piece of Microsoft documentation you are reading.
The issue was also blogged on by fellows Jason Sherry, Paul Cunningham while Tony Redmond has additionanal background details here.There might be a deadlock, or the program might not have responded to the server initialization code within the timeout period of two minutes". If the component GUID is: 3D14228D-FBE1-11D0-995D-00C04FD919C1, the event appears according to Microsoft when you try to browse Active Server Pages (ASP) pages. I removed Windows Messenger and I have not seen the DCOM error". I traced the problem back to dodgy registry permissions.The event can also occur when you complete a drive remapping during a Citrix Meta Frame 1.8 installation on a Microsoft Windows 2000 Terminal Server computer. Article ME266118 on how to restore default NTFS permissions fixed the problem.Symptoms are that the Transport service doesn’t start or stops shortly after starting the service or you can’t install the 3rd party product. Products experiencing the issue are Trend Micro Scan Mail, Mc Afee Email Security (Group Shield), Symantec Mail Security for Exchange, AVG for Servers, ESET Mail Security for Exchange and Code Two Exchange Rules.