Inplace Upgrade of Exchange 2010 on SBS 2011 to Exhange 2013

Is it possible to upgrade exchange 2010 that is on SBS 2011 to Exchange 2013?
George Zugg

No 'In Place' Upgrade.
You can move exchange to a new server running 2013.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Similar Messages

Upgrade From Exchange 2010 SP1 to SP3 - Schema Upgrade Question

Hello,
We're currently running Exchange 2010 SP1 in our environment and want to upgrade to SP3. I just had a couple of questions related to preparing AD for this new SP that I was hoping that someone could answer.
Setup
We have a single forest with two domains within it (A and B for example). The schema master is in Domain A but this domain doesn't contain any Exchange 2010 servers. Domain B contains our 2010 CAS and Mailbox servers.
Both domains have Windows 2003 SP2 domain controllers.
I understand that before I proceed with the upgrade to SP3, I first need to update the AD schema on our schema master. I was planning on doing the following :
Log onto an existing Windows 2008 R2 64 bit "member" server in domain A (containing the schema master) with an account which is a member of the Schema Admins and Enterprise Admins groups.
Run SETUP.EXE /PrepareAD.
Do I need to also run SETUP.EXE /PrepareDomain on domain A as well or does the /PrepareAD sort this out ?
I was then going to turn my attention to domain B (which contains the 2010 CAS and Mailbox servers) and do the following :
Log onto an existing Windows 2008 R2 64 bit 2010 Mailbox server with an account which is a member of the Domain Admins and Enterprise Admins groups.
Run SETUP.EXE /PrepareDomain
Is this the correct procedure to follow ? I assume that I can then go ahead and start to upgrade the Exchange 2010 SP1 servers in the following sequence :
CAS\HUB Server(s)
Mailbox Server(s).
Clarification on the AD upgrade steps would be appreciated.
Thanks
Mark

This has all the info you need:
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
Prepare Active Directory and Domains
and
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
Note: There is no harm in simply running setup/PrepareAllDomains.
You should break out each Prep step since you have multiple domains:
setup/PrepareSchema
setup /PrepareAD
setup /PrepareAllDomains
you can run all of these from the same DC you run the setup/PrepareSchema step!
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

TS3899 I have upgrade my to iOS7 and my company recently upgrade to Exchange 2010. My emails are not synching to my inbox. I can see all of my sent items. I have already deleted the account 3 times but this did not fix the inbox problem.

I have upgrade my phone to iOS7 and my company recently upgraded to Exchange 2010. My emails are not synching to my inbox. I can only see my Sent items. I have already deleted the account 3 times but this did not fix the inbox problem.

You need to have a different Apple ID for each of the other devices.

Planning on upgrading from Exchange 2010

Exchange 2010 sp3, 2008 R2 domain level
my AD and Exchange are all on VM. if i make a snapshot of all my Exchange 2010 servers, upgrade them to 2013, made a mistake, can we still go back to Exchange 2010 as if nothing has happened? i mean from the users point of view.
or will upgrading to Exchange 2013 do some changes in AD that going back or restoring the image snapshot of Exchange 2010 will not be possible anymore?

chances are you wil have big issues when you will try to use the SNAPshots recovery. see below.
http://thoughtsofanidlemind.com/2011/03/18/be-careful-with-vm-snapshots-of-exchange-2010-servers/
Exchnage 2013 does many changes to AD/Schema. Please see below.
http://technet.microsoft.com/en-us/library/bb738144%28v=exchg.150%29.aspx
http://technet.microsoft.com/en-us/library/bb125224%28v=exchg.150%29.aspx
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

CRES html email attachments not working after upgrade to Exchange 2010

We have just upgraded from Exchange 2003 to Exchange 2010. No other changes have been made to our network. No changes were made to user workstations. Now when users receive emails from Cicso Registered Envelope Service the HTML file attachments seem to be damaged. It seems as if Exchange 2010 is stripping part of the HTML attachment. The final error is "Incomplete Payload". Please let me know if you have any suggestions.

I'm sorry that you're having problems. Can you answer these questions so that we can better help you?
What "Adobe update" are you referring to? Adobe Flash Player? Adobe Reader? Something else? (Adobe produces countless products/services, so we need to know what got updated on your computer.)
Are you using the Adobe Send service? Note that you posted your question in a forum that's used for suggesting new features for that service.
Can you attach other files to emails, but not just PDFs?
What email program are you using?

Transport service does not start automatically after upgrade to exchange 2010 SP2 from Exchange 2010 SP1

Hi,
I am trying to upgrade Exchange 2010 SP2 from SP1, but Transport service does not start automatically.
Tried manually start services, it started successfully but again goes down within few seconds automatically.
Reboot server. but no luck.
Any help.
MD

Hi,
I recommend you use event viewer to check if there are any relate event logs. This may help us to find the cause.
In addition, as Amit mentioned, Exchange 2010 SP2 isn't supported by Microsoft, I think upgrading to SP3 is a much more sensible approach.
Thanks.
Niko Cheng
TechNet Community Support

Questions about upgrading from Exchange 2010 RTM to Exchange 2010 Service Pack 3

