Installing new Exchange 2007 server in a 2003 domain environment
OK, I am going to cut to the chase here and give you what has been done. 1. Windows 2008 on a 2003 domain 2. Ran ExBPA and noted that Domain was in Mixed mode and needed to be run in Native mode. Also something regarding a reg key called SuppressStateChanges (HKLM\System\CurrentControlSet\Services\RESvc\Parameters... however there was no reg entry listed there, so I did not create one. Issue? 3. Using an account with Domain, Enterprise, and Schema Admins, currently the account is not an Exchange Administrator. 4. Trying to run the setup /PrepareSchema on the Win2008 machine (non-DC) and getting the following error: Configuring Microsoft Exchange Server Extending the Active Directory Schema Progress ..............................................Failed Cannot find any usable connections to an Active Directory server <servername>.<domain>.local I know that if I can just complete this portion, the installation should complete. And this does the same thing for /preparedomain, /preparelegacyexchangepermissions as well. I have run the 2008 ADPrep on the SBS server in the same site, and that appears to have completed no issue. Not even sure that was required. Please help. I am stuck on exhausted to try and find any more answers.
September 17th, 2009 1:07am

Exchange 2007 can only be installed in a native mode domain environment. This means you can only have windows 2000 servers or later and only exchange servers after 5.5. Here's some more info http://technet.microsoft.com/en-us/library/aa996151.aspx. Unless that error is false I'd say that's your problem.Michael
Free Windows Admin Tool Kit Click here and download it now
September 17th, 2009 4:12am

Michael, Thanks for replying. I confirmed with the man at the scene, he has all 2003 servers in the domain and this is the first Windows 2008 server in the mix. Exchange in on an SBS 2003 DC at this time. I have bumped up to the Windows 2003 native mode for active directory. Replication would have started last Friday when I changed it. I have removed and rejoined the 2008 member server from the domain to see if that would change anything and it has not. Any other ideas? Edit: Here is a new twist. I just tried to run the setup /ps again on this box and now it is failing the Org Check, where before it completed successfully. I am thinking there is some Voodoo on this system, the likes of which is going to prompt me to pull my hair out.
September 17th, 2009 7:29pm

Check your sites and services. The Exchange Server IPs must relate to an IP Subnet that is connected to an AD Site that has a DC in that site. You're Schema Master and GCs servers must be at least Windows 2003 SP1. Exchange 2007 System Requirementshttp://technet.microsoft.com/en-us/library/aa996719.aspxSF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
Free Windows Admin Tool Kit Click here and download it now
September 17th, 2009 9:17pm

Exchange 2007 in an SBS 2003 Environment http://blogs.technet.com/sbs/archive/2008/01/10/exchange-2007-in-an-sbs-2003-environment.aspx How To Convert from Mixed Mode to Native Mode in Exchange http://support.microsoft.com/kb/327779 Besides, please disable IPV6 and then check the issue again. Regards, Xiu
September 18th, 2009 10:46am

Hi,Check out these articles on how to install Exchange 2007 and the prerequisites before proceeding with installationInstalling Exchange 2007http://www.msexchange.org/tutorials/Installing-Exchange-2007-Part1.htmlInstalling Exchange 2007 on Windows Server 2008http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/installing-exchange-2007-windows-server-2008.htmlAlso make sure thatin which siteExchange 2007 server is been installed must have a GC in that site, also stop any firewall services which causes issues, if its windows 2008 noneed to stop Windows Firewall service.
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2009 11:32am

Scott, That error has reared its ugly head in the setup of the Hub Transport, Client Access and Mailbox Roles. However, the two DC's I am checking against, one being the Schema Master and the GC, are patched with SP2. Why would this be happening?
September 18th, 2009 11:36pm

What's your forest level at? Is Exchange being deployed in the same AD site as a GC server and there are no firewalls between the Exchange Servers and the Schema master?The problem sounds like you're having a problem communicating with the Schema Master. This could be a result of domain/forest functional level, or it could be a result of the server running your DC/Schema Master.It could be the result of SBS in the environment as well.SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2009 11:52pm

Do you have any more detailed error messages? What's showing up in your application log and exchange setup logs?
September 19th, 2009 12:01am

Scott, Forest Level is set to Windows 2003 Native. I agree about the communication with the Schema Master, although it is in the same AD site and on the same IP subnet and the schema master. Both DC's in the site are also GC's. The Schema Master is a SBS 2003 R2 server running SP2. Issue? Here is the last setup attempt from the Exchange Setup Log. I hope this helps shed a little more light to this frustration. The guy I am working with who is on site at the customer location has set me up with Exchange Full Admin access, not Org Admin. He stated that in Exchange 2003 on the SBS under Delegate Control, he only had the options to make my setup account Admin, Full Admin, or View only admin. Could this be what is causing the setup to fail. [9/18/2009 3:18:13 PM] [0] ********************************************** [9/18/2009 3:18:13 PM] [0] Starting Microsoft Exchange 2007 Setup [9/18/2009 3:18:13 PM] [0] ********************************************** [9/18/2009 3:18:13 PM] [0] Operating System version: Microsoft Windows NT 6.0.6002 Service Pack 2. [9/18/2009 3:18:13 PM] [0] Setup version: 8.1.240.6. [9/18/2009 3:18:13 PM] [0] Logged on user: FUB\EthanHunt. [9/18/2009 3:18:14 PM] [0] Command Line Parameter Name='mode', Value='Install'. [9/18/2009 3:18:14 PM] [0] Command Line Parameter Name='sourcedir', Value='E:\Ex2k7'. [9/18/2009 3:18:14 PM] [0] Command Line Parameter Name='fromsetup', Value=''. [9/18/2009 3:18:14 PM] [0] ExSetupUI was started with the following command: '-mode:install -sourcedir:E:\Ex2k7 /FromSetup'. [9/18/2009 3:18:14 PM] [0] Setup is choosing the domain controller to use [9/18/2009 3:18:15 PM] [0] Setup is choosing a local domain controller... [9/18/2009 3:18:17 PM] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. [9/18/2009 3:18:17 PM] [0] [ERROR] An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. [9/18/2009 3:18:17 PM] [0] [ERROR] Logon failure: unknown user name or bad password. [9/18/2009 3:18:17 PM] [0] [ERROR] Logon failure: unknown user name or bad password. [9/18/2009 3:18:17 PM] [0] Setup will use the domain controller ''. [9/18/2009 3:18:17 PM] [0] Setup will use the global catalog ''. [9/18/2009 3:18:20 PM] [0] No Exchange configuration container was found for the organization. Message: 'An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. '. [9/18/2009 3:18:20 PM] [0] The following roles are unpacked: [9/18/2009 3:18:20 PM] [0] The following roles are installed: [9/18/2009 3:18:20 PM] [0] The local server does not have any Exchange files installed. [9/18/2009 3:18:20 PM] [0] Setup will use the path 'E:\Ex2k7' for installing Exchange. [9/18/2009 3:18:20 PM] [0] The server is cluster type: 'None'. [9/18/2009 3:18:20 PM] [0] The requested cluster type: 'None'. [9/18/2009 3:18:20 PM] [0] The installation mode is set to: 'Install'. [9/18/2009 3:18:20 PM] [0] Exchange organization name is required for this mode. [9/18/2009 3:18:20 PM] [0] Active Directory Initialization status : 'False'. [9/18/2009 3:18:20 PM] [0] Schema Update Required Status : 'False'. [9/18/2009 3:18:20 PM] [0] Organization Configuration Update Required Status : 'False'. [9/18/2009 3:18:20 PM] [0] Domain Configuration Update Required Status : 'False'. [9/18/2009 3:18:20 PM] [0] Applying default role selection state [9/18/2009 3:18:20 PM] [0] Setup is determining what organization-level operations to perform. [9/18/2009 3:18:20 PM] [0] Setup will run from path 'E:\Ex2k7\Setup\ServerRoles\Common'. [9/18/2009 3:18:20 PM] [0] InstallModeDataHandler has 3 DataHandlers [9/18/2009 3:18:20 PM] [0] Setup is determining what organization-level operations to perform. [9/18/2009 3:18:20 PM] [0] Setup will run from path 'E:\Ex2k7\Setup\ServerRoles\Common'. [9/18/2009 3:18:20 PM] [0] InstallModeDataHandler has 4 DataHandlers [9/18/2009 3:18:20 PM] [0] Setup is determining what organization-level operations to perform. [9/18/2009 3:18:20 PM] [0] Setup will run from path 'E:\Ex2k7\Setup\ServerRoles\Common'. [9/18/2009 3:18:20 PM] [0] InstallModeDataHandler has 5 DataHandlers [9/18/2009 3:18:20 PM] [0] Setup is determining what organization-level operations to perform. [9/18/2009 3:18:20 PM] [0] Setup will run from path 'E:\Ex2k7\Setup\ServerRoles\Common'. [9/18/2009 3:18:20 PM] [0] InstallModeDataHandler has 5 DataHandlers [9/18/2009 3:18:20 PM] [0] RootDataHandler has 1 DataHandlers [9/18/2009 3:19:41 PM] [0] The folder "C:\Users\ethanhunt\Desktop\" is the subfolder of "C:\Users\". [9/18/2009 3:19:41 PM] [0] The folder "C:\Users\ethanhunt\Desktop\" is the subfolder of "C:\Users\ethanhunt\Desktop\". [9/18/2009 3:20:01 PM] [0] Validating options for the 0 requested roles [9/18/2009 3:20:01 PM] [0] Validating options for the 0 requested roles [9/18/2009 3:20:32 PM] [0] ************** [9/18/2009 3:20:32 PM] [0] Setup will run the task 'test-setuphealth' [9/18/2009 3:20:32 PM] [1] Setup launched task 'test-setuphealth -DomainController $null -DownloadConfigurationUpdates $true -ExchangeVersion '8.1.240.6' -Roles 'Bridgehead' -ScanType 'PrecheckInstall' -SetupRoles 'AdminTools','Bridgehead','ClientAccess','Mailbox' -TargetDir 'D:\Program Files\Microsoft\Exchange Server' -ADInitError 'Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. '' [9/18/2009 3:20:35 PM] [1] Beginning processing. [9/18/2009 3:20:51 PM] [1] [ERROR] Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. [9/18/2009 3:20:51 PM] [1] [ERROR] Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site. [9/18/2009 3:20:51 PM] [1] Ending processing. [9/18/2009 3:20:51 PM] [0] ************** [9/18/2009 3:20:51 PM] [0] Setup will run the task 'test-setuphealth' [9/18/2009 3:20:51 PM] [1] Setup launched task 'test-setuphealth -DomainController $null -DownloadConfigurationUpdates $false -ExchangeVersion '8.1.240.6' -Roles 'ClientAccess' -ScanType 'PrecheckInstall' -SetupRoles 'AdminTools','Bridgehead','ClientAccess','Mailbox' -TargetDir 'D:\Program Files\Microsoft\Exchange Server' -IISInstalled $true -ADInitError 'Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. '' [9/18/2009 3:20:51 PM] [1] Beginning processing. [9/18/2009 3:20:55 PM] [1] [ERROR] Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. [9/18/2009 3:20:55 PM] [1] [ERROR] Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site. [9/18/2009 3:20:55 PM] [1] Ending processing. [9/18/2009 3:20:55 PM] [0] ************** [9/18/2009 3:20:55 PM] [0] Setup will run the task 'test-setuphealth' [9/18/2009 3:20:55 PM] [1] Setup launched task 'test-setuphealth -DomainController $null -DownloadConfigurationUpdates $false -ExchangeVersion '8.1.240.6' -Roles 'Mailbox' -ScanType 'PrecheckInstall' -SetupRoles 'AdminTools','Bridgehead','ClientAccess','Mailbox' -CreatePublicDB $true -TargetDir 'D:\Program Files\Microsoft\Exchange Server' -IISInstalled $true -ADInitError 'Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. '' [9/18/2009 3:20:55 PM] [1] Beginning processing. [9/18/2009 3:20:57 PM] [1] [ERROR] You must be a member of the 'Exchange Organization Administrators' or 'Enterprise Administrators' group to continue. [9/18/2009 3:20:57 PM] [1] [ERROR] Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password. [9/18/2009 3:20:57 PM] [1] [ERROR] Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site. [9/18/2009 3:20:57 PM] [1] Ending processing.
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2009 12:05am

Ok so I am a little furthter along then I was before. I have the Management Tools installed but am trying to install the Hub Transport Role, Client Access Role, and Mailbox Role. When it starts to check and install the Hub Transport Role it appears with the following error: An error occurred. The error code was 3221684229. The message was Access is denied. Then I get the Finish button at the bottom and have to try and restart the setup again. I will have latest setup log here soon.
September 19th, 2009 1:46am

[9/18/2009 3:18:17 PM] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password.[9/18/2009 3:18:17 PM] [0] [ERROR] An Active Directory error 0x8000FFFF occurred when looking for global catalogs in forest 1stunitedbank.local: Logon failure: unknown user name or bad password.[9/18/2009 3:20:51 PM] [1] [ERROR] Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site.Have you prepared the environment? It still shows that you're not hitting a GC which would lead me to think that Exchange is not in the same AD site as a GC. Check the IP address of the Server and validate that IP address(s) are connected to the same AD Site:Also, you need to have permission to access the GC, Enterprise Admin, Schema Admin, and Domain Admin would be the path of least existance. If you have been able to prepare the environment you're going to need Exchange Org Admin permissions. They could delegate you the permissions to the server setup but it still looks like you're having problems with your AD environment. Or setup an installation account...ExchangeAdmin or something like that with the permissions above. SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2009 3:37pm

The Windows 2008 server on which you are trying to install Exchange is it a Windows 2008 SP2 or Windows 2008 R2?you can also try to run the setup from the command prompt with the /DC switch and see if it is workingSetup.com /m:install /r:H,C,M /DomainController:FQDN DC Name.
September 20th, 2009 7:32am

Illusionist: I attempted the command line parameters you suggested, however, this is what I received in return. Configuring Microsoft Exchange Server Hub Transport Server Role .....................................FAILED An error occurred. The error code was 3221684229. The message was Access is denied.. So essentially I have the management console installed and no Server Roles. I am unable to install Hub, Client or Mailbox to this server. I have to be missing something that should be so fundamental that I will kick my own self in the rear end on this. Any further help would be appreciated from all. To answer your other question above, the Windows 2008 box is running SP2.
Free Windows Admin Tool Kit Click here and download it now
September 21st, 2009 9:05pm

Double check, but is the account you're using to install the server a member of the Exchange Org admins, Schema Admins, Enterprise Admins, and Domain Admins? (Path of least resistance....)SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
September 21st, 2009 9:07pm

Scott, I am looking at the account now. I show that my admin account as well as the account I also created to install Exchange both are members of the Schema Admin, Enterprise Admin, Domain Admin, and now the Exchange Organization Admin groups. For whatever reason, I am unable to install the server roles on Windows 2008. I am getting an Logon failure when trying to conenct to Active Directory, being that the username is unknown or a bad password. Or if I go through the GUI setup it says it is trying to call my secondary DC and cannot connect, either because no SP1 or not a GC, when in reality it is both. I have tried doing the following: setup.com /m:install /r:H /dc:name.domain.local and I am greeted most recently with the following. Setup encounterd a problem while validating the state of Active Directory: An Active Directory error 0x8000FFF occurred when looking for global catalogs in forest domain.local: Logon Failure: unknown user name or bad password. I know that it got almost all the way through installing the HUB Transport service but then failed and did not install the Client access or Mailbox roles on the setup. I can see some Org Configuration data and its spotty under the recipient config in the Exchange Management Console, but for the Server Config there are no roles listed, which the setup was telling me point blank. I have run the /prepare items successfully, but for some reason, I cannot get Exchange to install. DNS appears to be working fine, I can telnet LDAP to both DC's from my Windows 2008 box. I'm growing more frustrated and this new technology by the day.
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2009 1:13am

I will add that I did add both accounts into the Microsoft Exchange Security Groups OU and listed the accounts as member of the Exchange Organization Adminsitrators. Question, Do I need to have either account added as a Exchange Full Administrator on the Exchange 2003 organization? I know that I have not been able to be added to that org's admin structure at this point.
September 22nd, 2009 1:24am

The error code 3221684229 comes up frequently on the web regarding installing ex2007 sp1 on server 2008 R2. Although not recommened because they are not compatible many have made the install work by right clicking setup.exe and running as admin and, or right clicking and running in vista compatibility mode. I realize this isn't the case here, but it couldn't hurt to try. Michael
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2009 4:34am

and the computer is a member of Active Directory and resides in the same site as a GC? You're also not using W2K8 R2 right? This is indeed an interesting one. When you log into the computer to deploy Exchang eyou are logging in with an account that does have proper domain permissions, you're not accidently logging into the local workstation? Verify Domain Admins have local admin permissions.Also, try to ping your domain from your computer. The problem could be DNS related.SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
September 22nd, 2009 6:21am

Michael, What is the suggestion then for not using the ex2007 sp1? This was the download from Microsoft that was licensed to the customer. What is the preferred installation. I am still getting these damn 3221684229 errors when trying to install the roles.
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2009 1:26am

The computer is a member of Active Directory. and in AD Sites and Services, is located in the same site as the DC's it is trying to contact. Looking at the Properties page from "Computer" it lists Windows Server Standard SP2, no R2 listed. I am logging into the server with an account created with the necessary "admins" groups as members. Domain Admins are listed in the Local Administrators group on the Win2k8 server. Pinging the DC's from the server display the correct IP address and FQDN when initiated. Where can I go from here? How would I scrap the entire operation and start fresh again? Does this need to be run on the console as opposed to a RDP session? I have bever had an issue doing an install on Exchange 2007 on Win2k3 servers, but could this be different?
October 1st, 2009 1:36am

Ping your DCs make sure they can be resolved.at a command propmt type SET and validate which DC you're logging into.I think the bigest thing is name resolution.I would triple check AD Sites and Services. Actually open a command prompt and type "gpresult /r" without the quotes. What do you get? Make sure the AD Site is correct and then make sure you have the correct membership.Run that command on a DC and see what Site it comes back with. SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2009 6:54pm

It appears to be bigger issues then just Exchange. I tested by trying to promote the Windows 2008 server to a DC in the site, only to be given the same message that the account I was using to try and authenticate with on the promotion was an unknown username or bad password. I suppose I will be taking this issue to the Windows 2008 support forum for now and see what I can pin down there.
October 7th, 2009 7:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics