Hi,

I have got one Exchange 2013 production Server with Mailbox and Client Access Roles installed.

My goal is to migrate this server to another one in a different network (different IP) with the same version of Exchange without have any downtime.

I need to consider DNS, Active Directory migration as well.

What is the best method to perform this task?

Any suggestions that might help would be appreciated.

Regards,

Tarek

I see no selection for Exchange Server 2010, even on the Legacy page, so I will ask a question here.

I have Time Warner Hosted Email. They use  Exchange Server 2010 . ( server name  exchange.manage-cloud.local )

I have a problem they cannot fix for over 2 weeks. It goes like this.

I have an email account that existed for about 1 year. Say the email address is  "A"

The person was replaced with another person whose email address I want to be "B"

I changed the primary email address for the account to be "B".

And deleted the "A" address from the account.

The credentials were all updated to the new persons credentials.

In Outlook 2010 when I now send an email to the "B" address it shows me that I sent it to the "A" address, in the "TO" column.

The only time it shows the correct address is when I turn OFF    "Cached Exchange mode".

With "Cached Exchange mode"  ON, it shows the now defunct address "A".

When I look at the Offline Address Book I still see the  "A" address,  NOT the "B" address.

When I look at the Global Address Book, it is correct "B" is present, "A" in gone.

I have updated the Offline Address Book over and over again, every time Time Warner has said the problem is fixed.

I always update using the  Full Details selection.

I check the dates to see that it really downloaded. 

When I use Notepad to open the "udetails.oab" file, in the Offline Address Book folder, I always

can "FIND" the defunct email address "A". 

I never can "FIND" the now current email address "B".

They do not seem to be able to correct the problem.

Navisite is the company that runs the email system for them.

Any idea as to what they could be forgetting to do ?

Topology

• 2007 Hub Transport server
• 2007 Mailbox server
• x2 2013 Mailbox servers
• x2 2013 Client Access servers
• 2013 Edge Transport server (non-domain joined)
• Edge transport server is located inside a DMZ (port 50636/25 is open between this server and the MB servers)

My organization recently attempted to cutover into co-existence with Exchange 2007 and 2013.  One of the first things we did was create the edge subscription between the edge transport and mailbox servers.  Subscribing 2013MB1 worked fine but when attempting to join 2013MB2 to the subscription (used the config file generated and used with the 2013MB1) it failed, I believe the error was failed to lease, can't recall the exact wording.

My question is do I need to create a new subscription file on the Edge Transport for each mailbox server?

For co-existence to function properly, do I need to create an edge subscription between the edge transport and the 2007 mailbox server, is it even supported?

Also, after creating the edge-subscription I am unable to see or modify its configuration in the ECP.  Are there specific ports that need to be open or is this typical behavior?  Currently, there are ports open from Edge Transport into another DMZ that hosts an RODC so, if need be, I COULD join it to the domain but our security guy doesn't really want it to be domain joined.

I see no selection for Exchange Server 2010, even on the Legacy page, so I will ask a question here.

I have Time Warner Hosted Email. They use  Exchange Server 2010 . ( server name  exchange.manage-cloud.local )

I have a problem they cannot fix for over 2 weeks. It goes like this.

I have an email account that existed for about 1 year. Say the email address is  "A"

The person was replaced with another person whose email address I want to be "B"

I changed the primary email address for the account to be "B".

And deleted the "A" address from the account.

The credentials were all updated to the new persons credentials.

In Outlook 2010 when I now send an email to the "B" address it shows me that I sent it to the "A" address, in the "TO" column.

The only time it shows the correct address is when I turn OFF    "Cached Exchange mode".

With "Cached Exchange mode"  ON, it shows the now defunct address "A".

When I look at the Offline Address Book I still see the  "A" address,  NOT the "B" address.

When I look at the Global Address Book, it is correct "B" is present, "A" in gone.

I have updated the Offline Address Book over and over again, every time Time Warner has said the problem is fixed.

