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

Using SBS 2011 (Exchange 2010) with latest patches. When trying to search via OWA we get a message 'The action could not be completed. Please try again'. we also get application log error 9877 (ExchangeIS Mailbox Store) - error code 0x80043629

After much trial and error we have found the search (entire mailbox) will work if we start when clicked in a search folder (e.g. 'For Follow up' or a manually created search folder) but if we start clicked in a normal folder (Inbox or ever a folder created within the Mailbox). This gives us a workaround but not a solution. This implies that the search index is OK.

We have tried all the standard fixes
Run PrepareAD (from SP3)
Run Prepare Scheme (from SP3)
Rebuild Full Text Index Catalog

Nothing works.

The clue seems to be in the fact we CAN search if clicked in a search folder, even though we do a search on the entire mailbox but cannot search if we start in a normal folder (even if we just select search this folder only).

I think we need the help of a person well versed in the Exchange Search background process.

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

I had this question after viewing On an SBS 2011 server what do you think about turning off WSUS and how would you do that?.

The SBS Console shows that the 3 workstations are missing 10 or 11 updates that have been downloaded.  But the Updates tab of the console does not show any undeployed updates and the workstations think they are up to date.
A client of ours has an onsite Exchange 2010 server, in fact a SBS 2011 box. They previously had two accepted domains hosted in Exchange, Domain1 and Domain2. They wanted to move Domain2 off their server and onto Office 365. I successfully did that and DNS now points to their Office 365 server for Domain2. Unfortunately when users in Domain1 send mail it is still routed to the Domain2 mailboxes on the SBS 2011 box and not to Office 365. Outside users do not have the problem. I removed both the policy and the accepted domain settings in Hub Transport for the organization, but the problem persists. Do I also have to remove all the user accounts and mailboxes from the server to get it to send Domain2 mail to Office 365?
Since updating the  certificate o a windows server 20o12 r2 essentials I get the following error while trying   use remote access via the web remote access
has anybody seen this before ?
We have an SBS 2011 (Exchange 2010) for which OutlookAnywhere has stopped working, with some weird behaviour.

New Outlook profiles can't be set up at all from outside the network (Autodiscover is setup using the SRV record method and tests out fine at, but they setup fine inside the network.   Laptops that are setup inside the network may or may not work outside the network - we have one user who was set up recently who works fine outside the network, another that doesn't work outside.  It also doesn't seem to matter which Outlook version is used - both users described above are using Outlook 2016, but we also get the same client setup problem in Outlook 2010 and 2013.

When trying to setup Outlook from outside, the autodiscover part works fine, but it then bombards the user with credentials prompts and ultimately crashes Outlook.  The same thing happens if a working user takes their laptop outside the network.

Running the Outlook Connectivity test at results in the following error:

Attempting to ping the MAPI Mail Store endpoint with identity: localserver.localdomain.local:6001.
The attempt to ping the endpoint failed.

Additional Details
An RPC error was thrown by the RPC Runtime process. Error 1818 CallCancelled
Elapsed Time: 33713 ms.

Exchange version is 2010 SP3 Standard, it has now been updated to RU18, the problem existed before RU18 was installed.

Hi all,

Existing domain xxxxx.local, new domain xx.local. Existing domain is controlled by an sbs (2011). New domain DC is server 2012 R2 and a seperate server (again 2012 R2) hosting exchange 2016.

Subnet .252. some computers on 54.x and all others (inc;luding all servers) on 55.x. (52.x and 53.x to be utilized later on for voip/guest wifi).

Old AD is a complete mess, better to start from scratch than attempt migration. New AD has been set up correctly, all ad accounts exist, clean security groups, new mailboxes to boot.

Need to 2 phase the site migration as too much work to squeeze in over a single weekend whilst offering client a mostly live environment (they need to remain operational during most of the weekend too).

Phase 1 exchange migration, the intention is to set all outlook (2010 and 2013 mix) clients on site machines to have new profiles that are pointing at the new exchange server using outlook over http, using remote.<external domain>. Exchange 2016 virtual directories all configured to use the external domain, including autodiscover. New SSL cert for remote.<external domain> installed to new exchange 2016 server. The intention is at the point of phase 1 of migration, change sbs dns forward for remote.<external domain> from itself to the new exchange server.

Phase 2: over a weekend move all pc's to new domain and change domain on data server (which is seperate to the sbs but hosted on its own physical box currently on the sbs's domain).

I'll be spending my weekend migrating a customers SBS2003 server onto Server 2016 Essentials and Office 365.

What are you guys up to?  Any interesting projects?
LVL 24

Expert Comment

by:Brian B
Architecting an all-fibre network with 10 different switch rooms, VMWare with a 3PAR SAN and detailed on specs on hardware that won't be purchased for another 1.5 years. All at customer's request.
LVL 22

Author Comment

by:David Atkin
Makes an interesting day Brian!  They're sexy looking devices those 3PAR SANs
I'll preface by saying, yes, I'm rolling out a new 2012 based Active Directory, but...

Our FSMO master died in a way that didn't want to be resurrected.

Originally I had, all Win 2003 SBS AD domain controllers, currently running win Windows 2000 native mode:

AD01 - Primary, FSMO master
AD02 - secondary DC
AD03 - Tertiary DC

AD01 died in a way where it was not salvageable.  

With AD02, I Seized the FSMO roles, and made it the new "master"

Now, replication between the two are broken. AD02 (new master) has the "DSA Now Writable" Dword (4) in it's registry.
AD03 was up a while when we were configing AD02, so the databases became out of sync.

Most all instructions I see say the only way to fix replication is to demote, remove from domain, rejoin, and promote the "bad" server, in this case, my Master (now AD02).

Currently, I made AD02 as the Master via seized roles from dead AD01.
AD03 is my only other DC, acting as secondary to now-master AD02.

Another method crossed my mind, and wanted to see if anyone has tried this...or, if anyone else has another way out, other than demoting my primary AD02.

What if I were to DCPROMO AD03 (a secondary DC which is not receiving replicated data), and remove it from the domain as as AD server, then re-join as a new secondary server?
Would this also clear the "DSA Not Writable" flag on AD02?
I do not care about the orphaned objects on AD03. If it would simply pick up exactly what my new master has, that would…
My client has sbs 2011 server , exchange running, on her local machine she deleted a folder structure ,she needs to recover that structure.
We have storagcraft backup from the server , but no arrangement for individual PST files on users folders. Is there a way we can recover from the server her folder as its roaming profile?
thanks in advance

Her machine is windows 8 , with outlook 2010
They also have GFI mailmax
he whole system appeared to be running correctly and I have connected all of the workstations as well as the shared folders.  It is now live and running

I then attempted to run the configure Implement Group Policy Wizard after removing all of the old SBS2008 policies from AD.  It failed.

I then run the Essentials Tester Power Shell Script.

