Exchange 2007 ignite training

I’ve just finished delivering 2 days of Exchange 2007 training to a group of Microsoft Certified Trainers from across Europe.  It’s called Exchange Ignite training (Ignite the interest / ignite the spark / ignition).  There were 18 MCT’s in the room (2 women thanks to Anne and Ilse), with 2 Microsoftee’s (Jane and me).  You know Jane, you need to get a blog, share that massive amount of deep technical knowledge you have with the rest of the world, and increase the number of Technical women blogging on Exchange beyond KC and myself :-)  Mind you 20% female techies in a room was impressive (and certainly unusual!)

Well here are the answers to the questions we couldn’t answer during the course. Don’t forget that the technical documentation is still in the process of being written, as is some of the Exchange help, as is some of the product.  So, as promised, here are the answers and links where possible…

Q.What is the number of Transport Rules supported in Exchange 2007 ?
A.The maximum number of hub transport rules supported in Exchange 2007 is 1000

Q.A hub server will look to make a direct SMTP connection to a remote hub server role for delivery before considering the costing of the AD Site Topology. Is there a way to force the message to always take a specific route which may not be the most direct ip route due to the “cost  in $ value” of using the most direct route of the IP.
A.You can find a little more info about the question
here.  This topic (set-adsite) describes the process for setting the hub site. Note that the hub site must exist along the lowest cost route between the source and destination in order to stop at the hub site. Also, in that section of the help file, you will find information about setting an Exchange-specific cost to an Active Directory IP Site Link (set-adsite) to customize your Exchange routing. The deeper technical information on transport and routing is in process and is scheduled for RTM delivery.
Q. I understand that Exchange 2007 database no longer requires  a streaming (STM) database file for internet content. What are the technical reasons for the removal of this database, and why it is no longer required ?
A. In a nutshell it is because the Internet Protocols (IMAP/POP) were moved to CAS, so we no longer have native storage for Internet content as content conversion now occurs on CAS, instead of the store (except in Entourage where content conversion occurs on the mailbox).  Thus, there is no need for an STM file anymore.

Q. How do we emulate a mobile device on the demo screen to simulate direct push?A. See this link for the solution

Q. Where can I find out more about Powershell?

A. Paul has collected an amazing list of resources on his blog, and Brett’s blog is also the one to watch as he also gets to grips with Powershell.

…and I’ll record that Unified Messaging demo as a blogcast and beg Nino to host it on the Exchange team blog too..