Sorry for the long title, but I cant think of any other way of putting it. 

We are testing an Exchange 2010 - 2013 upgrade/migration and as part of the testing we migrated a mailbox from 2010 to 2013, and then moved it back to 2010 again - for testing purposes. Now, when we try and migrate it back from 2010 to 2013 we can select it, initiate the job, but within a couple of seconds the number of mailboxes to move drops to 0 (zero) and then the job completes, with no errors at all, but the mailbox is still on the 2010 Information Store.

Now, we dont plan on doing this but is this unique to use, or is this a bug/feature? Exchange 2010 is at SP3 with UR8MK2, and Exchange 2013 is with SP1/UR8.

Thanks

Phil

Phil

Hi,

I’ve migrated a customer from Exchange 2007 to Exchange 2013 successfully. However. There are troubles with booking resources. Users receive the following error message when booking a resource: Direct Booking – Cannot directly book a resource for this meeting.

The user follows the following procedure:
The user opens his/her ‘own agenda’, create a meeting, use Scheduling Assistant to schedule a meeting with another user and to add a Room. When hitting Send the above message appears.

When the user has Full Control to the resource mailbox and the user opens the agenda of the resource directly and follows the above procedure in the ‘resource agenda’ he/she is able to book the resource without a problem (this workaround is not preferred as a final solution).

To fix this, I’ve tried the following:

Add a registry key to the client. HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options\Calendar\EnableDirectBooking (0)

Turn cache mode ON, this works.
However for some users cache mode must be turned off, so this workaround doesn’t apply for all the users.

I worked with Full Control permissions on the resource, so that the user is able to book directly from the ‘resource agenda’.

Some more information:
Public Folders are not in use anymore.
There are several clients in the environment:
Windows XP with Outlook 2007
Windows 7 with Outlook 2007
Windows 7 with Outlook 2010  (I do not have a confirmation if these symptoms also apply on these clients as well).

Does anyone has a final solution for me?
Or how can I troubleshoot this any further?

Hi, all,

Exchange 2013 installation fails. This is the console output and the tail of ExchangeSetup.log:

--------------------------------------------------------------------------------------------------------------------

We have a test environment which was 2008R2 AD.  We properly went through the migration path and are currently at 2012R2 Active Directory functional level.

I'm installing Exchange 2013 with Sp1 into the domain.  I have successfully prepared the domain as outlined on technet, and verified its success with the logs and looking in ADSI edit.  No errors.  All seems to have ran correctly.

When I attempt to install the first exchange mailbox server, the Readiness check fails saying "the local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed"...  1 forest, 1 root domain, 1 child domain. The account I'm using is a member of Schema Admins, Enterprise Admins, Domain admins etc.  

Has anyone else come across this or have any suggestions?

We have a test environment which was 2008R2 AD.  We properly went through the migration path and are currently at 2012R2 Active Directory functional level.

I'm installing Exchange 2013 with Sp1 into the domain.  I have successfully prepared the domain as outlined on technet, and verified its success with the logs and looking in ADSI edit.  No errors.  All seems to have ran correctly.

When I attempt to install the first exchange mailbox server, the Readiness check fails saying "the local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed"...  1 forest, 1 root domain, 1 child domain. The account I'm using is a member of Schema Admins, Enterprise Admins, Domain admins etc.  

Has anyone else come across this or have any suggestions?

We have Exchange 2013 with legacy 2007/2010. My 2007 servers are at RU10. one of my sites has a need to replace their edge server and wants to install a 2013 edge server, but the internal 2007 hub server will require RU13 to communicate with the 2013 edge.

Will updating that single hub server to RU10, and leaving the rest of my 2007 environment at RUY10 cause issues?

Tom

Hi,

I have configured POP and IMAP on Exchange 2013. The setting was configured that when unchecked server require authentication POP and IMAP working fine and in advance settings configured 995 and 587 with None.

If select the server require authentication receiving error on configuration. I would like to know that how can I secure my server to require authentication while sending emails or it is fine as SMTP 587 and POP 995 secure ports configured and no need to setup server authentication on SMTP setting. Please guide.

