Why do I have to change the "msExchServerSite" value on my exchange 2010 obj during Exchange 2010 install?
Question: Exchange 2010 beta is not installing smooth (I have to change the "msExchServerSite" value on my exchange 2010 obj during install [via adsi edit]), what am I doing wrong?
So here is the break down. In my lab, I have 1 2k3 sp2 AD box w/ all the FSMO roles, and it's doing DHCP and DNS. I have an exchange 2k3 box that is patched to about last month and running on 2k3 sp2. Then I have some test 2k8 and 2k8 r2 boxs that I have been installing Exchange 2010 on.
In my lab I have done the following: I have done teh 2k8 r2 schema update. I have done the "Prepare Active Directory and Domains" for exchange 2010 [I.E. using the exchange 2010 disc to do the setup /pl, setup /ps, setup /p, setup /pd per the http://technet.microsoft.com/en-us/library/bb125224%28EXCHG.140%29.aspx. I've done these with an enterprise admin account.
But still during my exchange 2010 install, the install hangs and fails out if I don't go to adsiedit and add the distinguished site name to the "msExchServerSite" property of the newly created exchange server obj (this is while the install is happening). When I put in the correct value to the "<Not Set>" field, everything works.
I assume I have something wonky going on and I am not certain what. My fear is that there is some underlying systemic problem and that even though I can do the manual fix during the install, that something is messed up deep in the backend and will rear its ugly head later.
Can someone help me find what is causing the "msExchServerSite" not to update of its own accord?
All Replies
- I haven't seen that one before yet, but when you run setup are you doing it from an elevated command prompt?
Brian Day: MCSA 2000/2003, CCNA, MCTS: Microsoft Exchange Server 2010 Configuration, Overall Exchange/AD Geek. - Are you talking about the "setup /pl, setup /ps, setup /p, setup /pd" commands or the setup to install exchange 2010?
I did not run the "setup /pl, setup /ps, setup /p, setup /pd" as elevated (I assume that means opening the command propmt as administrator). But when I did the commands, I did not recieve any type of error.
I did not run setup for the exchange install as administrator either, so I am testing that now. - I have run setup to install exchange by right clicking on the setup.exe file and running as administrator, it still fails out because I didn't go to adsiedit and add the distinguished site name to the "msExchServerSite" property of the newly created exchange server obj.
I get 5023 and then 5003 errors in my applications log.
I follow the resolution for "Possible cause 1:" and that lets the install procced successfully.
http://social.technet.microsoft.com/Forums/en/exchangesvrtransport/thread/8126b31f-0b8b-4dd9-92b2-10e71dfd24af
Is there some place I should look to help identify why this is happening?
I assume that during the install, something is making a call to get the distingushed site name value, and then placing the result of the call into the new exchange obj's properties. My guess is that there is some gp our security permission change that I have made that is causing either 1: the call to get the distingushed site name value to fail, or 2: the placment of the data into the new exchange server obj's properties to fail. If anything like this is true, I don't know here to look. I have checked the link 2 paragraphs above and the permissions are set correctly. - Can anyone help with this?
