Exchange server 2013 proxy authentication

Hi All,
I wanted to know what is the recommended proxy authentication for exchange server 2013. 
I have observed the following from different proxy authentications:
1. Negotiate: By default, the proxy authentication is set to negotiate and uses anonymous as Log on network security(un-encrypted MAPI)
2. Basic: It always prompts for the user credentials and uses encrypted MAPI.
3. NTLM: Use negotiate at MAPI level by default
Please provide me some information on different authentication mechanisms and the one which is recommended to use. 
Thanks,
Srinivas.

Hi Srinivas,
According to my knowledge, there are my views below:
Basic authentication: If you select this authentication type, Outlook will prompt for username and password
while attempting a connection with Exchange.
NTLM authentication: If you select this authentication type, exchange does not prompt users for a user
name and password. The current Windows user information on the client computer is supplied by the browser through a cryptographic exchange involving hashing with the Web server. If the authentication exchange initially fails to identify the user, the browser
will prompt the user for a Windows user account user name and password. So, when Outlook is trying to connect to Exchange and if the machine is domain joined, there isn’t a need to provide password.
Negotiate authentication: Enabled by default in Exchange 2013. This is a combination of Windows integrated
authentication and Kerberos authentication. If we employ negotiate authentication, exchange will authenticate the client using NTLM authentication type and if unable to verify authenticity, will challenge the client to authenticate using a username and password.
And you could set the authentication type like this:
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
The command below for your reference:
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalHostname "internalServer.contoso.com" -InternalClientAuthenticationMethod Ntlm -InternalClientsRequireSsl $true -ExternalHostname "externalServer.company.com" -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $true -IISAuthenticationMethods Negotiate,NTLM,Basic
If you have any further questions, please let me know.
Best regards,
Eric

