If you do a lot of SharePoint demos, chances are you will be using tons of VMs (Virtual PC, Virtual Server, VMWare, anything..). And if you're like me, you would not like to fire up multiple VMs; the less the merrier. This translates to squeezing in as many products/components into a single virtual image - but there are some caveats to know about:
Installing SharePoint on a Domain Controller
- You lose the Document Conversion feature. Document Conversion services can start, but whenever you try to convert a document to web, it simply fails.
Installing SharePoint and Exchange on the same box
- You lose the Incoming Email feature. SharePoint relies on IIS' Virtual SMTP to listen for incoming emails. And Exchange cannot co-exist with IIS' Virtual SMTP. I'm not sure if there are some creative work-arounds available, but will post it if I found any.
On another point (pun-intended), if you want to install Performance Point Server or Commerce Server into the same VM as the DC, you will want to install them first, but don't run its configuration wizards. Promote the VM to DC only after installation, and then only run the configuration wizard.
While still on the topic of VMs, here's some guerilla tips to keep your VHDs small and lean (faster to move around)