What version of Exchange are you working with? I think you mentioned that you have NetBIOS disabled, is that correct?
I can confirm that in fact Exchange 2000 requires connectivity to the Schema Master FSMO role holder to install via /disasterrecovery. I've been told that this is not the case in 2003, but I can't confirm that definitively. I've also seen some cases where you can have difficulty installing Exchange via /disasterrcovery if NetBIOS is disabled and once NetBIOS was enabled Exchange installed fine.
Phil
On 9/6/05, Tom Kern <[EMAIL PROTECTED]> wrote:
I emailed awhile ago about this issue-i'm recreating my domain in a test forest for migration testing.in our real and test forest, we have no connectivity to the root domain and no EA or SA access(never will). we are primary dns for both the root and child domain however.I recreated our domain in a test lab.then i tried installing exchange using the /diasterrecovery switch and it complained about not being able to contact the schema master and refused to go on.I ran adsiedit.msc as local system on a child dc and put this child dc as the value for the fSMORoleHolder attrib and then exchange installed until 24hrs later it stopped working.It claimed it could'nt contact a dc or gc.when i tested the secure channel, i got access denied. It was behaving as if it wasn't a membr of the domain. disjoining and rejoining did nothing.so a ibm consultant took over from there and while on the phone with MS, seized the fsmo roles via ntdsutil(but without EA or SA access?!!)anyway, that exchange installed fine with the dr switch(however that was just less than 24hrs ago).Installing a new exchange server is impossible. i still get "can't connect to schema master" error. sometimes its a "can't connect to root domain" errorI'm currently talking to MS and so far they can't seem to figure it out.also they can't give me a answer as to why exchange setup needs to conect to the root domain(in fact as far as they're concerned, its the first time they heard of that).I'm wondering why MS can't explain conculsivley the behavior of their own products to me?Anyway, i was wondering if anyone knew the answer out here or could explain these symptoms in any way?Esp since i think my company needs to install a new exchange server for archival and compliance purposes in our production enviorment before we migrate(as in asap as we have been out of complaince and are about to be audited very soon).thought i'd ask here while waiting for MS to respond.you guys seem to be a higher quality of support than most companies pay to get from MS.thanks!!
