Dear Friends,

I would like to know the pre-installation process for a new branch of any office let's say a college, what are the parameters and requirement do i need to fullfill before to set up the network and which CLASS ip should i use etc.

Please provide as much as information in this regards it urgent.

1. How to confirugre a web server.

2. How to configure a bakcup server.

3. How to set the proxy server and how the other network devices are needs to be configure.

4. How to set firewall, do i need to off the firewall of all the server withing the intranet of college(example).

Regards, Ravi Kumar

I receive this error when Installing Cumulative Update 1.

Error:
The following error was generated when "$error.Clear();
            if ($RoleIsDatacenter -ne $true)
            {
            if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
            $sysMbx = $null;
            $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
            $dispName = "Microsoft Exchange";
            Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
            $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
            if ($mbxs.Length -eq 0)
            {
            Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
            $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
            if ($dbs.Length -ne 0)
            {
            Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
            $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
            {
            Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
            $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
            }
            }
            }
            else
            {
            if ($mbxs[0].DisplayName -ne $dispName )
            {
            Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
            Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
            }
            $sysMbx = $mbxs[0];
            }

            # Set the Organization Capabilities needed for this mailbox
            if ($sysMbx -ne $null)
            {
            # We need 1 GB for uploading large OAB files to the organization mailbox
            Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -MaxSendSize 1GB -Force;
            }
            else
            {
            Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
            }
            }
            else
            {
            Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            }
            }
        " was run: "Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear();
            if ($RoleIsDatacenter -ne $true)
            {
            if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
            $sysMbx = $null;
            $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
            $dispName = "Microsoft Exchange";
            Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
            $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
            if ($mbxs.Length -eq 0)
            {
            Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
            $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
            if ($dbs.Length -ne 0)
            {
            Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
            $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
            {
            Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
            $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
            }
            }
            }
            else
            {
            if ($mbxs[0].DisplayName -ne $dispName )
            {
            Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
            Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
            }
            $sysMbx = $mbxs[0];
            }

            # Set the Organization Capabilities needed for this mailbox
            if ($sysMbx -ne $null)
            {
            # We need 1 GB for uploading large OAB files to the organization mailbox
            Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -MaxSendSize 1GB -Force;
            }
            else
            {
            Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
            }
            }
            else
            {
            Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            }
            }
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".

Can Anyone help me figure out how I can resolve this error?

Hello,

I've recently introduced an Exchange Server 2013 in a single Exchange 2007 Server environment.

While most things seem to work out of the box, I have some issues:

When I use the Get-CalendarProcessing cmdlet on a mailbox hosted on the Exchange 2007 server or go inExchange admin center > recipients > resources, I get this error message:Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException: Cannot open mailbox /o=<org>/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=<server>/cn=Microsoft System Attendant. ---> Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227)

Another problem is that, when I navigate toOutlook Web App > People and try to search the directory, I get this:An error occured while searching. Please try again.

Same problem there:New mail > To: > Search Contacts and Directory: Can't connect. Please try again later.

And last but not least: I can’t connect Outlook to the Exchange 2013 server, unless I add the "DS Server" entry in [HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider]

Any help would be highly appreciated!

Hi everyone,

I have a single Exchange 2007 VM as well as 4 x Exchange 2013 SP1  servers in a single organisation. Exchange 2013 SP1 servers are also VM's, with 2 x CAS and 2 x MBX and a single DAG. All of these existing servers use a single namespace for CAS services of mail.domain.com. In public and internal DNS that name resolves to the IP address of the Exchange 2013 DAG IP.

I'm replacing the above 5 VM's with 4 physical servers running 2013 CU7. In the architecture I'm using IIS Application Request Routing (ARR) as a clustered load balancer and reverse proxy. This will be used for all HTTP(S) traffic. (OWA, RPC/HTTPS, OAB, Autodiscover etc.).

e.g. oa.domain.com (Outlook Anywhere), outlook.domain.com (OWA), oab.domain.com etc. A key point in this design is that Outlook Anywhere will go via the reverse proxy / load balancer,including internal traffic.

The new Exchange 2013 servers are in place, as is the load balancer / RP, databases created etc. At the minute the virtual directories for the new servers have their URL's / Hostnames set to the Exchange 2007 / existing Exchange 2013 single namespace. So Outlook Anywhere, OWA, ECP, OAB etc. all have their URL's / Hostnames pointing to mail.domain.com (which resolves to the DAG IP of the current / legacy Exchange 2013 environment).

