SBS

58K

Solutions

28K

Contributors

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Share tech news, updates, or what's on your mind.

Sign up to Post

A quick step-by-step overview of installing and configuring Carbonite Server Backup.
1
What does it mean to be "Always On"?
LVL 4
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' again!
0
If you are a user of the discontinued Microsoft Office Accounting 2008 (MSOA) and have to move to a new computer running Windows 8, you will be unhappy to discover that it won't install.  In particular, Microsoft SQL Server 2005 Express Edition (SSE), which is part of the product, refuses to install.  While you can find articles on the Internet explaining how to get SSE running, I was unable to find instructions for MSOA.
 

Notes:


  • I have tried this on Windows 8.1 and the UK Edition of MSOA.  There are other geographic variants of MSOA, and it is expected that these instructions will work for those as well.
  • While I have MSOA running and it appears stable, I have not tested all its functionality on Window 8.1.  The main functionality for running a company works, but it is possible that some bits don't.
 

Installation:


  1. Download Microsoft SQL Server 2005 Express Edition, currently at http://www.microsoft.com/en-us/download/details.aspx?id=21844
  2. Run SQLEXPR.EXE until it has unpacked the kit into C:\{generated hexadecimal number}\
  3. Copy C:\{generated hexadecimal number}\ to C:\inst.bak
  4. Quit install
  5. Run C:\inst.bak\setup\sqlncli_x64.msi
  6. Open a Command Prompt window as Administrator
  7. Run the following command: 
    C:\inst.bak\setup.exe -q qn ADDLOCAL=ALL INSTANCENAME=MSSMLBIZ /norebootchk REBOOT=ReallySuppress SQLAUTOSTART=1 ALLUSERS=1
  8. Download Microsoft Office Accounting 2008 and SP1
  9. Run the install file 
  10. Do a custom install, and choose advanced
  11. Specify that it is to use an existing SQL Server instance called MSSMLBIZ
  12. Run the SP1 install file
  13. Copy your .sbd and .sbl files to
0
I work for a company that primarily works with small businesses as their outsourced IT vendor. As such the majority of these customers utilize some version of Small Business Server. Due to the economics of running a small business, many of these customers were DSL subscribers.

In the past year or so, these customers who are AT&T subscribers have been systematically forced to convert to uVerse. While I am sure this is an amazing service for the home user, it is flat out awful for most business applications. The modem is hard coded to serve DHCP (cannot be disabled) and the service blocks port 25 outbound traffic.

I have never been a fan of using ISP provided equipment as the gateway device and in this case, it is imperitive that you do not. If you know SBS, you know it needs to serve DHCP for things to go smoothly.

So after many hours of searching internet articles, uVerse help pages, etc... I have come up with a method for using uVerse with SBS... assuming a better internet provider is not available.

The resolution is to install a firewall if they don’t already have one and configure uVerse to serve the public addresses and turn off any firewall features. AT&T equipment changes often but the following was documented on a Motorola NVG589.

The things you will need from AT&T:
      PPPoE login and password
      Static IP information
To fix the local network, login in to the uVerse modem using the access information printed on the label. The access code will be printed …
3
 
LVL 38

Administrative Comment

by:lherrou
Comment Utility
Gary,

When two or more editors agree, an article can be designated as Experts Exchange Approved (EEA). Thank you again for your quality work, and please note that is now honored by that EEA designation. As a bonus, as well as the honor, this also brings you some nice extra points.

LHerrou
Experts Exchange Editor
0
 
LVL 5

Expert Comment

