We are moving from a pilot to an enterprise wide deployment. Our plan was to do an consolodated enterprise deployment, but while going through the planning guide, it indicated that if we wanted to provide remote access in an enterprise depoyment, then we would need to deploy the expanded configuration internally, which is odd since a standard deployment gives you the ability to provide remote access (as long as you deploy the edge servers as well). Is this simply an example, or do you actually need to deploy and expanded configuration internally to support remote access.
I'm not sure where you are seeing that recommendation, but it's sounds like just an example. An Enterprise Edition Consolidated Front-End server can certainly support all external features using an Edge Server. It will work with either a single EE server (using a secondary virtual IP for the pool) or a pair of EE server's connected to a Hardware Load Balancer.Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
Enterprise deployment and remote access... expanded configuration?
