With regards to applying the schema extensions necessary for Exchange 2010 SP2, I need some clarification of the requirements from where the process is run. In my recollection with Exchange 2007, the server where you ran the extensions needed to be in the same forest and site as the schema master, but did not necessarily need to belong to the same domain as the schema master, and as long as you logged in with an *account* from the root domain with schema master rights then things worked okay. So, for example, if a customer had a forest with an empty root called empty.root that contained the schema master, and the operational domain was called company.empty.root, you could use a server in the company.empty.root domain, login to it with an account that exists in the empty.root domain, and run the schema extensions from there. I may have faulty memory, but thats my recollection. A customer has this situation and needs to install the SP2 schema extensions for 2010, and has asked us if they need to add a new server to the empty root, or if they can use an existing workstation in their prod domain. I dont have any definitive knowledge either way, so wanted to ask the team to see what you have experienced. This site says the server where you run the extensions needs to be a member of the same domain as the schema master: http://technet.microsoft.com/en-us/library/bb125224.aspx Which says the following: You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency. However, Im not certain that the information in that link is necessarily definitive, so wanted to check with all of you to see what your experiences have been, and/or if you have any documentation that states the requirement differently.

Your method will not work "use a server in the company.emtpy.root domain login to it with an account that exist..." since it's not in the same domain as the schema master. All you need to do is run the command on the schema master itself or another box thats in the same AD site\domain as schema master. And the account will need enterprise admin, exchange or and domain admin rights for company.empty.root.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com