by:Adam Ray
Comment Utility
Perhaps "Business Uverse" isn't exactly the same all across the country, but I set up a number of customers in the Austin, TX market and it wasn't quite that involved. (Or perhaps I just did it enough times so that I didn't realize all of the steps I was actually performing.)

Here is the outline of my process (from memory.) Gary's article above provides some of the details (e.g. what settings to use for the "Public Subnet") so I won't reiterate here. I.E. The steps below likely won't stand on their own to someone who hasn't done it before, so be sure to read the original article above.

It requires using the uverse gateway AND the customer's own router/firewall.
Use a laptop (DHCP) and go back and forth plugging into to the LAN side of the uverse gateway and the LAN side of the customer network as appropriate.
Don't be afraid to refresh pages, for a release/renew of DHCP IPs, do a power cycle, etc. if something isn't showing up as expected. The uvsere gateway doesn't always update it's "device list" in a timely fashion on its own.

1) Change the "LAN" IP and subnet on the uverse gateway to be outside of the customer's actual LAN subnet. Any two private ranges* that don't overlap will work. But I tend to use, for example, 172.16.0.1/24 (uverse) and 192.168.0.1/24 (customer LAN) to keep things clearly separate.

2) Add the Public Subnet to the uverse gateway as described in the article above. It helps immensely to be talking to a Tier 2 technician at AT&T on the phone to get these settings. I've found that many/most of the installers and Tier 1 support tech's don't even know what this is.

3) Set the customer's router to get the WAN IP via DHCP. Release/renew IP.

4) On the uverse gateway go to the firewall tab and change the settings for the "device" that shows up that is the customer's firewall. (Identify via the uverse LAN IP the customer router's currently has for it's WAN IP, or it's WAN MAC.) Give it a "public fixed" IP and choose the desired public IP from the second drop down. (I typically choose the first usable IP of the "Public Subnet" setup earlier.) Disable the firewall (enable DMZ plus mode) for the device. Save. (I also tend to disable packet filtering in the general firewall setup as mentioned above, but it shouldn't be necessary with DMZ plus mode enabled.)

5) Release/renew WAN IP on customer router, power cycle if needed. It should have the public IP from step 4 now for the WAN IP, rather than a uverse LAN private IP.

(Optional/alternative) I have been successful configuring all the customer's router with a static WAN IP, subnet, etc. And then getting it to show up in the devices of the of the uverse's firewall page so DMZplus mode can be enabled. But, from my experience, leaving the consumer's router WAN set to DHCP (and having the uverse gateway set to always issue it the public IP) tends to be more reliable than the various methods (mentioned a couple of sentences above and in the original article above) of getting it work such that the consumer's router WAN is set statically.