Hi,

After installing Exchange 2013 with SSL certificate with OWA, Active Sync and outlook anywhere. I observed that if someone from external network can telnet to my server is able to connect. I checked it and find that port 25 and 587 is open and bypass my Fortinet firewall.

I would like to know how can I block these ports and don't allow anyone can telnet on my Exchange server from externally. Please assist.

Hello,

We are receiving the below error while trying to install Exchange 2013 CU5 or CU6 on our Exchange Server running on Exchange 2013 SP1 on W2012R2

Thanks.

hi,

i've got problem when update to cu8.

the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi' in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.

please help me..

Hi all,

we traid to install Exchange CU6 as a upgrade from Exchange 2013 SP1. The Setup Fails like this:

E:\Sources\Ex2013CU6>setup /m:upgrade /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

                                                              FAILED
 An unexpected error has occurred and a Watson dump is being generated: Object r
eference not set to an instance of an object.

     Object reference not set to an instance of an object.

The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

[09/15/2014 13:53:00.0941] [0] **********************************************
[09/15/2014 13:53:00.0956] [0] Starting Microsoft Exchange Server 2013 Cumulative Update 6 Setup
[09/15/2014 13:53:00.0956] [0] **********************************************
[09/15/2014 13:53:00.0956] [0] Local time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
[09/15/2014 13:53:00.0956] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[09/15/2014 13:53:00.0956] [0] Setup version: 15.0.995.29.
[09/15/2014 13:53:00.0972] [0] Logged on user: LOC\administrator.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='mode', Value='Upgrade'.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='sourcedir', Value='E:\Sources\Ex2013CU6'.
[09/15/2014 13:53:01.0285] [0] RuntimeAssembly was started with the following command: '/m:upgrade /IAcceptExchangeServerLicenseTerms /sourcedir:E:\Sources\Ex2013CU6'.
[09/15/2014 13:53:01.0300] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[09/15/2014 13:53:01.0300] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[09/15/2014 13:53:01.0300] [0] Copying Files...
[09/15/2014 13:53:01.0316] [0] Starting copy from E:\Sources\Ex2013CU6\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[09/15/2014 13:53:02.0816] [0] Finished copy from E:\Sources\Ex2013CU6\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[09/15/2014 13:53:02.0816] [0] File copy complete. Setup will now collect additional information needed for installation.
[09/15/2014 13:53:02.0831] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[09/15/2014 13:53:06.0613] [0] Setup is choosing the domain controller to use
[09/15/2014 13:53:07.0003] [0] The MSExchangeADTopology has a persisted domain controller: LOC-srv1201.LOC.local
[09/15/2014 13:53:11.0253] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use LOC-srv1201.LOC.local
[09/15/2014 13:53:11.0253] [0] Setup is choosing a global catalog...
[09/15/2014 13:53:11.0331] [0] Setup has chosen the global catalog server LOC-srv1201.LOC.local.
[09/15/2014 13:53:11.0347] [0] Setup will use the domain controller 'LOC-srv1201.LOC.local'.
[09/15/2014 13:53:11.0347] [0] Setup will use the global catalog 'LOC-srv1201.LOC.local'.
[09/15/2014 13:53:11.0347] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:11.0347] [0] Exchange organization container for the organization is 'CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:11.0394] [0] Setup will search for an Exchange Server object for the local machine with name 'LOC-SRV7210'.
[09/15/2014 13:53:11.0738] [0] Exchange Server object found : 'CN=LOC-SRV7210,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:12.0128] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[09/15/2014 13:53:12.0128] [0] The following datacenter roles are unpacked:
[09/15/2014 13:53:12.0128] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[09/15/2014 13:53:12.0144] [0] The local server has some Exchange files installed.
[09/15/2014 13:53:12.0175] [0] Server Name=LOC-SRV7210
[09/15/2014 13:53:12.0238] [0] Setup will use the path 'E:\Sources\Ex2013CU6' for installing Exchange.
[09/15/2014 13:53:12.0238] [0] Setup will discover the installed roles from server object 'CN=LOC-SRV7210,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:12.0238] [0] 'BridgeheadRole' is installed on the server object.
[09/15/2014 13:53:12.0238] [0] 'ClientAccessRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'MailboxRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'UnifiedMessagingRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'CafeRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'FrontendTransportRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] The installation mode is set to: 'BuildToBuildUpgrade'.
[09/15/2014 13:53:13.0425] [0] An Exchange organization with name 'LOC' was found in this forest.
[09/15/2014 13:53:13.0425] [0] Active Directory Initialization status : 'True'.
[09/15/2014 13:53:13.0425] [0] Schema Update Required Status : 'False'.
[09/15/2014 13:53:13.0425] [0] Organization Configuration Update Required Status : 'False'.
[09/15/2014 13:53:13.0425] [0] Domain Configuration Update Required Status : 'False'.
[09/15/2014 13:53:13.0441] [0] The locally installed version is 15.0.847.32.
[09/15/2014 13:53:13.0441] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[09/15/2014 13:53:13.0535] [0] Setup is determining what organization-level operations to perform.
[09/15/2014 13:53:13.0535] [0] Because the value was specified, setup is setting the argument OrganizationName to the value LOC.
[09/15/2014 13:53:13.0581] [0] RootDataHandler has 1 DataHandlers
[09/15/2014 13:53:13.0581] [0]      Languages
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Transport service
[09/15/2014 13:53:13.0581] [0]      Client Access role: Front End Transport service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Client Access service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Unified Messaging service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Mailbox service
[09/15/2014 13:53:13.0581] [0]      Management tools
[09/15/2014 13:53:13.0581] [0]      Client Access role: Client Access Front End service
[09/15/2014 13:53:13.0613] [0] Validating options for the 7 requested roles
[09/15/2014 13:53:13.0613] [0] UpgradeModeDataHandler has 17 handlers and 17 work units
[09/15/2014 13:53:13.0675] [0] Performing Microsoft Exchange Server Prerequisite Check
[09/15/2014 13:53:13.0925] [0] **************
[09/15/2014 13:53:13.0925] [0] Setup will run the task 'Start-PreConfiguration'
[09/15/2014 13:53:13.0941] [1] Setup launched task 'Start-PreConfiguration -Mode 'BuildToBuildUpgrade' -Roles 'LanguagePacks','BridgeheadRole','FrontendTransportRole','ClientAccessRole','UnifiedMessagingRole','MailboxRole','AdminToolsRole','CafeRole'' 
[09/15/2014 13:53:15.0472] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:15.0472] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0144] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0144] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] [ERROR] Exception has been thrown by the target of an invocation.
[09/15/2014 13:53:16.0175] [0] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[09/15/2014 13:53:16.0175] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[09/15/2014 13:53:16.0175] [0] CurrentResult main.run:235: 1
[09/15/2014 13:53:16.0175] [0] CurrentResult setupbase.maincore:396: 1
[09/15/2014 13:53:16.0175] [0] End of Setup
[09/15/2014 13:53:16.0175] [0] **********************************************

