Here are some more bullet points I'm managing to pull from the presentation. No guarantees of accuracy as I'm in the back of the room. The question and answering is garnering some great information:

- Client Access Role is not optional for first server in organization. Some early documentation said that this was optional, but it is required for installation. This role is the equivalent of a front-end server role in 2003. Allows IMAP, POP3, HTTP, HTTP3, RPC over HTTP to work with Exchange server.
- Hub transport is the role that moves email. Also required. This service is needed to move email.
- Unified Messaging is optional. Integrates voice mail, inbound faxing, etc into Outlook.
- Mailbox role holds the mailbox database.
- All four of the above roles can lie on the same server.
- The Edge Transport role prevents the server from holding any of the other roles. Can support anti-virus and anti-spam at the edge.

- A 32-bit version of Exchange is available for testing, classroom, learning purposes, but is not intended for production. After 100 users, the server will completely stop working. After about 20 days or so (according to the speaker), the server will need a reboot to continue functioning. So, don't use it in production!

- The IMF is still available. It is incorporated into the Edge Transport role. Note that the Edge Transport role is optional. You can run the Edge Transport role in an Exchange 2003 environment and take advantage of its features. Edge does not join the organization, so it will work with previous versions and even work with other mail tools like Groupwise, etc. Edge role does require 64-bit.

- Management tools from the Exchange CD cannot be installed onto 32-bit Vista. They are 64-bit only. But, you can get the 32-bit eval code and use the management tools. The eval 32-bit management tools are supported for production use.

- Every server you choose to install Exchange to requires a license. If you have five servers, each holding a role, you'll have to purchase five server licenses.

- Exchange 2007 is not supported in virtualization environments, but will be supported when Microsoft releases Hypervisor.

- Exchange 2007 supports five databases, and each database can support five storage groups. There are no database limits on size. Because of this, most clients default to Standard Edition (unless you have need for clustering).

- SBS: If you have SBS 2003 today and want to use 2007. You must install a member server and install Exchange on that server. There are no plans in the short-term to include Exchange 2007 into SBS. So, the migration path at this point is Exchange 2007 on a separate server. (At least 3-6 months past Longhorn ship date)

- You can mix and match Exchange Standard and Exchange Enterprise editions.

- There is no in-place upgrade path from 2003 to 2007. You install 2007 onto a new 64-bit member server and join that server to the organization.

- You cannot cross-manage servers with the 2007 management tools. In a mixed environment, you will manage 2003 servers with the 2003 ESM and 2007 servers with the 2007 console.

- Welcome back to Exchange 5.5! There is NO MORE integration with the Active Directory Users & Computers (ADUC). Like with E5.5, user mailbox management is again done in the Exchange console and not within the ADUC. What are your comments about this change? Do you like this change?

- Unlike E2000 and E2003, which used the Microsoft SMTP stack, 2007 uses it's own SMTP stack (similar to how E5.5 did it). This new SMTP stack was completely re-written for 2007.

- Don't use the 2003 ESM to move mailboxes to 2007. Mailboxes must be moved using the 2007 console.

- Every task in the GUI actually calls a PowerShell cmdlet. The GUI will show you the cmdlet parameters for every command you attempt to use. At any point, you can do a Control-C to copy the cmdlet parameters to a script for future use.

- 2003 mailboxes, once moved to 2007, can be moved back to 2003 at any point. This is done with the 2007 console.

- 2007 only supports Outlook 2003 or higher. Previous versions are not supported.