Hello,

We are using Exchange server 2003 on Windows Server 2003 SBS. We have decided to migrate to cloud and use codetwo office 365 tool for migration due to its public folders support.

The migration tool requires SP2 on the server 2003 and due to some reasons which can not be fixed without a repair installation (we do not want to mess with it or stop it), we can not update the windows.

We decided to try a scenario that includes setting up a windows server 2003 on a virtualbox and installing exchange 2003 with the same server name.

We use ntbackup to backup the data and I used this backup to restore the mailbox store and public folder store (with and without Log Files). I followed the instructions in http://www.ciaops.com/storage/tech-docs/NTbackup%20exchange%20recovery.pdf. The problem occurred when I tried to mount the either mailboxes or the public folders at the last step (error id:c1041724). I have tried solving it with the Microsoft support information but I have neither the issues of free space on harddisk nor runningeseutil /p command on the system.

I would like to get some help about how I can do this migration successfully.

Recently I built two Exchange 2013 servers, CAS & mailbox and added them to my existing 2010 organization.  Now, people who HAVE NOT been migrated to the 2013 mailbox server are not getting an updated OAB.  Those on 2013 are getting an updated OAB.

Besides the obvious answer to hasten the migration to 2013, why aren't the 2010 mailbox users not getting an updated OAB?

Thank you,

Chris

Hi,

We are currently in a coexistence between Exchange 2010 and Exchange 2013.

We have migrated around 20 pilots and have a question regarding outlook provider.

EXCH is still mapi.company.com (used in legacy environment, CASArray was mapi.company.com)

EXPR is set to msstd:mail.company.com (mail.company.com is our new proxy server bound to a HLB)

Shall we clear everything or just EXCH used for legacy MAPI/RPC?

I have successfully performed a staged migration for a few users. However, they have each been plagued with different issues along the way. Currently, I am attempting to complete the migration of two users to Exchange 365 and have gotten to the last step, which is executing the PowerShell script Exchange2007MBtoMEU.ps1. This script fails at the first step, which is Disable-Mailbox. The error message I receive is:<o:p></o:p>

Disabling Mailbox<o:p></o:p>

A positional parameter cannot be found that accepts argument '-DomainController'.<o:p></o:p>

+ CategoryInfo : InvalidArgument: (:) [Disable-Mailbox], ParameterBindingException<o:p></o:p>

+ FullyQualifiedErrorId : PositionalParameterNotFound,Disable-Mailbox<o:p></o:p>

I have added the -DomainController parameter in just about every conceivable fashion, but have gotten this message every time. In turn, this causes the remainder of the script to fail.<o:p></o:p>

I really need to get this migration completed, as having an on-premise server and Exchange 365 is proving to be difficult.<o:p></o:p>

Thanks so much,<o:p></o:p>

Randy<o:p></o:p>

Hi All,

I have an exchange 2007 organization with 2 exchange sites. Below is a diagram of my current infrastructure.

From the above setup:

• Exchange is published to the internet on site A
• Exchange servers in site B route mail through site A, they also depend on DNS server at site A
• All users on both sites have the same email address type (user@richard.com)

Going forward, I want to upgrade this infrastructure from exchange 2007 to exchange 2013. This is what I intend to achieve after the up;

• Maintain the 2 exchange sites
• Send emails from either site independently

I have had to upgrade from exch 2007 to 2013 for a single exchange site. I however am not sure how to upgrade in the case of different exchange sites.

I will appreciate a step by step guide or pointers on the options I have + how to proceed. So far MS has not been forthcoming with any online doc or resource for this type of upgrade.

I assume this will be a lengthy discussion .. :)

Regards,

Richard

..forever is just a minute away*

Anyone know if the SMTP checkbox is required on the Certificate configuration in 2013?

Hey there,

Can somebody please explain to me why I need to set Outlook-Anywhere on my legacy (2010) servers if I'm not using Outlook Anywhere externally in the org and don't intend to? Keep reading that it's a must so that 2013 can proxy requests, but not really sure why it would need to proxy requests if I didn't want to allow OA externally (and going through 2013 CAS).

I'll also add that the only namespace I've cutover is Autodiscover. I have around 2000 mailboxes migrated over from 2010 on to 2013 and I don't really see any problems (still a good thousand on 2010). Not sure if I was supposed to point rpcclientaccessarray records at my 2013 cas, or what advantage that would give. 2010 Exchange mailbox users can connect to 2013 mailboxes when given access (presumably due to Autodiscover). Everything just seems to work.

So please, if someone could tell me the error of my ways or reaffirm that everything's going according to plan I'd really appreciate it. Apologies if my questions are a little diffuse!

Joe

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.

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ).  I have one 2010 edge server and one 2010 ht,cas,mailbox server.   I have added a 2013 server and started working on configuring virtual directories.  This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.

My issue is the edge server is already passing inbound internet mail to the new 2013 server.  I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox users never receive.

Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?

And why is it delivering to a server with now mailboxes on it yet?

Thank you for any help

dean

Hello,

When I am using the command  c:\Exchange2013\>Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms on my domain controller I am receiving the error below:

Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.

Performing Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis                                     COMPLETED
 Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareA
