QUESTION: Will the /NewProvisionedServer switch work with child domain computer objects and accounts? If so how/where do I need to run the command stated in #3.ENVIRONMENT: 1 empty root domain WITH Exchange 2007 already installed: i.e. state.org1child domain: i.e. district9.state.orgGOAL: All child domain admins to install subsequent Exchange 2007 servers WITHOUT Exchange Org Admin rights.PLAN: Use the /NewProvisionedServer switch based on whitepaper http://technet.microsoft.com/en-us/library/bb288906.aspxto delegate child domain Exchange server installations to child domain Exchange admins group.PROGRESS:1. Installed new server (2008 sp2) in child domain, say exchsrv2be.district9.stat.org.2. Logged on to Exchange server in root domain and ran the following command (w/ elevated rights): d:\Setup.com /NewProvisionedServer:district9\Exchsrv2be /ServerAdmin:district9\ExAdminsISSUE: The command runs but ends up failing with an unexpected error.

SOLUTION:1. Log onto the Exchange Server-to-be IN THE CHILD DOMAIN WHERE THE SERVER WILL BE PROVISIONED instead of one in the root domain.2. Run the following command (w/ elevated rights): d:\Setup.com /NewProvisionedServer:\Exchsrv2be.district9.state.org /ServerAdmin:ExAdminsPlease NOTE: While this command allows members of the delegated group to run Exchange Setup for all the roles, I ran into failures when they tried toupgrade and installSP2 on the CCR nodes.NEW ISSUE: A previously provisioned CCR setup does not allow delegated user/group to install SP2.My theory is that an Org Admin must install the specific role and updates for it first before delegated users can do so on subsequent servers. Having only one CCR cluster may prevent me from proving/disproving this theory.I don't see why a delegated user /group would need to contact an Org Admin/Enterprise Admin to upgrade their delegated server for them. Is this a onetime thing or an on-going by-design feature of Exchange 2007 setup permissions?