Add Mailbox Role to my First Exchange Server CAS Role

Hello I made a mistake I didn't check the Mailbox Role during the installation so I just installed the 1st Exchange Server 2013 SP1 into my organization with the CAS Server Role… can I add the Mailbox Server Role after doing this? Or do I have to decommission
this server to start a new installation within a Multi role Server (Mailbox/CAS)???? 
Thanks for the Help

https://technet.microsoft.com/en-us/library/bb124778(v=exchg.150).aspx
After you install any server roles on a computer running Exchange 2013, you can't use the Exchange 2013 Setup wizard to add any additional server roles to this computer. If you want to add more server roles to a computer, you must either use Add or Remove
Programs from Control Panel or use Setup.exe from a Command Prompt window.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • TCP packet out of state: First packet isn't SYN & Outlook is trying to retrieve data from the Microsoft Exchange Server [CAS-ARray]

    We are transitioning from Exchange 2003 to Exchange 2010.  We found Outlook online mode (non-cached mode) have many warning "Outlook is trying to retrieve data from the Microsoft Exchange Server [CAS-ARray]", usually happen when users tried to open
    address book but sometimes even normal operation like click the Send button.  The problem does not affect OWA and extremely rare when Outlook is running in cached mode.  Check the firewall logs, we notice a lot of "TCP Packet Out of State" drops.
    We have a lot from the CAS/HT to DC/GC on TCP_3268 and LDAP.  And the errors are "TCP packet out of state: First packet isn't SYN" with tcp_flags FIN-ACK, PUSH-ACK.
    We also have a lot from CAS/HT to the Outlook Clients on the static RPC port (TCP_59933).   And the errors are "TCP packet out of state: First packet isn't SYN" with tcp_flags FIN-ACK, PUSH-ACK and RST-ACK, ACK.
    This happens even on Outlook 2010 which I though it has TCP Keep Alive implmented to keep the session active within 1 hour. 
    Can somebody tell me if these out-of-state are the cause of our problem?  And how to fix it?
    THANK 1,000,000

    Hello AndyHWC,
    I did some consulting with our CAS team and received the following feedback to your post:
    It is difficult to determine what is causing resets without seeing the captures first hand however, the concern is that you are seeing dropped packets on the firewall logs.  Where is this firewall located?
    Based on the description "Check the firewall logs, we notice a lot of "TCP Packet Out of State" drops." and "We have a lot from the CAS/HT to DC/GC on TCP_3268 and
    LDAP." indicates to me that the firewall is between CAS and GC.  This not supported under any circumstances and would explain the issue they are seeing with clients trying to "retrieve data from the GC".
    If there is not a firewall between the GC and CAS then a Microsoft support engineer would need to have concurrent Netmon Captures from client, CAS, GC during the
    issue to analyze.  If only one GC exists consider adding another GC to handle the client requests and for fault tolerance.
    Also verify that all NIC card drivers are updated to the latest driver version
    More information about firewalls with Exchange 2007/2010
    http://msexchangeteam.com/archive/2009/10/21/452929.aspx
    http://technet.microsoft.com/en-us/library/bb232184(EXCHG.80).aspx
    You can install the Client Access server role on an Exchange 2007 computer that is running any other server roles except for the Edge Transport server role. You
    cannot install the Client Access server role on a computer that is installed in a cluster. Installation of a Client Access server in a perimeter network is not supported.
    http://technet.microsoft.com/en-us/library/dd577077(EXCHG.80).aspx
    “The Installation of a Client Access Server in a Perimeter Network Is Not Supported
    Issue You may want to install an Exchange 2007 Client Access server in a perimeter network. However, this type of installation is not supported in Exchange
    2007.
    Cause The Exchange 2007 Client Access server role is not supported in any configuration in which a firewall is located between the Client Access server
    and a Mailbox server or a domain controller. This includes firewall devices, firewall programs, or any program or device that is designed to restrict traffic between two network locations.
    For correct operation, Client Access servers require typical domain connectivity to domain controllers and global catalog servers. Because any devices
    or programs that restrict or reduce access to domain controllers or global catalog servers may affect the correct operation of the Client Access server, we do not support this type of configuration.
    Resolution To resolve this issue, move the Client Access servers to the internal network. For more information about the ports that Exchange 2007 uses
    for various services, see Data Path Security Reference.”
    Thanks,
    Kevin Ca - MSFT
    Kevin Ca - MSFT

  • How can I remove the first exchange server 2010 without any problems in DC

    Hi,
    our actually exchange is running on windows server 2008R2 with exchange 2010. I already install & configured a second Exchange 2010 server in the same domain. I also moved every mailbox to the new server. Now I have to deactivate the first server and
    I don't know, if I have to do something or can I deactivate the "old" server without any issues.
    If I can deactivate it, how can I do this? Is it enough to uninstall exchange 2010 on the server and after that I uninstall the windows server? Did I have to change something before?
    Thanks,
    Mesut Uygun
    btw. sorry for my bad english

    Hi MesutU,
    When you remove first Exchange Server 2010 in your organization, please confirm finish following steps:
    1. Move all mailboxes (including discovery and arbitration) to another server
    2. Move all Public Folder replicas
    3. Move OAB generation server
    4. Update SMTP flow from internet
    5. Update OWA/IMAP/POP/OA access from internet.
    6. Update any routing group connectors if 2003 is present
    7. Turn the old server offline for some days to check whether the new server works well.
    More information about How to Remove the First Exchange 2007 Server in a Coexistence Scenario (even if the version of Exchange server is different), for your conference:
    http://technet.microsoft.com/en-us/library/bb310767(v=exchg.80).aspx
    Best Regards,
    Allen Wang

  • Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

    Hello Team
    is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing  and deleting the mailbox database copies in exchange 2010
    normaly procedure is
    Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
    is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

    From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another.  Your note
    about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
    add a database copy on that third server?  Once it is fully seeded, you can remove the current passive copy.  This way, you never lose your redundancy.
    Yes i can add the third and fourth  serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
    and also currently my lab setup is  two member dag (with a server hosting your active database,
    and a second hosting the passive copy) in the same site named SITE A
    and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
    i want the  mailbox database copies from the mailbox server  database  in SITE A  to
    Mailbox server database in  SITE B as  passive copy
    That is why i want to move the mailbox database without deleting / removing it manually
    Hope you understand my situation!

  • How to uninstall first exchange 2013 server

    I have an existing exchange 2010 SP3 organization.  I am planning to install Exchange 2013 RTM on a production server
    to try it out.
    Can I easily uninstall the exchange 2013 completely after I am finished ? Is it just a matter of control panel/ add remove programs?
    Anand_N

    Hi Anand,
    Before you remove the first Exchange Server computer in the site, I would like to clarify the following thing:
    If there are any users or public folders (non-site) homed on this Exchange Server computer, you must move the mailboxes to another server in the site, and you must replicate any public folders to other servers in the site, to ensure that you do not lose
    data.
    Hope it helps.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

    Hi Guys,
    I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
    3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
    1 Exchange server MBX role For journlaing Exchange 2010
    1 CAS for internet owa access Exchange 2010
    Now i will be  installing exchange 2013 CAS on 2 box and MBX on 3 box 
    will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
    will keep the Journaling server as it is will not be decomming it as of now.
    My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
    to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
    Please suggest on the same.
    BR/Deepak

    Hi TheLearner,
    Thank you for your question.
    Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010  could communicate
    with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Exchange server Recovery Mailbox

    Hi Guys,
    I would like to ask if there's a log or any information that can check on the exchange server 2003 and exchange server 2007 if there's a restore mailbox occur on a particular exchange server 2003/2007? Is this can be audit? Let say for example how would I know if the admin guy perform any restore mailbox in a month? is there any log or auditing we can set so that we can track it?
    Thanks!

    Hi,
    You could search your event log whose source is “NTbackup” and check the restore data. Per my knowledge, there is no audit option for this operation.
    Thanks,
    Elvis

  • Cannot send email from Powershell on Mailbox Role

    Hi,
    I am trying to send an email from Powershell on Mailbox role of Exchange server. I have installed Symantec Mail Security on Mailbox Role.
    When I try to send email using Powershell, I got the following error.
    PS C:\a> Send-MailMessage -to [email protected] -Subject "Alert Closed.. Service is restarted on Computer" -from
    [email protected] -Body "The service was found stopped on Computer it was started automatically and it is now running normally." -bodyasHTML -priority High -SmtpServer smtp.domain.com
    Send-MailMessage : Service not available, closing transmission channel. The server response was: 4.3.2 Service not active
    At line:1 char:1
    + Send-MailMessage -to [email protected] -Subject "Alert Closed.. Service is ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (System.Net.Mail.SmtpClient:SmtpClient) [Send-MailMessage], SmtpException
        + FullyQualifiedErrorId : SmtpException,Microsoft.PowerShell.Commands.SendMailMessage
    This command is working fine on every server except exchange server (CAS, Mailbox). Firewall is off on the servers.
    Any help will be highly appreciated.
    Regards,
    Anees

    Hi,
    Please check the similar thread .
    http://social.technet.microsoft.com/Forums/exchange/en-US/ef699832-8da9-4709-9a50-c6223b13bd95/sendmailmessage-returns-the-server-response-was-432-service-not-available?forum=exchangesvrsecuremessaginglegacy
    smtp server (smtp.domain.com) is rejecting the connection from the
     Mailbox role of Exchange server.
    So please allow the mailbox server ip address on the smtp server's (i.e. smtp.domain.com)
    receive connector to get it done 
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • OWA setting for additional exchange server 2010

    Hi,
    I have exchange 2010 owa setup with public ip address for activesync, owa etc. I just installed a second exchange 2010, How does OWA going to work for this second exchange? I would like it to use the same certificate and ip from the first exchange
    server. Just making first server as front end, IIS enabled and second server as just backend. Is it possible? Any advise will be greatly appreciated.
    e. John's mailbox is server1. He can login to OWA.  Mary is on server2. Can she login to the same OWA address as John?
    Many thanks,
    pwint

    As per your description you are not going to have these servers in CAS array. If that's the case you can follow the below steps
    Modify the following entries in SAN
    SAN1 - outside.domain.com ( keep it as it is and do not modify)
    SAN2 - servername1.domain.local
    SAN3 - servername2.domain.local
    SAN4  - server1name (NetBios Name)
    SAN5 - Server2name (netbios name)
    SAN4 - autodiscover.domain.com (assuming domain.com should match your email addresses)
    SAN5 - mobile.domain.com
    That's it you are done and you do not need to make any other changes apart from this.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Exchange Server Installation

    Good day Sir/ Mam
    Based on installing Exchange Server 2013 on Windows Server 2012. What are the prerequisites if one wants to install it on the member server?

    Hi Simtandile,
    It depends basically which role you are deploying.
    Considerting its the first Exchange Server in your environment, below are the generic requirements.
    The computer you want to use to prepare Active Directory for Exchange 2013 has specific prerequisites that must be met.
    Install the following software on the computer that will be used to prepare Active Directory:
    Microsoft .NET Framework 4.5
    The version of Windows Management Framework that corresponds to the version of Exchange 2013 you're installing.
    Exchange 2013 CU3  
    Windows Management Framework 3.0
    Exchange 2013 SP1 or later  
    Windows Management Framework 4.0
    Note:
    .NET Framework 4.5 and Windows Management Framework 3.0 are included with Windows Server 2012 and don't need to be installed separately.
    .NET Framework 4.5 and Windows Management Framework 4.0 are included with Windows Server 2012 R2 and don't need to be installed separately.
    NOTE:- WindowsServer2012R2 would require minimum ExchangeServer2013SP1 to work properly.
    Exchange 2013 prerequisites
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
    I would recommend you using the
    Exchange Server Deployment Assistant for deploying it.
    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.

  • Exchange server 2013 public ip

    hello,
         can  any be  help  me  on  "how to assign  public  IP to exchange server  to configure   webmail  access".. please
    Mohammed Altaf Ahmed

    Hi,
    Rich's suggestion is pretty helpful. Public IP address is required to represent an Exchange server on the Internet. The router or Firewall will translate the public IP address to the internal one and forward communications from the internet to the Exchange
    server.
    Here is a related article for your reference, please refer to the "IP Addressing" topic.
    Planning for Your First Exchange Server:
    http://www.msexchange.org/articles-tutorials/exchange-server-2003/planning-architecture/Planning-First-Exchange-Server.html
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

    I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
    I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
    backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
    failure. I have always felt nervous with SBS because it only runs on a single server.
    My plan is:
    Install Windows Server 2012 Standard on a new server machine
    Join that new server to the existing SBS domain and sync the users, etc.
    Install Exchange Server 2013 on the new 2012 Server
    Migrate the existing Exchange data and account info to the new server
    Demote the SBS Server and promote the new server to primary DC
    Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
    Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
    Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
    services)
    Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
    failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
    SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
    Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
    Thanks,
    Colin
    Colin

    Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
    Constraints/objectives:
    None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
    Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
    Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
    Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
    maintenance.
    Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
    want to keep all IT tasks as simple as possible.
    We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
    A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
    Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
    server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
    to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
    from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
    New Plan:
    Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
    Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
    Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
    Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
    Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
    (or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
    Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
    Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
    Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
    it there. In any case, do NOT install Exchange directly on either DC.
    Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
    the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
    I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
    Thanks so much for all your help,
    Colin

  • 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.

  • Problems installing Mailbox role on Exchange Server 2010 SP3

    I am in the process of installing Exchange Server 2010 SP3 on a Windows Server 2012 server in order to migrate our existing Exchange 2003 server. Everything went well with the installation process until I went to add the Mailbox server role, which is giving
    me the following error (from the log file):
    [05/03/2013 21:58:09.0090] [1] Executing: 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
    [05/03/2013 21:58:09.0105] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'TAM-FS2.tacomaartmuseum.org', Preferred Global Catalog: 'TAM-FS2.tacomaartmuseum.org', Preferred Domain
    Controllers: '{ TAM-FS2.tacomaartmuseum.org }'
    [05/03/2013 21:58:09.0105] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [05/03/2013 21:58:09.0276] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" 
    [05/03/2013 21:58:09.0344] [2] Process standard output: 
    [05/03/2013 21:58:09.0344] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [05/03/2013 21:58:09.0347] [2] [ERROR] Unexpected Error
    [05/03/2013 21:58:09.0347] [2] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [2] Ending processing Start-SetupProcess
    [05/03/2013 21:58:09.0350] [1] The following 1 error(s) occurred during task execution:
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR] The following error was generated when "$error.Clear(); 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [05/03/2013 21:58:09.0351] [1] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
    [05/03/2013 21:58:09.0351] [1] Setup is stopping now because of one or more critical errors.
    [05/03/2013 21:58:09.0351] [1] Finished executing component tasks.
    [05/03/2013 21:58:09.0393] [1] Ending processing Install-MailboxRole
    I've searched all over but can't seem to find any reference to "exit code 87" - does anyone have any ideas?
    Thanks,
    Matt

    Error 87 -with these details below - and a fix. The situation that got me here by the way was an incomplete install that was uninstalled, then installed again.
    [02/24/2014 06:49:06.0967] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'xxxxxxxxxxxxxxx', Preferred Global Catalog: 'xxxxxxxxxxxxxxxxxxxxxxxx', Preferred Domain Controllers:
    '{ xxxxxxxxxxxxxxxxxxxxxxx }'
    [02/24/2014 06:49:06.0967] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [02/24/2014 06:49:06.0967] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
    [02/24/2014 06:49:07.0592] [2] Process standard output:
    [02/24/2014 06:49:07.0592] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [02/24/2014 06:49:07.0592] [2] [ERROR] Unexpected Error
    [02/24/2014 06:49:07.0592] [2] [ERROR] Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [2] Ending processing Start-SetupProcess
    [02/24/2014 06:49:07.0592] [1] The following 1 error(s) occurred during task execution:
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0608] [1] [ERROR] The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [02/24/2014 06:49:07.0608] [1] [ERROR] Process execution failed with exit code 87.
    I found I could fix this by removing the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Microsoft-Exchange-Troubleshooters/Operational
    and everything underneath it.
    My guess is that wevtutil didn't like adding an event log where it already existed but was slightly different in setup (no idea how, exactly).
    After 24 hours I'll try post again - giving things time to make sure they are actually working.

  • Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

    Dear all
    During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
    wa' on 'MONAMBX2'.".
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
    und on 'MonaDc1.mona.local'.".
    Any advice please !!

    I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive.  Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
    error messages saying the database does not exist.  It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting.  To get around it, I deleted the database and created a new one on the drive
    where we wanted it.
    I discovered this when I was configuring the Antispam settings.  I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server.  The shell on 2013 was making changes to 2007.
    I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens.  Or maybe my issues will be fixed if I just remove the Exchange 2007 server?  I'm not ready to do that yet because I can't configure the spam filtering
    on 2013 yet with its shell not being able to make the changes that we need.
    I don't know if your environment is in coexistence mode like mine.
    Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server.  Does this happen after the 2007 server is removed?

Maybe you are looking for