Hi!

I have a design implementation question. We are a small firm with 80 AD users, 100 mailboxes, DB store is 200 gigs and all on Exchange 2007 (Virtualized connecting to a SAN), but growing rapidly. Also, we currently have two sites in Chicago and New York(Exchange 2007 server in NY). We would like to upgrade from 2007(all roles installed on a VM server ESX 5.5 server) to 2013. Should we virtualized the Exchange 2013 or should they be physical servers? Also, since the servers will be in separate sites will I need a Load Balancer in both location? Also, should I split up the roles since we have two locations running the both roles on both servers. For example below:

1 Chicago server-CAS/Mailbox Role
1 New York server-CAS/Mailbox Role

Should I have the Chicago users connect to the Chicago Server? And the New York users pointed to the New York Server? Currently everyone connects to the mail sever in NY. Any advice or comments would be appreciated.

Thanks!

Hi,

We are currently exploring full envelope journaling service using Exchange 2013 with Sharepoint 2013 eDiscovery suite for ALL internal and external messages for a largish enterprise ~40K mailboxes and need to accurately plan storage for the dedicated Journal servers; we have used the standard messagestats powershell script to get send / receive and average message size and have some valid metrics to utilize however there is next to no actual guidance on how to plan storage for journaling published?

My question concerns which metric to use - unique send and receive OR total send / receive figures; I have reached out to some of my default Microsoft contacts and dug into how FE Journaling works under the hood and my understanding is that it is total send / receive for every message would be more valid to plan against?

Any guidance would be great!

We have to migrate Mailbox in a Cross Forest environment (from Exchange 2007 SP3-RU10 to Exchange 2013).For Account coesistence we already migrate Users/Group via ADMT, excluding Exchange Attribute.

The steps are:

• Enable-MailUser
• Prepare-MoveRequest.Ps1
• New-MoveRequest.

Before to Upgrade to CU6, the migrations steps described above worked fine (Exchange Server 2013 SP1 (alias CU4))

After ugrading we alway get the following error running New-MoveRequest:

New-MoveRequest -Identity "02909" -Remotelegacy -RemoteCredential $RemoteCredentials

-TargetDeliverydomain "old.mycompany.com" -TargetDatabase MBOX2A -RemoteGlobalCatalog "odl_dc.mycompany.local"

–DomainController “new_dc.newdomain.int”-verbose

New-MoveRequest -Identity "user200" -Remotelegacy -RemoteCredential $RemoteCredentials

-TargetDeliverydomain "new.mycompany.com" -TargetDatabase MBOX2A

-RemoteGlobalCatalog "old_dc.mycompany.local" -verbose

Recipient '4309a8a0-9edf-4ad1-991b-89d8d75a1c28' isn't a mailbox.

+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemotePermanentException

+ FullyQualifiedErrorId : [Server=mailbox1,RequestId=f3bd2350-a9dc-49d1-8cf6-f5564a47bd26,

      TimeStamp=17/11/2014 01:45:59]

      [FailureCategory=Cmdlet-RemotePermanentException]

            17FEEA0A,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

   + PSComputerName       : mailcas1.newdomain.int

I have found the below article which is the exact issue that I am having.

https://support.software.dell.com/migration-manager-for-exchange/kb/133684

Is there anyway to get HotFix on this problem. I cannot wait two months fo CU7.

In addition downgrade (e.g. Uninstall CU6 and re-installa SP1) is quite complicate and hard.

Hi Everyone,

   We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server.  We set up a trial of Office365 and linked our test domain to that account.  The test domain mimics our current domain, but ends in .net instead of .org. We set up a test Exchange 2013 server with a few database servers.  Internally, we can connect without issue (Outlook).  We mapped our test CAS to face the Internet, and can access what we need without issue.  We also set up the Hybrid configuration on both the Exchange 2013 and Office365 servers.  We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.

Now, here is the issue:

We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues.  We migrated a mailbox today to our on-premise server, but upon doing so, can no longer connect to, or add, that mailbox to Outlook.  When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes.  This also goes for distribution groups, conference rooms, etc.

I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above.  We NEED to make sure that when we batch migrate, the users DO NOT lose connectivity to their accounts.  We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally.  As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference. 

Any thoughts on this?  Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations.  Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.

Any help would be MUCH appreciated.  Thanks!

Dan

I searched TechNet en the exchange sites: nowhere to be found: the description en uses for the cmdlet "repair-migration"

It looks huge with loads of parameters.

like this one : would this rollback the previous migration of a user: ?

Repair-Migration -Revert -UserId <MigrationUserIdParameter> [-Force] [-Organization <OrganizationIdParameter>] [-Partition <MailboxIdParameter>] [<CommonParameters>]

A bit more explanation would be appreciated...

We have multiple sites all running their own Exchange 2010 servers with all Archive mailboxes hosted in our primary datacentre.

We are now migrating those sites to new Exchange 2013 servers, and the Primary Mailboxes are being moved to local Exchange 2013 servers, and the Archives are being moved to Exchange 2013 Archive Databases hosted in the primary datacentre.

For example, user is in Site B with Archive hosted in Site A. New Exchange server is in Site B. New Archive Exchange Server is in Site A.

When I instigate the move, the move request is using the MRS Server in Site B, which is moving the Primary Mailbox nicely. However, and here is the big issue, it is moving the archive in Site A, via Site B, back to Site A.

That is a real issue when the network link between site A and site B can only provide about a 10MB link, due to everything else running on the link.

How can we get the Primary to use an MRS Server in its own site, and the Archive move to use an MRS Server in its own site, without doing the move via the MRS Server in a different site?

We can't change the MRS Server setting using the set-moverequest and we can't move the Primary with one command and the Archive with another as they complain about being on 2010 or 2013 only, not one on each.

Please help, this is getting to be a big issue

Thanks

Microsoft Certified IT Professional Server Administrator

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

This is a new, new, installation of Windows Server 2012 R2 Essentials followed by Exchange 2013, all on a single server that is also the DC, in a lab environment.   This is to replace an existing SBS2000 installation in a small business.  Server 2012 setup without any significant issues.  The first pass at Exchange 2013 resulted in "access denied" when attempting to access the Exchange Management PS and login credentials failure for Exchange EAC (ECP).   After manually adding the installation Administrator to a number of the Exchange security groups, I was able to access Exchange Manager.  I checked that there was a mailbox associated with the Installation Admin ID, attempted to reset passwords and a number of other things to no avail.  I uninstalled Exchange (what a pain).

I reinstalled Exchange.  As with the first time, no prerequisite errors and no installation failure alerts.   Again, I could not access Exchange Manager (access denied) or the EAC (login credentials failure).   This time, I was not able change the security group permissions to gain access to Exchange Manager.  Again, checked about everything there was to check on the web and found a reference to Exchange possibly not installing correctly due to lingering entries from the first install.   As I could not access Exchange Manager to perform the uninstall prerequisites, I attempted to manually delete it (nothing to loose at this point), but made the anticipated mess.

Wiped the RAID and started over with a clean sheet install of Server 2012 Essentials-OK.  Progressed in the Exchange install prep to "Prepare Active Directory and Domains" (http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx) and stopped when I could not detect the confirming ADSI entries of AD prep set forth at the close of the TechNet document.

I methodically stepped through the install procedure and again received no prerequisite failures or installation failure alerts.  I examined the install logs and found no errors, either.

Any words of wisdom?

Hello,

A few weeks ago, we ran the necessary /prepareschema /preparead /preparealldomains commands to get our Exhange 2010 Org ready to install Exchange 2013 SP1.  When we tried installing the first server today, we get an error:

[11/14/2014 23:42:02.0466] [1] [REQUIRED] The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.

We verified the ObjectVersion of both the Forest (15844) and Domain (13236), and it appears to be consistent with what you would expect for 2013 SP1.