The next steps are to get the CAS traffic flowing over the new Exchange servers - which is a case of setting the virtual directories for the relevant services to point to the new per-protocol namespaces. So I'll set OWA to usehttps://outlook.domain.com/OWA.

My question is.... Do I do this ONLY for the new Exchange servers, or should I also update the URL's that the existing Exchange 2013 / 2007 servers use? For example:

Current Settings

Old Exchange 2013 Server 1
External OWA Virtual Directory: https://mail.domain.com/OWA

Old Exchange 2007 Server:
External OWA Virtual Directory: https://mail.domain.com/OWA

New Exchange 2013 Server 1:
External OWA Virtual Directory: https://mail.domain.com/OWA

New Setting

External OWA Virtual Directory: https://outlook.domain.com/OWA

Question

I need to set the NEW Exchange 2013 servers External URL for the OWA Virtual Directory to behttps://outlook.domain.com/OWA. But do I need to set this on the existing / legacy Exchange 2007 and Exchange 2013 Servers also? Or do I leave them, migrate the databases and then decommission the servers in due course without worrying about updating the URL's and hostnames on them?

In particular, what do I do about Outlook Anywhere? Again, I need to update the Internal and External Hostnames for the RPC Virtual Directory to point to the new name - oa.domain.com - but do I set this only on the NEW servers, or on all servers?

Any help greatly appreciated.

Big thanks in advance!

Steve

I'm having autodiscover issues with the new Exchange 2013 server. I rechecked the authentication and its fine. I rechecked my certificate with SAL and it has autodiscover.mydomain.com in it. Services are assigned to the certificate.

However, when I run the remote test for outlook connectivity it states its having trouble with autodiscover.

My main domain used for all services is m1.mydomain.com and I have an A record out there on DNS servers on the internet. Do I need one also for the the autodiscover.domain.com?  The test states it cannot The Microsoft Connectivity Analyzer is attempting to test Autodiscover for mymailbox@domain.com  testing autodiscover failed.   The Autodiscover service couldn't be contacted successfully by any method.  Also all other tests failed. What am I missing? Do I need to configure the autodiscover area in virtual directories? Currently when I click on the wrench there is no information in there. None in the external address. is something suppose to be there?

We are planning to upgrade Exchange 2010 to SP3 with latest rollup updates. We have 3 HUB/CAS servers and 3 mailbox servers in a DAG. We are not quite confident if we can install Rollup updates right after applying SP3 to all servers. We think we probably wait a few days after applying SP3 to identify any potential issues before move on to the rollup updates . However SP3 is quite buggy and it requires patching as soon as possible. What's your best practices and experience? Thanks in advance !

This posting is provided AS-IS with no warranties/guarantees and confers no rights.

I am trying to reinstall exchange 2013 and I have been getting the errors below in the exchange setup log. I have been going through a lot of knowledge bases and the suggestions hasn't been helpful.

[02-09-2015 08:42:24.0144] [2] [ERROR] Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0144] [2] Ending processing set-mailbox
[02-09-2015 08:42:24.0144] [1] The following 2 error(s) occurred during task execution:
[02-09-2015 08:42:24.0144] [1] 0.  ErrorRecord: Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0144] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] [ERROR] The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          {
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispName )
          {
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
          }
          }
        " was run: "Database is mandatory on UserMailbox.".
[02-09-2015 08:42:24.0159] [1] [ERROR] Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] 1.  ErrorRecord: Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] 1.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow)
   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[02-09-2015 08:42:24.0159] [1] [ERROR] The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          {
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispName )
          {
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
          }
          }
        " was run: "Database is mandatory on UserMailbox.".
[02-09-2015 08:42:24.0159] [1] [ERROR] Database is mandatory on UserMailbox.
[02-09-2015 08:42:24.0159] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___1DEE95834DBA48F2BB211C2FB6765A5A Component=EXCHANGE14:\Current\Release\Client Access\Unified Messaging
[02-09-2015 08:42:24.0159] [1] Setup is stopping now because of one or more critical errors.
[02-09-2015 08:42:24.0159] [1] Finished executing component tasks.
[02-09-2015 08:42:24.0206] [1] Ending processing Install-MailboxRole

The basic symptom is this: The PF migration appears to work perfectly but when trying to assign a user to test the new folders it still attempts to connect to the old folders even though the users's DefaultPublicFolderMailbox is set to the new server. Connection status in Outlook still shows a connection to the 2007 server.

