Greetings,

I am in porcess of migrating my Exchange 2007 to Exchange 2013, Please find below the scenario.

Exchange 2007    Single server solution. Not published externally, only for internal emails only.

CAS URL: mail.abc.com

Have another email system hosted with ISP :     xyz.com

Objective: Migrate from Ex2007 to Ex2013

Want to publish externally xyz.com (not abc.com), will do cutover from ISP hosted to my premises, 

MX records for @xyz.com will be pointed from ISP to on-premises, smtp domain will be @xyz.com

Will be added as accepted domain (abc.com will not be published anywhere, not even the mxrecords for abc.com will be used)

Exchange 2013

Configured 2 Mailbox and 2 CAS Server in Exchange 2013.

COnfigured NLB Unicast for both the CAS Server

DNS: Created one split DNS for xyz.com (as the default domain is abc.com) and then configured A record for mail.xyz.com pinting to CAS NLB Virtual IP.

Virtual Directories Config: I have not done any changes to Ex2007 CAS URLs, as the old namespace is no longer required. And new namespace is configured in Ex2013.

For Ex2007 server have done only change in Autodiscover internal uri to https://mail.xyz.com/autodiscover/autodiscover.xml

Have configured below mentioned URL in Ex 2013.

owa (Internal/External) : https://mail.xyz.com/owa

ecp (Internal/External) : https://mail.xyz.com/ecp

oab (Internal/External) : https://mail.xyz.com/oab

Autodiscover (Internal uri) : https://mail.xyz.com/autodiscover/autodiscover.xml

Webservices (Internal/External) : https://mail.xyz.com/ews/exchange.asmx

ActiveSync (Internal/External): https://mail.xyz.ae/Microsoft-Server-ActiveSync

Test Scenarios:

The Autodiscover resolves if put the url in Expolrer https://mail.xyz.com/autodiscover/autodiscover.xml to the xml page, which i think is fine.

But when i run test-outlookwebservices it gives the error.

Also 2013 Exchange users are not able to see OAB, it is  failing while accessing Address book. Says Outlook is not connected or Offline. 

Certainly i have misconfigured the Virtaul Directoies.

Kindly suggest if the above config is fine or any inputs will be appreaciated.

Thanks in advance.

Hi ,

I am planning to migrate exchange server 2007 to 2013 , Its simple environment exchange 207 all role are in one box and 2013 too.

I jsut want to know if this URL missing something or need any precaution rather than mentioned here.

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

<p>Don't forget to mark helpful or answer</p> <p>connect me :-</p> <p>http://in.linkedin.com/in/satya11</p> <p>http://facebook.com/satya.1000</p>

Hi all ,

I have a problem with move mailbox database :

[PS] C:\Windows\system32>New-MoveRequest -Identity 'tttviet@domain' -TargetDatabase "Mailbox Database D" -BadItemLimit 10

WARNING: When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to the destination mailbox. At move completion, these corrupted items will not be available at the destination mailbox. Mailbox 'T? Th? Thu Vi?t' is already being moved to 'Mailbox Database D'.
    + CategoryInfo : InvalidArgument: (tttviet@domain:MailboxOrMailUserIdParameter) [New-MoveRequest], ManagementObjectAlreadyExistsException
     + FullyQualifiedErrorId:7A2DAF34,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
    + PSComputerName        : exch02.domain

Please! 

Hi,

We are in need of another server in our deployment to handle the growing demand of mailboxes.

From what i understand, a DAG should be a similar server with the equavilent number of disks with the correct size?

Are a DAG the best way to go or should we have two separate servers?

I am also a bit confused about the deployment. When I install Exchange I have no option to leave it outside the current deployment..?! Will it automatically start taking on client requests?

Hello,

at this moment we are outsourcing our mail server to another company and have this infrastructure:

• Our companies domain A, where are all users accounts;
• Domain B where are Exchange Server 2013 servers with Linked mailboxes;
• There are trust between Domain A and Domain B;
• Users from domain A connecting to linked mailboxes in domain B and have mail addresses "user@domainA";

Now we would like to install our own Exchange server in our domain A and migrate all mailboxes from Domain B. So it would be cross forest Exchange 2013 -> Exchange 2013 Linked mailbox migration. 