Hello.

i have an issue when configuring Exchange hybrid deployment in my environment.

when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.

mail will can be sent out and will flow between internal users.

when i check the message trace on 365 the emails were failing with the following error.

Users were also getting a bounce back saying 

Diagnostic-Code: smtp;550 5.4.1 [user@domain.com]: Recipient address rejected: Access denied

i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,

it looks like it could be a receive connector issue however i am new to exchange so i am still learning.

the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.

Any Suggestions on what could be caused 

many thanks

I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.

Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

How can we migrate users from exchange server 2010 to new exchange server 2013. The two exchange environments are different. Once we installed new exchange server 2013, how do we import all exchange 2010 users mails into new exchange 2013.

I'm attempting to Configure Exchange 2013 on a fresh Win Server 2012 VM, in a domain that's currently using Exchange 2010.  I've got SP3, the various service packs and language packs, per the MS prerequisite suggestions.  The install runs through and ultimately fails during the User Mailbox creation (error message below).  

The support articles I've found indicate that removing the Arbitration accounts (FederationEmail, DiscoverySearchMailbox, HealthMailbox, Migration, SystemMailbox), with Powershell and then ultimately removing from AD.  
The proceed with the 2013 install and things should work.  Will this interfere, in any way, with my production Exchange 2010 box?