I'm using the TechNet PF migration article: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

This is a single server migration from 2007 SP3 UR10 to 2013 CU5 Standard. The migration of mailboxes is complete with no errors and I'm trying to move the 100mb in public folders over to the 2013 server. Using several guides but once I've had problems I've switched to using the "standard" TechNet article as follows. I am creating only one PF mailbox since there are 10 folders and 100mb in data roughly. My Mailboxmap.csv file shows only the following:

"TargetMailbox","FolderPath"
"PFRoot","\"

The entire PF migration steps work flawlessly with no errors that I can see at all. I've rolled back and ran this process a half dozen times now to see if I've missed something.

I'm stuck on Step 8: Item #2 testing the migration from the test user in Outlook.

I've assigned the DefaultPublicFolderMailbox properties as that Item #2 shows me to do and if I use Get-Mailbox (test user) | Select DefaultPublicFolderMailbox command I see the new PFRoot mailbox listed as the default. However, the test user can't access the public folders at all. If I look in EAC I still see no public folders listed at all. If I use this guide:

http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part2.html

It shows after setting "Set-Mailbox PFRoot -PublicFolder -IsExcludedFromServingHierarchy $False" I should be able to see the public folders in EAC. However, I can see the PF mailbox (PFRoot) but no public folders at all in EAC.

Where do I go from here? Even though I have no errors I don't want to complete the migration because the test isn't working.

Jeremy Regehr

Dear all,

for some reasons we are in Exchange Server Coexistance mode that is 1 Exchange 2003 Server and 2. Exchange 2010 servers.

We have CAS array(node-1 And Node-2) and DAG in place , but the problem is whenever my Node-1 is down emails are getting stuck routing group connector on legacy server and Exchange 2010 to Exchange 2010 emails are working.

oppositly

when my Node-2 is down everything works.

how do I FIX this ?

TheAtulA

This weekend we moved our mail server. After many troubles with copying we managed to get it running on the new host (ESXi5.5).

For the mail server we opened ports 80, 443, 135 and 25. All dns records point to the new IP. I also recreated the recursive lookup zone for the new internal ip.

Yet, mail flow is not working while I can connect and login on owa and connect with Outlook from both inside and outside the network. Internal mail, even from and to the same address is not working.

This is the first time we moved a mail server and we might have missed something. Any ideas where to look?

Hello!

We are on an hybrid deployment with some users on Exchange 2013 on-premises and others on Exchange Online (Office 365 E3 plan). We have enabled photo sync (PhotosEnabled attribute) in the organization relationship, both on-premises and online, but while Exchange Online users can see all profile pictures, Exchange on-premises can see only on-premises pictures.

It also looks like that online users can see only a low resolution version of on-premises users' pictures.

Do you have any idea how to troubleshoot or fix this, please?

Hi,

I have a 2 exchange 2013 servers in windows 2012 OS both servers are configured with DAG one is active and the other one is passive

I moved the 5 databases in other drive and it was successful but no matter what I try one of my database in passive server show "ContentIndexState: FailedandSuspended" 

I tried to manually copy the database file from the active server to passive server but still the status is the same. Tried to reseed the database and wait for at least 1 day to change the status from FailedandSuspended to healthy but still no changes happened.

I tried to delete the afftected database in passive server and copy the healthy database from active to passive again and do the reseed procedure but still the problem is the same. Please help. Thank you! 

Hi Everyone,

I'm hoping others on this forum have some thoughts on whether it is worthwhile deploying only the Exchange 2013 CAS role for the purposes of SMTP relay.

When using Exchange Online, most guides suggest installing the IIS virtual SMTP component in an environment if SMTP relay is required. This is simple enough, however Microsofts future plans for IIS vSMTP look uncertain.

So my question is, has anyone deployed only the Exchange 2013 CAS role in an environment solely for the purposes of SMTP relay?
One pitfall I'm thinking about is the autodiscover service. Once the CAS role is installed an AD SCP is created, so this could cause potential problems.

I'm not concerned about having to extend the AD schema, or the cost. It's the other technical bits :)

cheers!

I'm getting this error and can not receive email from anywhere.
However I can send email OK. Its the receiving part.

I uninstalled the old exchange and put this into production and now can't receive mail.

All connectors are the default ones out of the box. All roles are on one system.

