Migration from SBS 2003

We will be replacing our SBS2003 server with new (very beefy) hardware. We will use Windows 2012R2 as DC and ultimately Exchange 2013 (after installing 2010 first). Even though not recommended, we will install Exchange on the DC, as we have a tight budget
and won't require DAG. We have less than 15 users in AD & we plan to change the server name, so we can recreate the AD from scratch, so we realize this is not a true "migration".
If we change the server name on the new server, does this affect the import of Exchange mailboxes into 2010 as long as the usernames & email addresses are exactly the same?
Anything else to be aware of if changing the server name with regards to Exchange?
Thank you!

Hello,
I think you misunderstood my post. We are installing on new hardware and the old server will be decommissioned. On the new server we want to change the name to something else, and change the domain name. We then want to ultimately get mail into
Exchange 2013. Since it is not a migration, not sure if we need to first go to Exchange 2010. How best to do this if not doing a migration? Thank you.

Similar Messages

Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003. I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
Please tell me that I can get it back. It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message. It's like the account doesn't exist any more.
Can it be recovered and if so, how?
thanks,
Jeff

Hi Jeff,
Would you please let us know current situation of this issue? Just check if above suggestions can help you.
If any update, please feel free to let us know.
In addition, please also refer to following article and thread, and then check if can help you.
How
to use a Recovery Storage Group in SBS 2008
How
to recover a deleted user and mailbox on SBS 2008
Hope this helps.
Best regards,
Justin Gu

Migration from SBS 2003 to Server 2008

Couple things. First, I wouldn't bother with 2008 at this point. Here's a pretty handy guide for 2012R2.
http://community.spiceworks.com/how_to/57636-migrate-active-directory-from-server-2003-to-server-201...
Second, I'd switch them over to hosted Exchange.
Did you spec your server already?

Hi guys,Very new to dealing with servers too much so please excuse any lack of info/dumb questions!I have been tasked to do a server migration for a small business. The details I know thus far (more to follow soon) are:There is currently only one server. It is running SBS 2003. It functions as a domain controller, and provides AD, DNS, exchange, DHCP and file sharing services. It is a physical server (Dell I believe). They want to move to another physical server running Windows Server 2008.There are around 15 users/terminals.There is a VLAN set up, not sure how yet. The VLAN needs to 'have a strong connection because heavy architect software needs to be used'Here is the plan of action I have so far:Ensure licenses for win server and exchange are bought.Install OS on new server, install all updates, service packs etc.Configure AD...
This topic first appeared in the Spiceworks Community

Migrate from Server 2003 (no Exchange, single server) to SBS 2011

Are there any Technets or other Microsoft documentation on migrating from Server 2003 (no Exchange, single server) to SBS 2011? I understand it is possible, but I would like confirmation and some documentation before purchasing the appropriate hardware
and licenses.
Thanks,
Doug
Doug Orr

Hi Doug,
In general, the migration is the similar with migrating process from SBS 2003. In addition, also have main
difference.
“The main difference is that you don’t have to remove the source and that you have to follow the migration
instructions as the SBS migration wizard will not launch.”
You can get above description from following similar thread. Please refer to.
Migrate from Windows Server Standard 2003 (not SBS) to SBS 2011
http://social.technet.microsoft.com/Forums/en-US/68790e41-b833-4e81-8200-63852ab9e196/migrate-from-windows-server-standard-2003-not-sbs-to-sbs-2011?forum=smallbusinessserver
Meanwhile, please refer to the following article. It may be helpful.
Step By Step Guide To Migrating To SBS 2011
http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/
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.
However, as Robert suggests, would you please confirm specific version of SBS? It may help us to understand
clearly and provide correct information.
Hope this helps.
Best regards,
Justin Gu

Moving to Exchange Online from SBS 2003/Exchange 2003 using PST files instead of cut over migration?

