We help IT Professionals succeed at work.






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

DNS issues after replacing SBS 2011 Domain Controller with Windows 2019 Standard Server.
Setup 2019 server as domain controller. All users were picked up by the new DC. The issue is that some domain member computers loose contact with the domain. Drives mapped using server names fail but when mapped by IP address they work.
On some computers adding a domain user to the local administrators group the add function does not see the domain.
My rather unsophisticated assumption is that this is a DNS issue and I "blame" the new DC since it is also the DNS server and DHCP server for the domain.
Any troubleshooting tips would be very much appreciated.

I am looking for some help with planning the replacement of SBS 2011.  I see a few threads on the topic already, but they seem to cover a transition to Essentials.

I'm already looking at 30 users with potential to grow, so I think we have already outgrown the 'small business' part of SBS.  

I won't pretend to know much of anything about licensing/server features/etc., and don't stay current with M$ release 'news', so starting from scratch would be an accurate statement.

That said, I need to make sure I can replace/replicate the current functions of 2011.  

No doubt this list is far from complete, but these are the things I know it does that I'm worried about replacing (assuming DC/AD roles are covered no matter what route I go)...

  • On-site Exchange server
  • OWA features for rdp
  • Backups
  • File storage
  • Everything else I don't have the foresight to realize I'm losing

We don't use SP and don't have an intranet...so two things off the list of worries.

I know O365 is an option to replace the on-site exchange server, but I have my concerns about going cloud...namely cost effectiveness, security, and data retention.  I also don't know if it's a seamless transition in terms of features available to Outlook users.

As for the OWA side, we have a few users that remote in frequently from home.  I'm not really sure what …
I had a friend of mine with a very small company and a Windows SBS 2011 server that got hit with ransomware.     Her backup drive was also taken out by the attack.    I was able to help her get a new server up with Windows 2019; however, it would be helpful if we could get her old files back.   I see utilities from McAfee and others that may unencrypt, but I know knowing about them.   We also have the backup drive and thought about sending that off to be recovered.  Any ideas would be appreciated.  The suffix on all the files is U8E598.
Working through some issues on a Server 2016 Essentials server and noticed that the remote web access portal site (remote,domain.com/remote) is not accessible internally (on the LAN) but works fine externally. If I ping the site internally from the Server 2016 Essentials server, it replies back with the public IP address of the server. This seems correct and matches what we see on other Server 2016 Essentials servers with Anywhere Access/RWA working internally and externally. Likewise, if we compare DNS settings (Forward Lookup Zones) between working and non-working servers, settings appear to be the same.

Internally, if I enter the public IP in a browser, the page does not resolve. Externally, it does resolve, as does the DNS address - remote.domain.com/remote.

Running the Anywhere Access repair wizard did not address the issue. It completes successfully, but does not allow us to access the site internally on the same LAN as the server. Doesn't matter if I try from the server itself or a client workstation.
Microsoft exchange manage more than 1 domain internal and external mails
I have a SBS 2008 SP2. I need to install .Net Framework 4.8. I can't seem to be able to find the download that will not error when trying to instal. Te error referenced a compatibility problem.
SBS 2011 standard to Windows Server 2016 Essentials migration
Microsoft's docs recommend to move the DHCP funtion to the router.
Is there a good reason for this as opposed to moving it to the 2016 server?
Has anyone had favorable/unfavorable results either way?
If on 2016, can the existing scope/parameters be moved easily from SBS?
windows server 2011 sbs broken boot record server wont boot all files are there no blue screen just a boot loading error. Any thoughts Thanks in advance
Installing Windows server 2016 essentials from the sku, it has preinstalled the experience role.
When joining sbs 2011 standard domain for migration, should the wizard be used, or add the AD role?
If the role, is the essentials setup wizard to be run after?
Hello, I'm administrator of a Windows Server SBS 2011 machine which has been having problems with Windows Updates for several months.

It won't download the updates, so neither server nor clients (which use the server as update source) are updated.

When I try to manually download, I get error 8024400E.

On event viewer I've got many ID 16 events with "WindowsUpdateClient" origin, stating "Could not establish connection. It is not possible to connect to the Automatic Updates service and therefore it is not possible to download and update the updates according to the set schedule. Other connection attempts will be established." (This may not be the actual English text, I translated from Italian).

