Forestprep looking for Schema Master from non-existent server

I receive an error when I run forestprep. It is referencing a server that
does not exist anymore. I have removed all references using the ADSI Edit
tool, and also from the registry.

I am trying to upgrade Exchange server 2000 to EX 2003 on a server that I
upgraded from Windows 2000 to Windows 2003. I could not uninstall it because
it was lookin for a Windows 2000 AD

Microsoft Exchange Installation Wizard
---------------------------
The component "Microsoft Exchange Forest Preparation" cannot be assigned the
action "ForestPrep" because:

- Setup encountered an error while trying to contact the Windows Active
Directory. The error was:

- Failed to connect to the Schema Master server RC1. Please verify that it
is up, reachable, and that you have sufficient permissions to use it.



Any information would be helpful.

 

Hello Ed,

If the old server will never be online again (as you stated in your
post) you have to seize the FSMO-Roles from the unavailable server to a
available one. You can use the Roles context in ntdsutil to do this.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

 

Unfortunately, the drive was reformatted and that is the main problem.
Thanks for the info, though.

 

If the drive of the old server was reformatted, then be happy since you
_can make sure the old server never comes online again_, and go ahead
and seize the FSMO-Roles of that server on the new one.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
WebSite: http://www.windowsserverfaq.org

 

Es,

What Ulf is telling you is that you have to seize the roles to (from)
another server. You don't need the original server to do this. In fact,
its probably best that the original server is no more.

To seize the roles, you run ntdsutil and bind to another working DC -and
then seize from the DC that is no more.

Here's the KB(s). Google is the way to get a bit more info. on this process
and/ or ntdsutil.
-- http://support.microsoft.com/?id=255504
-- http://support.microsoft.com/?id=223787


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

 

Thanks for the info. Worked like a charm.

ES