Exchange Installation

I have a bare metal domain controller/DNS server. (Server 2012)
I also have an Exchange server running in a VM, which is joined to the domain. (also Server 2012)
I installed Active Directory Domain Services, so that the Exchange server can write to AD, and then it asked to promote the server to a Domain Controller.
In addition to the pre-reqs, does the Exchange server require the DNS server role?

Hi
Answering your question, you seem to already have a DC/DNS, and hence I didn't quite get where have you installed the ADDS Role and trying to promote it. If its on the Exchange VM its not recommened and won't work out.
Installing Exchange 2013 on directory servers
For security and performance reasons, we recommend that you install Exchange 2013 only on member servers and not on Active Directory directory servers. However, you can't run DCPromo on a computer running Exchange 2013. After Exchange 2013 is installed,
changing its role from a member server to a directory server, or vice versa, isn't supported.
Secondly regarding the DNS, you require access to a running DNS server yes. However you don't have to install the DNS role on the VM running the exchange server itself. I think you have already updated DNS server details on the LAN connection while
joining it to the domain. This is enough for Exchange to function.
Only roles required are as below:
Install-WindowsFeature RSAT-ADDS
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Exchange 2013 prerequisites
Best way would be to use
Exchange Server Deployment Assistant  , a web based tool from MS to walkthough the deployment process.
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Similar Messages

  • Existing exchange installation re-join to domain

    Hello Everyone,
    I'm just trying learn by doing, amateur with active directory and a complete newbie to exchange.
    Here's the scenario and issue:
    Had setup a domain with a single DC
    Had installed a separate server with exchange, configured and working internally.
    Had to then re-install and setup the domain, so removed Exchanged server from domain;
    Re-installed and configured domain
    Rejoined Exchange server in to the domain.
    Problem now is I can only log on to the exchange server in safe mode. I had thought that joining the server with exchange on it would do all the active directory entries it would have done at installation (falsely re-inforced by the fact that server sat
    at "Applying computer settings..." for hours on end). Checked event logs while logged in on safe mode, and event log's is riddled with exchange errors.
    So, could I save this server from losing the exchange data and make it functional again in this domain thus forth?
    Thanks in advance.
    EDIT 01:
    Clarification; I have rebuilt the DC with exact same IP and DNS  configuration as previously. Obviously, if those things did change, there could be configuration issues that the exchange server already has, therefore I took specific care with these
    information. Please also note that I cannot install or uninstall anything if I cannot log on in normal mode. At the moment I can only log on in safe mode. Currently it hangs at "Personalized Settings (Not Responding)...".
    Honestly, from what I have seen in the even logs (may be I should post them here?) I have a hunch that not all (if at all) AD object were created when the I re-joined the machine to the domain. I wonder if there's a way:
    1) I can get past the point where it hangs; then
    2) Recreate the AD object that Exchange would have during installation (Powershell?) without actually uninstalling and re-installing exchange (and losing exchange data in the process - I know BACKUPS!!!) thus restoring the usual relation an exchange server
    would have with an AD / DC server?

    Hi! 
    Try the following:
    uninstall exchange completely
    Install the Windows Server 2008 R2 operating system prerequisites
    http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2
    On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack
    http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en
    Start the Exchange setup again:
    Step 1 & 2 are already completed because you have installed the required features using the previous step.
    Click on Step 3 and Choose Install languages only from the DVD 
    Now click on Step 4: Install Microsoft Exchange
    On the Introduction page, click Next
    Accept the License Terms and click Next
    On the error reporting page select if you want to enable the error reporting feature or not, then click Next
    If you enabled it, Microsoft Exchange will automatically send error reports to Microsoft. This helps Microsoft improving their products.
    On the Installation Type page, Select Typical Exchange Server Installation. A typical installation consist of the Client Access, Hub Transport, and Mailbox server roles, along with the Exchange Management
    Console
    If you want to customize your selection, then click on Custom Exchange Server Installation
    Here you don't need to select the option Automatically install Windows Server roles and features required for Exchange Server, as we already installed these roles and features in a previous step using PowerShell and restarted
    our server.
    On the Organization name, Type your organization name and then click Next
    If the server is facing external access then type the name that your users will be using to access your mail server from the internet. For example, my users will be able to check their mails using any browse by typing http://mail.elmajdal.com
    On the Customer Experience Improvement Program, select if you want to join the program or not and then click Next
    Exchange Readiness Checks will start to check if all prerequisites are setup and installed, and will report to you if you have any prerequisites missing 
    The only warning you will receive is that Exchange Server 2010 setup will prepare your Domain for Exchange. The domain preparation operation will start once you click on Install .
    Make sure the user you are using to install Exchange is a domain admin, enterprise admin, schema admin. Make sure also that you are logged into the computer using your domain user, and not using a local computer account .
    Exchange installation will start
    Installation will be completed. Click Finish
    You will be notified that its better to reboot the server after the installation is completed, as setup has made changes to the operating system settings that require a reboot to take effect.
    Exchange Management Console will open. and you can start configuring your server, which we will discuss in future articles.
     Source:http://www.elmajdal.net/ExchangeServer/Installing_Exchange_Server_2010_SP1_on_Windows_Server_2008_R2_SP1.aspx
    I'm looking for alternatives to the solution you have provided, however, let's say I wanted to explore this option, any ideas on how I can get past the "Personalized Settings (Not Responding)..." part described in my edit to my original post? Thanks

  • Exchange Installation Error on Mailbox role: Transport Service Step

    The error I receive occurs at 47% of the Mailbox Role: Transport Service installation.  The details of the error are as follows:
        Mailbox role: Transport service                                                                  
    FAILED
         The following error was generated when "$error.Clear();
              if ($server -eq $null)
                set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
            " was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
    Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
            'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
    Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    Also, when opening the setup log I have this:
    [12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
    [12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.
    [12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
    [12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
    [12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [12/26/2012 17:51:25.0825] [0] End of Setup
    [12/26/2012 17:51:25.0825] [0] **********************************************
    I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/
    http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/
    Some additional information:
    This is a clean installation of Exchange 2013 in a forest that has never had exchange.
    The domain and forest preparations run without errors and are at functional level of 2003.
    The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.
    This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.
    I am running the installation as an enterprise, schema, domain admin.
    Thanks for your help in advance.

    Yes.  I cleaned out Exchange with ADSIEdit so I could re-run the Prepare Schema, domain and all domains and then re-ran setup to show the output here.  But the install still failed.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareSchema
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Extending Active Directory schema                                                                
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:AZGT
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
    een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
    aspx
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAllDomains
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Prepare Domain Progress                                                                          
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\>
    PS F:\> .\setup /IAcceptExchangeServerLicenseTerms /mode:install /roles:Mailbox /TargetDir:"C:\Program Files\Microsoft\Exchange Server\V15"
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Languages
    Management tools
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                                                        
    COMPLETED
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Preparing Setup                                                                                  
    COMPLETED
        Stopping Services                                                                                
    COMPLETED
        Copying Exchange Files                                                                           
    COMPLETED
        Language Files                                                                                   
    COMPLETED
        Restoring Services                                                                               
    COMPLETED
        Language Configuration                                                                           
    COMPLETED
        Exchange Management Tools                                                                        
    COMPLETED
        Mailbox role: Transport service                                                                  
    FAILED
         The following error was generated when "$error.Clear();
              if ($server -eq $null)
                set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainCo
    ntroller
            " was run: "Active Directory operation failed on DC1.XXXX.XXXX.com. This error is not retriable. Addi
    tional information: The object cannot be added because the parent is not on the list of possible superiors.
    Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
            'CN=EXCHMBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
    Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=XXXX,DC=com'
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS F:\>

  • Rights required after exchange installation

    Hi, we are cleaning up our privileged group(s) access and i was wondering what group access the exchange install account requires after exchange is running. currently our exchange install account is still a member of Account Operators, Domain Admins,
    Administrators as well as all the required Microsoft Exchange Security Groups.
    thanks
    Jason

    Hi Jason,
    In order to prepare schema, AD and install Exchange server, the account need to have the Schema Admins, Domain Admins, and Enterprise Admins permissions at least. What's more, the account should be a member of Organization Management AD role group.
    After installation, administrator should have the Organization Management permission and Server Management permission at least.
    For more information, here is the detailed information about my Exchange Security Groups for your reference.
    Besides, I don't understand why you want to remove some privileged groups.
    Hope my clarification is helpful.
    If you need further assistance, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange installation problem

    Error:
    The DNS domain name is invalid. It contains characters other than 'A'-'Z', 'a'-'z', '0'-'9', '.' and '-'.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ServerNameNotValid.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

    Hello,
    It is not recommended that installing exchange server on a DC server.
    According to the error, the DNS domain name set on the local computer is invalid. You can refer to the following article to solve the issue. (Note:Based on my known, it also applies to exchange 2013)
    http://technet.microsoft.com/en-us/library/bb430742(v=exchg.80).aspx
    For the third warning, you can ignore it.
    Cara Chen
    TechNet Community Support

  • Can't see Exchange Server after installation

    I know it must be simple, but after installation of Exchange Server 2013 on Server 2012 R2 and getting the "successful" installation message, I can't find the server. It was not problem on Server 2008 and Exchange 2010.
    Any ideas as to where I should go to look for Exchange?  I can't even setup mailboxes???!!!
    I really am lost on this one.

    Hello,
    In addition to above: make sure that Exchange 2013 is installed correctly. Check Exchange installation logs and run the Get-ExchangeServer command using Exchange Management Shell on the new server. You should see both Exchange 2010 and Exchange 2013 servers.
    Hope it helps,
    Adam
    CodeTwo: Software solutions for Exchange and Office 365
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

  • Exchange Server Installation for a DAG environment

    I have prepared 6 servers for exchange 2013 installation :
    2 for DC and ADC   -- OS windows server 2012 R2
    2 for CAS Role       -- OS Windows server 2012
    2 for Mailbox Role  -- OS Windows Server 2012 
    As Windows Server 2012 R2 is not supported for installing Exchange 2013 i decommissioned 4 Servers ( CAS and Mailbox ) and starting from scratch.
    Will the above scenario work now ... like having Domain controller OS  in Server 2012 R2  and CAS and Mailbox Server Roles in Server 2012 Version ?
    How to install individual Server role for exchange server 2013 ( i mean CAS role on 2 servers and Mailbox on 2 servers). are there any steps to follow on for this ?
    Please let me know on this.

    Windows 2012 R2 will work for a server OS for your Domain Controllers.  However, the Forest and Domain functional levels need to be Windows 2012 or less. 
    For your Exchange 2013 servers, there are a lot of unanswered questions here and these forums only give us a certain amount of space and time to explain the entire installation process.   If this is for production and your not sure what to do,
    your best bet is to hire a consultant to help you out to make sure you get all the ins and outs.  At the very least you can get assistance in your deployment.  If you don't have budget for this or are creating a test lab, you can always try using
    the Exchange Deployment -
    http://technet.microsoft.com/en-us/exchange/jj657516.aspx.  This might give you an idea of how to proceed.
    There are a lot of examples of Exchange installs out there as well.  If this is a lab, these are well worth looking through and tinkering with to get to know the product better: 
    Example -
    http://judeperera.wordpress.com/2012/07/19/step-by-step-guide-for-installing-exchange-server-2013-preview/
    Let us know if that is helpful.
    JAUCG - Please remeber to mark replies as helpful if they were or as answered if I provided a solution.

  • Installation error for Exchange Server-2013

    I am trying to install exchange server-2013 on my Windows server-2012
    machine. I have configured per-requisite applications and develop the server environment with active directory roles.
    At my readiness check option, it shows the following error:-
    "An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later  and windows server-2012".
    I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
    Regard
    Azad 
    Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

    Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through  the
    exchange 2013  management shell  
    "Get-Exchangeserver" 
    However still not able to connect to https://localhost/eac and when i re-run setup 
    01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
    [01-28-2014 21:10:16.0804] [0] **********************************************
    [01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
    [01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
    [01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
    [01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
    [01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
    [01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
    [01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole 
    [01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
    [01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
    [01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
    [01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
    [01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
    [01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
    [01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
    [01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
    [01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole 
    [01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked: 
    [01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole 
    [01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
    [01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
    [01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
    [01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
    [01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
    [01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
    [01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
    [01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
    [01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
    [01-28-2014 21:10:39.0664] [0] Applying default role selection state
    [01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
    [01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
    [01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
    [01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
    [01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
    [01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
    [01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
    [01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
    [01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
    [01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
    [01-28-2014 21:15:30.0513] [0] End of Setup
    [01-28-2014 21:15:30.0513] [0] **********************************************

  • Exchange 2010 Installation error

    Hi All,
    I'm at my over 10th installation of Exchange 2010 server and it is the first time I have to admit that I can't resolve the issue i'm faced off ;-)
    Here is some info about my issue. The installation is on a Windows 2008 R2 (Virtual) sit on a Windows 2012 R2 server with Hyper-V and it is a fresh vanilla installation that I'm trying to install for the 3rd time. Each attempts returned me the same error
    at the same steps.
    The Exchange installation is a typical, common, CAS, Mailbox and HUB installation without any particular configuration in the setup.
    Here is the error I get:
    Client Access Role
    Failed
    Error:
    The following error was generated when "$error.Clear(); 
    $urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
    new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
    " was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
    An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
    The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element'
    could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
    I Googled every single point of failure indication and I didn't get reliable fix or work around.
    I used ADSI edit  to see if the IIS folders are there and yes they are except the EWS one which is mentioned in
    the error message. Forest, Domain and AD have been prepared as it should, DCDIAG doesn't return any problem and the security has been set
    properly for Legacy migration with an Exchange 2003 organisation.
    Here is the par of the Exchange setup log where it stopped:
    [03-06-2014 16:15:26.0488] [1] Processing component 'Client Access Services Configuration' (Configuring Client Access services.).
    [03-06-2014 16:15:26.0488] [1] Executing: 
    $urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
    new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
    [03-06-2014 16:15:26.0503] [2] Active Directory session settings for 'New-WebServicesVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'powerhouse.parasuco.com', Preferred Global Catalog: 'powerhouse.parasuco.com', Preferred
    Domain Controllers: '{ powerhouse.parasuco.com }'
    [03-06-2014 16:15:26.0503] [2] Beginning processing new-WebServicesVirtualDirectory -WindowsAuthentication:'True' -WSSecurityAuthentication:'True' -InternalNLBBypassUrl:'https://mtl1ex01.parasuco.com/ews/exchange.asmx' -DomainController:'powerhouse.parasuco.com'
    -Force:'True' -GzipLevel:'High'
    [03-06-2014 16:15:26.0636] [2] Searching objects "MTL1EX01.parasuco.com" of type "Server" under the root "$null".
    [03-06-2014 16:15:26.0649] [2] Previous operation run on domain controller 'powerhouse.parasuco.com'.
    [03-06-2014 16:15:26.0650] [2] Processing object "MTL1EX01\EWS".
    [03-06-2014 16:15:29.0130] [2] [ERROR] Unexpected Error
    [03-06-2014 16:15:29.0130] [2] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
    [03-06-2014 16:15:29.0131] [2] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
    'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
    [03-06-2014 16:15:29.0138] [2] Ending processing new-WebServicesVirtualDirectory
    [03-06-2014 16:15:29.0139] [1] The following 1 error(s) occurred during task execution:
    [03-06-2014 16:15:29.0139] [1] 0.  ErrorRecord: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
    [03-06-2014 16:15:29.0139] [1] 0.  ErrorRecord: System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'. ---> System.Configuration.ConfigurationErrorsException:
    The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension,
    Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config
    line 2373)
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.Configuration.GetSection(String sectionName)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.WebConfigReflectionHelper.CommitToWebConfig(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task, String path, String site, String server, Boolean isTokenCheckingSpecified,
    Boolean isSpnListSpecified)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.CommitToMetabase(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessMetabase()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDirectory.InternalProcessMetabase()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
       --- End of inner exception stack trace ---
    [03-06-2014 16:15:29.0139] [1] [ERROR] The following error was generated when "$error.Clear(); 
    $urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
    new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
    " was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
    [03-06-2014 16:15:29.0139] [1] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
    [03-06-2014 16:15:29.0139] [1] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
    'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
    [03-06-2014 16:15:29.0140] [1] [ERROR-REFERENCE] Id=ServicesComponent___ca981854eaa74c1ca684178d9ea52fff Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [03-06-2014 16:15:29.0140] [1] Setup is stopping now because of one or more critical errors.
    I appreciate the time anybody would spend to help me with my issue

    Well, here is a status of what I did.
    After running the Cleanup tool, I ran the Exchange server setup again without re installing anything and I got the same error and I have found .NET issue in the application's event logs (Event ID 1111 .NET runtime optimization service with this error code:
    - Error code 0x80029c4a =
    Cannot Load Library); . Why that? because there still Windows Kernel Mode and User Mode .NET 1.11.
    So I uninstalled them and ran the exchange setup again. It failed a the same point but nothing in the application log that time.
    Going further to see if it is a .NET issue, I re installed from Windows Update the .NET
    1.11 packages (Which are required prior to reinstall .NET 4.5) restart the server + re install version 4.5.1 and ran the setup again without the two available security patches for .NET 4.5.1. Guess what, same issue. No .NET error and no specific or related
    log except the Exchange setup installation error.
    From the MSExchange Management log, i have found that 2 errors are logged each time I run the setup:
    Cmdlet failed. Cmdlet Install-ClientAccessRole, parameters {DomainController=powerhouse.parasuco.com, UpdatesDir=E:\Updates, ExternalCASServerDomain=webmail.parasuco.com}.
    Cmdlet failed. Cmdlet New-WebServicesVirtualDirectory, parameters {WindowsAuthentication=True, WSSecurityAuthentication=True, InternalNLBBypassUrl=https://mtl1ex01.parasuco.com/ews/exchange.asmx, DomainController=powerhouse.parasuco.com, Force=True, GzipLevel=High}.
    So it seems to me to be a IIS and security issue. Again, All other IIS virtual folders have been created without any problem. Why does the setup can't create the EWS one???

  • First installation of Opensuse-exchange... doesn't start!

    Hello to all.
    I'm a very linux noob.. sorry, but I'm also very bored of Winzoz!
    I need you help to solve my opensuse-exchange installation problem.
    I have a laptop installed with SLED 11.4, kernel 2.6.37.1-1.2; with yast I installed opensuse-exchange from opensuse.org. During this it adveses me about some conflict an software dependencies that I ignored.
    Finished the installation, I tried to access to "Email Settings", but nothing happened.
    I though about wrong installation or a SO damage caused by me, because it doesn't even start Evolution Client.
    How can I restore deleted dependencies and where is it saved the yast log file?
    Many thank to all.
    Arz77

    On 07/04/2011 08:36, arz77 wrote:
    > I'm a very linux noob.. sorry, but I'm also very bored of Winzoz!
    > I need you help to solve my opensuse-exchange installation problem.
    > I have a laptop installed with SLED 11.4, kernel 2.6.37.1-1.2; with
    > yast I installed opensuse-exchange from opensuse.org. During this it
    > adveses me about some conflict an software dependencies that I ignored.
    > Finished the installation, I tried to access to "Email Settings", but
    > nothing happened.
    > I though about wrong installation or a SO damage caused by me, because
    > it doesn't even start Evolution Client.
    > How can I restore deleted dependencies and where is it saved the yast
    > log file?
    This forum is for dealing with questions and/or issues relating to the
    Connectors for Novell's Data Synchronizer product.
    I suggest that you repost your question in the SLED:
    Configure-Administer forum @
    http://forums.novell.com/novell-prod...re-administer/
    HTH.
    Simon
    Novell Knowledge Partner (NKP)
    Do you work with Novell technologies at a university, college or school?
    If so, your campus could benefit from joining the Novell Technology
    Transfer Partner (TTP) program. See novell.com/ttp for more details.

  • Exchange management tools error "reboot from a previous installation pending"

    I am trying to install the Exchange 2010 Management Tools onto a client. We have Exchange 2010 running already elsewhere, but have been doing RDP to the server in order to add mailboxes, etc., need to have more administrators on their own Windows 7 client
    computers doing remote management.
    Windows 7 Enterprise (64bit) client computer in same domain as Exchange servers, UAC disabled, logged in as a domain administrator. Fresh restart. No updates pending. Noticed article
    http://technet.microsoft.com/en-us/library/cc164360(v=exchg.80).aspx "A Restart from a Previous Installation is Pending" and numerous posts that indicated I should
    clear "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile" or clear "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations" - but neither of these keys
    exist on my computer!
    Downloaded and unzipped Exchange2010-SP3-x64.exe to C:\Temp
    Ran C:\Temp\setup.exe
    Checked off the options:  a) Error Reporting - Yes (Recommended). b) Custom Exchange Server Installation. c) Select "Management Tools". d) LEAVE UNSELECTED "Automatically install Windows Server roles and features required for Exchange". 
    Get the following errors
    Summary: 3 item(s). 1 succeeded, 2 failed.
    Elapsed time: 00:00:22
    Configuring Prerequisites
    Completed
    Elapsed Time: 00:00:01
    Management Tools Prerequisites
    Failed
    Error:
    A reboot from a previous installation is pending. Please restart the system and rerun setup.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Warning:
    Setup cannot contact the primary DNS server (172.17.253.51) using TCP port 53. Check that the IP address of the DNS server is correct and that the DNS server is reachable.
    Elapsed Time: 00:00:17
    Languages Prerequisites
    Failed
    Error:
    A reboot from a previous installation is pending. Please restart the system and rerun setup.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Warning:
    Setup cannot contact the primary DNS server (172.17.253.51) using TCP port 53. Check that the IP address of the DNS server is correct and that the DNS server is reachable.
    Elapsed Time: 00:00:03
    Already have reviewed many articles on this topic, none seem to apply to my situation. I am going crazy trying to solve it.

    As I've said this workstation meets the requirements for installation of the Management Tools. It is 64bit.
    Thanks for the link to the exchangeserverpro.com installation instructions blog. It is something I had already reviewed. There are many comments with problems, so many in fact it is confusing what finally worked for people who ran into snags.
    Many also reported the "reboot from a previous installation is pending" problem (that I am getting), but their solution to that problem is not obvious, since, as I originally posted, the Microsoft answer to that error message is contained in "http://technet.microsoft.com/en-us/library/cc164360(v=exchg.80).aspx"
    and the registry keys do not exist on my Win7 client. The other solution in the comments seemed to be to exclude the "Automatically install Windows Server roles and features required for Exchange" during install (but so far Ed and Rajith want
    me to include that option). The blog is quite old, and so I hoped the SP3 for Exchange 2010 would have fixed the installer issues identified in the comments on that blog... but apparently not!
    DNS is working in our environment. The IP address in the error message points to a network load balancer (NetScaler by Citrix) and does not respond on telnet using port 53... It is our standard DHCP-provided configuration for client DNS. (Does the
    Exchange installer for Management Tools have some unique DNS requirements beyond normal name resolution? If so, does the Exchange admin need DNS admin rights?) Just to remove the load balancer from the equation, I changed my Win7 client network adapter settings
    to use two real, physical actual Microsoft AD domain controllers to resolve DNS. I performed an IPCONFIG /FLUSHDNS. Then re-ran the Exchange 2010 installer. The specific error for DNS has gone away now that I am not using our enterprise's standard load balancer
    DNS client configuation. I really need to know why this is an Exchange management tools requirement. Any ideas?
    But still no-go on getting the Exchange 2010 Management Tools to install. Here are the latest errors on the Readiness Checks:
    Summary: 3 item(s). 0 succeeded, 3 failed.
    Elapsed time: 00:00:25
    Configuring Prerequisites
    Failed
    Error:
    The following error was generated when "$error.Clear();
              if($RoleInstallWindowsComponents)
                # Install any Windows Roles or Features required for the Management Tools role
                if ($RoleIsWindows8OrHigher)
                  if($RoleADToolsNeeded)
                    $ADToolsNeeded = 1
                  else
                    $ADToolsNeeded = 0
                  Invoke-Expression " Powershell -Command {& $RoleBinPath\InstallWindowsComponent.ps1 -ShortNameForRole AdminTools -ADToolsNeeded $ADToolsNeeded} "
                else
                  Install-WindowsComponent -ShortNameForRole "AdminTools" -ADToolsNeeded $RoleADToolsNeeded
            " was run: "The system cannot find the file specified".
    The system cannot find the file specified
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
    Elapsed Time: 00:00:01
    Management Tools Prerequisites
    Failed
    Error:
    A reboot from a previous installation is pending. Please restart the system and rerun setup.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Elapsed Time: 00:00:20
    Languages Prerequisites
    Failed
    Error:
    A reboot from a previous installation is pending. Please restart the system and rerun setup.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Elapsed Time: 00:00:03
    If I remove the "Automatically install Windows Server roles and features required for Exchange" on the installer, I do not get the PowerShell error, just the "installation is pending" errors:
    Summary: 3 item(s). 1 succeeded, 2 failed.
    Elapsed time: 00:00:39
    Configuring Prerequisites
    Completed
    Elapsed Time: 00:00:00
    Management Tools Prerequisites
    Failed
    Error:
    A reboot from a previous installation is pending. Please restart the system and rerun setup.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Elapsed Time: 00:00:12
    Languages Prerequisites
    Failed
    Error:
    A reboot from a previous installation is pending. Please restart the system and rerun setup.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
    Elapsed Time: 00:00:02
    Which puts me right back to where I started in this thread. 

  • Exchange 2013 Installation

    I am installing Office 365 online for my network.  The present setup is that I have pop 3 mailboxes with my ISP - I don't have any exchange installation. 
    My question is should I install Microsoft exchange 2013 locally and then move online OR should I simply install online -- when I look at the Exchange Server Deployment Assistant  it seems to work with upgrading installations as opposed to clean installs.
    Apols if this Q has an obvious answer.
    Rgds
    O

    Hi
    As per the information and details provided by you, I think you should install Exchange 2013 on a member server.
    I hope this information will be helpful for you.
    Thanks and regards
    Shweta@G 

  • Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

    Hi Team,
    Need urgent help in resolution of following error:
    Environment Details: VMware ESXi 5.5 (vMotion)
    Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
    Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
    OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
    Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
    Prerequisites: Installed
    Error: Installation gives Error at Step 10 during installation of Mailbox Service
    Error Details Below:
    Error:
    The following error was generated when "$error.Clear();
    if ([Environment]::OSVersion.Version.Major -ge 6)
    $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
    $reg= join-path (join-path $env:SystemRoot system32) reg.exe;
    $servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
    if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
    if ((get-service wsbexchange).Status -eq "Running")
    Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
    Exchange /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
    Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
    " was run: "Process execution failed with exit code 1.".

    Resolved ! :)
    Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
    As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
    Thanks to all.

  • Windows Server 2012 R2 with Exchange Server 2013 SP1 Completely fresh install giving errors signing into EAC

    Hi,
    I am struggling with a completely clean installation of Server 2012 R2 and Exchange 2013 SP1.  I followed these steps:
    Installed Server OS
    Windows Updates
    Added Active Directory Role (This is a single standalone server that would have been SBS until it was dropped)
    Added DHCP & DNS
    Added Certificate Services
    Added Windows Server Update Services (WID Database & WSUS Services)
    Windows Updates
    Added Media Foundation
    Added File Server Resource Manager and Work Folders
    Added Windows Server Backup
    Windows Updates
    Checked all running without errors in Server Manager and performed a full bare bones backup.
    Ran Setup.exe from Exchange 2013 SP1 disc.
    Installed Pre-requisites and then rebooted
    Windows Updates
    Ran Setup.exe from Exchange 2013 SP1 disc.
    Installation completed without errors
    Rebooted
    Checked all running without errors in Server Manager.
    I Launch Exchange Administrative Center and get "problem with website's server certificate error" (normal on machine with self-assigned certificates).  Click Continue to Website and get:
    Windows Security dialog box:
    iexplore - "The server localhost is asking for your username and password.  The server reports that it is from Digest"
    however no username and password combination will work:  have tried [Administrator]; [Domain\Administrator] even created a user to no avail.
    I believe the issue is somewhere in the IIS configuration because I also get the same error when trying to log into the server website from either the server or another machine on the network.
    I have tried the complete installation three times now:  (full disclosure not all of the same features/roles each time).  On the first attempt I got this error immediately and on try number 2 was able to get into the EAC and created the mailboxes
    but then it started giving the same error.  The above steps are try number 3.
    Any ideas?
    Thanks in advance.
    Andy Halford
    P.S. A Follow up which might be significant:  The Default Web Site is not running and will not start (it was previously running before the Exchange installation) and when I try I get the message that Another Website may be using the same port however none
    of the others (Exchange Back End or WSUS Administration) are using ports 80 or 443 and I still get the error when they are both stopped.

    Could you post the list of sites:
    appcmd list site
    The ones listening on port 80:
    appcmd list site /bindings:http/*:80:
    And on port 443:
    appcmd list site /bindings:https/*:443:
    Step by Step Screencasts and Video Tutorials

  • Exchange 2013 Mail Receiving Issues

    Hi everybody,
    Yesterday I configured a new DC and Exchange on Hyper-V (Server 2012 and Exchange 2013)
    All functions and rolls are configured and installed but i am having issues receiving external e-mails.
    Almost all of the external mails are being deliverd a half hour to a hour after being sent.
    To start of on the first level.
    I got a Siemens Fiber modem with an external address connected to the WAN of my Draytek 2995 router.
    Alle the needed ports are forwarded to the Draytek (80,443,25,1723).
    The Draytek DHCP function is set to off.
    192.168.168.2  (DC) -> 80 (HTTP IIS)
    192.168.168.2 (DC) -> 1723 (RRAS)
    192.168.168.3 (Exchange) -> 25 (SMTP)
    192.168.168.3 (Exchange) -> 443 (SSL)
    My Draytek router is connected through LAN1 to a HP switch (unmanaged).
    The physical server has 3 NIC's, all of these are connected to the HP Switch
    I Disabled Hyper-V Queuing on the NIC's because this causes an issue with slow network connections.
    The network has been configured as following.
    I configured the Server 2012 R2 on the hardware(physical server) with only the Hyper-V roll.
    NIC1is setup for the physical server,
    IP Address: 192.168.168.1
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254 (Draytek address)
    DNS: 192.168.168.254 (Draytek address)
    The Server software firewall has been set to a private network through the local security policy.
    I have setup 2 VM's through the Hyper-V roll.
    The first VM is the Server 2012 R2 Domain controller.
    For this VM I created a virtual switch connected to my second NIC(2).
    I unchecked the box where my host can communicate with the NIC(2).
    The DC has been configured as following:
    Hostname: SERVER
    IP Address: 192.168.168.2
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254
    DNS: 127.0.0.1
    I can ping to all the adresses from this server (internal and external).
    The server has been promoted to domain controller with the following rolls.
    ActiveDirectory, Certificate Autohority, DHCP, DNS, RRAS, RDP.
    Alle these rolls have been set and working. (all have been tested)
    DHCP has all options configured (scope, router-192.168.168.254, dns-192.168.168.2)
    A DNS simple and recursive test work fine.
    I did no configuration on the DNS after the DC PROMO.
    So i created users in the AD.
    After that I created a second VM, this one is used for the Exchange.
    I setup a second virtual switch connected to NIC3 and installed Server 2012 R2 with the following config.
    Hostname: SERVER
    IP Address: 192.168.168.3
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254
    DNS: 192.168.168.2 (pointing to the DC)
    I joined this server to the domain, everything is working fine.
    Both servers have internet and network.
    Running portscans on 1723 and 80 all work like a charm.
    No its time to install Exchange.
    I ran all the prerequisits and PowerShell commands (IAcceptLicense. etc.)
    Installed de needed API and filters.
    Installed Frameworks 3.5 on both servers.
    And the Exchange installation was succesfull.
    CU3 is also installed.
    I configured the send connector, accepted domains etc.
    Created all needed certificates (self signed)
    Did a portscan on 433 and 25 and they work.
    All the hosting records are set mail.domain.nl etc. and MX records.
    I created inboxes for the users and was able to connect them to the users in the Active Directory on the DC without any problems.
    Connecting through the internet to OWA works perfect and i can login with users.
    Sending e-mail internally works perfect, the messages are being deliverd in an instant.
    Sending e-mail externally also works perfect, i receive mails in a few seconds on a person email address.
    But when i reply or send e-mail to my new Exchange it can take up to hours to receive the mails!
    I did online SMTP checks and e-mail checks, the all come out like it should.
    One message from MX TOOLBOX on the SMTP:
    SMTP Transaction Time
    8.408 seconds - Not good! on Transaction Time
    I have nog other receive connectors setup, just the standard connectors.
    So i got into the Exchange ECP and under "server" i setup the DNS to listen to 192.168.168.2 (DC).
    I've read that when this is set to all ip addresses it can cause mail delay, but no luck.
    I ran the best practices analyzer and get about 23 errors and 20 warnings.
    A lot of services are unhealt like the "ExchangeTransport).
    I have no idea what is causing the issues and read almost every forum.
    Does anyone have a clue what is going on?
    Did i miss something, is there a misconfiguration?
    Best regards,
    Tim

    The mailserver did not receive any e-mails in this timespan, it was not an issue with the connector to the user mailboxes.
    The internal e-mail also works flawless.
    The entire Exchange server just not received this mail in time.
    I sent an e-mail from my personal accout with the option in my outlook to receive a delivery-reply.
    I got the reply as soon as the mail was deliverd, this took about a half hour to a hour.
    After you asked me about the firewall, i got a hunch..
    It had to be on the incomming connection, so i checked every single firewall on the network and disabled them.
    Still the same problem...
    But there was still one ethernet device that could have a firewall, the internet modem!
    This ATM modem receives multiple external IP's from the ISP, so I figured there was no firewall on this device. (Just like all the cable modems that are deliverd in our area by Ziggo(ISP).
    But I was wrong, there was a firewall enabled on the modem!
    All the ports in the modem had been forwarded but somehow the modem-firewall filtered the traffic,
    creating the issue on the incomming e-mail.
    I disabled the firewall and all the external e-mails are being received in an instant!
    Re-enabled all the software firewalls on the servers and re-enabled the malware filter through powershell, after these steps I did another test, and everything still works like a charm!
    Many thanks for your help Kjartan!

Maybe you are looking for