Published: 2010-11-19 Updated: – Version: 1.0 Part: 2 (of 2) Configure Notes Migrator for Exchange (NME) NME will need at least SQL Express 2005 or SQL Server 2005 and newer. In my Lab environment I’m using SQL Express 2005 and the Management Studio for it. This should be installed before doing the NME installation. The installation of NME is pretty much a straightforward process and the first time it starts up, it will ask for a license, provide it with the license and go further. We will be…
Month: November 2010
Paper: Microsoft Exchange 2010 on VMware vSphere Best Practices Guide
VMware has released a best practice guide for how to deploy Exchange 2010. This paper hopefully will cover most parts including ESX host best practice, performance etc. The paper can be found here: http://www.vmware.com/files/pdf/Exchange_2010_on_VMware_-_Best_Practices_Guide.pdf Source: http://virtualization.info/en/news/2010/11/paper-microsoft-exchange-2010-on-vmware-vsphere-best-practices-guide.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Virtualization_info+%28virtualization.info%29
Configuring the Autodiscover Service for Multiple Forests
This text, is a copy and paste from: Exchange 2007 Autodiscover whitepaper (http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80).aspx) I wanted to publish it to spread the knowledge how to deploy autodiscover function in large user and resource forests. You can deploy Microsoft Exchange by using multiple forests. Two of the multiple forest deployment scenarios are the resource forest topology and the multiple trusted forest topology. The following sections describe how the Autodiscover service is used in these two deployment scenarios. Configuring the Autodiscover Service in a Resource Forest Topology If you use a resource forest topology,…