Email:
At least in the Austin, TX market, port 465 is NOT blocked in any way with uverse. And if you are talking to a Tier 2 AT&T tech on the phone they can unblock port 25 for your IP ranges. (Technically, the block is upstream of the uverse gateway, so no matter what your setting are on the gateway you can't get by the block without AT&T turning it off.)

Spending a few minutes on the phone, to me, is much easier than messing with all of the Exchange connectors/smart hosts. (Plus you don't have route your mail through AT&T SMTP servers.)

It bears repeating again. These steps are for "Business Uverse" accounts and assume you are talking to at least Tier 2 support. You're mileage may vary with "Residential Uverse" and it would likely be a lost cause talking to "Consumer/Residential/Tier 1" support.

One final note: Most people won't run into this, but you may if you customer uses multiple public IPs for their network. The uverse gateway has what can be thought of as a hardware limitation that limits one IP (public and/or uverse private LAN) per MAC address of devices connected directly to the uverse gateway (i.e. not NAT'ed behind the consumer router.) So unless you get clever (and/or have clever hardware) you in effect will only have 1 "usable" static Public IP, even though you are paying for 5.
0
I’m often asked about newer and larger USB drives connected to SBS2008 and 2011 failing Windows Server Backup vs the older USB drives not failing. As disk space continues to grow and drive technology change SBS2008 and some SBS2011 end up with the following error: “Backup started at '12/24/2013 7:45:26 PM' failed with following error code '2155348010' (One of the backup files could not be created.). Please rerun backup once issue is resolved.”

In this article I’ll explain 1. why newer / larger USB drives fail, 2. how to determine ‘byte sector size’ and 512e (emulation) of the drive in question, and 3. a resolution.

1. Why newer / larger USB drives fail: in June 2005 Dell, Hitachi, HP, Lenovo, LSI Maxtor, NVidia, Seagate, Western Digital started to ship harddisks with 4K sector size. As of 2011 all new HDD’s ship with that advanced format, and Windows server backup is not designed to run on this disk configuration.

2. How to determine ‘byte sector size’ and 512e:
Open an elevated command prompt and type: fsutil fsinfo ntfsinfo <USB drive letter>:
Under Bytes Per Sector: verify 512 emulation (see item 1)
Under Bytes Per Cluster: verify 4096
Under Bytes Per FileRecord Segment: 1024
SBS2008 and SBS2011 supports this backup configuration
Item 1item 1
Drives shipped after 2011 with advanced format (see item 2).
item 2item 2
3. Resolutions
5
 
LVL 17

Author Comment

by:WORKS2011
Comment Utility
any update to the status of this? thank you
0
Because virtualization becomes more and more common, and, with Microsoft Hyper-V included in Windows Server at no additional costs, and, most server hardware nowadays is more than capable of running a physical Small Business Server (SBS) 2008 or 2011 installation, and never get the full benefits of the hardware. It is worth considering to virtualize the SBS 2008 or 2011 server and run one or maybe two or more virtual servers beside it on the same hardware.

I first published this Article on my blog and thought I would also share it here.

In this Article I will put together some facts, tips and considerations you should look after before you start virtualizing a SBS 2008 or 2011 server. Of course a lot of this information can also be used for virtualizing non SBS servers.

Enable Hyper-V role on a SBS 2008 or 2011 server
So if you just want to add just one other server, why not install SBS 2008 or 2011 on the physical hardware and just enable the Hyper-V role?

The answer is really simple, because it is not supported!! Enabling the Hyper-V role on a SBS 2008 or 2011 server will break stuff, for some additional information read here: http://blogs.technet.com/b/sbs/archive/2009/08/07/you-cannot-install-the-hyper-v-role-on-the-sbs-2008-primary-server.aspx

Hyper-V Host
So as we …
4
The articles for turning off the Client firewall policy on the internet are for SBS 2008 and don't really help for SBS 2011. They actually moved the Client firewall policy.

In 2011, the client firewall policy has moved to the SBS computers container. If the computer is not in this AD container then the policy won’t work of course. The SBS 2008 policy in in the group policy objects folder, under SBS client policies.

When you Google this “turning off the client firewall policy in sbs 2011” you get this:

http://msmvps.com/blogs/robwill/archive/2011/04/06/disable-the-windows-firewall-on-client-computers-in-an-sbs-2008-domain.aspx

This article will lead you nowhere (it is for 2008 and not 2011) and that can be frustrating.

So… Here is the location if you have the need in SBS 2011 :
 SBS 2011 sbscomputers policy
The policy computer configuration-> windows settings->administrative templates->network->network connections->windows firewall->Domain Profile->make sure all the settings are changed to not configured. This will ensure the Clients have control of their own firewall.

 SBS 2011 windows firewall policy
Once they are all configured you can do your gpupdate/force and have the clients log off and back on again and viola.

Disclaimer :

I would not implement this in the organization unless you have a specific reason.

I wrote this article because there is currently not one out on the internet for how to do this in SBS 2011. One caveat is the public …
2
 
LVL 74

Administrative Comment

by:Glen Knight
Comment Utility
Hi louisreeves,

My first question, is why would you want to do this?

One of the most important features of any Windows Network is the centralised administration/control.

Giving the end users access to change security settings is a recipe for disaster, from that perspective, there has to be a clear reason to want to do this and a note indicating this is not best practice and should be avoided at all cost.

Thanks
demazter
Experts Exchange Page Editor

0
 

Expert Comment

by:MrGD
Comment Utility
If you want to allow the user to use alternative firewalls like one that comes with the Antivirus programs, do I really want both firewalls?  Also recently was trying to determine if the firewall was blocking something, I was not able to turn the firewall off.  Assuming there was no other options than to implement this type of approach.
0
I've often see, or have been asked, the question about the difference between the Exchange 2010 SP1 version, available as part of Small Business Server (SBS) 2011, and the “normal” Exchange 2010 SP1 Standard.

The answer to the question is relatively easy, there isn’t.

Alright there is one little difference, if you have configured your Small Business Server with predefined wizards, there are automatically created 3 receive connectors (with 1 that accepts anonymous email from the outside) and 1 send connector. With a normal Exchange 2010 server installation you need to allow anonymous access and create a send connector manually.

Small Business Server 2011 includes the Exchange 2010 SP1 standard version without any limitation. And the Small Business Server Client Access License (CAL) covers the Exchange 2010 CAL.

If you would like to use the so called enterprise functionality like: Custom Retention Policies, Personal Archive, Voicemail, Information Protection and Compliance, Cross Mailbox Search, Legal Hold, Advance Mobile Policies, and Per User/Distribution List Journaling, you need to buy additional the Exchange 2010 Enterprise CAL.

Q. May I use the SBS 2011 CAL Suite to access the Enterprise functionality of Microsoft Exchange Server Enterprise server software?

 A. You may use SBS 2011 CAL Suite instead of Exchange Server 2010 Standard CALs to access base functionalities in instances of Exchange Server 2010 Standard or Enterprise in the Windows Small
0
The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party utiliies to re partition the drives, where the system partition is a portion of the actual total drive space.  

However, in most cases, except perhaps the first released installations where the OEM's created system partitions as small as 10 or 12 GB, the issue of space on the system partition can be managed.  It takes a little work, but for some it is the best option.

Here are some  space saving/making tips accumulated from various sources, including this forum and the MS SBS newsgroups.
 
NOTE: When moving folders, especially your Exchange data base, revisit the exclusions in your Anti Virus program. It is "critical" that these not be scanned by your real time scanner.
 
Moving Data Folders for Windows Small Business Server 2003
http://www.microsoft.com/technet/prodtechnol/sbs/2003/maintain/movedata.mspx
 
How to move Exchange databases and logs in Exchange Server 2003
<http://support.microsoft.com/kb/821915>
 
How to Move Small Business Server 2000 Company and Users Shared Folders
<http://support.microsoft.com/default.aspx?scid=kb;en-us;329640>
 
How to Move the Client Programs Folder to Another Location in Windows Small Business Server 2003
 <http://support.microsoft.com/?scid=kb;en-us;830254>
 
How to Move …
4
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Small Business Server 2011.

NOTE: This guide has been written using the preview version of SBS2011 therefore some of the screens may look slightly different on the final release. 

For this migration to work you will need the following software:
Windows Small Business Server 2003 (SBS 2003)
Windows Small Business Server 2011
Microsoft Baseline Configuration Analyzer which can be downloaded from:  http://www.microsoft.com/downloads/en/details.aspx?familyid=1B6E9026-F505-403E-84C3-A5DEA704EC67&displaylang=en
Steps required:
1.   Health Checks on Small Business Server 2003
2.   Configure SBS2003 for single NIC
3.   Run Migration Preparation tool on SBS2003 & Create Answerfile
4.   Administrative User Creation
5.   Setting data locations
6.   Configure the Network
7.   Configure the Internet Address
8.   Migrate Exchange Mailboxes and Settings
9.   Remove Legacy Group Policies and Logon Settings
10.  Migrate users' Shared Data
11.  Migrate Fax Data
12.  Migrate Users and Groups
13.  Uninstall Exchange 2003 from Small Business Server 2003
14.  Check Transfer of the 5 FSMO roles to SBS2011
15.  DCPROMO SBS 2003 server so it is no longer a domain controller and remove from network


Step 1.   Health Checks on Small Business Server 2003

25
 
LVL 34

Expert Comment

by:Shreedhar Ette
Comment Utility
Hello Dematzer,

Does the procedure is same for SBS 2003 t0 SBS 2011 Essentials?
0
 
LVL 25

Expert Comment

by:Tony Giangreco
Comment Utility
Great article!!!

Do you have guides for the following?

Migrating from SBS2003 32 bit to Server 2008 R2 standard (not SBS) where exchange is not being used on the sbs2003 box and not planned for Server 2008 R2?

Migrating from SBS2003 32 bit to Server 2012 R2 Essentials where exchange is not being used on the sbs2003 box and not planned for Server 2008 R2?

Migrating from SBS2003 32 bit to Server 2012 R2 Foundation where exchange is not being used on the sbs2003 box and not planned for Server 2008 R2?
0
Free Tool: Path Explorer
LVL 9
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

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

The SBS 2011 release date (RTM) is supposed to be around Christmas, 2011.  This article is a compilation of my notes -- things I have learned first hand.  The items are in a rather random order, but I think this list covers most of what is new and different, and it might be helpful to readers who contemplate upgrading.

A single group mailbox can now have members who all have access to the mail in a single public folder.  Think:
    info@domain.com
All IIS sites are back inside the default website again.

SharePoint Disaster recovery can be done regardless of whether the Active directory matchers. BUT THE DATABASE IS NOT TIED TO WINDOWS INTERNAL DATABASE ANYMORE either!

10GB database size limit on SQL 2008 R2 (SharePoint). This will be a call generator and SQL RBS may need to be used.  Max usage is 1GB of RAM and MAX processor is 1.
SharePoint disaster recovery method unveiled by MICROSOFT trainer in SBS 7 class. It is in the SharePoint DOC I sent everyone.
There is a registry edit  you can make on the source server to make migration of an unhealthy server possible (disable health checks).  It was the source of 60% of migration failures.
OWA 2010 will allow drag and drop attachments with Silverlight.
Exchange 2010 supports iCAL integration (like Google calendaring)

Reinstalling CAS role is much simpler in SBS 7 than in the past.
1
 

Expert Comment

by:HBPROCK
Comment Utility
Thanks again for you help I think SBS2011 is the way we need to be going just awaiting the OEM Media to arrive in the UK as its still stuck In Germany somewhere apparently.
0
 
LVL 74

Expert Comment

by:Glen Knight
Comment Utility
Ahh...yes....I know that feeling very well :)
0

