Advice from Upgrading From SBS 2003

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

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
Gareth GudgerSolution ArchitectCommented:
You could install 2012 RTM (not R2) and go directly to Exchange 2010 SP3 RU7.

Guide on going from SBS 2003 to Exchange 2010.
pepps11976Author Commented:
Also just a quick questio if i ma creating a new domain and starting from scratch is it best not to use .local?
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Gareth GudgerSolution ArchitectCommented:
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 internally and externally. The big reason I see for this from an Exchange perspective is Hybrid mode with Office 365.
Lee W, MVPTechnology and Business Process AdvisorCommented:
Your internal namespace should be something like where is a domain you own.
pepps11976Author Commented:
so if I use does that effect anything in regards to exchange, will the internall users being able to browse to external website etc.

Garath you mention using internally and externally, Lee you mention using

I was going to use they will be hosting their own exchange so was hoping that it will not cause issues?
Lee W, MVPTechnology and Business Process AdvisorCommented:
Should not cause any issues - you specify what DNS domains Exchange will be responsible for mail for. is fine.  I said "like" (Honestly, I've used it, but I'm not super excited about THAT or 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 - this means your AD DNS is responsible for resolving * 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.
pepps11976Author Commented:
Ok Thanks Lee

1 more thing is it the Domain ie:, because if I use 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?
Gareth GudgerSolution ArchitectCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.