Anybody have any ideas what could be wrong?

Thanks.

Hello

I have virtualized Exchange 2013 CU2 on vmware environment. I need update server to newest Cumulative Update. Today is CU6 the newest CU. On Microsoft download Website is technical information that CU6 include all earlier updates. My question is that I should install first SP1 (CU4) and then CU6 or just install CU6? What problems I should anticipate?

Hi Experts,

We are planing to deploy exchange email server (Exchange Server-2013 Multi-Role servers) in our HQ (contoso.com) and 4 Edge Transport in other 4  client development sites(client1.com, clinet2.com, client3.com and Client4.com) so that applications running in HQ can send emails to respective client development sites domain using edge transport. Development sites are using external email address (mail.clinet1.com and so on). There is no requirement of incoming mail on Edge in Client site because they have compete hosted email solution. Just our Edge transport in client will process the mail received from HQ and will forward to Client's  External email address.

I would appreciate if you can help me to get answer for these queries.

Do you think this conceptual design is possible? Exchange solution in HQ and Edge transport in Client site and that Edge will forward emails to External Domain using send connector for  restive client's domain? 

What secure (Only secure) port we need to open on Edge so that It can talk to External Email servers to deliver emails? 

If we don't want to expose our Multi-Role exchange severs in HQ to Internet , do you think Exchange server in HQ  should be capable for incoming emails using one additional EDGE or still need to expose CAS services in HQ. We need Outlook, OWA and Active Sync as well for HQ (contoso.com).

What secure port we need to open in case of CAS server? 

I have updated our entire 2013 environment to CU6 except for one server that throws the following error on step 2 of 7.

I have ran the update as an Administrator and have rebooted the server several times.  I have also tried to uninstall Exchange on that server but it continues to try and recover the installation of CU6.

Please advise.

Greetings

I am upgrading the Exchange 2013 environment and want to run the Jetstress tool before putting the servers in production.

I have 2 Mailbox servers as member of DAG.

Please provide me inputs on below mentioned points:

1. As per microsoft recommendations, the Jetstress tool should be run before installing Exchange Server.

However, i have already installed Exchange server and done the CAS Virtual Directories configuration.

Is it possible if i can run Jetstress after installing Exchange Server.

2. Now, the Exchange is already installed. DO i need to run Jetstress on all DAG members.

Thanks in advance.

Is it possible to have multiple 365 federated trusts?

trying to separate  on premise to 2 x 365 subscriptions.

Or can I migrate half then delete the hybrid and setup another to a different 365 subscription and do the other half?

***Don't forget to mark helpful or answer***

Dear Experts

My requirement is to place one Edge Transport in Each client site so that Edge transport  in client site can forward emails to client's mailbox domain (Only client domain and mailboxes are on different hosted environment) to Internet and another requirement is  Edge Transport in Vendor site must be able to send/receive emails from Internet for Vendor's domain Only.

Same time in each site there is one Monitoring application that only uses insecure ports (pop/smtp) to send/receive emails in each client site. Monitor application has mailbox in Vendor site.

Do you thing this design is doable without any problem?

Thanks Cloudy Lynx

Moved Exchange 2013 SP1 mailboxes, system mailboxes, public folders and OAB to new server with Exchange 2013 SP1. Followed all the suggestions here:

https://social.technet.microsoft.com/Forums/en-US/1bdf67a1-ad0e-4e96-922f-3778d6bd8e98/move-exchange-2013-to-new-virtual-server-including-settings?forum=exchangesvrdeploy

Problem is when we shut off the old exchange server services, no mail flows and can not reach OWA. It seems as though the servers are "coexisting". I say coexisting because all the firewall rules point to the new server, all the settings in ECA/ECP point to the new server, all the DNS records point to the new server. We need to be able to run exchange on the new server without the old server running. Is there something I left off?

Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:

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;

          Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");

          Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;

          }

          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: "Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information: General Error.

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)

   at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)

   at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)

   at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)

   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>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.

Any ideas how to solve this?