• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1125
  • Last Modified:

SBS 2011 Network Configuration

I am getting ready to upgrade our SBS 2003 network to SBS 2011 Essentials.

It has been suggested that we run a separate server for our SQL Server as this should be on it's own (not part of a DC).  We need to run SQL Server 2005 Express in our environment for a seldom used application that has business info we look up for historical purposes.

It was also suggested that we run Hyper-V and consolidate our servers for cost reasons (we don't want to purchase a separate server for something that will be retired in a few years.

We currently have (2) servers, a SBS 2003 on a machine that needs to be retired and a file and MYSQL server on a Dell PowerEdge 2900.  The PE2900 is robust and new enough; we plan on using this as our primary/only server.

I am not familiar Hyper-V or SBS2011.  Does the following network layout make sense?
We will have about about 8-10 Clients on the network with about 6-8 users.

Some questions:
-Does SBS2011 Essentials recommend a hardware Firewall to protect the network?
-Will we run into problems using SBS2011 Essentials OEM, or should we purchase the retail version?
-Is there any problems assigning a static IP (from our ISP) to a SBS2011 Essentials on a Hyper-V machine?

 Network Map
0
EdgeTod
Asked:
EdgeTod
  • 3
  • 3
1 Solution
 
Cliff GaliherCommented:
Answers inline:

> I am not familiar Hyper-V or SBS2011.  Does the following network layout make sense?

Mostly. The "static IP" does not, but I'll address that more below.

> -Does SBS2011 Essentials recommend a hardware Firewall to protect the network?

A business network should *always* be protected by a hardware firewall. Sonicwall makes a good product so as long as you are using its firewall capabilities and keeping it updated with patches, you should be alright.

> -Will we run into problems using SBS2011 Essentials OEM, or should we purchase the retail version?

OEM is sold with a new server. Since you are talking about installing on a PE you already have, you are looking at retail. If your 2003 R2 license is OEM, same applies, moving it to different hardware or virtualizing may not be allowed, so you'll want to check your existing licenses *carefully* to stay legal.

> -Is there any problems assigning a static IP (from our ISP) to a SBS2011 Essentials on a Hyper-V machine?

You'll actually assign any static IPs from your ISP to your SonicWall. You'll then configure NAT/forwarding rules to forward traffic to the SBSe server. Your SBSe server will only have a private non-routable IP address.

-Cliff

0
 
Cliff GaliherCommented:
Sorry, one final note, your PE will need more RAM in your current configuration. I'd look at expanding to 8 gigs.

-Cliff
0
 
EdgeTodAuthor Commented:
Thank you!

My understanding of the OEM disk/server is that it can be installed on one machine, and can not be transferred.  So in a sense, it installs and runs the same as a retail disk, but has limitations on support and portability.  Not true?

If there is concern, I'll probably buy the retail.... however it seems that if I am willing to accept that I could never take it off that machine then OEM makes no difference.  Also, if that is the case, then does using it under Hyper-V cause further problems?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
EdgeTodAuthor Commented:
This is the OEM that I was thinking of buying:
http://www.provantage.com/microsoft-2vg-00202~7WWFF6M8.htm
0
 
Cliff GaliherCommented:
OEM software is intended to be sold to OEMs, which in turn sell it with their systems. Some retailers will sell OEM versions with a peice of hardware to get around this, but doing so is legally a grey area. More importantly, OEM software is supported by the OEM. So purchasing an OEM version and installing it on a Dell would not even be grey, as Dell would have to be the OEM that made the purchase, not you. More importantly, you could not call MS for support since it is OEM...they'll say call your OEM. Since *you* purchased the OEM version, that makes YOU the OEM, so who do you call...yourself?

You could then sign up to be an MS partner, then call partner support (expensive) and MS will see that this is installed on a Dell and tell you that you are in an unsupported state. Quite messy for you (and pays my bills some months) so believe me, don't go this route. Go retail.

-Cliff
0
 
EdgeTodAuthor Commented:
Great answers all around.  Thank you!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now