Have setup a test multi-tenant environment and implemented the ABP Routing Agent as per the Microsoft guidelines in order that contact details of other tenants cannot be resolved when sending between tenants. The Address Book Policies themselves are working correctly and tenants only see their own GAL etc, however when sending to another tenant, instead of their details appearing as an external address, they are being 'resolved' and all contact information visible in Sent Items for instance. I was under the impression that the ABP Routing Agent should get around this issue? Thanks.

I'm having an issue getting EX2013 to complete a cert request. I generated the request via ECP. I hit complete request and specify the location to the publicly trusted cert (godaddy). The cert status does not change from "Pending Request" However if i connect to the cert store on the box (server 2012) I see that the cert was imported into the certificate store.

Thoughts? 

Hello,

I have recently tried to migrate a user to another database and I am having some issues. I originally was trying to migrate the user to another database but I stopped it midway and tried to create another migration batch to move the users mailbox. Now I am getting an error saying that MigrationPermanentException: Mailbox 'X' is already being moved to "Y"

Mailbox"X" is already being moved to "Y"

I have since deleted the old Migration Batch and have not been able to figure out how to fix this problem. Any help would be appreciated I am running a VM with Server 2012 and Exchange 2013

thanks in advance

We will be replacing an SBS 2003 server that runs Exchange 2003 withnew hardware. There only 12 mailboxes but some are over 2GB. We will have a new server that has Exchange 2013 installed and will also be a DC and it will have a different name and FQDN from the SBS. We will be manually creating the AD with same user names that are on the SBS.

How can we get the mail from 2003 to 2013?

We will be replacing an SBS 2003 server that runs Exchange 2003 withnew hardware. There only 12 mailboxes but some are over 2GB. We will have a new server that has Exchange 2013 installed and will also be a DC and it will have a different name and FQDN from the SBS. We will be manually creating the AD with same user names that are on the SBS.

How can we get the mail from 2003 to 2013?

Here are the list of errors it reports

Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
My user is in the Enterprise Admins group.    

Error:
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.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx

My user is in the Enterprise Admins group and it is also in the Organization Management Role

Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

I am

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

I am

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

I am

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

I am

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
I am

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

I am

Error:

You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

I am

Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have been created but have not yet replicated to the local domain.  Wait for replication to complete and then run setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

While this is showing up, I do have the Exchange objects availabe on all of my DCs in all of the sites.

Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx

Its currently at 2008 Which is the highest I can make it in my organization at this time.

Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

I'm able to communicate with all the DCs from the machine I'm attempting to install exchange on.

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

Has anyone encounterd this?  

I've run Setup /PrepareSchema and Setup /PrepareAD on the DC in the site Exchange specified.

I have installed all of the Prereqs

Here's an example of my set up

One Forest

AwesomeCompany.net -

There's Two sites

Atlanta-HeadQuarters

Atlanta-DataCenter

and Two Sub Domains

HeadQuarters

DataCenter

Exchange Machine is in Atlanta-DataCenter Site and attached to DataCenter domain.

Exchange requested the /PrepareAD and /PrepareSchema be run on a Domain Controller in the root domain that is in site Atlanta-HeadQuarters.

Any guidance would be appreciated.

Hi ,

I am currently testing a cross forest migration from exchange 2007 to exchange 2013. i do not have trust between my forest but i did set up conditional forwarding in both the source and target environment.

The Mailbox replication service does not behave as expected when i submit a new move request.

the move request : New-MoveRequest -Identity "f2867850-5e88-4f97-9efb-0b867a1fdb4b" -BadItemLimit "10" -TargetDeliveryDomain "TargetDomain" -TargetDatabase "{cbc90e5e-6124-458c-8105-464bc27d26c1}" -RemoteCredential (Get-Credential "sourcecredential") -RemoteGlobalCatalog "FQDN of source GC" -RemoteLegacy:$true

the error : "The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (15.0.775.35 caps:3F)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client."

I can ping both global catalog in the source environment and in the target from both side. nslookup and autodiscover is working as well.

MRS Proxy is enable on the exchange 2013 side and i have enable remote Powershell on both side.

i do not have any load balancer configure.

If anyone can point me in the right direction where to look it would be greatly appreciated.

thanks you

Frédéric Bédard

Hello,

I've installed Exchange 2013 in an Exchange 2007 environment.  I have Exchange 2013 servers (CU5) in 2 AD sites (US and UK) and I'm connecting with Outlook 2013 internally via Outlook Anywhere.  Our main site is in the US and secondary site is in the UK.  I've created two namespaces - mail.domain.com for the US and mailUK.domain.com for for the UK.  I've set up the OWA, ECP, OAB, Outlook Anywhere and AutodiscoverInternalUri to use these.  The names point to a E2013 server and not E2007.  I also have a second OAB generated in the UK site.  When I'm on a UK workstation, in the UK AD site and on a domain joined machine (SCP lookup), I start outlook and run the test email autoconfig, it returns the correct namespaces for EWS, OOF and UM but the OAB is pointing to the US namespace.  For example:

Availability Server: https://mailuk.domain.com/ews.Exchange.asmx

OOF URL: https://mailuk.domain.com/ews/Exchange.asmx

OAB URL: https://mail.domain.com/oab/OabGuid

UM URL: https://mailluk.domain.com/ews/UM2007Legacy.asmx

