Step by step Setup walkthrough for Exchange 2007 Beta 2

This post should be helpful to you if you are planning to install Beta 2 of Exchange Server in your lab. It is not meant to be a replacement for any documentation that is included with Exchange 2007, but is provided as supplementary help.


PLEASE NOTE: You should NOT be installing Exchange 2007 Beta 2 in your production environment unless you have been specifically approved to do so by Microsoft. Please read this if you are thinking of doing this.


Also please note that we do not recommend that you attempt to upgrade earlier versions of Exchange 2007 (such as Beta 1 or CTP builds) to Beta 2 build. There were multiple significant changes since those builds were released and best approach is to start fresh.




Active Directory prerequisites:


- A Schema Master FSMO role holder and GCs need to run Windows 2003 SP1 or Windows Server 2003 R2; it is recommended that all DCs run Windows 2003 SP1

- Domain functional level of all domains in the forest has to be "Windows 2000 Server native" or higher


Exchange organization prerequisites (if you are joining an existing org):


- Exchange organization needs to be in Native Mode


Exchange Server computer OS prerequisites:


- System and Exchange partitions have to be formatted with NTFS file system

- W2003 Service Pack 1 or Windows Server 2003 R2 need to be installed on the server

- Microsoft .NET Framework 2.0 needs to be installed

- Microsoft Command Shell (MSH) (aka Monad); In builds Beta 2 and higher, the Setup.exe gives you a link where to download the Microsoft Command Shell (MSH) from. Remove any older versions you might have installed previously and install that version.

- Microsoft Management Console (MMC) 3.0

- If you are installing on a 64-bit machine, you might also get a popup to install a QFE hotfix.


For more information on prerequisites, please see Beta 2 release notes.


NOTE: If you are installing Exchange Server 2007 on a 64 bit OS, you should be installing the 64 bit version of Exchange Server 2007 too. 32 bit version of Exchange Server 2007 does not run under WOW on a 64 bit windows. Additionally, if you are installing Exchange 2007 on a Windows Server 2003 R2, you will not have to install .NET Framework 2.0 and MMC 3.0 as they are already installed. When in doubt, follow the links on the first Setup screen as shown below.


Exchange Server computer IIS requirements:


- NNTP service must not be installed

- SMTP service must not be installed

- Mailbox role requires the following IIS components: Enable network COM+ access, Internet Information Services, World Wide Web Service

- Client Access Server role requires the following components: World Wide Web Service, ASP.NET


Please see the Release Notes for more information on prerequisites!


Note: Many new features in Exchange 2007 require Outlook 2007 to experience them to the fullest. Example of those would be the new Availability improvements as well as Autodiscover functionality.


Running UI setup (installation)


Note: The following steps assume that you are running Setup in a simple AD environment with speedy AD replication. Steps for installation into multi AD site and multi domain environment are more complex and will be covered at a later time.


If you have installed all of the prerequisites as listed above, once you double-click on Setup.exe you should see a screen like this:




Note that if .NET Framework 2.0, MMC 3.0 or Microsoft Command Shell (MSH) are not installed, the links on the above page can take you to download locations. Note that even if you have Microsoft Command Shell (MSH) already installed, Setup might not detect it if it is too old to be used. See "OS prerequisites" section earlier in this document for help on what to do.


Once you press the "Step 4: Install Microsoft Exchange" link, Setup will copy some files first. Then you will be taken to the 1st step of Exchange Server 2007 Installation Wizard where you can press Next.


You will then have to accept the EULA and press Next yet again.


The next step is deciding if you want to set up automatic error reporting for this Exchange 2007 installation. Please read and make a selection. While we encourage you to enable error reporting, it is not a mandatory step:




On the next screen, you get to choose what kind of installation you want to run. There are two choices here:


Typical Exchange Server Installation - this will install Hub Transport Role (formerly Bridgehead), Client Access Role, Mailbox Role and the Exchange Management Tools (formerly known as Exchange System Manager) - on this same machine.