I always update using the  Full Details selection.

I check the dates to see that it really downloaded. 

When I use Notepad to open the "udetails.oab" file, in the Offline Address Book folder, I always

can "FIND" the defunct email address "A". 

I never can "FIND" the now current email address "B".

They do not seem to be able to correct the problem.

Navisite is the company that runs the email system for them.

Any idea as to what they could be forgetting to do ?

I have an onsite exchange 2013 that I am starting to migrate to exchange online and have reached the stage of running the Hybrid setup wizard.  This is the first hybrid setup that I have carried out. 

The current set up is as follows (set up before I joined) in that the internal domain name is company-name.co.uk and the external domain and email domain is companyname.co.uk.  The external and internal autodiscover is configured to use the companyname.co.uk URL.

The hybrid wizard has completed with the follwoing error:

HCW8057 - office 365 was unable to communicate with your on-premises Autodiscover endpoint.  The Office 365 tenant is currently configured to use the following url for autodiscovery queries: http://autodiscover.company-name.co.uk/autodiscover/autodiscover.svc/wssecurity

My question is this: Is it ok just to manually change the URL that the office 365 tenant is using to the correct autodiscovery url?

thanks in advance.

Hi,

For testing purposes I'm setting up an Exchange 2013 environment and now I'm trying to install CU 8 (also for testing purposes) but it's not working. When I just start the executable, I get the following error:

"The upgrade patch cannot be installed by the windows installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch."

When I unpack the installer and try to run setup via an elevated command prompt, using:

Setup /m:upgrade /IAcceptExchangeServerLicenseTerms

I get the following error:

"Exchange Server 2013 requires .NET Framework 4.5 or later. Download it from..."

While this Framework is already installed.

I'm currently having Exchange 2013 SP 1 version 15.0.847.32

Thanks already for the help!

I recently learned our Exchange 2013 server is on CU 11 which is a year old.

CU 15 is the most current update, is it possible and safe to install CU 15 over CU 11??

Is there anything I should know or do before running this update??

Thank you, Tom

Just wanted to confirm the below information is still current for Exchange 2016 for patching a 12 node single dag cluster. 

Patching Scenario – Medium Sized Deployment

This is a slightly larger environment – a single DAG with 4 or more servers in the DAG, all located in one location. Let’s use a 6-member DAG for our example this time. Refer to this diagram for this example:

Also note that for this example, we’re going to say that we have designed this DAG to support two concurrent failures. This means that if we take two servers out of actively hosting mailboxes for patching, by having three copies of all databases, we are assured that we can continue to provide email services. It is possible to modify this solution to only take a single server out of service at a given time, and that is a perfectly acceptable solution – this is just an example presented here for discussion.

1. Ensure that your replication is healthy and all copies are up to date.
2. In our example we are going to patch two servers at a time, starting with Server 5 and Server 6. 
3. Activation block Server 5 and Server 6 so that a failure at this time won’t activate copies of the mailbox databases on those servers.
4. Perform a switchover of all databases away from Server 5 and Server 6 to the other four servers in the DAG.
5. Drain-stop all connections to the CAS on Server 5 and Server 6, and then remove them from the load-balanced array
6. Patch Server 5 and Server 6.
7. Add Server 5 and Server 6 back into the load-balanced array, drain-stop all other servers and remove them from the load-balanced array.
   1. Notice that for a short period, we have both upgraded and not-upgraded servers in the load-balanced array. This is not an issue, because we still have all mailboxes on the not-upgraded mailbox servers.
8. Remove activation block from Server 5 and Server 6, activation block Server 3 and Server 4, perform the switchover of all databases from Server 3 and Server 4 to the other four servers, patch Server 3 and Server 4 and add them back into the load-balanced array.
9. Remove activation block from Server 3 and Server 4, activation block Server 1 and Server 2, perform the switchover of all databases from Server 1 and Server 2 to the other four servers, patch Server 1 and server 2 and add them back into the load-balanced array.
10. Remove activation block from Server 1 and Server 2, and redistribute your databases evenly across all three servers.