And secondly, is the appropriate route to resolve the 2013 setup/install?

Error:

The following error was generated when "$error.Clear();

     if (($server -eq $null) -and ($RoleIsDatacenter -ne $true) )

     {

       Update-RmsSharedIdentity -ServerName $RoleNetBIOSName

     }

     "was run: "Database is mandatory on UserMailbox.  Property Name: Database".

We have an odd issue when trying to move mailboxes to Databases with Exchange 2013 Build 847.32 on all servers affected. 

We have 2013 successfully deployed within the UK (3 servers, with a DAG) we are looking to deploy an additional 2 servers in the US across an MPLS WAN. The US has it's own DAG in the US and its own MAPI network (this MAPI network is tested routable to the UK) DAG own replication network not routable, and simply a cross over...

The Migration Arbitration mailbox is located within the UK DAG, it exists as do the other Arbitration mailboxes and everything works fine moving mailboxes across DBs in the UK...

As soon as I try and move a mailbox in the US between the two server (or even on the same server within the US) it comes up with the following error after about 20mins: Worth stressing that all migration within the UK DAG work perfectly fine... 

Error:MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionMdbOffline: Unable to make connection to the server. ‎(hr=0x80004005, ec=1142)‎ Diagnostic context: Lid: 41192 dwParam: 0x1 Lid: 63464 Lid: 34792 StoreEc: 0x6AB Lid: 51176 StoreEc: 0x80040115 Lid: 48104 Lid: 39912 StoreEc: 0x80040115 Lid: 41192 dwParam: 0x2 Lid: 55272 Lid: 34792 StoreEc: 0x6BE Lid: 51176 StoreEc: 0x80040115 Lid: 48104 Lid: 39912 StoreEc: 0x80040115 Lid: 41192 dwParam: 0x0 Lid: 49064 dwParam: 0x1 Lid: 37288 StoreEc: 0x6AB Lid: 49064 dwParam: 0x2 Lid: 38439 EMSMDBPOOL.EcPoolConnect called [length=48] Lid: 54823 EMSMDBPOOL.EcPoolConnect returned [ec=0x476][length=20][latency=796] Lid: 53361 StoreEc: 0x476 Lid: 51859 Lid: 33649 StoreEc: 0x476 Lid: 43315 Lid: 58225 StoreEc: 0x476 Lid: 39912 StoreEc: 0x476 Lid: 54129 StoreEc: 0x476 Lid: 50519 Lid: 59735 StoreEc: 0x476 Lid: 59199 Lid: 27356 StoreEc: 0x476 Lid: 65279 Lid: 52465 StoreEc: 0x476 Lid: 60065 Lid: 33777 StoreEc: 0x476 Lid: 59805 Lid: 52487 StoreEc: 0x476 Lid: 19778 Lid: 27970 StoreEc: 0x476 Lid: 17730 Lid: 25922 StoreEc: 0x476

I assume this is looking for the Migration Arbitration mailbox in the UK, across the WAN and is failing but all other features seem to work fine... In fact if I try to migrate using the Shell on a US server, it works fine so this seems to be limited to the Console...

WAN connectivity is fine, I have done a TCP any any on the ASAs to make sure there is full communication and everything else works fine... 

Any ideas as to why it seems to be failing to see the Arbitration mailbox? I t is also worth mentioning I have re-run the ADPREP /Alldomains to ensure there is no corruption within the Arbitration mailboxes...

I have probably missed something very simple somewhere but for the life of me can't think where... 

Any help gratefully received... 

I am migrating to exchange 2013 from ex2007sp3.  Prior to moving mailboxes to the ex13 server, I have been tasked with deleting messages from the Exch2007sp3 database older than 90 days. 

This is my pshell cmd so far:

Get-Mailbox -Database "private information store" | Export-Mailbox -EndDate “1/1/2015” -ExcludeFolders "\Calendar" -DeleteContent -BadItemLimit 100

I plan to change the Delete Item Retention to 0 days so that the messages are truly gone.