Custom Exchange Server Installation - here you can choose exactly which server roles you want to install. If you want to install a clustered mailbox server, you should use Custom Setup. When installing a clustered mailbox server, you can choose if you are installing the Active or Passive node.



If you pressed the Custom Exchange Server Installation button and pressed next, you will see the following:




Few next screens will differ on the situation:


Specify the organization name - if you are creating a new Exchange organization, you will get asked for the name of the new org here.


Mail Flow Settings – if Setup detects that you are joining an existing organization, then you will be prompted to select an existing Exchange 2000/2003 server in the routing group that Exchange 2007 will connect to. Press the Browse button and select an existing server.


If you are creating a new Org, the next screen asks if there are any clients in the organization that run Outlook 2003 or earlier. The reason why this is important is that - if the answer to this question is "Yes" then Exchange 2007 Mailbox role will also include a public folder database. Seeing that the public folders are an optional component (if all clients are using Outlook 2007) - answering "No" to the above will give you an Exchange 2007 server without a public folder database.




After the above, Exchange 2007 will run prerequisite checks for the roles that you have selected to install. The result of those prerequisite checks will be displayed in the wizard, and can be copied out of the wizard if you want to - by pressing CTRL+C. If all prerequisites are met, the Install button will become available; ideally you will end up with a screen looking like this:




NOTE: the prerequisite check will give you a warning if you are installing a 32 bit version of Exchange Server 2007. As we discussed before on this blog, 32 bit version of Exchange Server 2007 is not supported in production environments, but you are not installing this Beta 2 in production anyway, right?


When the Install button is pressed, Setup will be installing the roles you have selected in previous step. The "Organization Preparation" step typically takes the longest of all other steps (if it was not run previously). After all roles are installed correctly, press the Finish button.


Maintenance setup


If you want to modify your Exchange 2007 installation (add or remove server roles), you should go to Add/Remove Programs Control Panel applet; to add server roles, press the Change button. To remove them, press the Remove button:




Pressing the Change button allows you to check only the roles that are available to install (meaning - can be possibly installed on the server, as they do not conflict with roles already installed and are not yet installed). Other roles will be either grayed out (not available to install concurrently with other roles already installed) or will be checked and grayed out (already installed roles). Checking new roles and pressing Next will start the prerequisite check and then later installation of those roles only:




Pressing the Remove button will show you roles that are currently installed as checked checkboxes that can be unchecked. Unchecking the role here and pressing next will start the prerequisite check and then remove the selected roles:




Setup logs


In newer builds of Exchange 2007, all of the Setup logs are stored in a single location, in a folder on the C: drive. The default log path is:




There are several files in there; the ones that are used the most are:


ExchangeSetup.msilog - this log file contains information about the unpack phase of setup where Windows Installer extracts the binaries and places them on disk for use during setup.


Exchange Server Setup Progress.log - this log file was included in previous version of Exchange and contains information related to the configuration data.


ExchangeSetup.log - this log file is new to Exchange 2007 and contains more information about the task that are run in setup. This log is usually the primary log for you to look at Setup problems, especially if there are some server roles that have failed the Configuration stage.


The ExchangeSetup.log is broken out in subcomponents highlighting different levels (indents). These levels can be used by future parsers.


        [0] - Begin main run of a particular task

        [1] - High level run of a specific task

        [2] - Subset of a particular task


Setup run of this log file are separated by the following markers:


[7/14/2006 4:49:42 PM] [0] **********************************************

[7/14/2006 4:49:42 PM] [0] Starting Microsoft Exchange 2007 Setup

[7/14/2006 4:49:42 PM] [0] **********************************************




[7/14/2006 6:28:30 PM] [0] End of Setup

[7/14/2006 6:28:30 PM] [0] **********************************************


Additionally, major setup tasks are separated by the following:


