Ed
Wed Sep 19 17:10:23 PDT 2007
That would figure since you already have an Exchange organization.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"Veejar" <rajeevk.sharma@gmail.com> wrote in message
news:1190246642.771155.299290@r29g2000hsg.googlegroups.com...
> On Sep 19, 7:51 pm, Andy David {MVP}
> <ada...@pleasekeepinngcheesebucket.com> wrote:
>> On Wed, 19 Sep 2007 13:28:54 -0700, Veejar <rajeevk.sha...@gmail.com>
>> wrote:
>>
>>
>>
>> >On Sep 19, 3:58 pm, Andy David {MVP}
>> ><ada...@pleasekeepinngcheesebucket.com> wrote:
>> >> On Wed, 19 Sep 2007 12:53:41 -0700, Veejar <rajeevk.sha...@gmail.com>
>> >> wrote:
>>
>> >> >On Sep 19, 3:37 pm, Andy David {MVP}
>> >> ><ada...@pleasekeepinngcheesebucket.com> wrote:
>> >> >> On Wed, 19 Sep 2007 12:29:44 -0700, Veejar
>> >> >> <rajeevk.sha...@gmail.com>
>> >> >> wrote:
>>
>> >> >> >On Sep 19, 3:02 pm, Andy David {MVP}
>> >> >> ><ada...@pleasekeepinngcheesebucket.com> wrote:
>> >> >> >> On Wed, 19 Sep 2007 11:58:10 -0700, Veejar
>> >> >> >> <rajeevk.sha...@gmail.com>
>> >> >> >> wrote:
>>
>> >> >> >> >I have two Windows Server 2000 SP4 domain controllers.
>> >> >> >> >(Server1 and
>> >> >> >> >Server2) Server2 also has Exchange 2003 SP2 installed on it.
>>
>> >> >> >> >I want to get Exchange 2007 going. So I setup a new Server
>> >> >> >> >(Server3)
>> >> >> >> >with Windows 2003 SP2. This Server is a domain controller. I
>> >> >> >> >transferred all the FSMO roles and Global Catalog over so it's
>> >> >> >> >now the
>> >> >> >> >primary domain controller. The original domain controller was
>> >> >> >> >Server1, a Windows 2000 Server.
>>
>> >> >> >> >I created a Windows Server 2003 x64 SP2 Server that will be
>> >> >> >> >used for
>> >> >> >> >Exchange 2007. When I run setup
>> >> >> >> >/PrepareLegacyExchangePermissions I
>> >> >> >> >get no errors:
>>
>> >> >> >> >D:\Admin\en_exchange_2007_standard_and_enterprise_dvd_X12-98653>setup /
>> >> >> >> >PrepareLegacyExchangePermissions
>>
>> >> >> >> >Welcome to Microsoft Exchange Server 2007 Unattended Setup
>> >> >> >> >Preparing Exchange Setup
>> >> >> >> >No Server roles will be installed
>> >> >> >> >Performing Microsoft Exchange Server Prerequisite Check
>> >> >> >> > Organization Checks .........................
>> >> >> >> >COMPLETED
>> >> >> >> >Configuring Microsoft Exchange Server
>> >> >> >> > Updating legacy permissions .........................
>> >> >> >> >COMPLETED
>> >> >> >> >The Microsoft Exchange Server setup operation completed
>> >> >> >> >successfully.
>>
>> >> >> >> >However, when I run setup /PrepareSchema I get the following
>> >> >> >> >error:
>>
>> >> >> >> >D:\Admin\en_exchange_2007_standard_and_enterprise_dvd_X12-98653>setup /
>> >> >> >> >PrepareSchema
>>
>> >> >> >> >Welcome to Microsoft Exchange Server 2007 Unattended Setup
>> >> >> >> >Preparing Exchange Setup
>> >> >> >> >No Server roles will be installed
>> >> >> >> >Performing Microsoft Exchange Server Prerequisite Check
>>
>> >> >> >> > Organization Checks .........................
>> >> >> >> > FAILED
>> >> >> >> > The Active Directory schema will be upgraded if you continue.
>> >> >> >> > Verify
>> >> >> >> >that the organization is ready for Exchange 2007 by running the
>> >> >> >> >Exchange 2007 Readiness Check, which is part of the Exchange
>> >> >> >> >Best
>> >> >> >> >Practices Analyzer. Setup encountered a problem while
>> >> >> >> >validating the
>> >> >> >> >state of Active Directory: Domain Controller
>> >> >> >> >'Server1.domain.com'
>> >> >> >> >Operating System version is 5.0 (2195) Service Pack 4. The
>> >> >> >> >minimum
>> >> >> >> >version required is 5.2 (3790) Service Pack 1.
>>
>> >> >> >> >The Exchange Server setup operation did not complete. Visit
>> >> >> >> >
http://support.microsoft.comandentertheError ID to find more
>> >> >> >> >information.
>> >> >> >> >Exchange Server setup encountered an error.
>>
>> >> >> >> >I am not sure why it is looking for the old primary domain
>> >> >> >> >controller, Server1. It should look at Server3 which is
>> >> >> >> >Windows
>> >> >> >> >2003. All the FSMO roles have been properly copied over. The
>> >> >> >> >event
>> >> >> >> >viewer stated this when I transferred the roles over. I even
>> >> >> >> >ran
>> >> >> >> >netdom query pdc and netdom query fsmo and it all points to
>> >> >> >> >Server3.
>>
>> >> >> >> >Any idea why when I try to install Exchange 2007 or run setup /
>> >> >> >> >PrepareSchema it points to the old domain controller,
>> >> >> >> >Server1???
>>
>> >> >> >> Server 1 is still a DC and in the same AD subnet?
>>
>> >> >> >> >Any help would be great.
>>
>> >> >> >Yes, Server1 is still DC. I was debating to demote it. I guess a
>> >> >> >tad
>> >> >> >afraid to perform it since Exchange 2007 is thinking its the
>> >> >> >primary
>> >> >> >DC.
>>
>> >> >> >AD are all on the same subnet.
>>
>> >> >> You can specify the DC running setup:
>>
>> >> >> setup /mode:install /domaincontroller:servername
>>
>> >> >sorry for the basic question, which setup do i run?
>>
>> >> In your case, setup/prepareschema yes?
>> >> THen use the domaincontroller switch
>>
>> >Perfect, that work. Thank you.
>>
>> >I've encountered another error. When I run "setup /PrepareAD [/
>> >OrganizationName: <organization name>" using the domain controller
>> >switch I get the following:
>>
>> >D:\Admin\en_exchange_2007_standard_and_enterprise_dvd_X12-98653>setup /
>> >PrepareAD
>> > /OrganizationName:Org_Name /domaincontroller:servername
>>
>> >Welcome to Microsoft Exchange Server 2007 Unattended Setup
>> >Preparing Exchange Setup
>> >No server roles will be installed
>>
>> >Exchange organization name cannot be specified. There already exists
>> >an Exchange organization with name 'Domain"
>>
>> >Exchange Server setup encountered an error.
>>
>> >D:\Admin\en_exchange_2007_standard_and_enterprise_dvd_X12-98653>
>>
>> >Can't Exchange 2003 and Exchange 2007 be in the same domain?
>>
>> You mean the same org? Absolutely.
>> I think your problem is that you are specifying it. No need to do that
>> since it already exists.
>
> I used different org name and even left it blank but its still looking
> at the org that exists.
>