Does anyone have a better suggestion?

 Thanks

Hello,

We have 2 Exchange 2013 (build 712) servers in a DAG with distinct subnets. Cisco ASA in between was set to have no filtering between servers in subnet.

We cannot add database copies nor move mailboxes.

Tes-Mapiconnectivty fails with

unspaceId  : e8a087f1-6197-48df-b094-d5c93a7b6070
Server      : CLI-SRV01
Database    : CLI-MDB01
Mailbox     : SystemMailbox{376e8d54-7154-484a-a0a3-58f22d73236f}
MailboxGuid :
IsArchive   :
Result      : *FAILURE*
Latency     : 00:00:00
Error       : [Microsoft.Exchange.Data.Storage.MailboxOfflineException]: Cannot open mailbox /o=First
              Organization/ou=Exchange Administrative Group
              (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CLI-SRV01/cn=Microsoft System Attendant. Inner error
              [Microsoft.Mapi.MapiExceptionMdbOffline]: MapiExceptionMdbOffline: Unable to make connection to the
              server. (hr=0x80004005, ec=1142)

In event log:

Adding database copy fails with

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'CLI-SRV02.CLI.ch'. Hresult: 0xc7ff07d7. Error: Failed to open a log truncation context because the Microsoft Exchange Information Store service is not running. [Database: CLI-PFDB02, Server: CLI-SRV01.CLI.ch]

How can I further verify communication from CLI-SRV02 to CLI-SRV01 ?

Any help welcome

/Patrice

I am in the process of testing Exchange 2007 to 2013 migration. I have a question regarding Outlook Anywhere settings on Exchange 2013.  Sorry for the long post, question is at bottom.

My current Exchange 2007 server is setup to use Basic Authentication for Outlook Anywhere.  I have many domain joined laptops that frequently leave the internal network.  I have ISA 2006 setup to proxy Outlook anywhere and it works great; when the laptop is on the internal network, Outlook connects via RPC and NTLM as expected.  When the laptop is outside the network, Outlook connects via ISA 2006 using Basic authentication.

I have a Kemp Load Balancer setup to proxy the new Exchange 2013 server, the kemp balancer does handle pre-authentication (basic) just like the ISA 2006 server does.

I am now at the point where Exchange 2013 is installed in the environment and configured (URLs, certificates, DB's, etc).  I have not started to configure co-existence yet so all DNS still points to the Exchange 2007 server.  What I have done though is tested Exchange 2013 creating a mailbox on 2013 and tested operation by modifying HOST file on a client to point to the new Exchange 2013 server.  Outlook 2007 connects successfully to the Exchange 2013 account. 

However, this is where I run into the issue: When I change the HOST file of the test client to point to the Kemp Load Balancer to test operation, Outlook will no longer connect, but instead will provide an endless password prompt!  So I look at the Outlook 2007 Outlook Anywhere settings and it has the Proxy Authentication settings set to NTLM and not basic which explains the issue.  If I change to basic, Outlook can then connect just fine through the Kemp Proxy.

But of course once I simulate the client being back on the internal network by changing the HOST file back to point to the Exchange 2013 server, autodiscover then changes the Outlook Proxy Authentication type back to NTLM!  I would then have to manually change back to Basic when not on the internal network!

TLDR:

My question is this:  How can I setup Exchange 2013 Outlook Anywhere to use NTLM inside the network and Basic Outside the network like is done in Exchange 2007?  Or can you only use one authentication method?

What is confusing me is I can see an Internal Authentication method and an External Auth method in Exchange 2013 outlook anywhere settings but it looks like I can only change External Authentication method.  Outlook 2007 configures itself via Autodiscover to use the Internal settings. 

thanks

Hello everybody,

I'm upgrading from Exchange CU7 to CU8, I got a DAG with two servers.

I did an upgrade friday of the first server of the DAG : no problem, it works well.

I tried to upgrade my second server this morning and I'm blocked during the installation : "Step 8 of 17 : Languages", it's at 0% for about 1h now.

What could be the problem and the step to do in order to fix this ? Or have I just to wait ?

Thanks,