I am preparing to perform an maintenance upgrade on our current Exchange 2010 Server, to Service Pack 3 (and any post-SP3 roll ups), but I have a couple questions about the process.
Current Exchange Server details:
Exchange 2010 Standard
Version: 14.0 (Build 639.21) - from Exchange Management Console
Version: 14.0.702.4000 - from Outook client
Active Directory forest and domain levels: Windows 2008 R2 native
The questions I have are:
1. Can I assume that because it's version 10.0.702.4000 I am on Exchange Server 2010 RTM Update Rollup 4?
2. Can Exchange 2010 Standard RTM be patched directly to Service Pack 3, or would I need to perform incremental patches (i.e. SP1, SP2, etc.) before going to SP3?
3. Do I need to manually perform the AD domain schema prep before applying Service Pack 3, or will the Service Pack 3 update process automatically handle the modifications of the AD schema?

Hi,
Here are my answers you can refer to:
1. Firstly, I’d like to explain , we can use connection status to check our Exchange server version from Outlook client:
http://office.microsoft.com/en-in/outlook-help/determine-the-version-of-microsoft-exchange-server-my-account-connects-to-HA010117038.aspx
And I check my version from both EMC and Outlook client. It’s same.
2. We can directly update RTM version to SP3 , and the update will take an additional 30 minutes or longer per database.
3. Since Exchange 2010 SP3 makes updates to the Active Directory schema, we need prepare AD domain schema. However, it will automatically prepare AD and the domain when you install the update.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Error upgrading form exchange 2010 to exchange 2013

Hello,
I have Exchange 2010 sp3 running on win server 2012 R2 sp1 standanrd. I would like to upgrade to exchange 2013 and I read that installation of exchange 2013 is coexistent with exchange 2010 already installed. But When I try to install exchange 2013 I keep
getting this error :"Exchange server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer to recover this Exchange server." But after closing set up the server is still running
fine.

Hi,
Based on my research, the issue can occur when the Exchange server object already exists within Active Directory.
Thus, I’d like to confirm the following information:
1. Does your new Exchange 2013 server have the same server name with the previous one?
2. Have you change your Exchange 2010 server name to legacy.domain.com?
Here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/20bab6f7-56e6-49b9-94df-48707fb915f7/installation-errorfresh-install-on-a-fresh-clean-server-2012?forum=exchangesvrgeneral
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Upgraded to Exchange 2010 now outlook 2013 can't connect externally

Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
Any suggestions?
ICHC

Hi ICHC,
Just as Ed said, we should create new rule on TMG during the upgrading.
Found an blog for your reference:
Upgrade from Exchange 2007 to Exchange 2010 - Part II
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software of information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 mac outlook 2011 external

Hi there,
We have Exchange 2010 autodiscover working internally/externally on a Windows desktop Outlook 2010.
However for Outlook 2011 on a mac, this only works internally and not externally.
On mac with Outlook 2011, i put my email address, select User Name and Password for Method and select configure automatically.
I then get the prompt for allowing redirectiong to
https://webmail/autodiscover/autodiscover.xml , i click allow.
It fails to configure automatically.
i then manually enter the server as https://webmail/ews/exchange.asmx but it still doesnt work. Ive even tried putting in our domain controller into the directory settings.
I've turned logging on outlook 2011 and it seems to connect into our enviornment, i can see our Exchange partition in the logs:
/o=org/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=clientaccessarray</
It picks up our domain controller, our public folder server, all the correct EWS URL's eg OOF, OAB, UM.
But for whatever reason it keeps failing with this error in the log:
Outlook Exchange Auto Configure: Testing external autodicover settings: BAD
any help appreciated.
thanks

Hi,
I recommend you refer to the following article to troubleshoot the issue:
http://www.officeformachelp.com/outlook/exchange/autodiscover/
Troubleshooting
Where Autodiscover services are either partially or incorrectly configured, users may experience the above from their mail client indicating they are being redirected to a different server, which may not exist or may be inaccessible. This can happen when
an external DNS entry points to an internal server that is not accessible via the Internet. Administrators can either:
Correct the Autodiscover settings on the network to properly direct mail clients to the correct server (preferable).
Disable Autodiscover for the Exchange account in the mail client itself.
To disable Autodiscover in Outlook for Mac run the following AppleScript command in AppleScript Editor.app:
tell application "Microsoft Outlook"
set background autodiscover of exchange account 1 to false
end tell
Exchange administrators may also need to test their external Autodiscover settings during setup or to troubleshoot connectivity issues. Microsoft has provided the
Exchange Server Remote Connectivity Analyzer tool for them. This is a secure Microsoft website that will test a company’s Autodiscover settings and provide feedback about network and Exchange settings.
Thanks.
Niko Cheng
TechNet Community Support

Migrate from Standard 2003 domain with seperate Exchange 2003 to SBS 2011 - possible? how-to?

