I don't have much procedures except backup everything, then convert. As much as possible have everyone off the system.
I've used Converter at several clients, most of whom have small networks with less than 20 users so it's easy to make sure everyone is logged off. Single server networks where the server is DC, Exchange, SQL and IIS. (Often running Windows SBS so all apps have to be run on one physical box.) Both Win2k and Win2k3 servers.
I have much better success with hot-cloning than with cold-cloning. Install and run Converter on the physical server to be converted. I haven't had a hot-clone fail yet. (knock on wood.) In a few cases, even with a hot-clone, I've had to restore Directory Services. But as long as the users are not logged on, so Exchange & SQL can quiese, then I've not had a problem with using Converter on Exchange and SQL.