[7/14/2006 4:06:59 PM] [0] **************


To read more about Exchange 2007 configuration post setup, please check out Exchange 2007 Help file (ExchHelp.chm)


- Malvin M. Seale and Nino Bilic

Comments (52)
  1. Josh says:

    My previous installation of PowerShell RC1 was not detected by the Exchange installer. In fact, when I went to install Monad RC0, I had to first UNinstall PowerShell. What’s with that? Not even mentioned in the Release Notes or here.

  2. Exchange says:

    Hi Josh – you are right, we mentioned that Monad can be too old but the same principle applies if it is too new…

  3. ANDREY says:

    Does anyone else think that the new logo looks like a swastika?

  4. Josh says:

    Thanks for your reply. I’ve completed the install now and am getting started with a test domain. Thanks for all your hard work on Exchange; I’m really looking forward to using it.

    Question: Is it possible to install the Exchange Management Console and/or the Shell on a 32-bit XP box? I’ve got the x64 files. Do I need the x86 files for this? If so, will you be including mgmt tools for x86-based systems on the final release? Thanks.

  5. Thiyagu says:

    IF we complete a typical installation.

    Is there any additional config reqd to have a basic internal message flow.

    i have a singlebox on which ad and exchange 2007 is installed.

    but the mailflow is not happening.

    wht needs to be done on this?


  6. Andrew says:

    I have some screenshots of OWA and the Exchange Management Console up as well at, as well as an installation and setup guide.

  7. Rose says:

    Very good info, specially the setup logs tips good for troubleshooting.


  8. Desmond Lee says:

    Windows Setup
    Please go to the Control Panel to install and configure system components.

    The above error mesage is persistent on the AD root DC running W2k3 Enterprise Ed R2 (Schema Master role, GC, W2k3 Native mode – forest and domain).

    The following have already been installed prior to running "setup /prepareschema" or "setup /preparead" in a test environment:

    – MMC 3.0 (part of W2k3 EE R2)
    – Monad (
    – MS .NET Framework 2 Runtime

    Any clues as to why this first phase fails? Thanks!

    Sorry but there is NO link via to enable beta feedback (even though it provided a link to and landed back to the same page :(


  9. ninob says:

    Desmond Lee,

    If you go to SETUP.EXE on the Exchange 2007 files and double-click on it – what happens? It is unclear to me when you get this error. Did you burn the bits to the DVD?

  10. ninob says:


    Please open up the Exchange Help file (it is located under Exchange group under Start menu) – steps differ based on the environment and your needs, but it should all be there.

  11. Karsten says:

    Two colums I freqently use with Exchange 2003 are "Mailbox below quota or not" and "Last Connected Time". I didn’t found that in the Mailboxview of Exchange 2007 – Is it possible do get those colums?

  12. Andy Grogan says:

    Hiya, got it installed – works great, but, I would like to import a pst into a mailbox in my test lab (for  testing purposes) – the Exchange 2003 version of EXMERGE does not work (which I can understand) – can this be done?

  13. Karsten says:

    Bug? I Installed the 4 Main Functions of Exchange 2007 (German 32 Bit) and for some reason it stopped after Management Tools. Later I tried again and Mailbox, Hub Transport and Client Access worked – UM dosne’t.

    It sems to be a problem whith the path (I installed from a Network Mapping whitch I changed from Z: to W:). I changed the driveletter in the Wizzard but for Unified Messaging that Wizzard seems to foregt the change.


    Opening package ‘Z:ISO-IMAGESExchange 2007 Beta 2 x86 dSetupServerRolesUnifiedMessaginges.MSI’ failed. Das System kann den angegebenen Pfad nicht finden. Error code is 3.

  14. David says:

    The beta release specifies support for XP x64, is this wrong?  

    I get the following message in the "Readiness Checks" section of the install:

    "Active Directory does not exist or cannot be contacted."

    Can Active Directory be installed w/in XP?

    I tried installing the ADAM utility (ADAMSP1MUI_X64.exe), but that didn’t help.

  15. Desmond Lee says:

    Running off from a local disk instead of from a NT share fixed the error reported earlier today. Thanks ninob.

    Now there is another interesting requirement which was not clearly stated in any existing E12 documention about mandatory requirement of at least 2 DCs per AD domain.

    My test environment has only 1 DC in rootdomain.local and 1 DC in child.rootdomain.local. Does that mean that there is no way to install E12B2 with this setup, including the single DC child domain?

    See error below reported in ldif.err:

              —– cut here —–

    Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=rootdomain,DC=local

    changetype: add

    Attribute 0) adminDescription:ms-Exch-Access-Control-Map

    Attribute 1) adminDisplayName:ms-Exch-Access-Control-Map

    Attribute 2) attributeID:1.2.840.113556.1.4.7000.102.64

    Attribute 3) attributeSyntax:

    Attribute 4) isMemberOfPartialAttributeSet:FALSE

    Attribute 5) isSingleValued:TRUE

    Attribute 6) lDAPDisplayName:msExchAccessControlMap

    Attribute 7) name:ms-Exch-Access-Control-Map

    Attribute 8) oMSyntax:64

    Attribute 9) objectCategory:CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=rootdomain,DC=local

    Attribute 10) objectClass:attributeSchema

    Attribute 11) schemaIdGuid: UNPRINTABLE BINARY(16)

    Attribute 12) searchFlags:0

    Add error on line 1: Busy

    The server side error is "The FSMO role ownership could not be verified because its directory partition has not replicated successfully with atleast one replication partner."

    An error has occurred in the program

              —– cut here —–

    Thanks for your help!

  16. Exchange says:

    Andy Grogan,

    At this time, you will have to use Outlook for PST imports.

  17. Exchange says:


    Nope – XP is not the OS where you can install Exchange Server 2007. Where did you see this as a supported platform for server installation?

  18. Exchange says:


    Sorry I don’t 100% follow – can you tell me what you did exactly? Does Setup work if you run it from local drive?

  19. Exchange says:

    Desmond Lee,

    What you are seeing is not what we’d expect, no… in fact few of us have E2007 B2 installed in a single DC domains in our labs and it works. I would suggest looking into AD related issues, possibly running DCDIAG and NETDIAG?

  20. Karsten says:

    Exchange – Thanks for your answer.

    I installed Exchange in two parts. First I installed from (network)drive z. I choosed the 4 Roles "Mailbox", "Hub Transport" "Client Access"  and "UM".

    That Installation crashed (I am not shure why – maybe because I had forgotton to install ASP.Net or because AD modification needed some more time because I didn’t preparated it seperate.) However the Management tools had been installed.

    I rebooted and remapped the installation drive "net use * \…". Windows choosed a different driveletter (w:).  

    I used "Add / remove software" to change my Exchange Installation (adding the 4 roles).  

    The installation Wizzard remebered drive z: for the installation files. I changed that to w: whitch worked fine for "Mailbox", "Hub Transport" "Client Access". But UM din’t install because it was looking for a file from z:

    After I corrected the path to the installaition files in 3 keys in the registry I could Install UM. One key was:


    So I had two crashes in the installation process but my question / bugreport is mainly concerning the installation stop whith UM.

  21. dcuccia says:

    Exchange, thanks for your quick response.

    I must have confused the requirements w/ MSH reqs, I see clearly that the install requires Server.

    Any reason (besides resource sharing and cost) that I shouldn’t install Server on my XP machine w/in a virtualization environment like Parallels Workstation and run Exchange 2007 inside of it?



  22. Exchange says:


    Thanks for additional detail… say – can you ZIP and email me the ExchangeSetup.log from c:ExchangeSetupLogs? I’ll make sure we file a bug on that one. ninob AT microsoft DOT com.

  23. Exchange says:


    For testing, you can definitely run E2007 in a virtualized environment, sure. The exact support details for this at RTM have not been announced yet though, so – I’d say if the virtualization software lets you do it – go for it. Just to give you an idea, here
    is our support policy for Exchange 2003:;[LN];320220

  24. Desmond Lee says:

    The AD forest (root and child domains) have now been successfully prepared using /prepareAD and /prepareDomain on the first root DC and the only child DC respectively. This was after a second root DC has been added. Prior to that, netdiag and dcdiag were executed with no reported problems (with DNS or AD for instance). Still a mystery as to why this resolved the previously reported problem. Do you know why?

    Test environment now is 2 x root DCs and 1 x child DC and Exchange 2007 Beta 2 is working.

    Question: when will the Microsoft Learning curriculum be updated to cover Beta 2? Does it still make sense to take the Ignite or existing MOC  3910A and 3910B Exchange 2007 courses (got no answer from no one from MS so far :-(

    Thanks Ninob.

  25. Hi,

    I’ve noticed that during the org preparation part of the setup (during the executing of the LDIF scripts), that there is a dependancy to the remote registry service on the DC`s.

    My setup was failing because the remote registry service was disabled on our DC’s.  Once i`ve modified the GPO to allow the service to be started, the setup ran fine.

    I think this may cause major headaches.  Most of my clients have this service disabled on all servers.  

    Maybe I am mistaken in my diagnostics.  Anybody else noticed this kind of issue?



  26. I am commenting on my previous post :)..

    Actually I can probably just run the forestprep and domainprep parts on the DC instead of running it on the exchange server in order to avoid my issue with the remote registry service.


  27. espryte says:

    Hi guys,

    According to release notes: Anonymous mail submission and open relay are turned off by default. I cannot turn it on with the provided command (get-receiveconnector -server %SERVERNAME% | set-receiveconnector

    -AnonymousAllowed:$True -RelayControl:Open). It sais "A parameter cannot be found that matches parameter name ‘AnonymousAllowed’".

    Parameter name not in the help files. What do I do wrong? Any ideas?


    Roles: Cas/Hub/Mailbox, no Edge in place

    Version: 08.00.0605.016




  28. Exchange says:


    Yup, that seems to be bug in release notes… but here is where it should be right:

  29. Lance Wilson says:

    I believe this is the correct command Espryte:  get-receiveconnector -server %COMPUTERNAME% | set-receiveconnector -PermissionGroups AnonymousUsers


  30. emess says:

    Exchange 2007 coexistence with Exchange 2003?

    I’ve tried to install Ex2007 in a Ex2003 org. The installation went fine, I can mount the public folder database but not the mailbox database on the new exchange 2007 server. I can’t create a new one either. I get the following error message:


    Microsoft Exchange Error


    Failed to mount database ‘Mailbox Database’.

    Mailbox Database



    Exchange is unable to mount the database that you specified. Specified database: 7cb36a6a-bd3e-418f-8975-8f98909a22d4; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-2147467259).




    Ther is now .edb file where the database is supposed to be and no one is created when I try to create a new one.



  31. Mark says:

    I’ve installed Exchange 2007 Beta 2 and have been impressed with the progress made from the CTP/Beta 1. But I’ve found a bug with the SendConnector. I am on a SBC dsl connection for my testing which requires me to relay all my outgoing email through their mail server. I setup a smarthost with basic authentication and it doesn’t work. I did some testing and discovered that it was changing my username from to sbcglobal.netsomeone which causes the authentication to fail. Any ideas on how this can resolved so I can test the Beta? If you want more info on the issue you can email me mark at davidsons dot org. Also where is the correct place to file a bug report. I couldn’t find anyplace to do that.

  32. Exchange says:


    Thanks for letting us know – we just filed a bug on this. On where you can report bugs – the Connect site should have the link if you are on the Beta or if not – then you could discuss this in our new forums. As far as the workaround for this, the only thing that comes to mind right now is to bounce email off Windows SMTP service 1st and then from there to the SBC server. It would have to be SMTP running on a different machine though.

  33. John says:

    For exchange 2003 there’s an article in the knowledge base;en-us;821897

    In exchange 2007 everything is "a little" different and I can’t figure out how to give one account unrestricted access to everything on the server.

    I know it is possible to add mailbox permissions with (technet example)
    Add-MailboxPermission MyServiceAccount -user Test2 -accessright fullaccess -inheritanceType all

    but it does not accept an astrix (*) so this does not work
    Add-MailboxPermission MyServiceAccount -user * -accessright fullaccess -inheritanceType all

    still if it would work, it would not appy permissions to future users/new mailboxes.

    I need something to give MyServiceAccount full access at a higher (store) level.

  34. Yev says:


    After installing and playing around i noticed that i can’t run exchange tasks on users in AD Users and Computers, also i cant see the exchange attributes in the properties of users.

    Is the EMC the only place to manage exhcnage tasks?

    If so then it’s not so good since there is no hiarchy and mail enabled users can’t be managed easily according to the AD tree logic.


  35. ninob says:


    This should be the way to do it from the EMS:

    get-mailboxdatabase server1db1 | add-adpermission -user someuser -accessRights <rights> -extendedrights <exrights>

  36. hasan1st says:


    I’ve installed Exchange 2007 all running well, except I can not find any documentation on configuring UM.

    I need information on what I should do on my IP Gateway (Nortel) and on Exchange itself to get UM to start working.


  37. Extremefilter says:

    Has anyone tried to install Exchange 2007 64Bit on Longhorn Beta 64bit!? Am in the process of trying this… EX2007 seems to require IIS6 and fails Metabase checks… by adding in IIS6 Management Compatibilty service to IIS7 then gets passed this bit.. then fails on Mailbox Role readiness check.

    I am trying to replace msdaps.dll with version from KB904639 to enable Exchange 2007 B2 to pass the readiness check for the Mailbox Role. It fails saying the needs version 2.82.2492.0 or higher. This is contained in KB904639, but it wont install, so want to over-write the dll manually.. But have run into permissions problem!

    I have no permissions to do so. The only group that has full control is the built-in account "TrustedInstaller". If I can add my admin account to this group then will be OK… however the trustedinstaller group does not appear in either AD or in local users and groups… so am a bit stuck!

    Any ideas on how to do this? Apologies if this is not correct place to post this!


  38. KC Lemson says:

    Extremefilter – we do not support running on longhorn yet.

    hasan1st – try the exchange UM forum.

    Yev – Correct, there is no longer an ADU&C snapin for exchange, and management of exchange attributes must happen within EMC. You can configure filters in EMC or modify the AD scope to narrow things down.

  39. blake says:

    What command do I use to set SMTPSubmitAcceptAnySender to true?  So the SMTP connector will accept email from any sender address?

  40. Ramburst says:

    Is it tecnically possible to install "Exchange 2007" B2 on a Domain Controller running Windows 2003 Server R2 64-it OS?

  41. Exchange says:


    Yes, that is possible. R2 is a supported OS platform for E2007 B2.

  42. newbee says:


    I am setting up a front end and backend senario.  Does any one knows what I have to do to setup the SMTP, so all the mail flow goes through the front end server only and I have all my mailboxes on the back end server?

    On the backend I have Mailbox, Hub Transport, Client Access. and On the front end I have Hub Transport and client access only.

  43. fortscmr says:

    Does anyone have an update for the post below.  I have attempted installation of Exchange 2007 twice in a lab environment.  The installation runs with no errors, no problems are indicated in the log files, but the mail database is not created on the disk.  When I attempt to delete and add the database back into the First Storage Group the wizard appears to run fine, but no edb file is created.  The account that installed Exchange 2007 has all of the required permissions, and there are no permission settings on the disk that would prevent creation of the file.  The wizard does create the other files (transaction logs….).  Does anyone have a fix for this?

    emess said:

    Exchange 2007 coexistence with Exchange 2003?

    I’ve tried to install Ex2007 in a Ex2003 org. The installation went fine, I can mount the public folder database but not the mailbox database on the new exchange 2007 server. I can’t create a new one either. I get the following error message:


    Microsoft Exchange Error


    Failed to mount database ‘Mailbox Database’.

    Mailbox Database



    Exchange is unable to mount the database that you specified. Specified database: 7cb36a6a-bd3e-418f-8975-8f98909a22d4; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-2147467259).




    Ther is now .edb file where the database is supposed to be and no one is created when I try to create a new one.



    July 26, 2006 6:36 PM

  44. kalam says:

    Dear all,

    I am trying to install Exchange 2007 on Windows 2003 R2.

    I can successfully install Client access role and hub transport role but when I try to install Mailbox role recieved the error that an internal component is not responding.

    I am also pasting the error and error code from the setup log file.

    [12:43:07] mode = ‘Install’ (61953) CBaseAtom::ScSetup (f:8.00.0605sourcesdevadminsrcudogsetupbasebasecompbaseatom.cxx:537)

              Error code 0XC1037989 (31113): An internal component is not responding.

    [12:43:07]  ScSetupAtom (f:8.00.0605sourcesdevadminsrcudogexsetdataexsetds.cxx:1032)

              Error code 0XC1037989 (31113): An internal component is not responding.

    [12:43:07] Leaving ScSetupAtom

    Help me please.



  45. Pablo says:

    Testing LCR Recover using page 31 from "Administering Local Continuous Replication" Microsoft documentation. But the Store won’t mount, getting error…

    Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-528).

    At line:1 char:15

    Any ideas?

  46. Pablo says:

    Regarding LCR, recovery worked nicely using the Move-StorageGroupPath, Move-DatabasePath -ConfigurationOnly commands, with the instructions on page 30 of the Microsoft "Administering Continuous Replication" document BUT the "Recover from Missing Database" steps fail. Has any one else noticed this?

  47. Assad says:

    there is a flash tutorial, may be helpful

  48. Philbert says:

    Exchange 2007 Beta 2, Lab enviroment, single DC, will be building E2k7 server as part of existing E2k3 Org.   I’m having problems with the Orgnaization Preparation portion of the install.  Error:  Either a required impersonation level was not provided or the provided impersonation level is invalid.  

    The account being used is Ent. Admin, Schema Admin, Exchange Full Admin., local admin on what will be E2K7 box.

    Andy Ideas?

  49. Robert says:


    Simple setup: One virtual windows 2003 x64 dc, one virtual windows 2003 x64 with all the prerequisites. The setup dies at this location

    Do i still need to install net version 1.1 or net 2.0 is enough?

    Summary: 5 items. 3 succeeded, 1 failed.

    Elapsed time: 00:23:58

    Organization Preparation


    Elapsed Time: 00:06:07

    Copy Exchange Files


    Elapsed Time: 00:02:05

    Hub Transport Role


    Elapsed Time: 00:05:23

    Client Access Role



    An error occurred while trying to access IIS (Internet Information Service) metabase. Make sure the Internet Information Service Manager component is installed and configured properly.

    Unknown error (0x80005000)

    Elapsed Time: 00:01:37

    Mailbox Role


    Thank you


  50. Cailin says:

    I I am having problems installing 2007 when it comes to the hub transport role.I have tried typical and custom. The error reported is "Unable to register the service principal name smtpsvc", the logon attempt failed. This is a DC that I am installing it on. Any ideas ?SMTP is not installed prior to exchange attempting it.


Comments are closed.

Skip to main content