Install ES2003 on WS2003 in W2K Domain with ES2K also running on another server.

Hi Folks,



I have a Windows Server 2000 domain controller running Exchange Server 2000.

I have a Windows Server 2003 (SP2) member server. I am trying to install
Exchange Server 2003 on the member server.



During the Deployment Preparation I am alerted to basic incompatibility
between WS2003 and ES2003 which is apparently solved with judicious
application of service packs. Noted. No problem there. I followed the
deployment steps and DCDiag and NetDaig reported minor problems that were
negligible, according to MSKB.



I prepared the Forest, and the Domain and I installed. I was not alerted to
any problems.



I can't find any artifacts of this installation. No menu entry, no service
definitions, no MCC Snap-ins, no new directories anywhere...



The Installation GUI reported zero problems but the setup.log reports errors
of the following form:



Repeated 3 Times:

setup.exe: ***ERRORLOG EVENT*** : ModuleID not found in map in
GetSetupComponentByModuleID() -- [{DA943894-7A14-4FFF-BBDC-C004FAE2310B}]



Repeated 8 Times:

WizardUI: ***ERRORLOG EVENT*** : ISetupManager::GetGlobalCustomProperty()
failed in CPageBase::GetGlobalProperty()





So, I am mystified. With zero problems reported through the installation
GUI and nearly zero anywhere else, I would think this was a successful
installation and I would think I should be able to find a dialog to begin to
configure this baby, but there are none in evidence. And I'm not the only
one that thinks so - if I try to install an Exchange Server service pack, he
thinks there is no Exchange Server installed on this machine either.



Am I missing something? Any thoughts on this mystery?





Chris.

Paul
Wed Mar 12 17:54:31 CDT 2008

You originally mentioned that the 2003 server was a member server and not a
Domain Controller. Yet Exchange won't install unless you have configure
your 2003 as a Domain Controller and assigned it as a Global Catalogue.

Take me through the steps of your installation...


"Chris Miller" <Chris(a)InfoGreat.com> wrote in message
news:O%23kfnrIhIHA.5164@TK2MSFTNGP03.phx.gbl...
> Hi Folks,
>
>
>
> I have a Windows Server 2000 domain controller running Exchange Server
> 2000.
>
> I have a Windows Server 2003 (SP2) member server. I am trying to install
> Exchange Server 2003 on the member server.
>
>
>
> During the Deployment Preparation I am alerted to basic incompatibility
> between WS2003 and ES2003 which is apparently solved with judicious
> application of service packs. Noted. No problem there. I followed the
> deployment steps and DCDiag and NetDaig reported minor problems that were
> negligible, according to MSKB.
>
>
>
> I prepared the Forest, and the Domain and I installed. I was not alerted
> to any problems.
>
>
>
> I can't find any artifacts of this installation. No menu entry, no
> service definitions, no MCC Snap-ins, no new directories anywhere...
>
>
>
> The Installation GUI reported zero problems but the setup.log reports
> errors of the following form:
>
>
>
> Repeated 3 Times:
>
> setup.exe: ***ERRORLOG EVENT*** : ModuleID not found in map in
> GetSetupComponentByModuleID() -- [{DA943894-7A14-4FFF-BBDC-C004FAE2310B}]
>
>
>
> Repeated 8 Times:
>
> WizardUI: ***ERRORLOG EVENT*** : ISetupManager::GetGlobalCustomProperty()
> failed in CPageBase::GetGlobalProperty()
>
>
>
>
>
> So, I am mystified. With zero problems reported through the installation
> GUI and nearly zero anywhere else, I would think this was a successful
> installation and I would think I should be able to find a dialog to begin
> to configure this baby, but there are none in evidence. And I'm not the
> only one that thinks so - if I try to install an Exchange Server service
> pack, he thinks there is no Exchange Server installed on this machine
> either.
>
>
>
> Am I missing something? Any thoughts on this mystery?
>
>
>
>
>
> Chris.
>
>
>

Chris
Wed Mar 12 18:05:15 CDT 2008

Hi Paul,



I am migrating everything from my one server running W2K and ES2K to a new
server running W2K3SP2 and ES2K3SP2. My thought was bring up the new
machine as a member server and migrate everything and then handle the domain
replication stuff afterward. After reading your post, I now believe that
my first mission has to be domain controller foolishness.



It didn't occur to me that Exchange needed to run on a domain controller - I
blissfully thought it could simply reference one. Silly me.



Let close this thread and after I struggle with the domain stuff, I'll
report back with results. Thanks for the help.


Chris.


"Paul King" <paul@servlan.co.uk> wrote in message
news:u26gKQJhIHA.5088@TK2MSFTNGP02.phx.gbl...
> You originally mentioned that the 2003 server was a member server and not
> a Domain Controller. Yet Exchange won't install unless you have configure
> your 2003 as a Domain Controller and assigned it as a Global Catalogue.
>
> Take me through the steps of your installation...

Paul
Wed Mar 12 18:08:12 CDT 2008

No worries Chris, let us know the outcome.

"Chris Miller" <Chris(a)InfoGreat.com> wrote in message
news:uPqwJWJhIHA.3940@TK2MSFTNGP05.phx.gbl...
> Hi Paul,
>
>
>
> I am migrating everything from my one server running W2K and ES2K to a new
> server running W2K3SP2 and ES2K3SP2. My thought was bring up the new
> machine as a member server and migrate everything and then handle the
> domain replication stuff afterward. After reading your post, I now
> believe that my first mission has to be domain controller foolishness.
>
>
>
> It didn't occur to me that Exchange needed to run on a domain controller -
> I blissfully thought it could simply reference one. Silly me.
>
>
>
> Let close this thread and after I struggle with the domain stuff, I'll
> report back with results. Thanks for the help.
>
>
> Chris.
>
>
> "Paul King" <paul@servlan.co.uk> wrote in message
> news:u26gKQJhIHA.5088@TK2MSFTNGP02.phx.gbl...
>> You originally mentioned that the 2003 server was a member server and not
>> a Domain Controller. Yet Exchange won't install unless you have
>> configure your 2003 as a Domain Controller and assigned it as a Global
>> Catalogue.
>>
>> Take me through the steps of your installation...
>
>

Vladimir
Mon Mar 17 14:52:24 CDT 2008

Actually, you don't have to install W2K3 DC in order to have Exchange Server
2003 in your organization. Not having W2K3 DC on your network will cause
that you will not have for example RPC over HTTP.

However, you can install Exchange 2003 on W2K3 member server, in order to
migrate your mailboxes, and have the current W2K DCs.

http://technet.microsoft.com/en-us/library/cc164322(EXCHG.65).aspx (System
Requirements for Exchange Server 2003)

Regards,


Vladimir Meloski




"Chris Miller" <Chris(a)InfoGreat.com> wrote in message
news:uPqwJWJhIHA.3940@TK2MSFTNGP05.phx.gbl...
> Hi Paul,
>
>
>
> I am migrating everything from my one server running W2K and ES2K to a new
> server running W2K3SP2 and ES2K3SP2. My thought was bring up the new
> machine as a member server and migrate everything and then handle the
> domain replication stuff afterward. After reading your post, I now
> believe that my first mission has to be domain controller foolishness.
>
>
>
> It didn't occur to me that Exchange needed to run on a domain controller -
> I blissfully thought it could simply reference one. Silly me.
>
>
>
> Let close this thread and after I struggle with the domain stuff, I'll
> report back with results. Thanks for the help.
>
>
> Chris.
>
>
> "Paul King" <paul@servlan.co.uk> wrote in message
> news:u26gKQJhIHA.5088@TK2MSFTNGP02.phx.gbl...
>> You originally mentioned that the 2003 server was a member server and not
>> a Domain Controller. Yet Exchange won't install unless you have
>> configure your 2003 as a Domain Controller and assigned it as a Global
>> Catalogue.
>>
>> Take me through the steps of your installation...
>
>