The GUID for the OAB is correct (UK OAB) but it's connecting to the US server and coming back to the UK server for the OAB.  The US databases are configured with a different OAB than the UK databases.  It looks like autodiscover is returning an internal OAB URL from one of the US servers.

Doesn't autodiscover return the OAB URL based on the location of the mailbox (UK) and the OAB GUID?  Can anyone see something that I'm missing?

Thanks

I have used a hybrid configuration for a while but have recently finished moving all mailboxes to 365 and I have also removed the Dir Sync so the authority point is 365, all DNS records point to 365 and mail flow is all directly to 365.

I have 2 on premise exchange servers that are doing nothing,

What are the steps to remove the hybrid configuration and remove these exchange servers from the domain?

Thanks

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

I went to install the CU5 update today and it fails on the step Mailbox role: transport service.

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\MFP". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   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)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Client Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   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)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

When I try to re-run the setup, it fails at the same spot. I can't use the ECP nor the Shell to remove the Receive Connector (it is just a receive connector for the MFP).

Is there any way to remove this receive connector with Powershell not working?

Hello,

When I try to launch Exchange server 2013 Powershell I got the following error:

VERBOSE: Connecting to GMS-S12EX2K13.gmsinc.local.
New-PSSession : [gms-s12ex2k13.gmsinc.local] Processing data from remote server gms-s12ex2k13.gmsinc.local failed with
the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan
Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully.
Change the request including a valid shell handle and try again. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: gms-s12ex2k13.gmsinc.local

Can someone help me please.

Thanks

Jimmy

ok  so I have a fresh build of Exchange 2013 on a new AD domain, there is no old remnants of a previous version.

I have a  send connector created:

• Specify how to send mail with this connector.

• MX record associated with recipient domain is checked

  Use the external DNS lookup settings on servers with transport roles is checked

  TYPE =SMTP

  FQDN =*

• COST=1
• Source server is properly selected and FQDN of server is entered correctly
• Manually entered DNS settings
• Forced IPv4 preference

Any suggestions?

David Sheetz MCP

Last week I used technet page to migrate our exchange 2010 public folders over to exchange 2013. I'm still new to exchange management so I'm trying to understand what to do next.

The migration move showed 100% complete and successful and now show up as a mailbox in the 2013 admin center. I thought to myself Great! I did it. So I attempted to decommission my 2010 exchange server.

I attempted to remove my public folder database in the 2010 EMC and it tells me the database still contains folder replicas.

I found a couple options as possible fixes, either to remove it in ADSI edit or delete the files in the folder. I just want to make sure doing so won't effect the 2013 public folders.

Or should I do this a different way? Thanks in advance.

We will be replacing an SBS 2003 server that runs Exchange 2003 withnew hardware. There only 12 mailboxes but some are over 2GB. We will have a new server that has Exchange 2013 installed and will also be a DC and it will have a different name and FQDN from the SBS. We will be manually creating the AD with same user names that are on the SBS.

How can we get the mail from 2003 to 2013?

Afternoon all.

So our company is going through a change of name, which means new tree domain and new exchange server infrastructure. We started installing exchange 2013 in the root domain but decided to hold off as the company was set to change name anyway. So..... Now have built the new domain and it works perfectly, ensured all the necessary preps have been done at the root domain. Installed exchange, no problems, exchange 2013 can see the other 2010 exchanges but cannot send or receive mail from them. I have created custom smtp connecters with the following settings:

http://2share.co.za/Files/ex1.PNG

http://2share.co.za/Files/ex2.PNG

http://2share.co.za/Files/ex3.PNG

And have created a front end transport connector on the EX2013 box with the same settings. The emails just sit in the drafts folder if you login to the user mailbox via OWA. It's highly frustrating.

Any idea how to resolve this, would be nice if MS could make their products a little more compatible with one another. Just saying MS.

Shaun Crosby Senior Network Admin L@W Active

Hi,

This is my third installation of Exchange 2013 server in the same forest but different Active Directory site /domain.

2 Exchange 2013 server are in one active directory site /domain i.e abc.xyz.com and this third server is in different AD site /domain i.e def.xyz.com.

To my surprise i am missing Microsoft Exchange Server Auth Certificate on this server.It is there on rest two exchange 2013 servers. 

I am getting below warning message in event log due to this:

I am also getting one more error event which seems to be related to this:

Any idea what went wrong here and how to resolve it now...?

Regards,

Vishal Malhan

The error I receive occurs at 47% of the Mailbox Role: Transport Service installation.  The details of the error are as follows:

    Mailbox role: Transport service                                                                   FAILED
     The following error was generated when "$error.Clear();
          if ($server -eq $null)
          {
            set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
          }
        " was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
        'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
".

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

Also, when opening the setup log I have this:

[12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
[12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.

[12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
[12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
[12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/26/2012 17:51:25.0825] [0] End of Setup
[12/26/2012 17:51:25.0825] [0] **********************************************

I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.

http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/

http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/

Some additional information:

This is a clean installation of Exchange 2013 in a forest that has never had exchange.

The domain and forest preparations run without errors and are at functional level of 2003.

The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.

This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.

I am running the installation as an enterprise, schema, domain admin.

Thanks for your help in advance.

Upgraded Lotus Notes version into newer 8.5 it has complex functionalities. These functions are not easily graspable and it takes long time to understand, I decide to export my data into another (MS Outlook) platform, is it possible, I want new updates about conversion in cost-effective manner. And if yes then suggests me the way?