UPDATE: Note that this post is based on Exchange 2010 RTM. Guidance has been changed slightly for SP1. Please see the wiki post HERE. In one of my recent Exchange 2010 deployments at a client, the design was a highly available 3-node Exchange environment with all roles (MB, CAS, HUB) installed on each server. So…
In my previous post, I gave an example of how Pairwise Analysis works, and presented a conceptual model in Excel of the driver and project prioritization engine within Microsoft Project Server 2010. That model worked well with simple driver prioritization scenarios, but seemed to display a wide variance with Project Server calculations in more complex…
Catapult uses cookies to enhance your experience, to display customized content in accordance with your browser settings, and to help us better understand how you use our website. By continuing to browse or closing this banner, you indicate your agreement. To learn more about the cookies we use and to set your own preferences, see our Privacy and Cookie Policy.