I've been working from the excellent post on migration: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html?sfQueryTermInfo=1+10+2003+2008+2010+30+exchang+r2+sb
The only difference being that i wanted to use our existing (SBS) SSL certificate on the new 2008R2 server so that weboutlook and users pda's, outlook - rpc over https settings etc would not all need to be changed, to this end I followed this handy guide: http://www.jppinto.com/2009/04/moving-ssl-certificate-fwindows-2003-server-windows-server-2008/
After running though the process on our test setup a few times it all seemed cool, but when doing the live migration over the weekend (of dec 10th,11th,12th) we hit snag after snag (as is always the case i guess!). Anyway the result was that by early monday morning I decided to abort the mission and roll back to Fridays' backup (acronis to the rescue). Reviewing what happened, it all seemed to go disastrously wrong around the SSL certificate, for some reason when people started connecting remotely the server would lock up and require a hard reboot.
So anyway, I now have a few quiet days where we're closed for chrimbo and i can rerun the process (avoiding time consuming pitfalls from first run) to get this working properly - can anyone tell me if what i'm trying to do is reasonable or do i basically have to take it on the chin and install brand new certificate? Any useful pearls of wisdom or helpful war stories regarding setup of owa, activesync and rpc-https on 2008R2/Exchange 2010 will get points! (I'm not using Forefront btw)