?
Solved

Advice from Upgrading From SBS 2003

Posted on 2014-10-16
9
Medium Priority
?
118 Views
Last Modified: 2016-11-23
Hi Guys just after some advice really

We are currently Running SBS2003, we have just Purchased a New Dell Server and are going to Virtualize the New Environment.

So we have a VM for the DC, a VM for the Exchange Server, and a VM for TS.

Given that there is no Upgrade Path from SBS 2003 to Server 2012 R2, we are just going to start from Scratch.

Just after advice on doing this process smoothly, ie should I call the new domain the same as the old one?, is there an easy way to rejoin the machines to the new domain without them loosing their profiles?.

Is the best way to move Exchange over is to backup to .pst and completely reinstall Exchange as fresh?

Any help much appreciated

John
0
Comment
Question by:pepps11976
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
  • 2
  • +1
9 Comments
 
LVL 7

Expert Comment

by:tolinrome
ID: 40384327
It would probably depend on how many users are on this domain, just a handful and I would make a new domain and email to pst. But then again since its SBS it probably is just a handful of users.

To make sure I did everything clean and fresh from the start I would create a new domain and the users profiles can always be saved and copied back to their desktops.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40389485
You could install 2012 RTM (not R2) and go directly to Exchange 2010 SP3 RU7.

Guide on going from SBS 2003 to Exchange 2010.
http://supertekboy.com/2014/05/27/designing-a-simple-name-space-for-exchange-2010/
0
 

Author Comment

by:pepps11976
ID: 40394154
Also just a quick questio if i ma creating a new domain and starting from scratch is it best not to use .local?
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
LVL 31

Assisted Solution

by:Gareth Gudger
Gareth Gudger earned 1336 total points
ID: 40395077
Correct. Microsoft has been back and forth on this over the years. But now the best practice is to use a shared namespace. So, you would use domain.com internally and externally. The big reason I see for this from an Exchange perspective is Hybrid mode with Office 365.
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 40396066
Your internal namespace should be something like corp.domain.com where domain.com is a domain you own.
0
 

Author Comment

by:pepps11976
ID: 40396382
so if I use ad.domain.com does that effect anything in regards to exchange, will the internall users being able to browse to external website etc.

Garath you mention using domain.com internally and externally, Lee you mention using corp.domain.com.

I was going to use ad.domain.com they will be hosting their own exchange so was hoping that it will not cause issues?
0
 
LVL 96

Assisted Solution

by:Lee W, MVP
Lee W, MVP earned 664 total points
ID: 40398563
Should not cause any issues - you specify what DNS domains Exchange will be responsible for mail for.  ad.domain.com is fine.  I said "like" corp.domain.com... (Honestly, I've used it, but I'm not super excited about THAT or AD.domain.com... haven't found something I'm really happy with yet.  (It's a silly thing, just my preference... though the recommendation in general (and not my preference) is to use SOMETHING.domain.com - this means your AD DNS is responsible for resolving *.something.domain.com and queries to your web site, for example, will still be handled by your public DNS, as it should be.  Otherwise, you start having to maintain a separate internal DNS config for your external sites that you want your users to have access to.
0
 

Author Comment

by:pepps11976
ID: 40399308
Ok Thanks Lee

1 more thing is it ok.call the Domain compname.compname.com ie: Microsoft.microsoft.com, because if I use ad.compname.com users logging in where that used to be looging in via companyname\username, will now be presented with ad\username.

it just takes away the whole company feel to the thing?  the ad part I only used because it stands for active directory.

and also what is the problem with using .local I cannot really see the issue?
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 1336 total points
ID: 40399484
I actually see more companies on .local because that was the Microsoft best practice years ago, You can run Exchange on .local. It is fine. It can become an issue if you plan to run Exchange Hybrid. But there are still ways around that.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question