I already had similar problems years ago, but the errors were different.

Under the registry folder I have two keys WUServer and WUStatusServer pointing to http://SBSNAME:8530, so I guess the server is unable to connect to itself?
sender getting bounce back
#< #5.0.0 smtp; 550-Requested action not taken: mailbox unavailable> #SMTP#
I'm using Exchange 2010, where can I allow this in in Exchange
Migrating from SBS 2011 Window Server Essentials 2016. I have done this migration a few times but have never migrated redirected folders.
I see this info which seems straightforward. https://docs.microsoft.com/en-us/windows-server-essentials/migrate/configure-folder-redirection-on-the-windows-server-essentials-destination-server

Assuming I follow the directions are there any gotcha's with the process? I almost feel like it's too easy, lol.
Hello, there is a problem (new one, it wasn't happening until a few days ago) on a W10 Pro client inside a Windows Server SBS 2011 domain. Folder redirection is enabled for all users (desktop, documents, downloads, everything mostly) but suddenly on this one client Word and Excel can't seem to open files on the server anymore. Office version is 2019 Pro.

You can take a look at the screenshot at the bottom: it's in Italian, it says the file can't be opened because either it doesn't exist (it does), it's in use by other software (it isn't), its name is already being used by an open file (it isn't).

If I copy that file on the local drive, it will just work. This happens only with Office apps, Openoffice and all other apps open files in the same locations with no problem.

I already tried an online recovery of Office to no avail, and also adding the server's main share with all its subfolders to the allowed paths, to no avail again.

Do you guys have suggestions? Thanks.

The damn error.
Looking for some help here so we can get the server running long enough for our migration to the new one we ordered. We have an ongoing issue where the server blue screens every 60-90 minutes all day long. I pull the server on overnights and now two weekends and not one reboot or BSOD (currently up time is 2 days and 18 hours). But from history when I return it to the site it will again start like clockwork. So far:

•      I have moved to another power outlet (but power doesn’t seem likely because once I disabled auto restart it always stays on just with a BSOD).
•      Scanned drives both at boot and with external tools
•      Run Windows Memory Diagnostics Tool many times (No problems Detected)
•       Unplugged any device attached (even changed USB keyboard and mouse)

I couldn’t see it being hardware, driver, or a service since it runs clean at my site. I even ran all day today since our office is closed just in case it was some “work hours” thing. No issues. I spent the last 48 hours going entry by entry in the event viewer and found some disturbing items. It looks like we were attacked based on a share we did not create in


Value name
Path=D:\Virus Files\User Folders\Tom H\Tom H\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5

Also I found in the log TermDD Event 56 several entries that …
I need to copy all the email content from SBS2011 Standard running Exchange to a Synology NAS. This is in prep of removal of SBS and going to Office 365 E3
Is there any issues with running SOPHOS on top of SBS2011?
I have an SBS 2011 server I am trying to retire. In preparation of this job I have been running some DNS checks, I seem to have a DNS Delegation issue and have no idea how to correct this. We have two domain controllers, wmkl-sbs and DC1.

Here is the specific error I am seeing. I have also attached a bunch a zip file that contains a bunch of text file from other tests and information that I think might be helpfulDNS-Tests.zip in finding a answer to this.

 TEST: Delegations (Del)
                  Delegation information for the zone: WMKL.local.
                     Delegated domain name: _msdcs.WMKL.local.
                        DNS server: dc1.wmkl.local. IP: [Valid]
                        DNS server: wmkl-sbs. IP: [Valid]
                     Delegated domain name: wmkl.local.WMKL.local.
                        Warning: Delegation of DNS server dc1.wmkl.local. is broken on IP:
                        Error: DNS server: dc1.wmkl.local. IP:
                        [Broken delegation]
                        Error: DNS server: sbs.wmkl.local. IP:
                        [Missing glue A record]
                        Warning: Delegation of DNS server wmkl-sbs.wmkl.local. is broken on IP:
                        Error: DNS server: wmkl-sbs.wmkl.local. IP:
                        [Broken delegation]

Thank you for your time and help
SBS 2011 standard - self-issued cert expired.
Reissued but resulting cert doesn't work and console continually crashes.
All updates are applied.
Console crash detail:

Problem signature:
  Problem Event Name:      CLR20r3
  Problem Signature 01:      console.exe
  Problem Signature 02:      6.1.7900.1
  Problem Signature 03:      4ce6d9cf
  Problem Signature 04:      Microsoft.UpdateServices.BaseApi
  Problem Signature 05:      3.1.7600.307
  Problem Signature 06:      5c4247ae
  Problem Signature 07:      600
  Problem Signature 08:      1b
  Problem Signature 09:      N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
  OS Version:      6.1.7601.
  Locale ID:      1033
  Additional Information 1:      d268
  Additional Information 2:      d26823b5dae45a83a876df02894236e9
  Additional Information 3:      6515
  Additional Information 4:      6515434508b5c763aabf95beda54d416

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:

Remote attempt yields:
Your connection is not private
Attackers might be trying to steal your information from mail.clientxyz.com (for example, passwords, messages, or credit cards). Learn more
I would like to setup a test environment of VMs on Server 2019 Hyper-V that eventually migrating  all current physicals to VMs.   I currently have Small Business Server 2011 standard with a backup domain controller and File server on a given network.  I would like to make sure I can safely setup and test the VMs on an isolated network.  I have setup a test workgroup for the Hyper-V machine separate from the current domain. Is that enough to prevent any issues or do I need to create a separate subnet for the Hyper-V as well?
I have a client site that were forced to upgrade from Office 2003 and Windows 7 to Office 2010 and Windows 10.  They are connected to an older server running SBS 2011. I am getting the security alert that the security certificate has expired for their domain name whe starting Outlook 2010 and I cannot get it stop with the error message.  We have not needed a certificate in years until we went to Outlook 2010.  Is there anyway to disable the message at the workstation level?
I am trying to remove the DHCP Server role on SBS 2008, hangs on "Initializing removal" step.
This is SBS2011 which has Exchange 2010 running on the same server.
I would like to let my associate be the Exchange Admin to fully manage Exchange 2010 on his own PC without working on SBS2011.
Is this possible?
I think the challenges are
1. How can I assign him Exchange Admin privilege? He should not be assigned domain admin.
2. What software should I install on his PC?
3. Anything else?
Please help
Hi, i'm facing weird issue with an extremely slow Win10 client connected to an SBS2008, other computers are connected to it with exactly the same material and confirguration  with novembrer update and it works fine (shared folders access is quick and computer respond quickly).

This computer is very slow, the profile used on this one is the most important (14,4 Gb data), while other user profiles are only 3 to 5 Gb.
It shows difficulties to download emails and access shared server directories.

It runs normally when it is disconnected for this network and connected to another one (without any server)

Any help would be very helpful,

Thank you very much
I have a single server running 2008 SBS that will be replacing with a new 2019 STD server. When trying to promote 2019 to a DC I found that I need to migrate FRS to DRSR, no biggie. Looking at the event viewer on the 2008 SBS DC under File Replication Service I came across error 13568 which is a Journal Wrap Error.

My question is if I enable the registry flag to Enable Journal Wrap Automatic Restore on a site with a single DC where will the SBS 2008 DC pull a copy of the SYSVOL folder from? Or, am I other thinking it and it will restore the current SYSVOL folder and clear the error state that AD is in? I just don't want to set this registry value and the machine will delete the SYSVOL folder and have nothing to restore from. I haven't run into this in an environment with a single DC and want to use caution.

Always best to ask others in a case like this. :)

Thank you,
I migrated 10 users from Exchange on a SBS 2011 server to a hosted Exchange 2016 solution. Everything went smoothly using MFCMAPI from http://mfcmapi.codeplex.com to export the autocomplete list to .msg except on 2 Windows 10 machines running Office 2013. I exported the autocomplete msg from every machine on the network before the migration and these two didn't work. When I import the exported autocomplete msg file, it doesn't show up in the list and, of course, doesn't re-populate  the autocomplete. These two PCs have in common that they were using roaming profiles. I have gone back to the old server with another computer, allowed the roaming profile to configure itself, exported the autocomplete msg again, copied it to a test PC so I don't keep disturbing the end user, and it behaves the same on the new machine, so it's not the PCs, there's something about those two files or that tool just can't export data from roaming profiles.
I'm stumped and any help is appreciated.






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