I have a friend who runs a small company with approximately 10 users. They are currently using Small Business Server 2003 and are using Exchange 2003 to a limited degree. They are using POP accounts with a hosting company for external email and
are using Exchange for internal email and calendar sharing. They have several different versions of Outlook including 2003, 2007, and 2010. Most of the users have two mail accounts configured in Outlook - one Exchange account and one account with a hosting
company which provides POP mail boxes. Their MX record currently points to the hosting company not their exchange server. As far as I know, they do not have any static IP addresses or if they do, they are not using them.
I do not believe Outlook versions about 2010 will work with Exchange 2003 and their server is getting older and probably needs an upgrade.
I think they should probably move to Exchange Online since they do not have an IT person on staff.
I've done some research and it looks like the recommended solution is a cut-over migration from Exchange 2003 but it looks like that would require some changes to the existing SBS 2003 / Exchange 2003 server and I'm not sure that we would be comfortable
making those changes.
Would it be possible to sign-up and create the user accounts using Exchange Online and just import the data from the user's PST files?
I tried doing some research it looks like it is possible but one post mentioned needing to modify the mailbox’s legencyDN or they may not be able to reply to old messages. How difficult is that? Can it be done after the messages have been migrated
to Exchange Online.
They only have about 10 users so we are looking for the simplest way to move to Exchange Online, not necessarily the fastest or most efficient.
Any advice would be greatly appreciated.

Hi,
Based on your description, I understand that you want to migrate Exchange 2003 Public Folders to Exchange Online. We can get following messages from this article:
Public Folders in Exchange Online
You can’t migrate public folders directly from Exchange 2003. If you’re running Exchange 2003 in your organization,
you must move all public folder databases and replicas to Exchange 2007 SP3 RU10 or later. No public folder replicas can remain on Exchange 2003.
It seems that can’t migrate on-premise Exchange 2003 public folders to an Office 365.
àOn the client
side we are using Exchange 2007
Did you mean Outlook 2007? Please refer to the following thread and check if can help you.
Migrating Exchange 2003 Public Folders to
Wave 15 Office 365
Hope this helps.
Best regards,
Justin Gu

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

Migration from Exchange 2003

Hi,
We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
Can Office 2011 connect to Mac mail services? If so, what protocols?
Many thanks,
Ciaran.

We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
What features of Exchange are you using? Push notifications? Calendaring. Sharepoint? Figure out what you want and what you need (and which are two separate lists) and then map that over to what Mac OS X Server, or to what a Mac box with the Kerio Connect package loaded, might provide you.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
That's rather open-ended. It's possible, but there's no single definition of small business mail requirements. Some small businesses can and have, and some might find themselves missing critical features.
Can Office 2011 connect to Mac mail services? If so, what protocols?
iWork does well enough to read and write Office files locally, so I don't have experience with Microsoft Office. The Windows mail clients can certainly access Unix mail servers. As for what connectivity is present within Office, I'm way too rusty with Windows to comment. What used to be the Outlook Express client worked just fine with Unix mail servers. The full-on Office Outlook client was pretty flaky with stuff other than Exchange, but that was some years ago.
Biggest issues with SBS migrations tend to be with shared Address Book, with shared Calendars and with Sharepoint services; if you're heavy users of those features, you might find the Mac OS X Server implementations lacking. Kerio can potentially help here.
Look around the forums for some other folks. This particular SBS migration has been fairly common fodder for discussions.

SPAM rules on Inbox after migration from Exchange 2003 - GFI Mail Essentials

Hello,
Few times ago, we had an Exchange 2003 server with mailboxes which were configured with "rulemgmt.exe" tool (from Microsoft ?) to manage users mailboxes and SPAM redirection in these mailboxes.
GFI MailEssentials (antispam) was installed on a mail relay and once a SPAM was detected, it was redirected in Inbox/SPAM folder on user mailbox thanks to the rule defined by "rulemgmt.exe".
Recently, we did a migration from Exchange 2003 to 2010. Unfortunately, "rulemgmt.exe" doesn't work anymore on Exchange 2010 and it's replaced by a "Transport Rule" which works fine but only to redirect SPAMs in Junk e-mail folder. However,
if I don't set up this transport rule, SPAM redirection still works from mailboxes which were created on Exchange 2003 and e-mails go to Inbox/SPAM as before... For new mailboxes on Exchange 2010, it doesn't work which is normal.
My question is: for old mailboxes from Exchange 2003, where are the SPAM redirection (Inbox/SPAM) information stored? I don't understand how SPAM can be redirected if the information is not stored in Exchange...
The aim is to use Junk E-mail folder with the Transport Rule at the end everywhere and to clean old rules used for Inbox/SPAM.
I contact GFI support but they couldn't help me.
Any idea?
Regards,
DeltaSM