I'm consolidating users from companyA to companyB.  CompanyA will keep it's domain name and be added as an Accepted Domain in companyB's exchange environment.
CompanyA has autodiscover and webmail DNS pointing to there exchange server.  I'm not sure if I'm correct or not and would like a little guidance but what I think I want to do is modify the
certicate and remove webmail and just have autodiscover and import the certificate into the companyB's exchange? Also, point CompanyA's DNS record for autodiscover to CompanyB's exchange server?
Does this sound accurate?

The final goal is to have CompanyA be able to have Outlook Anywhere working as it did before and webmail through CompanyB

All users from CompanyA are created in AD, SMTP addresses modified to the accepted domain and they can send and receive email however they can't do the above and I believe that is because of the
autodiscover?

The exchange environment is 2013.

Hi,

We're in the process of planning a migration to Exchange 2013 from a legacy 2007 system that currently has no external access for security reasons. The new system will allow ActiveSync connections for mobile devices to sync their mailboxes but I'm not sure about the steps required to provide this feature.

I've used the "Exchange Server Deployment Assistant" and can follow the steps to getting the new 2013 servers installed but am not sure if we can allow access to their 2007 mailboxes via ActiveSync from the 2013 CAS servers?

The document seems to suggest that the 2013 CAS will re-direct ActiveSync connections to the 2007 mailbox server but I'm not sure if this happens externally (in which case we'd need to "open up" the legacy servers) or internally which would be the preferred method?

Any ideas?

Cheers for now

Russell

Hi everyone,

I am currently experiencing issues when running the HCW, which throws the following error at the very end:

[02/06/2015 15:09:21]    INFO : Task='Configure MRS Proxy Settings' Step='NeedsConfiguration' START
[02/06/2015 15:09:21]    INFO : Session=OnPrem Cmdlet=Get-WebServicesVirtualDirectorySTART
[02/06/2015 20:19:07]   ERROR : System.Management.Automation.RemoteException:An IIS directory entry couldn't be created. The error message is The remote procedure call failed.
                                . HResult = -2147023170
[02/06/2015 20:19:07]    INFO : Session=OnPrem Cmdlet=Get-WebServicesVirtualDirectory FINISH Time=18586211.3298ms
[02/06/2015 20:19:07]   ERROR : Subtask NeedsConfiguration execution failed: Configure MRS Proxy Settings
                                Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.
                                An IIS directory entry couldn't be created. The error message is The remote procedure call failed.
                                . HResult = -2147023170
                                   at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors)
[02/06/2015 20:19:07]    INFO : Task='Configure MRS Proxy Settings' Step='NeedsConfiguration' FINISH Result=False Time=18586211.3298ms

We currently have a deployment of Exchange 2007 and 2013 servers across the world (coexistence between the two is working fine). At the moment, I am trying to configure 3 Exchange 2013 servers in London as our Hybrid servers (these servers are multi-role and also host users mailboxes).

Manually running Get-WebServicesVirtualDirectory takes ages to run as it is normal in global deployments.

Initially, Exchange 2007 servers were not members of the Exchange Trusted Subsystem group (http://support.microsoft.com/kb/2995725/en-us). However, after fixing this, the issue remains.

All requirements for hybrid are in place (certificate, virtual directories on the hybrid servers are configured correctly and available externally, DNS, etc). I ran the Hybrid Configuration Diagnostic tool but none of the warnings are relevant for this.

Any help is much appreciated! Thank you so much.

Best regards,
Nuno

http://LetsExchange.blogspot.com

Greetings!  We currently have an Exchange 2010 on prem environment and I have been tasked with getting us into a hybrid state with O365.  We already have the tenet portions set up, AD Sync working, etc.  My initial thought was to just use our existing Exchange 2010 servers for the hybrid role, however, upon research it appears that standing up new Exchange 2013 servers specifically as hybrid servers is the suggested route.

My main goal is to do this hybrid deployment with as little impact and change to our environment (and thus user impact) as possible.  From what I have read, I will have to change the autodiscover and ews records to point to the new Exchange 2013 servers.  Is it also the case that I will have to redirect OWA to the Exchange 2013 servers?  Is there any way to deploy Exchange 2013 hybrid servers in a way that I do not have to change owa, autodiscover, etc? 

Thanks in advance!

This posting is provided AS-IS with no warranties/guarantees and confers no rights.