Does there are any document, where we could find information about similar cases? Could someone help me with steps what to do, to achieve this goal?

Regards,
Nerijus

Nerijus

Hi

I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise Admins" and "Schema Admins"

in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case

I have to install exchange 2013 in windows Server 2008 r2 sp1

the functional level  2008 R2 I getting these errors please help.

Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx

Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx

Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx

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

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

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

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

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

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

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

Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

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

Exchange 2013 CU2

3 Mailbox Servers(MBX#), 1 DAG, 3 Databases and 2 copies for each database.

On my MBX3 server, the passive copy of DB01 has an Unknown content index state. All other active or passive copies have Healthy content index states on all servers.

1. Already have ContentSubmitters group with the permissions. "Netstat -a" shows the ports 3800, 3801, 3803, 3863... 

2. When I look at the folder "...\Mailbox\DB01\", I could not see any content index catalog folder with GUID.

3. When I run the command "Update-MailboxDatabaseCopy -Identity DB01\MBX3 -CatalogOnly", I get the error:

WARNING: Seeding of content index catalog for database 'DB01' failed. Please verify that the Microsoft Search
(Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There
was no endpoint listening at
net.tcp://localhost:3863/Management/SeedingAgent-6F2FD4DC-54FF-40B7-9A2A-4F40785E4CAA12/Single that could accept the
message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more
details..

4. Stopping the search services and starting them did not solve the problem.

5. I removed the copy and deleted the folder. Then I added the database copy again. But the same issue continues.

Any help?

Best Regards.

Dear,

I have an hyperd exchange server 2013 with office 365, and it's working fine

now I want to cancel the office 365 and keep just Exchange server 2013, 

what are the process steps that I need to do it,

Many thanks,

We have Exchange Server 2013 (Build 847.32) at CU4 and was put into production in 8/2014 on a Windows 2012R2 server. It has been working fine since that time but we are considering getting it updated to the latest CU9. It has all Exchange roles.

1. Is it advised to upgrade it even though there are no issues?

2. If so, can we go straight to CU9 from CU4, or do we have to install some other CUs first?

Please advise.

Thank you!

There is zero Exchange Server 2013-specific documentation on how to set this up for Exchange Server 2013.

Microsoft has posted instructions only for Exchange Server 2010 in a 2012 blog posting.   The only reference to Exchange 2013 is a note on the top of the page that says:"Exchange Server 2013 Cumulative Update 5 and later supports certificate-based authentication with ActiveSync."

http://blogs.technet.com/b/exchange/archive/2012/11/28/configure-certificate-based-authentication-for-exchange-activesync.aspx

What are the differences in steps required to get this working for Exchange Server 2013 vs Exchange Server 2010?

I am bit puzzled and frustrated with this issue I have in my lab.  I have exported my test mailboxes from my 2010 environment (other settings are minor and easily reproduced), and uninstalled 2010.  Next I went and installed 2013 RTM from TechNet.

The first time I installed 2013 the install was successful, but when the ECP came up it was just a empty browser window - it would never display.  So I thought, maybe there was something left over from the previous 2010 server.  I blew away the OS (was 2008 R2) and built a clean 2012 server.  Installed all the Exchange 2013 prerequisites, extended the Schema and installed 2013 using all the defaults in the wizard.

This time the the ECP login came up, but here is where it gets puzzling and frustrating.  I put my Admin credentials in (this account has all proper group membership that I'm aware of) and the screen goes blank for a second and then the OWA login is displayed.  The ECP never comes up again, just goes straight to the OWA login.  If I enter my credentials in the OWA login, the screen just flashes and the password field clears but doesn't login.

I have tried uninstalling and cleaning up AD and reinstalling, but the same thing keeps happening.  I can't help but think it has something to do with permissions, but I'm not sure what that would be.

On windows Server 2012 R2

Exchange 2013 instalation error:

URGENT! please help. Any help is appreciated.

I have an Exchange installation that is giving me issues. The server was migrated from an old SBS system into a standalone exchange server. All exchange services are supported by a single server.

The issue is that when an internal client connects to the server a SSL error occurs, every time. (See Below) 

Any input is appreciated.  

Some other points:

• The Active Directory is a .local domain while the Email Addresses are .com 
• A certificate was purchased for the .com domain (OWA Access)
• The Server is a member of the domain 

Hello All...

Trying to uninstall Exchange 2013 CUv2 v2. I've moved all the Mailboxes, Arbitration, Discovery, Public Folder, etc to another working server. Everything was moved over fine. Uninstall via the control panel proceeded as normal, then just failed. No choice but to exit. Now when trying to recover, and uninstall again....I cannot. I get the vague error of "An incomplete installation was detected.  Run setup to complete Exchange installation." 

Not that I want to, but tried to reinstall, but can't do that either.

I know it's a last resort and not supported, but can I just use ASDIEdit ,and manually remove the server references? If so, what is a good guide on the procedure....? I don't want spend hours pouring over setup logs and the registry if I don't have to- just want this removed from AD.

I've searched the net quite a bit on manual removal, but can't find a concise how-to...

Any help is appreciated ...Thanks

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?

I currently have a production bare metal Windows 2008 Std SP2 running Exchange 2007 (with the proper update for migration to 2013).  I have two Exchange 2013 Std CU9 servers up and running on Windows 2012 DC.  DAG is configured and working.

At one point, I created a couple of new test mailboxes on the new servers and their respective databases and connect to them without issue.  I was also able to create a couple of test mailboxes on my Exchange 2007 server, migrate and then connect to them successfully as well.  I am planning a full migration this coming weekend.  

In doing some lead work, I have managed to now create an issue with, (I believe), my virtual directories on my Exchange 2013 servers, namely Autodiscover. (NOTE: Exchange 2007 server is still working fine).

When I now try and launch Outlook, (v.2010), for a mailbox that connects to a database on the new 2013 servers, Autodiscover does not complete.  It detects the e-mail account, I get a prompt about my local certificate and I reply "Yes" to continue.  However, at the last step to "Log on to the server" I receive the error:

"The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

I can log on to this account's OWA just fine.  With that, I suspect that I messed something up with regards to the Autodiscover virtual directory.  I tried putting it back to the default and resetting IIS, but I receive the same errors within Outlook.

I was reading this article that references Autodiscover using the oldest Exchange Server within the domain.  

https://social.technet.microsoft.com/Forums/office/en-US/484604a9-d2e3-4a1b-8ac2-8d8c700e8957/outlook-does-not-connect-to-exchange-2013-after-name-change-due-to-marriage?forum=exchangesvrclients

However, this was working fine for me previously, so I'm stumped.

Any help would be greatly appreciated, and let me know any additional info needed.  Thanks.

Hello everyone.

So, my organization has some issues. My primary focus is ramping up security, and one thing sticking out like a sore thumb is our legacy Windows 2003 Server x64 running Exchange 2007. Spiceworks has identified known threats probing this server on three separate instances in the past 4 weeks.

Our exchange server, again, is currently operating on Windows Server 2003 x64 SP2 with Exchange 2007.
The goal would ultimately be Windows 2012 R2 with Exchange 2013.

The specs of the server are as follows:
Supermicro / X7DB8
8 x Intel Pentium III Xeon
16GB RAM

I know that the migration process from Server 2003 is not exactly painless. I was considering purchasing a new SSD drive, placing the drive into one of our unused workstations, doing a full install and configuration, performing a live test on the network during the weekend and then, upon success, swapping out with the primary drive on the server. I will obviously have the drivers on hand, but I am still wondering if there would be an easier way to go about doing this?

Also, does anyone have any suggestions or detailed links to the steps I can take for this migration? I have experience working with Server, but not so much when it comes to the Exchange end. The videos I have watched look pretty straight forward with the setup and Powershell procedures... just wanted to know if this would be something I could try or will we inevitably be better off forking out a massive chunk to acquire outside assistance?

Hi,

I've been asked to set up an active/passive DAG that will be on the same site, the active node will be linked to one set of storage and the passive node would run connected to a slightly slower bit of storage (they're both still fast though :)) The FSW would run on the same hardware as the active node.

The idea is the passive node could be made active during a failure/patching and used to backup straight to tape.  Could I run the passive node with dynamic ram?

Does this sound like an ok setup?

Thanks