Those old mailboxes probably have old rules still set. You can use the Outlook.exe /cleanrules switch to purge those old rules. This would require that you create an outlook profile for each of those impacted mailboxes.
You can also look at using MFCMapi -
http://support.microsoft.com/kb/2860406/en-us
When that is done, you might want to perform a Clean-MailboxDatabase and then look at the mailbox rules (get-inboxrule). If that does not work for you, could be something else within the mailbox and as such, I would recommend working with MS to get
more info.
DaDougInc

OS Migration from Windows 2003 cluster to Windows 2008 R2 MSCS

We want to go for windows 2008 R2 server ( 64-Bit) MSCS by migrating from windows 2003 Cluster ( 32- Bit) . We are running on ECC 6.0 and oracle 10.2.0.2 DB.
Is it possible ?
Is it traditional System copy if so how to migrate the cluster ?
Regards

> 2. If the oracle version is 10.2.0.2 then does it will support Windows 2008 R2.
You need at least 10.2.0.4 (you need to install that version with a separate DVD, you can't install with the normal Oracle DVD (10.2.0.1). See
Note 1303262 - Oracle on Windows Server 2008
Be aware of the fact that the normal standard support for 10.2.x is ending at end of july (you'll have to pay an extra maintenance fee if you continue to run that version) - see
Note 1110995 - Extended maintenance for Oracle Version 10.2
So if you now do a system copy to new hardware with a new os anyway, I would upgrade to 11.2.
Markus

MDT 2012 to Migrate from Windows 2003 32 Bit to Windows 2012 R2 64 Bit

I have used MDT for so long however only for client OS upgrade - XP to Windows 7/8.
We wish to use MDT to migrate from Windows 2003 32 Bit to Windows 2012 R2 64 Bit. All servers are virtual on HyperV or VMWare - plan is to use USMT hardlink Migration.
Is this supported? Has anyone used this for server migration?
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Thanks Keith for your reply.
Even is USMT does not work, we are ok. SMIGdeploy will be helpful.
Basically, want MDT to run some scripts on the Windows 2003 server, post which install Windows 2012 and join it to the existing domain with the same computer name.
Then hydration kit to help with the installation of features etc. Also, we would like to take a complete backup to a WIM before migrating.
I am sure this is workable.
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Migrating from DHCP 2003 to DHCP 2012

Hi,
i'm planning to migrate from DHCP 2003 to DHCP 2012 or DHCP 2012 R2 failover.
Saw those instructions:
extract the configuration in .TXT
netsh dhcp server export c:\temp\dhcp.txt all
copy this file on your server 2012 in temp or elsewhere
import the configuration with this command
netsh dhcp server import c:\temp\dhcp.txt all
if you have the error "TLS supported but not configured"
remove all the option in "Server Option" like 003 Router 006 DNS SERVERS and put it back after doing the import
now i have some questions:
1. is it recommended to build 2 2012 DHCP configured as failover on virtual machines ? (hyper-V)
2. do those dhcp servers have to or recommended to be DNS also or can they be only DHCP servers ?
3. my AD functionality level is 2003 - is it a problem for this migration ?
4. virtual or physical ? whats is recommended ?
5. any other considerations ?
TNX

Hi,
Virtual or physical will both work. It doesn't matter, as long as the two servers can communicate with each other.
You do not need DNS installed on the same server, but you can install it without hurting anything.
I believe that the AD level has no effect because you can have DHCP failover even on workgroup computers.
-Greg
http://technet.microsoft.com/en-us/library/dn338983.aspx#specs

Calendar Free/Busy permissions being ignored for users migrated from Exchange 2003, fine for new users created on Exchange 2010

I have uncovered a situation where it seems the free/busy permissions are being ignored for users that were migrated from Exchange 2003 to Exchange 2010.
I have the default permissions set to only show Free/Busy Time, not Details. However if I look at the calendar for a users who was migrated from the old Exchange 2003 server, I can see details. If I look
at a newer user who was added directly to the Exchange 2010 server, I (correctly) only see the times and "Free" or "Busy", not the specific details.
I verified the permissions on the migrated mailboxes many different ways (Exfolders, cmdlets, etc) and all signs point to only allow showing Free/Busy Times, but alas, I can still see the Details as well.
My users are using Outlook 2010.

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Client PC migration fails from SBS 2003 to SBS 2012 Essentials

Please check out this entire message before making an assumption about what it says, thanks.
Our old SBS 2003 Server hard failed a few weeks ago.
Rather than repair it, we ordered a new server with SBS 2012 Essentials and loaded the backup data from the old server.
The Server is just fine. We are having no issues whatsoever with the server. I kept the old domain name and server name.
The Client Computers, some Win7 some Win8.1, have turned into a nightmare to re-connect.
What happens is, the user can log in, but has no files in desktop, downloads or documents, nothing has been migrated:
The process I'm using is this:
1> I take them off the old domain and set them up as workgroup: NOGROUP... that works fine.
2> I bring up http://SERVERNAME/connect and begin installing the server software, no problem yet...
        >> This goes to a point where it asks for a restart, followed by a lot more waiting.
        >> Eventually it crashes with a message I have, unfortunately, not documented (sorry).
3> When I restart the PC, I'm able to log into the user account : DOM\username, but none of the users files are there.
Looking at the file tree at C:\Users I see a folder structure like this:
C:\Users
        |_ _client.setup_ (essentially empty)
        |_ username         (the old account... and yes, it has all of the files and app data)
        |_ username.DOM (the new account, but essentially empty)
It appears that the setup was supposed to migrate 'username' thru '_client.setup_ into 'username.DOM' but failed.
I can move all of the data from 'username' to 'username.DOM' to solve the data and files problem.
But the AppData folder cannot be moved in its entirety (I tried, and it clobbers the user completely), I have to manually transfer files from 'username\AppData' folders (Local, LocalLow and Roaming) making sure to transfer only the files that don't exist
in the 'username.DOM\Appdata' folders.
I realize that this process leaves me with a 'Less Than Perfect' AppData setup.
Since I have many Clients left to convert, I'd like to know if I'm doing something wrong, or how to make it right.

With a new server with a new domain you have started down the right path. Disjoin and the http:// technique should have worked, but we can address that when you can give us more info.
When joining a new domain the old users profiles get blocked by security to the new users. But the local admin or the domain admin should have access. The way I do it is to copy out the required data from the old profile to a safe place then
copy it back to the new profile when finished. But there are profile migration wizards, one of them at
www.forensit.com, that work very well.
As for the system crash when you did the join... please see if you can get the message, and then examine the logs in both the server and the client.   For the server, look here:
http://blogs.technet.com/b/sbs/archive/2014/09/30/windows-server-essentials-log-files.aspx
For the client, scroll down in the link above to the section about client side logs.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

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

Issues with Shell32.dll, NTDLL.DLL and Migration from Windows 2003 to Windows 2012

Hello all,
I am new to ThinApp and working as a consultant to help a company migrate older Windows 2003 software to Windows 2012. They have purchased ThinApp 5.0.4.5 so that is what we will be using.
We have created a clean 2003 VM and did a pre-scan
We loaded the application and configured it and then did a capture.
We then tested the capture the 2003 VM and it works
We then loaded the capture on a Clean 2003 VM and it works
We then loaded onto a 2012 VM and when running the app from a command window get an error -missing import shell32.dll:StrCpyNW
If we run the capture in Emulation Mode on 2012 VM, we do not get the Shell32.dll error but instead the cmd fails with a Fault Module Name - NTDLL.DLL error
I am sure I am just missing the correct location to identify or configure the capture - but do not have the experience to know where yet. (Taking training next week).
Until then, is there any suggestions which I can try?
Thanks for your time in advance,
Vince

Tried and done that. The main issue while configuring the printer from the printer Web Interface is that there is no access to the Digital Sending section due to a problem with the "Sun Java plug in" I think the code mentions 1.31. or similar.
We downloaded the java plug in and installed it. No progress.
We reset the printer to defaults and reconfigured it .. It sees the smtp gateway and access it but fails sending email with scanned documents..
We have tried in very different ways. We connected the printer to another domain SBS server 2003 and it works beautifully. So, I have no idea on what is the problem. We created a firewall exception for ports 390. 1783 from the SBS to the Printer
and still no go..
We have tried four different accounts and nothing. Same results as stated originally.
Any other suggestions??
JFM

Migration from SBS 2003

Similar Messages

Maybe you are looking for