Introduction

At 19:33 (UST) on Tuesday 21st September the long awaited email arrived with the subject title of “ANNOUNCING THE AVAILABILITY OF WINDOWS SBS 7 PREVIEW”.  It was time to drop whatever I was doing and dedicate as much bandwidth as possible to downloading the latest version of Small Business Server.

The contents of the email went on to brag about the technologies used in this release:
Built on Windows Server® 2008 R2, this exciting new edition of the all-in-one solution server for small businesses will include Microsoft® Exchange Server 2010 SP1, Microsoft SharePoint® Foundation 2010, and Windows Software Update Services. Small business customers will find significant security and management enhancements over previous versions, as well as much richer features for providing file-and-print, email and Internet services to employees.
Once the ISO was downloaded and virtual machine ready I proceeded with the installation.

Installation of SBS 7

The hardware requirements as advertised by the SBS team are:
 hardware-requirementsThe first noticeable difference in this specification is the RAM requirements, in SBS2008 the minimum requirement was 4GB to allow installation to proceed.  I have only configured my Virtual Machine with 4GB so let’s see if the installation starts.

The initial installation phase was something I was familiar with.  In fact it was identical to the SBS2008 installation and any other Windows 2008 R2 …
4
Written by Glen Knight (demazter) as part of a series of how-to articles.