This showed that there where two certificates for the dashboard, on OK and one not (I don't think this was relevant).  I removed the incorrect certificate from the personal store and the script now shows no errors

The dashboard log is showing an error, but I cant work out what it is telling me.  I 'think' this is certificate related but I cant see where.

I then ran the Office 365 integration wizard to see  if that was also affected, which it is

The log is as follows:-

[10300] 170720.095223.4991: General: Initializing...C:\Windows\system32\Essentials\Dashboard.exe
[10300] 170720.095223.5772: General: Failed to open ADTestHook registry key.
[10300] 170720.095223.5772: General: Failed to open ADTestHook registry key.
[13916] 170720.095223.6085: General: Color branding started
[13916] 170720.095223.6085: General: Processing Microsoft default SKU branding colors XML
[13916] 170720.095223.6085: General: Branding colors XML parsing started
[13916] 170720.095223.6085: General: Branding colors XML parsing ended
[13916] 170720.095223.6085: General: Looking …
Get 15 Days FREE Full-Featured Trial
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

We have a SBS 2008 server at the office.
We are going to phase out the office server and move to SharePoint.
We have Office 365 and as a test we have setup a new employees Surface on AzureAD.
We need to still be able to access the SBS 2008 shares but can not see them.
We get an error 5 access denied
Ping works.
I have exchange 2010 on sbs 2011. I accidentally deleted a users inbox, went to try to recover the orphaned inbox but exchange did not save the orphaned inbox. I found a back up of the edb file and want to try to retrieve the users inbox from it. is it possible to mount the old edb file and export his inbox to a pst so I can import it into his new inbox? can this be done without causing issues on the current live mailbox?

On a server we administrate, the POP3 Connector seems to stop randomly once every week or so for the last 6-8 weeks. This is resolved by just starting the service and all goes back to normal.

Going through the event log doesn't show up anything, just various errors relating to failed email delivery.

Does anyone have any suggestions as to what may be causing this to happen?
We are migrating from Windows Small Business Server 2008 (SBS) to Windows Server 2016.  The DHCP Server has been migrated to the new server.  Both domain controllers now have the DNS and Active Directory roles.  I am moving the file server role to a third server, and DFS Replication is not running on either server.

I ran DCDIAG to see if there are any issues and discovered that the new DC does not have the NETLOGON and SYSVOL shares.  After doing a google search I have found a bunch of reasons this could be happening.  I see something about DFSR, but the shares are present on the old 2008 DC.

Where do I start?  I would rather not make any more changes than necessary on either server.
Hi all,

I'm attempting to update what is an SBS 2011 server's Exchange version 2010 to SP3, so that the organization can install a 2016 Exchange server.  The current version of the Exchange is 14.01.0438.000.

When attempting to install I get the following error.

[REQUIRED] The Mailbox server role is not installed on this computer.

Whats more odd; is about 50% of the time, I also get same error relating to the hub transport role.

And even the log file thinks Exchange role is installed, line 31.

Line 25: [07/18/2017 01:54:18.0286] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
Line 31: [07/18/2017 01:54:18.0468] [0] 'MailboxRole' is installed on the server object.
Line 49: [07/18/2017 01:54:35.0017] [1] Setup launched task 'Start-PreConfiguration -Mode 'BuildToBuildUpgrade' -Roles 'LanguagePacks','BridgeheadRole','ClientAccessRole','MailboxRole','AdminToolsRole''  
Line 51: [07/18/2017 01:54:35.0651] [1] Beginning processing Start-PreConfiguration -Mode:'BuildToBuildUpgrade' -Roles:'LanguagePacks','BridgeheadRole','ClientAccessRole','MailboxRole','AdminToolsRole'
Line 57: [07/18/2017 01:54:35.0933] [1] Loaded component 'Prereq Configuration' with 2 task information blocks from 'res://MailboxPreConfig.xml'
Line 81: [07/18/2017 01:54:36.0606] [1] Executing: $RoleRoles = 'LanguagePacks,BridgeheadRole,ClientAccessRole,MailboxRole,AdminToolsRole'
Line 257:             # Install any
I'll be doing this tomorrow but wanted to get a head start as far as information goes today..

Added a Windows essentials Server 2012 into an environment and set up so they both sync to each other.  Everything worked fine for a couple of weeks.  With intentions of getting rid of the 2003 server shortly. They were replicating to my knowledge because all of the users etc transferred over to the new server.

Fast forward to now the 2003 server is shutting down every hour saying that there is a license issue. This is causing clients to lose internet access and other resources.

What do I need to do to completely get rid of the 2003 server?
I was there this morning and the 2003 server is getting a journal wrap error?
I had an issue with a PC losing the trust relationship earlier, therefore I had to remove it from the domain and re-add it. At the same time, a colleague was decommissioning an SBS 2011 server as it had been migrated over to Server 2012. However I was unable to join the domain and kept getting an EM saying the DC could not be contacted.

I tried adding the DNS of the server to the NIC, using domainname.local etc and nothing worked. I powered the old SBS server back on and I was able to join the domain. What I need to know is why the old SBS server is still needed to join the domain, I am looking down the DNS route, possible a rogue srv or ptr record but I'm unsure where to start.
hello I have a Dell poweredge server running SBS 2008 which hangs when applying computer settings. I can log on to it with safe mode for networking, when I try to go into directory Services restore mode I get an error that there are no logon servers available.  I've disabled any non-critical Services, ran sfc scannow.

any advice would be greatly appreciated, TIA
I have domain currently on Windows Small Business Server 2003. It has 20 users. It provides Active Directory logins, DNS, DHCP, limited file sharing (most I’ve migrated to Office 365).

I’ve created an account in Azure and have it linked with our business Office 365.

Instead of a migration, can I purchase a new Windows Server 2016 Essentials and sync it to the Azure account I’ve already created?
Do I just use the same domain name that is with Azure during setup?
What fees would be associated with this on Azure? It’s is per user or per device?
Should I even be considering this type of setup?

This is at a church and I’m the IT department.

Any suggestions or advice is greatly appreciated.
Ready to get started with anonymous questions?
Ready to get started with anonymous questions?

It's easy! Check out this step-by-step guide for asking an anonymous question on Experts Exchange.

Recently a user's mailbox became corrupted and could not be accessed by Outlook or OWA.  I deleted the mailbox and then created a new mailbox for the same user.

The delete process instructed me that the user would be deleted also.  We don't use the server for anything except email and no other servers involved so I was okay with that.  I created a new user account and mailbox using the same alias and info as the original account and mailbox.

Windows Small Business Server 2011
Exchange Server 2010
Outlook 2016

When users attempt to send an email to this user, the cached version of the email address must be pointing to the deleted mailbox because the email bounces back with a recipient not known condition.

If you delete the cached address in Outlook and then select that person, the emails flow fine from that time forward.  Deleting the cached version is all that is needed.

However, I don't have that same functionality in OWA and I have one user who refuses to use the Outlook Windows client.  :(

Is there a way to remove the one address from the OWA cache so that like Outlook it will pick up the new version of the address?

This OWA user is 80+ years old and refuses to use Outlook because her recipients are not cached in Outlook and she doesn't want to have to re-enter them into Outlook.  As a result, clearing the entire OWA address cache is not a solution as then she would have no addresses in the cache.  :(

Any suggestions?

Thanks in advance!
So we're doing some housekeeping on the server to cleanup any unused accounts etc before we start migrating emails to hosted exchange and then migrate to server 2016. When deleting a user account we get the warning 'Powershell pipeline returned an error. Please consult your log file for further details', firstly I'm not sure what log file it's referring to and secondly I'm not even sure this is something we need to be concerned with as the account and associated email address does seem to get removed, at least it no longer shows in the SBS console or in Exchange.
Does anyone know what steps we need to take to identify and resolve the problem or even if we need to bother if we're planning to migrate to hosted exchange and server 2016 in the next few months? By the way, this only affects deleting accounts, creating new accounts works fine.
I setup a distribution group on a SBS 2011 machine (Exchange 2010) and forgot to put in members to the group.  So email did get delivered, and I can find them in the message tracking results, but how do I get exchange to re-submit them now that there are people in the group?  As I recall, there isn't a way to do it, but I am hoping someone knows a way.
In the process of adding 2016 servers to an existing 2008 SBS domain - should I have a 2016 DC in the mix before doing this?
After replacing a failed disk in my server ,it appears as if the db isn't mounting.
It worked for a while after the hot swap,but has been down since about 5 yesterday.

Any suggestions
Have SBS 2011 w / 1TB drive this morning it shows maybe 30 MB on drive . Not sure what's eating up the disk space since Users Files and Exchange database is on separate drive showing plenty of room ...
Could this be log files doing this ? best way to find out what's taking up the space and if it can be deleted ASAP to put the Server back in operation ..






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).