Moving from SBS 2011 to Exchange 2013

Make sure you get a clean DCDIAG before you start any migration.

Hi fellow spiceworkers,
I am planning on migrating from SBS 2011 to 2012 r2/Exchange 2013 and having a separate 2012 R2 DC.
It has been mentioned and my understanding that it is important to raise the forest functional level (currently 2003) before installing Exchange 2013. My intention is to raise it to 2008.
Current configuration:
2011 SBS with FSMO ROLE and 2003 functional level.
2012 R2 DC.
3 x 2012 R2 DC's at various remote sites connected via VPN.
Should I move the FSMO role to the 2012 R2 DC first, wait to replicate, THEN raise the functional level or should I raise the functional level, wait for replication then move the FSMO role?
Also, would anyone have any other considerations I should take when doing this?
Thanks for any advice in advance.
Ralph
This topic first appeared in the Spiceworks Community

Similar Messages

SBS 2011 and Exchange 2013

Hey Experts,
So an associate of mine decided to do a little freelance work for a business who's requirements were;
-File Shares
-AD DS/DNS/DHCP
-Exchange Server
-SQL Server
The current server is a SBS 2003 box, with 2003 Exchange also installed. The plan was to migrate AD/Exchange to SBS 2011, however, he soon ran into a road block. Exchange 2003+ is not supported by SBS 2011, only Server 2008/2012 standard and upwards.
What should he do in this scenario?
Currently we're looking at purchasing Server 2012 R2 Standard and installing Exchange 2013. Advice?

How would we go about licensing, as far as I understand, exchange and 2012 have different CAL restrictions.
I'm not a licensing advisor.
Exchange and Server 2012 indeed have separate licensing requirements, each have a Server License requirement (for the server), and you each product also requires their own Client Access Licenses for users/devices who will be accessing the products.
You're looking at Windows Server 2012 license, and Exchange Server 2013 license, and probably 15 client access licenses for each (15 for Server, 15 for Exchange).
Windows Server 2012 specifically has a 1+2 server license. With this, you can install the Server license on a system (that's the "1"). If you enable only the Hyper-V role on the physical server, and run Virtual Machines as children in
this parent server, you are entitled to run two Virtualized instances of this same license on that hardware (that's the "2). This also applies if you are virtualized on another virtualization platform; one license for Server 2012 allows 2 virtualized
instances on the same host hardware. If you don't virtualize your workloads and you have two hardware installs of Server 2012, well you'll need two server licenses in that model. For a small business such as described, I'd virtualize every time.
Larry mentions a good point; you can enable the 'Essentials' role on the Server 2012 R2 platform that provides wizard driven interfaces for enabling Remote Web App, and PC backups from a Dashboard console. Weigh the value in this, as you will have
more work in front of you if you want to enable this and still provide remote access to email on your Exchange 2013 system (multiple external IP's and a modern firewall or the Microsoft ARR utility can address this). Generally OWA and Outlook Anywhere require
HTTPS redirection at your gateway to the Exchange server. RWA in Essentials uses the same protocol, so plan accordingly.
Hope that helps,
Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

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+

Moving from SBS 2003 to Hyper V 2012 R2 VM's

Hi Folks,
Apologies if I have posted on the wrong Forum
I will keep this brief .
My customer currently has an old SBS 2003 standard physical server. They utilize the integrated Exchange 2003 system. It now needs to be changed/upgraded due to lack of hard disk space and incompatibility between Outlook 2013 and exchange 2003 amonst other
thing.
SBS is no longer available but as the company has grown substantially in the last few years SBS would have been unsuitable anyway. The company has about 80 user accounts across 60 Computer systems.
I have decided after much research to replace the old SBS2003 system with one new Physical server running Windows 2012R2 Hyper V as the Host O/S.. I have also setup 2 Gen 1 VM's running Server 2012 standard, (NOT 2012 R2). I have then promoted one of the
VM's to be a domain controller simply by adding Active Directory Domain services role. The othe VM will be used as an exchange 2010 server .. I have the Exchange 2010 SP3 installation lying in wait on the second VM but I havent installed yet as it requires
access to domain accounts.
The new Server has about 1 terabyte of Hard drive space and 32 gig Ram. The DC has been allocated 8 gig of Ram and 500 gig of Hard drive space. The exchange 2010 VM has been allocated 12 gig Ram with 150 gig Hard drive space.
What I need now is a guide on how to get this new server installed on my existing network and removing the existing SBS2003 box.
I know i have to attach the new domain Controller VM to the existing domain and allow active directory account information etc to replicate onto the new DC VM. Apparently this can take a few days. I am unsure however at which point I connect the exchange
server to the old sbs2003 box in order to move the mailboxes.. actually I am not even sure if I ever connect the new exchange VM to the old sbs 2003 box. Would it be better to get the DC replaced first. i.e attach the DC to the existing domain.. let the active
directory info to replicate.. transfer the roles, demote the sbs2003 box?? I am concerned that the old mailboxes on the sbs2003 box will then be irretrievable..
Perhaps someone can clarify the steps in sequence that I need to follow to end up with my DC VM and Exchange 2010 VM with migrated mailboxes installed as replacement for the current sbs 2003 box.
Some other notes: Although i have used 2012 R2 for the hyper V host I have decided that 2012 made better sense for the VM operating systems due to the better compatibility with exchange 2010 in one VM and simply because of online advice on the DC VM.
Thanks in advance

This doesn't really have anything to do with Virtual Server 2005 (this forum, or even Hyper-V).
This is migration from SBS to a regular domain. Look at the SBS forums, or Exchange and AD forums for advice moving from SBS to regular Exchange and 2012 AD.
Maybe here:
http://social.technet.microsoft.com/Forums/exchange/en-US/3fae661d-1c34-4728-96ce-7eaf79af64c3/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2?forum=exchange2010
http://technet.microsoft.com/en-us/library/jj200112.aspx

Server 2012 and Exchange 2013 Migration from SBS 2011

Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
This topic first appeared in the Spiceworks Community

I recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...

SBS 2011 - Using Exchange / Static IP - Cannot send e-mails to certain domains

Hi,
Client is running SBS 2011 using Exchange to send and receive e-mails. For some reason 5 days ago they got call from clients stating they had not received e-mails from them (stpeterdeland.org). I ran the online Exchange Analyzer - (No errors). The
strange thing is the client was not receiving "NDRs". i talked with one IT admin for one of the domains. He saw our e-mails being held up by his spam filter and has since "White Listed" the domain IP (65.34.20.210).
I also ran Exchange BPA - No problems noted. Any help on this would be greatly appreciated.
Thank you,
Frank
Frank

You have your answer: spam filtering. The clue was 'no NDR', when emails disappear without trace, it is almost always because something has designated them 'spam'.
You can't really do much about this unless you know why the emails are being flagged. Possibly your contact can help here, most anti-spam systems do explain why they mark down particular emails. Spam filters use many criteria, some of them even rational.
I once found that a client's emails were disappearing because of a picture used as a signature: it was a .jpg file, and the problem was solved by substituting a .png file. That's one hint: do not include files which can carry malware, or at least not unless
zipped, preferably with a password. Unfortunately, there are not many file types which cannot include malware. Outlook drops broad hints if you try to attach certain files, and suggests you might wish to reconsider.
Another minus is the use of HTML email, which is unfortunately almost universal now. Plain text emails are less likely to get the thumbs-down, but I'm not sure if the MS webmail can even originate plain text emails. Obviously, there are certain words to
be avoided, and I won't mention any here, but many apparently innocent financial and entrepreneurial words will bump up the spam score. Multiple exclamation marks, lots of upper case, the list is endless. I was once trying to help a client's salesman set up
a VPN connection, and had my email killed by Yahoo because it contained a URL and some other networking information.
The only really certain way to find out why emails have been dropped is to ask the admin of the recipient, or of any smarthost used on the way. You do have to hope that they actually have an admin to ask...
Joe

Archiving migration from Symantec EV to Exchange 2013

Hi all,
We have a customer who has Exchange 2007 email system and Symantec EV 7 for archiving email. We need to migrate their email from Exchange 2007 to Exchange 2013 and activating Exchange 2013 archives. The customer asks to use this tool "Archive
2-Anywhere" from Archive360 to migrate archives from Symantec EV to Exchange 2013.
My question is I need to do this (migrating a user mailbox archive) in parallel with moving his mailbox to new exchange?

Search the Internet for a phrase like "Migrate Enterprise Vault to Exchange 2013". You should get some hits for ideas for third-party solutions.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Error when using super admin account to migrate from Communigate Pro to exchange 2013

Hi everyone,
We are facing issues to migrate mails from communigate pro to exchange 2013 using 'MigrateIMAP.pl' tool. Communigate pro has a super-admin account which can retrieve the mails from any mailbox but when sending to Exchange 2013, there is no such super-admin
account. I have created a user account granting it full access to all databases using the following:
Get-MailboxDatabase -identity “mailbox name” | Add-ADPermission -user <account name> -AccessRights GenericAll
Get-mailbox | Add-MailboxPermission -User <account name> -AccessRights FullAccess -InheritanceType All
The tool uses the following command: (x.x.x.x is for server IPs & mytestlist contains user accounts to be migrated)
./migrateIMAP.pl -d -I -U -s 100 -L mylog7 -e superadmin:password\<i -S x.x.x.x -f
exchangeadmin:password -D x.x.x.x -i mytestlist
The IMAP4 logs shows the following error:
2014-02-04T13:32:37.699Z,0000000000000579,1,x.x.x.x:143,x.x.x.x:47688,,1,65,34,authenticate,PLAIN cmJhbGxjaGFuZAByYmFsbGNoYW5kAEwwZ09uQDEyMw==,"R=""1 BAD Command Argument Error. 12"""
Anyone, please help me out, i've spent a whole week trying to solve this. Thanks in advance

I would suggest you go for third party tool.
One such tool is CodeTwo, it does the job and very cheap. It will get the job done is ziffy
http://www.codetwo.com/exchange-migration/
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

How to export from Outlook 2011 to Outlook 2013?

As an Outlook user of old when I bought my Mac I was keen to try out Outlook 2011 for Mac which managed to import my Windows PSTs without any issues.
However, now I have a Windows 8 machine running Outlook 2013 I want to go the other way and I don't see any easy way of doing so.
I'm hoping that someone can tell me how I export all of my mail from Outlook 2011 to Outlook 2013
without having to buy a 3rd party tool given the investment I've already made in the Microsoft platform.
Many thanks in advance.
Many thanks and kind regards, Cliff Hobbs Microsoft MVP - ConfigMgr/ SMS (2004 - Present) Owner FAQShop.com - Giving You the FAQs | http://www.faqshop.com/wp/

As an Outlook user of old when I bought my Mac I was keen to try out Outlook 2011 for Mac which managed to import my Windows PSTs without any issues.
However, now I have a Windows 8 machine running Outlook 2013 I want to go the other way and I don't see any easy way of doing so.
I'm hoping that someone can tell me how I export all of my mail from Outlook 2011 to Outlook 2013
without having to buy a 3rd party tool given the investment I've already made in the Microsoft platform.
Many thanks in advance.
Many thanks and kind regards, Cliff Hobbs Microsoft MVP - ConfigMgr/ SMS (2004 - Present) Owner FAQShop.com - Giving You the FAQs | http://www.faqshop.com/wp/
Hi,
As in my estimation, it’s not viable to export Outlook 2011 to Outlook 2013 Windows 8 without having any third party tool, somehow without any payment it is possible, by using any free trial version for limited file conversion you can try any reliable third
party tool but for multiple or unlimited Mac OLM files conversion you have to make use of a third party tool. In the midst of various third party tools it’s too complicated to find out that, which tool is reliable for making this conversion.
Or else can try manual procedure for this conversion, but its lengthy and no surety. Outlook Mac Exporter software is one of the reliable tool for exporting Mac Outlook 2011 items to PST file format. You also can try this tool and I am sure it will provide
you desiring Outcome by exporting OLM files to PST file format.
Read more through this article: http://articles.abilogic.com/39444/transfer-olm-pst-windows-outlook.html

Migration from Lotus Domino to Exchange 2013

Hi,
I need to migrate from Lotus Domino 8.5.3 to Exchange 2013, there's a tool to do it?
Kid Regards

Smart way to perform migration from Lotus Domino to Exchange 2013 is only Mail Migration Wizard software. That is affordable in cost and times saving at all just grabs it for excellent server migration.
Visit for for more info: http://www.exportnotes.com/domino-to-exchange-server.html

Migrating from SBS 2011 to Windows Server 2012R2 Standard with 365

Im looking to move SBS 2011 to Server 2012R2 standard and with a 365 migration as well.
Im thinking
BPA for AD (health check)
Add the Server2012R2 as a DC
Ensure replication
Move DHCP
Change DNS
Now this is where I get lost, now Im lost to use either dirsync or add essentials service, I have gone for standard and 30 cals with the option as I have 28 users and the essentials service would make everything quite nice for remote access and backups
etc.... however I don't know whether to just use dirsync with password replication instead ?
Currently Im aiming towards getting the dc up and running then enabling essentials on the dc but I dont know how it will effect SBS and having essentials on the same network and sync'ing people to the cloud ? So Should I use DirSync on a different server
instead to sync up to azure ?
Finally with 365 I have only ever done a migration involving an export of pst's from an exchange box and then on a new domain with new pc's and reimport the pst's on the user accounts in outlook.
However I have read when migrating to 365 was using exchange 2010 there was a application
to move everything across however you needed an ssl cert iirc ? so I dont know how it works now since the nice new dashboard upgrade (assuming the tool has been updated like dirsync)
along with the above how does AD now know where exahcnge if you use the migration app with an ssl cert and is it a case of still running the 365 config tool to configure each user to look at their mail in the
cloud ? Also is it a good idea to enable essentials from the start of the 2012r2 dc for replication top 365 or to use dirsync ?
then finally when replications is all good start transferring the FSMO roles over to the new DC and demote and remove the SBS server
I have seen (below) but i dont think it covers this scenario and I cant be the only person in this situation =\ ?
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
http://social.technet.microsoft.com/Forums/en-US/f552ef12-07a9-4f7a-bf5e-24500c3e1dc3/migrate-sbs-2011-to-server-2012-standard?forum=smallbusinessserver
http://social.technet.microsoft.com/Forums/en-US/e1d4b09f-8857-4ef6-9a80-6a906e76b688/how-to-migrate-sbs-2011-to-standard-2012-server?forum=smallbusinessserver

Hi,
Would you please let us know current situation of this issue? If any update, please feel free to let us know.
à
Currently Im aiming towards getting the dc up and running then enabling essentials on the dc but I dont know how it will effect SBS and having essentials on the same network
and sync'ing people to the cloud?
I’m a little confused with the description. Did you mean that set up DC (Windows Server 2012 Standard) and
then install the Windows Server Essentials Experience role? If so, when you migrate, please refer to the article:
Migrate from Previous Versions to Windows Server 2012 R2 Essentials or Windows Server Essentials Experience
Regarding to migrate Exchange to Office 365, please refer to following articles.
Migrate
All Mailboxes to the Cloud with a Cutover Exchange Migration
Step-By-Step:
Migrating from Exchange 2007 to Office 365
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Meanwhile, there is an additional article that you can refer to:
Manage Office 365 in Windows Server Essentials. It may help us to understand Office 365 in Server Essentials clearly.
If anything I misunderstand, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

SBS 2008 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

Migrating a customer to Exchange 2013 from SBS 2008.
Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
The customer only has a single external IP address...
So what do I do for this external DNS of legacy.customer.com?

Hi Allister -
You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
is inside AD, Ex2013 will find it.
These are the URLs you need to change in 2007/2010
ClientAccessServer
webservicesvirtualdirectory
oabvirtualdirectory
owavirtualdirectory
ecpvirtualdirectory
ActiveSyncVirtualDirectory
AutodiscoverVirtualDirectory You can read more on how to set these here:
http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
A wise man is a fool, with a good memory.

Migrating from Linux Mail to Exchange 2013

Is there any official documents of the Best Practices of migrating Linux Mail (Exim) to Exchange 2013?
I appreciate any help that I can receive. Thanks in advance.
My best regards.

Hi,
Basic on my research, I’m afraid that there is no tool for this kind of migration, we may need to start from PST file.
We can use Microsoft Exchange PST Capture to search for PST files on computers in your organization and then import those files to mailboxes in your organization, for your reference:
https://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
Besides, I find an similar thread about Migrate Exim to Exchange:
https://social.technet.microsoft.com/Forums/office/en-US/0ff095c4-2334-4dd6-8d08-bbee1c98867e/migrating-from-linux-to-exchange-server-2010-question?forum=exchangesvradminlegacy
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Converting from InMotion Hosting to Exchange 2013 Migration

Hello everyone,
We are looking to convert our current mail service being hosted on InMotion using POP3 to our Exchange 2013 server. Is there a migration guide somewhere I could find or something to lead me in the right direction? We want to forward the mail from InMotion
to the Exchange mailboxes as well. I know this involves converting MX records and the such but I feel like something is missing in the grand scheme of things.

Hi,
The migration can include:
1. Account migration.
2. Database migration.
3. Some A and MX records need to be configured.
For more details, you can either consult Inmotion support or Microsoft support below:
Inmotion Support
https://www.inmotionhosting.com/support/launch-chat/?rdid=2324923566971164486&url=http%3A//www.inmotionhosting.com/support/email/general-information/getting-started-guide-email
Microsoft Advisory Support
https://support.microsoft.com/gp/advisoryservice
Thanks,
Simon Wu
TechNet Community Support

Anyone done SBS 2008 to Exchange 2013 migration - disable IPv6 on SBS?

IPv6 enabled on ours without any problems. THanks for the links Anil, had not heard of those problems before

Well, considering over the scenario you have mentioned, I would like to refer you on this informative article that covers few parts of causes when disabling IPV6 on Exchange 2013 Server installation : http://mike-graham.co.uk/blog/2013/08/12/disabling-ipv6-on-exchange-2013-servers-causes-problems/Here is a well documented technet resource that also provides step-wise instructions when proceeding to migrate from Exchange 2007 to 2013 by checking all the required prerequisites : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migra...Moreover, while need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on LepideMigrator for Exchange tool that provides a hassle-free environment to get this job done without having downtime or any further interruption.

Moving from SBS 2011 to Exchange 2013

Similar Messages

Maybe you are looking for