Introduction

One of the biggest consumers of disk space with Small Business Server 2008(SBS) is Windows Server Update Services, more affectionately known as WSUS.

For those of you that don’t know what this is, it provides Windows Updates to both the SBS server and all the client machines when correctly joined to the SBS Domain.  Coupled together with Microsoft Updates (discussed in my article here: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_7/A_3236-Get-more-from-Windows-Updates.html ) this can be a very effective method of keeping your network of Microsoft products up to date.

There is however one drawback, by default SBS 2008 is configured to download updates for all Microsoft Products, and if you change this you will see the “Updates = Not Available” message under the network Essentials Summary in the SBS Console.  Which whilst not technically a problem, if you are providing consultancy to a company who use this monitoring screen as a method to check the health of their server will result in the “My servers not working properly, what am I paying you for?” (screen shot below)
 WSUS-Error.jpgFear not, we can simply move the WSUS Data to a different drive so it is no longer clogging up valuable space on the System Drive.

Moving the data

Where ever possible with Small Business Server we should always use the wizards to make …
6
This guide is intended for migrating Windows 2003 Standard with Exchange 2003 to Windows Small Business Server 2008.

You will need the following:

Before we can start the migration process there are a few things we need to do on the Windows 2003 server.

First and foremost make sure you have a SYSTEM STATE backup.  This can be done with the built in Backup tools or a 3rd party product, but this needs to be done PRIOR to any of the following steps and is probably the most important step of the whole process.
If the Windows 2003 server has more than 1 Network card then all apart from the LAN connection will need to be disabled.
The assumption is that this is a single server scenario and DHCP/DNS are also installed on the server you are migrating from.  Therefore please ensure that the Windows 2003 server has got ONLY its own IP address configured in the TCP/IP properties of the network card.  There should be no external DNS servers listed here.
The gateway should be the LAN IP address of your router.
If you have made any changes to the above configuration it's best to restart the server so that DNS is updated and all the services are bound to the correct adapter.
15
 