Hi there,
I am currently planning on replacing two servers (one server 2003 standard (DC) and one server 2003 standard with exchange 2003) with a single machine running SBS 2011.
I already did several migrations SBS 2003 to SBS 2011, SBS 2008 to SBS 2011 - and I am wondering if the same can be done from 2003 Standard with separate exchange server 2003 to a single SBS 2011. Technically I can see no reason why this shouldn't work -
but so far I have been unsuccessful in finding guidelines or at least some success-stories from other users.
Did anyone do something like that? Any caveats I have to be aware of? Or is it supposed to be flawless as the SBS to SBS migrations I did so far?

Hi,
From the problem description, I understand that you would like to migrate Exchange server 2003 on Windows Server 2003 to SBS 2011.
At first, I would like to clarify one thing. Microsoft doesn’t have the official documentation towards this scenario. And Microsoft doesn’t
recommend dealing with that.
I noticed that there are two servers in your organization. One is Windows server 2003 for DC; the other one is Exchange server 2003. So it can’t
be the same as the documentation (Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server
2003).
I got your key point that you would like to know the detailed procedures (HOW TO). I suggest that you could visit the
SBSmigration.com to get further information you need. Since it’s not the Microsoft official method,
please do the test before your put it into your production environment.
Regards,
James
James Xiong
TechNet Community Support

Upgrading to Exchange 2010 SP1

When I'm upgrading Exchange 2010 to SP1, I get to tthe Hub Transport Role and it errors out with the following messsage:
Summary: 8 item(s). 3 succeeded, 1 failed.
Elapsed time: 00:08:15
Language Files
Completed
Elapsed Time: 00:04:40
Restoring services
Completed
Elapsed Time: 00:00:01
Languages
Completed
Elapsed Time: 00:02:59
Hub Transport Role
Failed
Error:
The following error was generated when "$error.Clear();
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
        " was run: "There should only be a single RMS Shared Identity user. Found CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=corporate,DC=internal and CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,OU=migrate,DC=corporate,DC=internal.".
There should only be a single RMS Shared Identity user. Found CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=corporate,DC=internal and CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,OU=migrate,DC=corporate,DC=internal.
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:00:34
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled
I haven't been able to find anything on the web regarding this error, so any help would be appreciated. We used to ADMT to migrate users into a new domain, but what it looks like to me (and I'm sure I'm wrong) is that the same user is set up in migrate
OUT as the regular Users Container.
What am I missing???
Thanks in advance.
Jeff

Hi,
Please try to use ADSIedit to check if you have two federated email account. You may need to delete the double one.
Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
Click Start, click Run, type adsiedit.msc, and then click
OK.
Locate the Default Naming Context node, and then locate to the
CN=Users container.
Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
Delete.
If that is not help, then I recommend y ou to remove all those two federatedemail account and then create a new one.
Rerun the Exchange Server 2010 Mailbox role setup application.
Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
Regards,
Xiu

Exchange Upgrade from exchange 2010 to SP3 - error

Organization Preparation
Failed
Error:
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")"was run: "There was an error while running 'ldifde.exe' to import the schema file
'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file:
'C:\Users\dimallick\AppData\Local\Temp\ldif.err'".
There was an error while running 'ldifde.exe' to import the schema file
'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file:
'C:\Users\dimallick\AppData\Local\Temp\ldif.err'
Elapsed Time: 00:00:01
Preparing Setup
Cancelled
Stopping Services
Cancelled
Languages
Cancelled
Remove Exchange Files
Cancelled
Preparing Files
Cancelled
Copy Exchange Files
Cancelled
Language Files
Cancelled
Restoring services
Cancelled
Languages
Cancelled
Hub Transport Role
Cancelled
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled

Hi,
Have you checked DareDevil's suggestion? Have you resolved this issue?
If there is any update, please feel free to post here for further research.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Upgrade share point 2010 web application to share point 2013 with BI solutions.

HI
we have sharepoint portal web application ( publishing enabled , Annonymous access for internet users)
and BI dashboards also we published in this portal.
1 ) so for content db upgrade to 2013 we will follow db attach method, but what about BI pointers list,dashboards list
it also be upgrade with content database.
2) now the BI dashboards connected to SQL Serve Analysis server 2008 r2 datasources, so after upgrade ,
we need to be must upgrade these SSAS datasources to SSAS 2012 ?
adil

Given you aren't using PowerPivot for SharePoint, you can continue using SSAS 2008 R2 for your cubes and data connections. BI dashboards, Lists, and so forth are just SharePoint content, and they get upgraded when you migrate to 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SBS 2011 and upgrading Exchange 2010 to enterprise

Hi All,
We have A client running exchange 2010 on sbs 2011.
The client would like to upgrade to exchange enterprise so in place archiving can be used.
Can someone tell me if this can be done with our current install - and what it is I need to purchase to allow it do be done.
As I said above its exchange 2010 running on SBS 2011. Outlook 2013 and 2010 is used.
I'm sure this has already been asked at some point, but i just need a clear answer of what my next step is.
Thanks in advance.

Hi:
You need to purchase Enterprise CALs and key in the quantity and license number:
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx
You only are required to do this for the users that want/need the additional features.
Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

Inplace Upgrade of Exchange 2010 on SBS 2011 to Exhange 2013

Similar Messages

Maybe you are looking for