Similar Messages

  • Exchange Server 2013 with RADIUS authentication

    Hello,
    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS server which is not on my Windows Server 2012. I have to use their RADIUS server, the RADIUS server from the
    company where I am doing my internship.
    I already created a NPS and added the RADIUS Client + Remote RADIUS Server Groups. I created a Connection Request Policies with the condition:
    User Name *
    I forwarded the Connection Request to the Remote RADIUS server that I created in Remote RADIUS Server Groups and then I registered the NPS in th AD. But it's still not working. 
    Maybe I did something wrong or I misunderstood something or does this even work with Exchange Server 2013? To authenticate mailbox users with a RADIUS server before they can login into their mailbox and use their mailbox?
    Thanks in advance.

    On Wed, 26 Mar 2014 09:21:25 +0000, DavidIntern wrote:
    I already put the NPS as a RADIUS proxy. I followed this check list http://technet.microsoft.com/en-us/library/cc772591.aspx
    But the things is I want to make it work with our freeRADIUS2 that we have in place here. Without changing our freeRADIUS2. But I found out this is not possible since we are not using any Active Directory with it. Since I am still a newbie in this environment,
    I am not sure if it is possible.
    But my main question was if it was possible to use freeRADIUS2 and that my NPS would be the RADIUS proxy. So my question is answered, if I understood right, without making any changes to our freeRADIUS2 this is not going to be possible right? Because we have
    no AD?
    Our setup is freeRADIUS2 + MySQL database where all the users are stored.
    As I mentioned in my previous response this really isn't the right place
    for this question but why would you want to try to use a MySQL store for
    authenticating against Exchange in the first place when you've already got
    an authentication store (Active Directory) that is tightly integrated with
    Exchange?
    I still really don't understand what it is you're trying to accomplish nor
    why you're trying to use such a complicated, convoluted method to
    authenticate Exchange users.
    Paul Adare - FIM CM MVP
    Any sufficiently advanced bug is indistinguishable from a feature.

  • Exchange Server 2013 to 2010 mailbox proxy is not working

    I have exchange server 2013 and exchange server 2010 in co-exist. I have 3 cas server and 3 mbx server 2013 on windows server 2012 standard, 2 hub/cas server and 2 mbx server 2010 on windows server 2008 r2. when I try to access owa of exchange server 2010
    mailbox using exchange 2013 url, I am getting the error as "something went wrong. sorry, we can't get that information right now, please try again later. If the problem continues please contact your helpdesk"
    Vishal C. Kalal | MCITP: Exchange 2010-2007 | Windows Server 2008

    Hi,
    To narrow down the cause, I recommend the following troubleshooting:
    Check if the issue happens on all users.
    Try to directly login OWA 2010  and check if it works well.
    Check the IIS log on CAS 2013 server and find the error related to OWA.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 and RADIUS server(freeRADIUS2)

    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange
    Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS
    server which is not on my Windows Server 2012. I have to use their RADIUS server ( freeRADIUS2 ), the RADIUS server from
    the company where I am doing my internship.
    I already did the checklist that is on http://technet.microsoft.com/en-us/library/cc772591.aspx. I configured the NPS as
    a RADIUS proxy, because that's what I need.
    So after doing everything that is on that checklist, my question is:
    Is it possible that the Exchange Server 2013 will use my NPS which is now configured as a NPS RADIUS proxy to authenticate my mailbox users that I have on my Exchange Server 2013?

    thanks for such a quick response.
    Just a small question about the link that you put. Does member server mean other server other than domain controller?
    Regards,
    Yes, Also the server on which you are installing Exchange should have exchange installed.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange Server 2013 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • Exchange Server 2013 Edge Transport Role

    Dear,
             I have a question regarding Exchange Server 2013 SP1 that, I have installed Edge Transport Server Role on separate box without Domain Joined. Obviously I installed Exchange CAS and Mailbox on Same box with
    Domain Joined in Corporate LAN.. But my edge is placed on DMZ and it is ready with all configuration, Mailbox Server Synchronization is also installed with Edge. Means all required configuration are properly configured and it is verified. But I want clients
    to OWA Access from Edge only. Because I want to restrict my internal network from the internet. So kindly provide me any possible ways to access OWA from Edge only ??. I have see some another methods like "Web Application Proxy instead of TMG because
    TMG is expired"..
    Kindly provide me possible ways or URL so I will configure it..
    Thanks.
     Fuzail (FM)

    Hi,
    Is there any further question on this thread?
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange Server 2013 - Sizing

    Can some please provide me Exchange server 2013 sizing for 180 Mailbox users with mailbox profile size 10 GB With 1 DAG with two mailbox servers.
    Please provide for Exchange Server in Virtual environment.
    I have already created a setup on Environment going through test mode.
    Existing Environment
    2 X CAS servers -  2 Core - 4 GB Memory - 500 GB Hard disk space
    2 X Mailbox Server - 2 Core -  12 GB Memory - 1.5 TB disk space
    Theses servers are build on VMWare hosted on ESX server
    Please provide your feedback for best practice and solution to support 180 Mailbox profile with Mailbox size limit 10 GB
    Thanks in adavance
    Benhur
    benhur007

    Hi Benhur,
    we have over one thousand mailboxes ( inc. room,shared,calendar and so on).We only have 2 servers With Mailbox and CAS role.No need to seperate those roles if you really dont have to.2013 CAs only Proxy/redirect requests and nothing is stored (other that
    daily performance log and iis log).C: drive for Exchange install i recomend 70gb on each server.
    When it comes to mailbox database,are you planning to use Public folders?In 2013 Public folders can be stored on seperate databases.
    Also it is not recomended to have Exchange and mailbox database on same physical disk,so you should seperate those out and expand over time without taking Down the server.
    In easy sample the server can look like this:
    C: Install Exchange  70GB
    D: Database files 1GB ( here you map multiple databases in different folders,so it look like D:\DB01,D:\DB02,D:\DB03 and so on.And each folder is an own 300 gb disk that you Mount into one of these folders at time.Path and name have to be identical on both
    servers when setting up DAG.)
    E: Log files 1GB ( here you map multiple databases in different folders,so it look like E:\LOG01,E:\LOG02,E:\LOG03 and so on.And each folder is its own 70 gb disk that you Mount into one of these folders at time.Path and name have to be identical on
    both servers when setting up DAG.)
    Approx 300GB each database and 70 gb each log(for each database) should be fine.
    10gb database pr user can cause performance issue if they are working online (Citrix or other apps),if cache locally it might take time if they are not inside worknetwork.
    Dont forget that you should also have your own replication network or it will consume bandwidth when you move over multiple users to different databases.
    Hope this helps!
    Please 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. Thank you! Off2work

  • Exchange Server 2013 on Srvr2012r2 fails on preinstall

    During the preinstall of the Exchange server 2013 on virtual Server 2012r2 the installation fails at the second step of the preinstall. I tried the wizard and it also fails station the user does not have the correct rights.
    This was probably caused by myself.  When I first installed the Exchange I did not install the client and mailbox items.  When I found out this was an error I uninstalled it and tried to reinstall.
    Bonnie Whalon

    hi Bwhalon.. your both the commands are incorrect..
    1. it misses a parameter required somwhere
    2. the role service which you have asked to install is incorrect..may be mistyped
    ok now you can use below two way ...
    1. Command...
    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
    take from http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx
    after this you can start the install
    2. Graphical install : check below links .. this is step by step procedure
    http://www.techieshelp.com/exchange-2013-step-by-step-configuration/                                
    Let me know if this helps...
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Writing client app to connect to Exchange Server 2013 and set OOF for users on vacation

    I am coding an C# app that should connect to Exchange Server 2013 on-premise (Servers Location is not in our Company). I`ve got an account (User and Pass) with readonly admin-rights for now and want to read and set OutOfOffice Objects for other users. I
    decide to use EWS Managed API over Autodiscovery but I am bit confuse how
    I tried to connect with "service.UseDefaultCredentials = true" and read contacts -> this code works:
    try
                ExchangeService _service
    = new ExchangeService(ExchangeVersion.Exchange2013_SP1);
                _service.Credentials
    = new WebCredentials("service.exchange",
    "1234", "domain");
                _service.TraceEnabled
    = true;
                _service.TraceFlags
    = TraceFlags.All; _service.UseDefaultCredentials
    = true;
                _service.AutodiscoverUrl("[email protected]",
    RedirectionUrlValidationCallback);
                foreach
    (Contact contact in _service.FindItems(WellKnownFolderName.Contacts,
    new ItemView(2)))
    var test = contact;
            catch
    (Exception exception)
                Console.WriteLine(exception);
    After that I tried the same with _service.UseDefaultCredentials = false; got error -> "The Autodiscover service couldn't be located." I am not shure if this "direct log on" is the right way, On msdn I've read about "delegate access"
    and "Impersonation" (NTLM and Basic Authentication) I'am a bit confused. Can anybody help me?

    hi,
    when you set a credential, you don't have to set the UseDefaultCredentials property (it is already updated).
    For autodiscover, you should try to set the property EnableScpLookup to True if you are in the Exchange domain or it is known by the current domain.
    Autodiscover uses a domain query (through Active Directory) and/or a dns query (this requires a DNS register for autodiscover.domain.net) to determine the access to the autodiscover service URI.
    Regards,
    Désiré GOVIN Refresh IT Solutions

  • Trying to install Exchange Server 2013 and receive this error.

    Hello,
    I have a computer running Windows Server 2012 R2 Standard. I have completed all the prerequisites to install Exchange Server 2013. It all was going good until the install started. Then I received the below error. Does anyone have any suggestions? I am new
    to Exchange Server so would thank and appreciate any help I could get to resolve this issue.
    Thank You,
    Stan
    Error:
    The following error was generated when "$error.Clear(); 
    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
    " was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:16cd035a-6201-492f-b85f-1e28cc9f9ee0,CN=Deleted Objects,DC=MULTIAXCNC,DC=local on
    the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MULTIAXCNC,DC=local points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.
       at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Here is the error I am getting and the last setup log I can find. Any help how to get past the error would be helpful.
    Thank You,
    Stan
    Error
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRuleCryptographicException: Could not grant Network Service access to the certificate with thumbprint 845C42A131A8A73487400A91491182FB95B81612
    because a cryptographic exception was thrown. ---> System.Security.Cryptography.CryptographicException: Access is denied.
       at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)
       at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, String websiteName, Boolean requireSsl, ITopologyConfigurationSession dataSession, Server server,
    List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Setup Log Below
    # Default Install steps for ClientAccessRole.
    # Programmatically generated on 7/5/2014 10:58:24 PM.
    # Variable Declarations
    $RoleAllRoles = 'BridgeheadRole,GatewayRole,ClientAccessRole,MailboxRole,UnifiedMessagingRole,FrontendTransportRole,AdminToolsRole,MonitoringRole,CentralAdminRole,CentralAdminDatabaseRole,CentralAdminFrontEndRole,LanguagePacksRole,CafeRole,FfoWebServiceRole,OSPRole'
    $RoleBinPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Bin'
    $RoleCustomerFeedbackEnabled = $True
    $RoleDatacenterPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Datacenter'
    $RoleDatacenterServiceEndpointABCHContactService = '<ServiceEndpoint><Url>http://pvt-contacts.msn.com/abservice/abservice.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointDomainPartnerManageDelegation = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointDomainPartnerManageDelegation2 = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation2.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveFederationMetadata = '<ServiceEndpoint><Url>https://nexus.passport.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveGetUserRealm = '<ServiceEndpoint><Url>https://login.live.com/GetUserRealm.srf</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveServiceLogin2 = '<ServiceEndpoint><Url>https://login.live.com/RST2.srf</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointMsoFederationMetadata = '<ServiceEndpoint><Url>https://nexus.microsoftonline-p.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
    $RoleDomainController = 'MULTIAX2012.MULTIAXCNC.local'
    $RoleExternalCASServerDomain = $null
    $RoleFqdnOrName = 'MULTIAX2012.MULTIAXCNC.local'
    $RoleInstallationMode = 'Install'
    $RoleInstallPath = 'C:\Program Files\Microsoft\Exchange Server\V15\'
    $RoleInvocationID = '20140705-2258240578829153548'
    $RoleIsAdminToolsRoleInstalled = $True
    $RoleIsBridgeheadRoleInstalled = $True
    $RoleIsDatacenter = $False
    $RoleIsDatacenterDedicated = $False
    $RoleIsFfo = $False
    $RoleIsPartnerHosted = $False
    $RoleLanguagePacksPath = 'C:\Exchange\'
    $RoleLoggedOnUser = 'MULTIAXCNC\Administrator'
    $RoleLoggingPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Logging'
    $RoleNetBIOSName = 'MULTIAX2012'
    $RoleNoSelfSignedCertificates = $False
    $RolePreviousVersion = $null
    $RoleProductPlatform = 'amd64'
    $RoleRoleName = 'ClientAccessRole'
    $RoleRoles = 'BridgeheadRole,AdminToolsRole'
    $RoleSetupLoggingPath = 'C:\ExchangeSetupLogs'
    $RoleTargetVersion = '15.00.0913.022'
    $RoleUpdatesDir = $null
    # Component tasks
    # Tasks for 'All Roles Common First' component
    # [ID = AllRolesCommonFirst___3e69ba31a53e4c29a2d6bffcf78cc614, Wt = 5, isFatal = True] "Starting the WMI service."
    7/5/2014 10:58:24 PM:
              if (Get-Service winmgmt* | ?{ $_.Name -ieq "winmgmt" })
                Set-Service winmgmt -StartupType Automatic
                Start-SetupService -ServiceName winmgmt
    # [ID = AllRolesCommonFirst___56139ce4432346ecb7936afae4c3a9cc, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:24 PM:
              & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoleName.Replace('Role','')
    # [ID = AllRolesCommonFirst___edc23bc11a4e4119a6a4ee802ff1ea49, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:24 PM:
              if ($RoleRoles)
                & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoles.Replace('Role','').Split(',')
    # [ID = AllRolesCommonFirst___62f13a063b2846a5ab20765bb7a3fc51, Wt = 5, isFatal = True] "Starting the Remote Registry service."
    7/5/2014 10:58:25 PM:Start-SetupService -ServiceName RemoteRegistry
    # [ID = AllRolesCommonFirst___00573a17b6e34c26842a6646830d57fa, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:25 PM:Set-LocalPermissions
    # [ID = AllRolesCommonFirst___77668249568048d3812fb7cdba08c58b, Wt = 1, isFatal = False] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
              $mofFilePath =  ($RoleInstallPath + "bin\Exchange.MOF");
              $mflFilePath =  ($RoleInstallPath + "bin\en\Exchange.MFL");
              compile-moffile -MofFilePath:$mofFilePath;
              compile-moffile -MofFilePath:$mflFilePath;
    # [ID = AllRolesCommonFirst___f557448f44964e5eaa5dba792a3c4f09, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCByPortRule)
    # [ID = AllRolesCommonFirst___84a0f0e2c2f44db2b537e9696c26fc3e, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCEPMapByPortRule)
    # Tasks for 'ClientAccess Permissions Configuration' component
    # [ID = ClientAccessLocalPermissionsComponent___6246589bb8494a3580c22c26e18451d1, Wt = 1, isFatal = True] "Setting folder or registry permissions for the Mailbox role: Client Access service. "
    7/5/2014 10:59:35 PM:Set-LocalPermissions -Feature:"ClientAccess"
    # Tasks for 'Exchange 2003 Registry Configuration' component
    # [ID = LegacyRegistryMarkersComponent___7d6dadc1069b42ac93eadd1143c04a1a, Wt = 1, isFatal = True] "Installing/Removing registry values used by Exchange 2003 components"
    7/5/2014 11:00:01 PM:set-ExsetdataRegistryMarkers
    # Tasks for 'Client Access Perf Counters' component
    # [ID = ClientAccessPerfCountersComponent___deb99c54869843b68426390615283ab7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:01 PM:new-PerfCounters -DefinitionFileName OwaInstallSingleCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ca78563ec1f1468982d1a2e59c6001bd, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:15 PM:new-PerfCounters -DefinitionFileName EcpPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e69a559428fb42029ca3261e795b216d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:21 PM:new-PerfCounters -DefinitionFileName RwsPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___c335490f948a4b16b5e2d2ce5f1eb9e7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:26 PM:new-PerfCounters -DefinitionFileName InfoworkerAvailabilityPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___5af856aa00ae485ca206c5cdd13e9128, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:31 PM:new-PerfCounters -DefinitionFileName InfoworkerSharingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___86121d1b951e43fb934f1f1d573362eb, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:35 PM:new-PerfCounters -DefinitionFileName ThrottlingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ea5896b92c494834b1a93c4620fcaef4, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:42 PM:new-PerfCounters -DefinitionFileName MiddleTierStoragePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___dab6f03bdf5141efb7b017c3009fb9e6, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:48 PM:new-PerfCounters -DefinitionFileName ActiveManagerClientPerfmon.xml
    # [ID = ClientAccessPerfCountersComponent___5471455db0ef4610bf68fe7ad9417e19, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:53 PM:new-PerfCounters -DefinitionFileName RmsPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___81ad52cb2950483196b52371b4d992c8, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:58 PM:new-PerfCounters -DefinitionFileName InfoworkerMailTipsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___072bf6737f1c42a0a8847ce35cf8a0c7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:03 PM:new-PerfCounters -DefinitionFileName InfoworkerUserPhotosPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___50b64611f7444bb49d50e00c206d2c13, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:08 PM:new-PerfCounters -DefinitionFileName AirSyncCounters.xml
    # [ID = ClientAccessPerfCountersComponent___f2620ff8c3754396a8ea7d77257e2895, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:14 PM:new-PerfCounters -DefinitionFileName ClientAccessRulesPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___4ef0f16c017840a583ace9f062300207, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:19 PM:new-PerfCounters -DefinitionFileName Imap4Counters.xml
    # [ID = ClientAccessPerfCountersComponent___135fb06dadd9403a83ceebb290638efe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:24 PM:new-PerfCounters -DefinitionFileName Pop3Counters.xml
    # [ID = ClientAccessPerfCountersComponent___312e8d44e92b45e0809f9d3d5dc2cfc0, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:29 PM:new-PerfCounters -DefinitionFileName WsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___3c333497697041cb854190ec31c17b18, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:48 PM:new-PerfCounters -DefinitionFileName UMClientAccessCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ba015b97cc0b4beba7b25b6cb297fcac, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:54 PM:new-PerfCounters -DefinitionFileName AutodiscoverPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___3daffea50d5a4318aab4aa737e508146, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:59 PM:new-PerfCounters -DefinitionFileName OAuthCounters.xml
    # [ID = ClientAccessPerfCountersComponent___c71073d7f1ab4c119af83efb513b3a9d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:04 PM:new-PerfCounters -DefinitionFileName InfoWorkerMessageTrackingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___abdaf0bf21f4473b88819ee85cada219, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:10 PM:new-PerfCounters -DefinitionFileName RpcClientAccessPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___9f160f3e42984edfa25b62424ebc05b5, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName RpcClientAccessServerPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e55cb179521a4dacbeaa588c6948cf14, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName AddressBookServicePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___064a7856cf7c4b0399c85cf4f3bc2f1c, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:20 PM:new-PerfCounters -DefinitionFileName RpcEntryPointsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___42325F33-A961-41FE-B6B5-5CFB3AA9820A, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:22 PM:new-PerfCounters -DefinitionFileName MapiHttpEmsmdbPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___4C04D747-3B5C-400A-980F-45504324EF42, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:28 PM:new-PerfCounters -DefinitionFileName MapiHttpNspiPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___5ab36fffacd04975bb1bc681a214bf71, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:33 PM:new-PerfCounters -DefinitionFileName ThrottlingServiceClientPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___6ca23933132d44b39d6586cb3f9f8f21, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:39 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___6602c41b35254405bed412fab7d527fe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:44 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerMdbPerformanceCounters.xml -FileMappingSize 2097152
    # [ID = ClientAccessPerfCountersComponent___74e45a45ea8c449092a10929ae24ba4b, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:50 PM:new-PerfCounters -DefinitionFileName MlbPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___a3bcb686add64cf296c8616d387d0323, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:55 PM:new-PerfCounters -DefinitionFileName MlbMultiInstancePerformanceCounters.xml -FileMappingSize 2097152
    # [ID = ClientAccessPerfCountersComponent___c00c15c4ef6f479b9f5deb852d8eda7d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:01 PM:new-PerfCounters -DefinitionFileName ProvisioningPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___fe1a2a7c828f4b57abc2e50dc09baddf, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:06 PM:new-PerfCounters -DefinitionFileName GalsyncPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___35D14CB8B01949818832943A391D77B9, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName BackSyncPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e69599d235234effb6d2740f3c52f7e1, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName AdminAuditPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___09bd11b57f6445e890391a507262cf32, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName InfoworkerMultiMailboxSearchPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___324687361E1C473A834C22A66104679f, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName ProvisioningCachePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___98C36FFEC7944065889DB24067CFD3EE, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:21 PM:new-PerfCounters -DefinitionFileName OABRequestHandlerPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___1F5A7B68C95B42568E02FAA15A05EF17, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:26 PM:new-PerfCounters -DefinitionFileName DlpPolicyTipsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___995DEA7A1AC5467C89939F5F8CE5F2AF, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:31 PM:new-PerfCounters -DefinitionFileName ConfigurationCachePerformanceCounters.xml
    # Tasks for 'Client Access Configuration' component
    # [ID = ClientAccessComponent___d5119205104847bcb275cb63b65160b6, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:03:35 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Owa\Bin\Microsoft.Exchange.Clients.Owa.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___954344d74d8849e9ae7123b91761ed9d, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:03:57 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Sync\Bin\Microsoft.Exchange.AirSyncHandler.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___6632d6c1d5054563942db4f180976238, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:04:01 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\AutoDiscover\Bin\Microsoft.Exchange.AutoDiscover.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___390b4ffddd484dcb9edc01dd725e020a, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:04:07 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\exchweb\ews\bin\Microsoft.Exchange.Services.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___178a10624c88445093855c4ede7e9b9c, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:42 PM:
              . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
              Set-NtlmLoopbackCheck $false
    # [ID = ClientAccessComponent___14a6761e144e428b93c62249acc814fe, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:42 PM:install-ClientAccessIisWebServiceExtensions
    # [ID = ClientAccessComponent___28fdfe8bec984e809cdeef6d4d59bf4e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:43 PM:
            if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})
                restart-service MSExchangeServiceHost
    # [ID = ClientAccessComponent___7816256880dc4be0baf5b005b2af8cd3, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
            if (get-service MSExchangeProtectedServiceHost* | where {$_.name -eq "MSExchangeProtectedServiceHost"})
                restart-service MSExchangeProtectedServiceHost
    # [ID = ClientAccessComponent___e95499b43bd1484dbc03098fb1b4e592, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:set-ExchangeServerRole -Identity $RoleFqdnOrName -IsClientAccessServer:$true -DomainController $RoleDomainController
    # [ID = ClientAccessComponent___f4c48e196e374cf3af269b1cea0602c8, Wt = 1, isFatal = True] "Installing/Removing the WebReady Document Viewing service."
    7/5/2014 11:04:45 PM:Install-TranscodingServiceEx
    # [ID = ClientAccessComponent___f50fd59d231140eb9b2405bbed2b93d4, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if ($RoleIsDatacenter -eq $false)
                uninstall-FBAService
    # [ID = ClientAccessComponent___9fad9d51b3ec4ecdad567ab58e470be7, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if ($RoleIsDatacenter -eq $false)
                stop-setupservice -ServiceName MSExchangeFBA
    # [ID = ClientAccessComponent___1c7a7da2ab9d41bb8db75522ad28b9db, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              $tpath = "$env:SystemRoot\system32\inetsrv\microsoft.web.administration.dll";
              add-type -Path $tpath;
              $sm = new-object Microsoft.Web.Administration.ServerManager;
              if ($sm.Sites["Exchange Back End"] -eq $null)
                $ppath = "$env:SystemDrive\inetpub\wwwroot";
                $s = $sm.Sites.Add("Exchange Back End","http", "*:81:", $ppath);
                $s.ServerAutoStart = $true;
                $sb =$s.Bindings;
                $b = $sb.Add("*:444:","https");
                $sm.CommitChanges();
    # [ID = ClientAccessComponent___a5f211d837784aea931b9ba55c39996d, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              Get-ExchangeServer $RoleFqdnOrName | Add-AdPermission -User "S-1-5-20" -ExtendedRights "Exchange Web Services Token Serialization";
    # [ID = ClientAccessComponent__SetInstallPathInMrsAppConfig, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              Set-InstallPathInAppConfig -ConfigFileRelativePath "Bin" -ConfigFileName "MsExchangeMailboxReplication.exe.config"
    # [ID = ClientAccessComponent___765cc444ba07411aa81d58397b0401fd, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if (!(get-service MSExchangeMailboxReplication* | where {$_.name -eq "MSExchangeMailboxReplication"}))
                install-MailboxReplicationService
    # [ID = ClientAccessComponent___151b722e327b42a69411df32afdbbcbb, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:46 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationFirewallRule)
    # [ID = ClientAccessComponent___7d69bb94f08245589e49eb569c6d5f4f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:46 PM:
              if (!(get-service MSExchangeMigrationWorkflow* | where {$_.name -eq "MSExchangeMigrationWorkflow"}))
                install-MigrationWorkflowService
    # [ID = ClientAccessComponent___95f051d9dc5941c4b6014181b6e5ce93, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeABRPCFirewallRule)
    # [ID = ClientAccessComponent___959c2d6566984da6b8e0e3235c1c11c2, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangePOPBeByPortRule)
    # [ID = ClientAccessComponent___29864e7462374fdb84fc75eec931d8e4, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeIMAP4BeFirewallRule)
    # [ID = ClientAccessComponent___052e1b794d0641ada4d6d417061af2a8, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeOWAByPortRule)
    # [ID = ClientAccessComponent___975efd8911fd41cca8b17462535d710e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationByPort)
    # [ID = ClientAccessComponent___023036e43f004bda9f4f4e0b1e0d233f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              Install-ResourceHealthActiveFlags
    # [ID = ClientAccessComponent___3a51c2876e2c4643bc892d2665754228, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\PushNotifications\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___FCC16AC1FFED43518F8292DBE770C621, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\emsmdb\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___E9C71786D02E40CBB1403E2E1A4B0758, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\nspi\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___abcab6b91ac844848c58b4ee66fcbea6, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
                ."$RoleInstallPath\Scripts\Install-OutlookServiceVirtualDirectory.ps1";
    # [ID = ClientAccessComponent___9D94915F-B12D-4579-93EE-36B6DF42CF4A, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
              $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
              $MapiMailboxClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\emsmdb");
              $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiMailboxAppPool_CLRConfig.config");
              Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiMailboxAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
    /processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiMailboxClientAccessPath`" /applicationPool:MSExchangeMapiMailboxAppPool /path:`"/mapi/emsmdb`""
    -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
    # [ID = ClientAccessComponent___B551AAAC-0F36-428B-B1BB-3B9AFDC9EAEF, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:50 PM:
              $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
              $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
              $MapiAddressBookClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\nspi");
              $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiAddressBookAppPool_CLRConfig.config");
              Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiAddressBookAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
    /processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiAddressBookClientAccessPath`" /applicationPool:MSExchangeMapiAddressBookAppPool /path:`"/mapi/nspi`""
    -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
    # [ID = ClientAccessComponent___178FD1A31B5949A0B4A819E39311B1FD, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:52 PM:
                $ExchangeLabsRegKey = 'HKLM:\SOFTWARE\Microsoft\ExchangeLabs'
                $E4eCertificateDistinguishedNameRegValueName = 'E4eCertificateDistinguishedName'
                if ($RoleDatacenterE4eCertificateDistinguishedName -ne $null)
                    New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eCertificateDistinguishedNameRegValueName -Value $RoleDatacenterE4eCertificateDistinguishedName -Force
                    Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. value: $RoleDatacenterE4eCertificateDistinguishedName"
                else
                    Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. Value is null."
                $E4eServiceUrlRegValueName = 'E4eServiceUrl'
                if ($RoleDatacenterE4eServiceUrl -ne $null)
                    New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eServiceUrlRegValueName -Value $RoleDatacenterE4eServiceUrl -Force
                    Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. value: $RoleDatacenterE4eServiceUrl"
                else
                    Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. Value is null."
    # [ID = ClientAccessComponent___240c7e5d07f941cfbe69a692dc33a31a, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:52 PM:
              ."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
              CreateCustomHeadersNodeForBackend 'autodiscover'
              CreateCustomHeadersNodeForBackend 'ecp'
              CreateCustomHeadersNodeForBackend 'ews'  
              CreateCustomHeadersNodeForBackend 'oab'
              CreateCustomHeadersNodeForBackend 'owa'
              CreateCustomHeadersNodeForBackend 'powershell'
              CreateCustomHeadersNodeForBackend 'pushnotifications'
              CreateCustomHeadersNodeForBackend 'rpcproxy'
              CreateCustomHeadersNodeForBackend 'sync'
              CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
              CreateCustomHeadersNodeForBackend 'mapi\nspi'
              CreateCustomHeadersNodeForBackend 'outlookservice'
    # [ID = ClientAccessComponent___75f8c93d15314369983d33ec0742e189, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:53 PM:
              New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    # Tasks for 'POP/IMAP Backend Configuration' component
    # [ID = PopImapBeComponent___d91be94d83bb4dc28e1fbdf7d94ca60e, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:05 PM:
              if (!(get-service MSExchangeIMAP4BE* | where {$_.name -eq "MSExchangeIMAP4BE"}))
                install-Imap4BeService
    # [ID = PopImapBeComponent___e2debc6ecabf457eb6f278096ad5102c, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              if (!(get-service MSExchangePOP3BE* | where {$_.name -eq "MSExchangePOP3BE"}))
                install-Pop3BeService
    # [ID = PopImapBeComponent___7ee4dbb3fe884d26bb3e060ac68061ee, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Pop3Service.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
              set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
    # [ID = PopImapBeComponent___9b86c2af9f364990aa196cb6e69905b6, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Pop3.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
    # [ID = PopImapBeComponent___01c604c08fd6402e9de6b3c45e3431c8, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Imap4Service.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
              set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
    # [ID = PopImapBeComponent___2528980001a444fcb7097d123e879728, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Imap4.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
    # [ID = PopImapBeComponent___bbfdc492aaf748298977cb9b98e00029, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:install-Imap4Container -Name:"IMAP4" -DomainController $RoleDomainController
    # [ID = PopImapBeComponent___091c98cfe0f145189c0966717496795e, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:install-Pop3Container -Name:"POP3" -DomainController $RoleDomainController
    # [ID = PopImapBeComponent___42cb9f4ac2924c27b6ebf60b92a03628, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:new-ImapSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
    # [ID = PopImapBeComponent___181f5361a5df4e7ca009f21f26f8c0d5, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:new-PopSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
    # Tasks for 'ClientAccessExchangeCertificate' component
    # [ID = ClientAccessExchangeCertificate___fb5e9028e669404d94dba90aace8c2f9, Wt = 1, isFatal = True] "Installing Client Access server certificates."
    7/5/2014 11:05:07 PM:
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController

  • Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?

    Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?
    We recently upgraded from Exchange 2010 to Exchange 2013.
    The links that used OWA Web parts have completely stopped working and generate the " :( something went wrong contact your help desk" screen for domain Authenticated users other than myself. The links accessed content of a Shared Account of which
    I am an owner and can set the necessary permissions using the Outlook 2013 client.
    Using the example from the link provided below we were able to provide calendar access to all authenticated users in our area. The link for calendar still works for me but for noone else. Additionally, all navigation menus are missing when I use this link.
    <server>/owa/<SMTP address>/?cmd=contents&module=calendar&view=weekly name
    Another crafted link provided web access to our group's task list. This has completely stopped working for anyone including myself. However, when I use "open another mailbox" I am able to navigate to the needed pages.
    <server name>/owa/<SMTP address>/?cmd=contents&module=tasks
    These links were crafted using advice provided from this provided link.
    technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
    Is it still possible to use Outlook Web App Web Parts in Exchange Server 2013 - OWA?
    Or
    Is this a misconfiguration of some sort?
    My IT support has given up and closed out the ticket stating that maybe Microsoft will fix this someday...

    Hello,
    At present, there is no official article to verify whether we can use Outlook Web App Web Parts in Exchange Server 2013. In exchange online, the Outlook Web App Parts is supported.
    Cara Chen
    TechNet Community Support
    Hi, you said this feature is supported in Exchange Online (I understand you're referring to Office 365). Can you please point me to some documentation as I was trying to use it with my E3 account and it doesn't seem to work?
    What I'm trying to acomplish is something similar to our old URL (Exchange 2010) in Office 365:
    https://ourserver.mydomain.com/owa/[email protected]/?cmd=contents&module=calendar&view=monthly
    The best I can do in Office 365 is this:
    https://outlook.com/owa/mydomain.com/[email protected]/#path=/calendar
    But it's clearly not the same and Office 365 ignores all the information I add to the URL. I would greatly appreciate something in the line of the document referred by 'MarquetteENG' (technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx)
    Thanks.
    Paulo.
    Paulo Dias - IT Pro Evangelist

  • Internal NAV2013 to relay email externaly through our internal exchange server 2013

    ello,
    We are using NAV 2013 to externally relay email outside and inside through our in house Exchange server 2013.
    I created a new Frontend connected with "TYPE" Custom and selected specific ip to configure relay through exchange server.
    Once created the Receive connectors I want only Anonymous permission to be set under permission group and not exchange users as this is allowing external 3rd party exchange server to relay emails through our exchange server.
    When i edit the properties of the exchange server to uncheck Exchange Server it gives me an error
    "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative."
    My motive is that I want to allow only the NAV2013 to relay emails through our exchange and no other exchange server or any other application for security reasons.
    Once i created a Receive Connectors bydefault TLS is selected and then i put a tick mark on Anonymous but as soon as i save i get error "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter
    to a value of ExternalAuthoritative." and it doesn't let me save unless i select Exchange Server
    I have followed the same link that you provided me.
    There is another problem as well, I have restricted a distribution group from receiving email from external to the organisation but as soon as i created this relay connectors this group starts receiving email external to the organisation which is very strange.
    I tested by disabling the relay connector and then sending email from gmail and then i get a bounce in gmail and the DG doesn't receive email but as soon as I enable relay connector the distribution group starts receiving email.
    I have also recreated the connector as well but still the same issue.
    Please help

    Hi,
    Please double check whether the "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative" is an error, we can safely ignore it if it
    is only a warning message. 
    I found a related KB for your reference even if the Exchange server version is mismatched.
    Exchange 2010: Get-ReceiveConnector warns that an Exchange 2007 connector is corrupted and in an inconsistent state
    http://support.microsoft.com/kb/2291884
    Please double confirm the following setting:
    Authentication tab: Checked TLS and Externally Secured.
    Permission Groups: Anonymous users, Exchange Servers
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Issues with setting up Exchange Server 2013

    Hi All
     Not sure what im doing wrong yet i am having issues with exchange server 2013.
    Currently I have got general SMTP Mail flow working. as long as i log onto the local servers OWA (https://10.x.x.x/owa) i can log into a users mailbox. i have tested sending and recieving mail using this and it works.
    My main issue now is with accessing the OWA externally via our website.  (owa.xx.xx.au/owa) or connecting ANY Outlook to the server.
    When i connect to the exchange server via outlook it asks for the password again multiple times never authenticating it then time's out and says:
     " the action cannot be completed. the connection to microsoft exchange is unavailable, outlook must be online or
    connected to complete this action "
    then when i click on OK it goes to the General Tab and under microsoft exchange server: the name for it appears as 
    [email protected]
    with mailbox set as:
    =SMTP:[email protected]
    Currantly on our DNS i have
    mx=  10  mail.xx.xx.au
    CNAME= autodiscover  = mail.xx.xx.au
    CNAME= OWA = mail.xx.xx.au
    A = mail = 12.34.56.78 
    On our modem/router i have set one-to-one nat to our firewall IP
    On our firewall i have
    SMTP SAT and NAT to Exchange server
    HTTPS Sat and NAT to exchange Server
    HTTP Sat and Nat to exchange Server
    Port 587 SAT and Nat to exchange server
    pop SAT and NAt to exchange server
    Im willing to bet its something stupid i have overlooked but i was wondering if anyone would be able to help me out
    Regards
    Sibsy

    Hello,
    Firstly, please follow the Shadab's suggestion to check related virtual directory settings.
    Please make sure you use certificate that's created by a CA that's trusted by the client computer's operating system. 
    Please use get-outlookanywhere | fl cmdlet to check ExternalClientAuthenticationMethod. By default, the authentication is Negotiate.
    Cara Chen
    TechNet Community Support

  • Outlook 2013 not connect with Exchange server 2013 in internal network

    Hello All,
    I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
    but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
    I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network. 
    Can you please suggest as soon as possible.
    Thanks,
    Parvez

    Hi,
    Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
    Thus, let’s try the following resolutions:
    1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
    2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
    3. Check if the above host name is in your certificate.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Sizing IIS ARR for Exchange Server 2013

    Hi Everyone,..
    I planned to publish Exchange 2013 through IIS ARR server, but I've had trouble finding any data on CPU / memory usage for a dedicated ARR server based on Microsoft recommendation. There are 8000 users that will be access from ARR server. 
    Hopefully you can help for sizing so
    there isn't bottleneck on that server.
    Thanks
    ~IH~

    Hi Irfan
    The concurrent connections depends upon appConcurrentRequestLimit which has a default value of 5000. I think you need to increase this if  in your case the concurrent connections exceed 5000
    I have found few articles for your reference
    http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/achieving-high-availability-and-scalability-arr-and-nlb
    http://blogs.technet.com/b/tristank/archive/2008/03/11/maxuserport-what-it-is-what-it-does-when-it-s-important.aspx
    https://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
    https://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
    https://blogs.technet.com/b/exchange/archive/2013/08/05/part-3-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
    Its better to submit this to  http://forums.iis.net/ since this is more kind of IIS related issue and you will get better response
    Good Luck !! 
    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

Maybe you are looking for

  • Editing from two computers

    I have an iMac at home that I have been editing and publishing a site from iWeb to .Mac. I now have a macbook and would like to work on pages or blogs with that computer also. I vaguely understand the issue now with the files stored on my iMac and ed

  • File Type associations will not change!

    This is a problem with Parellels / VMfusion (???) I have a problem with some filetype on the Mac OS side associated with the same (or similar) program running on the windows side. I do not want macside docs or files launching with the windows applica

  • How can I get my iPad to show that little apple tv icon?

    How can I get my iPad to show that little apple tv icon? My husband s iPad shows the icon and we can watch tv or movies, but mine does not.. Is there a setup that I am missing?

  • Purchase requisition with MRP controller

    Hi everybody, I need support because I have to control during purchase requisition to block users with specific MRP controller. I mean, user A only have permission to create purchase requisition with MRP controller Z and user B only have permission t

  • I need to reboot my laptop

    How can I find free reboot information for my laptop