Expert Comment

by:clesin
Comment Utility
What about the DNS settings after the install of the SBS?? I'm getting dcdiag errors.
0
In the event you manage a Small Business Server 2003, and you are audited for PCI compliance, there are several changes you must make in order to pass the audit. I can take no credit for discovering any of these fixes or workarounds, but there is no single place to find all of the information you need, so I have put it together in this article. When you complete all steps, reboot your server, and you should be good to go. (You can restart IIS after each step, but I recommend you simply do all of them and then reboot). If you are strong with technology, you may conduct your own security audit to verify these changes to your server.  There is a tool called Nessus (http://www.nessus.org) which is free to download and use for 14 days.

I STRONGLY recommend you backup your entire server before you begin, and backup or export any files/registry keys that you change in the process of following these instructions.

Audit issue 1: SSL Weak Cipher Suites Supported

Description from Audit:
The remote service supports the use of weak SSL ciphers.
The remote host supports the use of SSL ciphers that offer either weak encryption or no encryption at all.

Workaround:

Click Start|Run, and type regedit, and click ok
Navigate to the following Key: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers
For The following subkeys: RC2 40/128, RC4 40/128, and RC4 56/128 do the following:
Right-click to create a DWORD value called "Enabled" and leave…
7
 

Expert Comment

by:MrSteven
Comment Utility
it appears that the workarounds for 3 and 4 are reversed
0
A lot of problems and solutions are available on the net for the error message "Source server does not meet minimum requirements for migration" while performing a migration from Small Business Server 2003 to SBS 2008. This error pops up just before the Migration Wizard starts and after reading the answer file SBSAnswerFile.xml.

Since me and one of my colleagues just spend a Friday night searching, an extra post/article could be helpful for others.

Our issue was caused by using two versions of the SBS 2008 DVDs.  One with SP integrated, and one without. In the new DVD, the SourceTool has been updated.

An important change is that the new tool has an installation package (SourceTool.MSI) while the existing one is a standalone executable (SourceTool.exe). This MSI package needs to be installed on the source domain controller. The new tool must be used with the new media. The new tool will work with older media, but not the other way around.
1
 

Expert Comment

by:EXhermelin
Comment Utility
I love you ;-)

Just wasted a day because of this, rather silly, problem.
Suites me right for trying to be clever and prepare things on the source server using my old trusted files.

Thanks
0
 

Expert Comment

by:IBS_Tech
Comment Utility
Wish I had found this 6 Hours ago!

0

SBS

58K

Solutions

28K

Contributors

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).