Impact(s) of this process:

• For a period of time, you will be running with a possibly lower availability stance than normal operating conditions. You only have 2 servers providing CAS services until you have patched those other servers and added them back into the load-balanced array. (If you only have 4 servers in the DAG, this might not be the case.)
• In the case where you have very high numbers of users in this physical location, it is possible that you would introduce a performance impact on CAS services, because of the reduced number of Client Access servers in service.
  • Think about the situation where you have 8 or 10 servers in the DAG in this physical location, and you have only patched 2 servers. In that case, those 2 servers could probably not handle the load of all users under full production load. But, you typically won’t be patching during a “full production” time of the day – you’ll have a maintenance window that you will be working in, and users will know to have a lower expectation of availability and such. As long as you understand this and are willing to accept this risk, this is fine, but you should almost certainly make sure that you document this case and make sure that it really is acceptable!
  • The other way to think about this is to make sure that the two servers you bring back into the load-balanced array have enough processing power and memory to support the entire load. This is probably the best engineering solution for a highly available Exchange 2010 environment, but it does have a cost associated with it just like everything else in HA. If I were going to recommend a solution, this is how I would recommend it – make sure you have enough processing that if you end up in a production environment on two upgraded servers, that they can handle your full production peak load.

https://blogs.technet.microsoft.com/exchange/2010/07/22/patching-the-multi-role-server-dag/ 

Good Morning,

We are deploying Exchange 2013 CU 14 as a hybrid server to replace the existing Exchange 2010 hybrid that is in place at the moment. As part of the Exchange 2013 installation, I need to prepare and update the AD schema for the additional attributes required by Exchange 2013.

I have a process detailed on how this will play out but have questions around using snapshot in VMware as a recovery method.

The forest contains three domain controllers and the DC upon which the changes will be made is the least utilised and will have replication inbound and outbound disabled prior to running the PrepareSchema and PrepareAD switches on the Exchange setup.exe.

My question is whether the snapshot would be a supported method of rolling back the DC in the event of the schema update causing corruption? The forest contains services such as System Centre which are sequence sensitive and my concern is that by rolling back the snapshot, we may introduce problems with USN's and sequence sensitive processes. There will also be BMR, System State and Service Database backup's taken immediately before but I'm ultimately trying to avoid having to invoke forest recovery by hopefully using the snapshot.

Hi,

I have an environment in which each user mailbox is configured with a PST file as the default delivery location for his\her emails. Each user's PST file is saved on his\her home drive on the file cluster. We will be doing exchange migration from 2007 to 2013. Now how can I do the mailbox migration alongside with the PST? Do I need to import first for all users their PST files into their current exchange  2007 mailbox then do the move or there is other way? We have about 900 mailboxes.  

Hi everyone,

We have successfully migrated our mail server to MS Office 365 and changed our DNS records successfully. Now we want to delete our on-premises Exchange server and leave SBS as a file server only ( We also want to keep using the remote web workplace) So I have the following quesions.

1- How to backup the databases to external drives before deletion? we have 2 .edb files one for all the inboxes (60GB) and one for the public folders (12GB)

2- What's the best way to delete Exchange 2007? from Add/Remove programs directly?

3- I want to make sure that everyone will still be able to use remote web workplace after deleting, how to do that?

I appreciate your help for my "very basic" questions in advance,

Hello All....I need few pointers with respect to Hosted Exchange Environment.

1.  Is Hosted Exchange Supported in Exchange Server 2016?

2.  Any recommendations for Control Panel for both Administrators as well as Customers?

3.  Any link to official/unofficial documentation that I can utilize?

4.  Any blog/article/link to help with the designing aspect?

5.   Any blog/article/link to help with the capacity planning?

6.  Any blog/article/link to help with the hardware sizing?

