sbs 2003 to 2008 std

Hi, my client has sbs 2003 and deciding if I should upgrade them to sbs 2011 or install server std 2008.

If  I was to upgrade them to windows 2008 std, upgrading AD how do I update the windows sbs 2003 schema? Will this break anything? I would also need to move their mailboxes off the sbs box to the windows 2008 server with Exchange server std on?

Help please?
Who is Participating?
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.


If you plan on moving them away from the SBS platform, you will need to have separate servers for AD and Exchange. It is highly recommended by Microsoft to not have everything on one box unless it is SBS. You can achieve this by utilizing Hyper-V but all of this is quite expensive. If your client has less than 75 users, then stay with SBS and go to 2011. It's cheaper with licensing and much more simple to manage. Remember too that if you do away with SBS, you will lose Remote Web Workplace which they may find important.

If you do choose to go to SBS 2011, you can't do a direct upgrade, you will need to migrate. Unless you upgrade to 2008, then 2011.
Lee W, MVPTechnology and Business Process AdvisorCommented:
In general I agree, but there is a problem in that SBS 2011 is only available via OEM right now and will not be available at all come January.  Further, while the cut-off is 75 users, if your client is anywhere near that, then SBS is NOT the solution - you need room for the client to grow.

I would not be recommending you move to 2008.  Move AT LEAST to 2008 R2 and even then, 2012 R2 is out (or about to be) and moving to at least 2012 would be better.  Buying 2012 licenses grants you TWO instances of server in a VM.  So the costs aren't quite as bad as mcdaddy513 (implies (as I interpret)).  The migration process to Exchange 2013 from SBS 2003 would be difficult - you'd have to migrate to 2010 first) so you can go to 2010 instead of 2013 and leave 2013 for a future upgrade and/or skip it in my opinion.

As for how to migrate, since you've never done this before, you should STRONGLY consider the swing migration kit from - it's not free but it's cheap and they provide support. One of the best parts about this method is that you don't destroy the server - if you mess up, you can start over.
I simply meant that licensing Exchange Standard +CALS is much more expensive than SBS, IF the client doesn't have a lot of users.
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

monarchitAuthor Commented:

What do you think to the upgrade link from sbs 2003 to sbs 2011?

Also, do you know if I need SBS premium add on to allow RDS on my second server? Or will SBS standard be enough?

The second server will just be a member server in the domain running terminal services?

Also I have read up that once you have SBS 2003 and SBS 2011 running together to transfer mailboxes etc, you have to install a patch so you get the full 21 days to remove the old SBS 2003 server?

I have purchased 5 TS CALS. Is this all I need?

Thanks both for your advice and will award you guys the points.
Yes, you do have a time limit for your migration. If you follow the steps exactly in the link below, you should be fine. Make sure you BACKUP ALL DATA before you proceed.

As for the TS cals, if you buy the premium add-on, you get a license for Server 2008 R2 Standard, and SQL Server 2008 Standard. This comes with two administrative TS cals, not users. So you will need to purchase 5 TS CALs for that solution. You may want to check pricing, if you are not using the SQL server, it may be cheaper to buy a license for Server 2008 R2, rather than the entire SBS add-on. Just check with your vendor for pricing.
monarchitAuthor Commented:
Sorry didn't include the link

So, can you confirm I don't need SBS 2011 premium add to have another server acting as a member server  with RDS on?

Lee W, MVPTechnology and Business Process AdvisorCommented:
The SBS restriction is that you can only have one SBS server on the network.  This is because the SBS server MUST be the FSMO master.  There is an exception in that (as you've understood) you can have a second SBS server on the network for migration purposes for up to 3 weeks.

OTHER DCs CAN be added to the network PROVIDED you do not transfer the FSMO roles.

Other non-DCs CAN be added to the network since there is no issue with FSMO roles on them.  (FSMO roles are only on DCs, potentially).

So to more directly answer your question, YES, you don't need to have the Premium Add On to have an additional server on the network.  Indeed, if you don't need SQL, then it's a WASTE OF MONEY to get it.

(NOTE: SBS 2011 CALs cover access to all other servers on the network running 2008 R2 or older.  If you add a 2012 Server, then you need 2012 CALs for that server so that your users can connect to it.  Otherwise, buy 2012 and use downgrade rights to install 2008 R2 and you don't need 2012 CALs.

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
monarchitAuthor Commented:
Can you just confirm one more thing. I don't need the premium add on to have RDS services on my second server?

The premium add on PDF for SBS 2011 says it allows RDS connections but I guess that's from the SBS 2011 server itself?
Lee W, MVPTechnology and Business Process AdvisorCommented:
If you read the documentation, NO WHERE does it state that RDS services are only available in the premium Add-on.  

The SBS server CANNOT host RDS services, but there is NO DIFFERENCE in an SBS domain's capabilities over a non-SBS domain EXCEPT in that:
1. There can be only one server running an edition of Small Business Server (SBS 2003, 2008, 2011, Essentials) for the reasons mentioned above
2. You cannot have trusts in to or out of the domain.

Otherwise an SBS domain, when you add NON-SBS servers to it, can do just about anything - clusters, certificate services, digital rights management, e-mail, databases, pretty much anything so long as it doesn't violate the FSMO holding requirements of SBS or need a trust.
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
Microsoft Legacy OS

From novice to tech pro — start learning today.