Outlook Clients for Exchange 2013 Prompt for Password

I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem: 
- Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows: 
RunspaceId                         : b43cd829-a81f-4b00-bb4d-73389c9df50d
ServerName                         : EXCH-HTCA13
SSLOffloading                      : False
ExternalHostname                   : webmail.first.pt
InternalHostname                   : exch-htca13.first.pt
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
Can anyone help me identify the problem?

Hi,
Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
In addition, I recommend you refer to the following article:
Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
Thanks.
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.
Niko Cheng
TechNet Community Support

Similar Messages

  • Outlook 2013 - Exchange 2013 - Prompts for username and password when EWS basic authentication is enabled

    So we have an Exchange 2013 environment, and a CRM solution that requires basic authentication to EWS internally.  Problem is, after a reboot of our Exchange server, all of our Outlook clients begin prompting for username and password (which nothing
    works) which also starts locking users AD accounts out due to failed login attempts (somehow).  If I disabled basic authentication on EWS, Outlook authenticates as normal using NTLM and there are no issues.  Once Outlook has authenticated, I can
    turn back on basic authentication, and Outlook will be fine until the next time the Exchange server is rebooted.
    Any ideas?

    Hi,
    According to your description, I understand that Outlook client prompted for username and password when Exchange server restart and basic authentication is enabled for EWS.
    If I misunderstand your concern, please do not hesitate to let me know.
    It’s normal. This caused by the difference between basic authentication and NTML authentication:
    Basic, with any version of Outlook prior to 2010, results in a pop up dialog asking for creds. Outlook 2010 makes the 'save this password' actually work, so in an Outlook 2010 or later world, Basic can mean no need to authenticate every time you open/reconnect,
    but in all earlier versions, you will have to enter creds every time.
    NTLM, when used by a client that is domain joined and logged in with cached creds, results in the client simply sending the cached in creds to the server, resulting in what looks like a pretty seamless single sign on experience. However, if you want to do pre-authentication
    at something like TMG, and not let the traffic go all the way to CAS, you need to configure TMG for this.
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • F5 Big IP 4000 Send /Return String for Exchange 2013

    Hi,
    I need to Implement F5 Big IP 4000 and need to set send / return string for Exchange 2013 server for OWA monitoring... Can anyone help me with Exact output String.
    Amit

    Hi,
    In the Send String box enter in GET /owa/healthcheck.htm.  In the
    Receive String box, enter in 200 OK.
    Here is a related article for your reference.
    http://port25guy.com/2013/07/24/how-to-use-managed-availability-in-exchange-2013-with-your-load-balancer/
    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 is helpful to you.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Outlook PRF file settings for Exchange 2013 environment

    Hi Team,
    Client - Outlook 2007
    Existing environment - exchange 2007
    New environment - exchange 2013
    Recently migration of exchange 2007 to exchange 2013 happened in our environment subsequently some users mailboxes are moved from exchange 2007 to exchange 2013.
    In the Exchange 2007 environment, users outlook profile settings are applied via importing the below prf file and it works fine.
    ;Automatically generated PRF file from the Microsoft Office Customization and Installation Wizard
    ; Section 1 - Profile Defaults
    [General]
    Custom=1
    ProfileName=outlook
    DefaultProfile=Yes
    OverwriteProfile=Yes
    ModifyDefaultProfileIfPresent=false
    ; Section 2 - Services in Profile
    [Service List]
    ServiceX=Microsoft Outlook Client
    ServiceEGS=Exchange Global Section
    Service1=Microsoft Exchange Server
    ServiceEGS=Exchange Global Section
    ; Section 3 - List of internet accounts
    [Internet Account List]
    ; Section 4 - Default values for each service.
    [ServiceX]
    CachedExchangeMode=0x00000002
    CachedExchangeSlowDetect=true
    [ServiceEGS]
    CachedExchangeConfigFlags=0x00000900
    MailboxName=%UserName%
    HomeServer=mailboxserver.exchange.xxx.xx
    [Service1]
    OverwriteExistingService=No
    UniqueService=Yes
    MailboxName=%UserName%
    HomeServer=mailboxserver.exchange.xxxx.xa
    AccountName=Microsoft Exchange Server
    ; Section 5 - Values for each internet account.
    ; Section 6 - Mapping for profile properties
    [Microsoft Exchange Server]
    ServiceName=MSEMS
    MDBGUID=5494A1C0297F101BA58708002B2A2517
    MailboxName=PT_STRING8,0x6607
    HomeServer=PT_STRING8,0x6608
    OfflineAddressBookPath=PT_STRING8,0x660E
    OfflineFolderPathAndFilename=PT_STRING8,0x6610
    [Exchange Global Section]
    SectionGUID=13dbb0c8aa05101a9bb000aa002fc45a
    MailboxName=PT_STRING8,0x6607
    HomeServer=PT_STRING8,0x6608
    RPCoverHTTPflags=PT_LONG,0x6623
    RPCProxyServer=PT_UNICODE,0x6622
    RPCProxyPrincipalName=PT_UNICODE,0x6625
    RPCProxyAuthScheme=PT_LONG,0x6627
    CachedExchangeConfigFlags=PT_LONG,0x6629
    [Microsoft Mail]
    ServiceName=MSFS
    ServerPath=PT_STRING8,0x6600
    Mailbox=PT_STRING8,0x6601
    Password=PT_STRING8,0x67f0
    RememberPassword=PT_BOOLEAN,0x6606
    ConnectionType=PT_LONG,0x6603
    UseSessionLog=PT_BOOLEAN,0x6604
    SessionLogPath=PT_STRING8,0x6605
    EnableUpload=PT_BOOLEAN,0x6620
    EnableDownload=PT_BOOLEAN,0x6621
    UploadMask=PT_LONG,0x6622
    NetBiosNotification=PT_BOOLEAN,0x6623
    NewMailPollInterval=PT_STRING8,0x6624
    DisplayGalOnly=PT_BOOLEAN,0x6625
    UseHeadersOnLAN=PT_BOOLEAN,0x6630
    UseLocalAdressBookOnLAN=PT_BOOLEAN,0x6631
    UseExternalToHelpDeliverOnLAN=PT_BOOLEAN,0x6632
    UseHeadersOnRAS=PT_BOOLEAN,0x6640
    UseLocalAdressBookOnRAS=PT_BOOLEAN,0x6641
    UseExternalToHelpDeliverOnRAS=PT_BOOLEAN,0x6639
    ConnectOnStartup=PT_BOOLEAN,0x6642
    DisconnectAfterRetrieveHeaders=PT_BOOLEAN,0x6643
    DisconnectAfterRetrieveMail=PT_BOOLEAN,0x6644
    DisconnectOnExit=PT_BOOLEAN,0x6645
    DefaultDialupConnectionName=PT_STRING8,0x6646
    DialupRetryCount=PT_STRING8,0x6648
    DialupRetryDelay=PT_STRING8,0x6649
    [Personal Folders]
    ServiceName=MSPST MS
    Name=PT_STRING8,0x3001
    PathAndFilenameToPersonalFolders=PT_STRING8,0x6700
    RememberPassword=PT_BOOLEAN,0x6701
    EncryptionType=PT_LONG,0x6702
    Password=PT_STRING8,0x6703
    [Unicode Personal Folders]
    ServiceName=MSUPST MS
    Name=PT_UNICODE,0x3001
    PathAndFilenameToPersonalFolders=PT_STRING8,0x6700
    RememberPassword=PT_BOOLEAN,0x6701
    EncryptionType=PT_LONG,0x6702
    Password=PT_STRING8,0x6703
    [Outlook Address Book]
    ServiceName=CONTAB
    [LDAP Directory]
    ServiceName=EMABLT
    ServerName=PT_STRING8,0x6600
    UserName=PT_STRING8,0x6602
    UseSSL=PT_BOOLEAN,0x6613
    UseSPA=PT_BOOLEAN,0x6615
    EnableBrowsing=PT_BOOLEAN,0x6622
    DisplayName=PT_STRING8,0x3001
    ConnectionPort=PT_STRING8,0x6601
    SearchTimeout=PT_STRING8,0x6607
    MaxEntriesReturned=PT_STRING8,0x6608
    SearchBase=PT_STRING8,0x6603
    CheckNames=PT_STRING8,0x6624
    DefaultSearch=PT_LONG,0x6623
    [Microsoft Outlook Client]
    SectionGUID=0a0d020000000000c000000000000046
    FormDirectoryPage=PT_STRING8,0x0270
    WebServicesLocation=PT_STRING8,0x0271
    ComposeWithWebServices=PT_BOOLEAN,0x0272
    PromptWhenUsingWebServices=PT_BOOLEAN,0x0273
    OpenWithWebServices=PT_BOOLEAN,0x0274
    CachedExchangeMode=PT_LONG,0x041f
    CachedExchangeSlowDetect=PT_BOOLEAN,0x0420
    [Personal Address Book]
    ServiceName=MSPST AB
    NameOfPAB=PT_STRING8,0x001e3001
    PathAndFilename=PT_STRING8,0x001e6600
    ShowNamesBy=PT_LONG,0x00036601
    ; Section 7 - Mapping for internet account properties.  DO NOT MODIFY.
    [I_Mail]
    AccountType=POP3
    ;--- POP3 Account Settings ---
    AccountName=PT_UNICODE,0x0002
    DisplayName=PT_UNICODE,0x000B
    EmailAddress=PT_UNICODE,0x000C
    ;--- POP3 Account Settings ---
    POP3Server=PT_UNICODE,0x0100
    POP3UserName=PT_UNICODE,0x0101
    POP3UseSPA=PT_LONG,0x0108
    Organization=PT_UNICODE,0x0107
    ReplyEmailAddress=PT_UNICODE,0x0103
    POP3Port=PT_LONG,0x0104
    POP3UseSSL=PT_LONG,0x0105
    ; --- SMTP Account Settings ---
    SMTPServer=PT_UNICODE,0x0200
    SMTPUseAuth=PT_LONG,0x0203
    SMTPAuthMethod=PT_LONG,0x0208
    SMTPUserName=PT_UNICODE,0x0204
    SMTPUseSPA=PT_LONG,0x0207
    ConnectionType=PT_LONG,0x000F
    ConnectionOID=PT_UNICODE,0x0010
    SMTPPort=PT_LONG,0x0201
    SMTPSecureConnection=PT_LONG,0x020A
    ServerTimeOut=PT_LONG,0x0209
    LeaveOnServer=PT_LONG,0x1000
    [IMAP_I_Mail]
    AccountType=IMAP
    ;--- IMAP Account Settings ---
    AccountName=PT_UNICODE,0x0002
    DisplayName=PT_UNICODE,0x000B
    EmailAddress=PT_UNICODE,0x000C
    ;--- IMAP Account Settings ---
    IMAPServer=PT_UNICODE,0x0100
    IMAPUserName=PT_UNICODE,0x0101
    IMAPUseSPA=PT_LONG,0x0108
    Organization=PT_UNICODE,0x0107
    ReplyEmailAddress=PT_UNICODE,0x0103
    IMAPPort=PT_LONG,0x0104
    IMAPUseSSL=PT_LONG,0x0105
    ; --- SMTP Account Settings ---
    SMTPServer=PT_UNICODE,0x0200
    SMTPUseAuth=PT_LONG,0x0203
    SMTPAuthMethod=PT_LONG,0x0208
    SMTPUserName=PT_UNICODE,0x0204
    SMTPUseSPA=PT_LONG,0x0207
    ConnectionType=PT_LONG,0x000F
    ConnectionOID=PT_UNICODE,0x0010
    SMTPPort=PT_LONG,0x0201
    SMTPSecureConnection=PT_LONG,0x020A
    ServerTimeOut=PT_LONG,0x0209
    CheckNewImap=PT_LONG,0x1100
    RootFolder=PT_UNICODE,0x1101
    [INET_HTTP]
    AccountType=HOTMAIL
    Account=PT_UNICODE,0x0002
    HttpServer=PT_UNICODE,0x0100
    UserName=PT_UNICODE,0x0101
    Organization=PT_UNICODE,0x0107
    UseSPA=PT_LONG,0x0108
    TimeOut=PT_LONG,0x0209
    Reply=PT_UNICODE,0x0103
    EmailAddress=PT_UNICODE,0x000C
    FullName=PT_UNICODE,0x000B
    Connection Type=PT_LONG,0x000F
    ConnectOID=PT_UNICODE,0x0010
    I have changed the home server in [ServiceEGS] and [Service1] with the CAS Array VIP configured with the DNS name
    autodiscoverservices.exchange.xxxx.xx  but it is not working and getting "Exchange server unavailable" error. Some one have any idea how to
    configure the user outlook profile via a prf file which works with exchange server 2013 autodiscover services. Is there any more settings to be applied to the PRF file to make it work.
    [ServiceEGS]
    CachedExchangeConfigFlags=0x00000900
    MailboxName=%UserName%
    HomeServer=autodiscoverservices.exchange.xxxx.xx
    [Service1]
    OverwriteExistingService=No
    UniqueService=Yes
    MailboxName=%UserName%
    HomeServer=autodiscoverservices.exchange.xxxx.xx
    AccountName=Microsoft Exchange Server

    May I ask why you changed the home server to autodiscoverservices.exchange.xxxx.xx?
    Basically, we set it to Microsoft Exchange server address.
    Flynn

  • Configuring IIS and DNS for Exchange 2013 running on Second Win2012 R2 Server

    Hi Folks,
    I have a Windows 2012 R2 Server with Essentials role and I'm running a Hyper-V instance of Windows 2012 R2 with Exchange 2013 installed joined to domain.  I have been through the wizards and the Exchange Server deployment wizard but I'm stuck with configuring
    DNS records correctly.
    Currently I can browse to https://remote.contoso.com externally and internally which works as expected but not https://remote.contoso.com/owa or any other Exchange pages.  All I get is 404 - File or directory not found.  However if I browse
    internally to https://exchangeserver.domain.local/owa it works. So I'm guessing 404 is coming from the DC server not the exchange server.  Hence I think its DNS.
    Although I have noticed that IIS is on the DC and the Exchange server, showing different Sites.  Does this have anything to do with the issue at hand.  Also the guides are not perfectly clear on how to add the DNS CNAME records.
    Would someone be so kind as to point me in the right direction.
    Thank you 

    Hi Jatin,
    It turned out to be a little more involved in the end.  I had to call Microsoft in the end.  ARRconfig wasn't running correctly and after creating a new certificate it was able to run successfully.  I'm waiting for the detailed report which
    will hopefully explain the issue with Bindings between the two IIS on Essentials and Exchange 2013 which was also and issue.
    Then I had an issue trying to connect Outlook clients to Exchange.  The resolution for this was:
    Created new SAN certificate with issued to name as “mail.pinewoodonline.co.uk” using the CA server
    OutlookProvider EXCH and EXPR value was not set
    Set OutlookProvider EXCH and EXPR value as “msstd:mail.pinewoodonline.co.uk” by running the below command
    Set-OutlookProvider EXPR -Certprincipalname msstd:mail.pinewoodonline.co.uk
    Set-OutlookProvider EXCH -CertPrincipalName msstd:mail.pinewoodonline.co.uk
    All seems good now.  I will post the report as soon as I get it.  This took 6 hours on the phone to Microsoft.  Wasn't easy.
    Thanks
    Brandan

  • Exchange 2013 DNS for internal and external domain

    Hi All,
    I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
    We have an Active Directory domain myinternaldomain.net, and we have a public domain
    mypublicdomain.com and we have setup email policy to have
    mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
    mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
    hardware LB is out of scope due to budget constrains.
    We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
    that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
    Thanks

    Hi Sccmnb,
    You can easily achieve this using split DNS.
    Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
    Reverse proxy server IP.
    Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
    The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
    SN= mail.mypublicdomain.com
    SAN= autodiscover.mypublicdomain.com
    You don't need to have the active directory domain name present in the certificate.
    Additional  to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
    Some additional Info:
    *Internal vs. External Namespaces
    Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
    based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
    This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
    Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
    *Managing Certificates in Exchange Server 2013 (Part 2)
    *Nice step by step article
    Designing a simple namespace for Exchange 2013
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Running setup.exe for Exchange 2013 does nothing

    Hi All,
    Unable to find this issue anywhere else, please excuse if it's a duplicate of another issue.  
    Basically, I have a new 2008 R2 server setup, added it to a domain, and want to install Exchange 2013 on this new server.  There are no Exchange servers anywhere on the domain.
    The server is fully up to date, including .Net 4, and looking for updates results in zero new updates found.
    When I run setup.exe for Exchange 2013, a command prompt appears for less than a second, then closes, then nothing else happens.
    Did a fresh reboot before trying to install, and after waiting about 20 minutes to see if anything happened after the vanishing command prompt, rebooted again, tried again, same result.
    There is nothing called Exchange anywhere on the server that I can find, no setup logs or anything, and I am totally stumped.
    Thanks in advance for any advice.
    Michael

    Hello,
    Exchange 2013 need to be installed on windows server 2008 R2 SP1. If you use windows server 2008 R2 SP1, I sugegst you check if there is any exchange server via ADSIEDIT.
    CN=Configuration,DC=Domain ->CN=services ->CN=Micorosft Exchange ->CN=Organization ->=Administrative Groups ->CN=Exchange Administrative Group ->CN=Servers
    Here is the article for your reference.
    Exchange 2013 Prerequisites
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx#WS2008R2SP1
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Configuring Lync Server 2013 to be a partner Application for Exchange 2013

    Hello Guys,
    I just want to share my experience while configuring Lync server 2013 to be a partner Application for exchange 2013 sever. 
    As mentioned on technet you need to run Configure-EnterprisePartnerApplication.ps1 script that ships with Exchange 2013. 
    But when I tried to run the script as described on the technet article, I found it always fails with " the accepted domain is not valid"
    I have checked my accepted domains many times and i found that there's no issues with my configured accepted domain. 
    So I started to review the script to find the issue and I found that the script was configured  as below 
    $acceptedDomains = Get-AcceptedDomain ;
      if ($acceptedDomains -eq $null)
        WriteError ("There is no accepted domain so user can not be created.")
      $acceptedDomain = $acceptedDomains[0].Name;
      if($UseDomainController -eq $true)
        $user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
      else
        $user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true; 
    which is totally wrong as below: 
    firstly it makes $AcceptedDomain variable to equal the Name of the accepted domain. 
    Not all customers configure the name of the Accepted Domain to be the Domain Name.
    Secondly  it makes $AcceptedDomain variable to equal the name of the first Accepted Domain.
    The first domain may be not the default Accepted Domain. 
    So I have configured the script as below
    $acceptedDomains = Get-AcceptedDomain | ? {$_.Default -eq "True"}  ;
      if ($acceptedDomains -eq $null)
        WriteError ("There is no accepted domain so user can not be created.")
      $acceptedDomain = $acceptedDomains.DomainName;
      if($UseDomainController -eq $true)
        $user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
      else
        $user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
    set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true; 
    I hope This help. 
    Thanks 
    Ahmed Fouad

    Hi,
    This is helpful, thanks for sharing.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Is smb 3.0 already supported for exchange 2013

    Hello,
    We are looking to deploy exchange 2013. We have a netapp storage and vmware environment.
    I was wondering if smb 3.0 is already supported for exchange 2013. I read in a blog of 2012 that it wasn't supported at the time. We would like to use it instead of a iscsi lun.

    Hi,
    Based on my knowledge, it is still not supported for Exchange 2013 up to now.
    Here is an article for your reference, please refer to the "Exchange storage requirements" section.
    Exchange 2013 Virtualization
    http://technet.microsoft.com/en-us/library/jj619301.aspx#BKMK_Prereq
    Another related article for your reference.
    Exchange 2013 Storage Configuration Options
    http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • It is there an alternative to the Test-SystemHealth powershell cmdlet for Exchange 2013?

    Hello
    The Powershell cmdlet Test-SystemHealth, that was available on Exchange 2010, is no longer available on Exchange 2013.
    Test-SystemHealth cmdlet gathered data about the Microsoft Exchange system and analyzed the data according to best practices.
    Are there any alternatives to this for Exchange 2013?
    Thanks!

    Haven't really played with it too much, but check out Get-ServerHealth
    http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
    Looks to have replaced Test-SystemHealth.

  • SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

    SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The virtual directory 'ecp' already exists under 'server/name'.
    Parameter name: VirtualDirectoryName".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    !! And now transport service won't start and mail is unavailable !!
    Any help would be appreciated.
    I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

    Hi,
    Thanks for your response.
    From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Best Practice Analyzer for Exchange 2013

    Greetings,
    I have upgraded the messaging infrastructure from Exchange 2007 to Exchange 2013.
    I want to test the Health of the system through ExBPA for Exchange 2013.
    But i don't find any setup for Exchange 2013 like it was in 2010.
    I went through an article by Office365 community, according to which for In-premises Exchange also we need to have office 365 account (can use trial account also) to get the downloader file for ExBPA 2013.
    http://community.office365.com/en-us/w/deploy/office-365-best-practices-analyzer-for-exchange-server-2013.aspx
    But to run the setup the servers needs to be connected to internet.
    And, i don't want to expose my environment to internet in any condition.
    Somebody, please suggest me if there is any setup available so that i can install directly without exposing to internet.
    Thanks in advance.
    Best Regards,
    K2

    Welcome to Exchange 2013.
    Exchange Server 2013 doesn't come with ExBPA for health check. This might help
    http://exchangeserverpro.com/powershell-script-health-check-report-exchange-2010/
    Apart from that you can run these commands too
    Get-ServerHealth -Identity Exchange2013ServerName
    Test-ServiceHealth
    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.

  • EXMON "exchange server user monitor" for Exchange 2013?

    Hello,
    it Looks like EXMON is not supported for Exchange 2013. Is this correct or can i use it with Server 2012 R2 and Exchange 2013 (CU6++)  ?
    Is there any alternative to check high log growth rate to see which user is responsable for this?
    Thanks for Feedback.
    best,
    Martin

    Hi Martin,
    Yes, ExMon is not supported for exchange 2013.
    Except the suggestion above, here is an exclusive application for you reference, it could retrieve statistics for all or selected mailboxes in a specified database and server, it may give you some help:
    Exchange Server Mailbox Statistics Tool - v1.6.2
    The tool retrieves mailbox statistics which includes Folder Count, Total Items, Associated Items, Deleted Items, Total Items Size, Deleted Items Size, Oldest Item Date, Newest Item Date, Items Age, Mailbox Age and Quota details. It also includes an additional
    option named "Archive Statistics Planner" which will let you search mailboxes and provide statistics report with specific dates. 
    Best regards,
    Niko Cheng
    TechNet Community Support

  • BPA for Exchange 2013 still in beta!?

    Exchange 2013 is over 2 years old.
    Is Microsoft ever going to release a BPA for their flagship messaging platform that's NOT in beta? 

    Hi,
    At present, there is only a beta of Best Practices Analyzer for Exchange 2013 available. If you want to get the latest information about it, please pay attention to the Exchange blog.
    For your convenience:
    http://blogs.technet.com/b/exchange/
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • PowerGUI Powerpack for Exchange 2013

    Is there a powerpack that can be added to the powerGUI script editor for scripting in exchange 2013?

    Hi,
    Based on my search, currently, there is no official document about
    PowerGUI Powerpack for Exchange 2013.
    However, we can connect to Exchange server using remote shell.
    For more details about this, please refer to the following article.
    https://technet.microsoft.com/en-us/library/dd335083(v=exchg.150).aspx
    Hope this is helpful to you.
    Best regards,
    Belinda Ma
    TechNet Community Support

Maybe you are looking for