thanks in advance

Hi All,

IP Less DAG witness folder is not created

used this below command to create IP less DAG, the command was successfully run

New-DatabaseAvailabilityGroup -Name MBX-DAG02 -DatabaseAvailabilityGroupIPAddresses ([System.Net.IPAddress]::None) -WitnessServer DAGWitness2.domain.com -WitnessDirectory C:\DAG02WitnessDir

on witness server we already added exchange trusted subsystem group into local administrator group

when try to check folder on Witness server at given path the folder is not available

so we tried to set the same path again by running the below command

Set-DatabaseAvailabilityGroup MBX-DAG02 -WitnessServer DAGWitness2.domain.com -WitnessDirectory C:\DAG02WitnessDir
then also witness folder is not created 

anyone help on this what else need to check and how successfully create witness share                                                               thanks in advance

Regards, Kesavan K M. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi All,

Good Day!!!,

Recently we are install new set of exchange servers in Site2 and created DAG02.

still we are in migration phase from Exchange 2007 to 2013 at site1. After install new set of exchange servers we are getting more on more email queue in 2013 servers .

Next hope try to connect internet

Attached image for further understand.

How can we solve this email generations and how to clear all.

thanks in advance,

Regards, Kesavan K M. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi all,

            Exchange 2007 to 2013 batch migration job, all seemed to go fine.. there were a few thousand corrupt items in one specific folder that were known about - these items were skipped - all other items completed successfully according to the GUI, powershell and the generated reports.

Post migration, we did some basic checking, everything looked fine.

After two days, the client contacted us to let us know some contents were missing..... and while the majority of content appears to be there, the are a couple of folders which are empty. The database is also approximately 14GB smaller in 2013 than it was in 2007. The foldercount is the same....

Given there were no errors, im a bit baffled as to why there are items missing.

The only odd thing that happened on this part of the migration was that the logs, even though circular logging was enabled, grew to 50,000-ish logs. Once I saw that, I ran a backup, flushed the logs, then circular logging seemed to be able to "keep up" again.... with the logs growing up to approx. 100, then back down to 80 etc. and repeat for the rest of the migration.

This seemed strange at the time, but once the logs flushed, I didn't think anything more of it. Could it be possible that these logs were waiting to be written to the database - which is why they grew instead of over-writing, and flushing them effectively lost data ? (that's not my understanding of how exchange databases work....  but I cant think of any other plausible explanation)

We upload HD pictures to exchange using set-userphoto cmdlet.
However, exchange and lync still use blurry 96x96 AD attribute photos.
I check photos with different exchange utilities -> HD photos are there.
Get-userphoto also retrieves HD photos.
I may access photos with this URL's in all resolutions

https://mail.domain.com/ews/Exchange.asmx/s/GetUserPhoto?email=user@domain.com&size=HR648x648
https://mail.domain.com/ews/Exchange.asmx/s/GetUserPhoto?email=user@domain.com&size=HR240x240

Dear all,

We have an exchange 2013 server deployed in our environment and recently i came across a situation where my IP address was blacklisted due to which our emails were dropped. When i checked with our security team they informed that my exchange domain/server is used by spammers to send emails to outside and inside company.

How can i prevent the spammers use my server/domain to stop spamming.(Also i have checked that our server is not open relay when i tested with mxtoolbox)

Please do help in configuring my exchange to prevent spammers using my domain name.

Thanks in advance

Hello,

we want to migration archived data around (160 TB) from Enterprise Vault to native exchange 2010. what is the easiest way to migrate this huge data? Can we do in this way;

1. Modify the EV Archiving policy from for example archived older than 1 month to archived older than 1 year. in this way, is it possible that the 11 months (as we change the policy from 1 moth to one year mean the policy will not be applicable on the difference which is 11 months) newer items should be moved back to Exchange Server and let exchange server archive them later on according to exchange archiving policy. Is it possible or no?? please guide me.

Thanks in advance.