D'. No Exchange 2007 server roles have been detected in this topology. After thi
s operation, you will not be able to install any Exchange 2007 servers.
 For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms
.exch.setupreadiness.NoE12ServerWarning.aspx


Configuring Microsoft Exchange Server

    Organization Preparation                                  FAILED
     The following error was generated when "$error.Clear();
        initialize-ExchangeConfigurationPermissions -DomainController $RoleDomai
nController

" was run: "Active Directory operation failed on domain.com
. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521D0, problem 4003 (INSUFF
_ACCESS_RIGHTS), data 0
".

I am using an admin account with full rights. Could you give me any advice what might that be? 

Thank you in advance

Hi,

I am working on our Exchange 2010-2013 migration and have come upon an issue after migrating test mailboxes. After migrating a mailbox to the 2013 database I am able to open it in OWA but when I try to open it via Outlook I get the error message "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)". I also get the same message when I create a new mailbox in the 2013 database and try to open it.

I have deleted and recreated the profile on the client. When I create the profile and let autodiscovery configure the information I get a message that the Ex2013 server is not available and the window comes up allowing me to enter the server and mailbox name. If I enter the Ex2013 server name I get the same error whether I enter the hostname of the server or the full DNS name. When I enter the Ex2010 server name it accepts it and converts it to the DNS name of the Ex2013 server but Outlook will still not open.

Both servers are single servers hosting all the roles. The Ex2010 server is using an internal certificate using the internal DNS. When I originally set up the Ex2013 server I did the same thing but have since purchased a SAN certificate based on our public DNS and installed that. The 2 names on the certificate are webmail.(xxxx).com and autodiscover.(xxxx).com. I was getting certificate errors on machines and now I have the SAN certificate that seems to have solved that problem.

I have a feeling I might have 2 problems, 1 with the autodiscover settings and another with the mailbox looking at the 2010 CAS rather than 2013. After doing some research I'm still a little lost in how I move forward on this one. Any help would be appreciated.

Peter Haase

We are currently running Exchange 2013 CU6.  We have multiple application servers relaying bulk mail thru our 4 EX servers. 

We would like to bring up a dedicated exchange server to handle the delivery of smtp application relay mail only.  What would be the steps involved?   

I'm fairly sure the issue is related to the fact that I had installed Exchange server 2013 CU1 on a Windows server 2012 box, and then uninstalled it. I then installed Exchange Server 2013 SP1 after rebuilding the servers to 2012 R2.

When I try to install a Mail App I get the error "Exchange Server doesn't support the requested version.".  I don't see any correlated errors in the event logs to figure out what exactly is going on.  If I use the powershell commandlet get-app to see what apps are available for a user I get the same thing.

I do have Exchange Server 2010 SP3 servers in my domain that I will eventually be migrating off of.  If anyone can give me some pointers of where to look for what might be broken I'd really appreciate it.

Hi,

We have 1 cas server and 2 mbx servers in a DAG outlook anywhere for internal works flawlessly. We do not use autodiscover externally yet so we set them up manually.

When i use test exchange connectivity and i use the CAS server as servername to connect it gives me the error message:

Attempting to ping RPC proxy mail.domain.com. 
  RPC Proxy can't be pinged. 

 Additional Details 

A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: a932b166-cb19-4feb-b751-f98c4c549279
X-CasErrorCode: MailboxGuidWithDomainNotFound
Persistent-Auth: true
X-FEServer: EXCH-CAS
Content-Length: 0
Cache-Control: private
Date: Fri, 27 Dec 2013 00:29:32 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

However only when i specifically use the MBX server which holds the active copy of the mailboxdatabase it connects properly without errors. But the casserver should use active manager to see which server holds the active mailboxdatabase automatically doesn't it? I have recently updated to CU3 I have no errors in the eventlogs of both the casserver and the mailbox servers. It doesn't matter which kind of authentication i set in Outlook Anywhere also it doesn't matter wether or not i set the EXCH and EXPR settings of set-outlookprovider. I have tried reinstalling the RPC over http feature and tried resetting virtual directories of the casserver already.

Will this be fixed when i start using autodiscover?

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?

Hi,

This is my Folder to Mailbox file, migrating public folders from 2010 to 2013:

"FolderPath","TargetMailbox""\","Hierarchy-PF""\IPM_SUBTREE\Office1","Office1-PF""\IPM_SUBTREE\Office2","Office2-PF""\IPM_SUBTREE\Office3","Office3-PF""\IPM_SUBTREE\Office4","Office4-PF"

All these PF mailboxes live in a dedicated database. But only the mailbox DB containing Hierarchy-PF is growing and my initial migration (New-PublicFolderMigrationRequest / Step 5 in the technet article) is over 50% percent complete. This mailbox is going to be over 300GB big and I gather the limit is 100GB, I'm sure that can be exceeded without problems, but I had several different reasons splitting the mailboxes and data the way I wanted above. 

Questions:

1. How do I achieve the end result I want? Do I need to add a \ to the end of the office1-5 ipm_subtree perhaps?

2. Is there any problem with me stopping the existing migration, deleting that request/mailbox/DB and starting over?

Thanks.

Good afternoon

I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.

According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.

'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'

http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx

Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary site and I would like to keep that traffic to the replication network I have configured.

Any insight would be helpful.