SBS Trench Notes v.1.0
An Unofficial list of FAQs from the SBS
The following is not an official MS
technote, heck, it not officially anything. This is a compilation of common
approaches to SBS for different circumstances and a rumor guide. There are
MS technotes referenced and embedded below with preferred solutions when
handy. This document has not been review or approved by MS or anyone. This
may have some controversial ideas and may even harbor outright errors. This
is a compilation of information, not a substitute for smart management of
your own situations.
If you have recommendations, corrections,
or additions, please be kind enough to forward them to me in an HTML format
or plain text. Include any technotes you have reason to believe would help.
I'm not really looking to start a newspaper here or become an investigative
reporter. I'm trying to avoid some of us posting the exact same stuff over
and over again. I know someone will suggest making a "Table of Contents" or
outline format, numbering or whatever. Sorry. I put in my 3hrs already,
maybe next revision.
㯰yright 11/09/99 Prepared by Jeff Middleton of Computer Focus, Inc.
Distribute this freely, don't misquote me,
no warranties or assurance provided for errors or anything. Don't charge to
provide this to anyone. Leave my copyright notice in the document to retain
this as a public document. TMs to their respective owners. The attachment to
this has not been reviewed in any regard by Microsoft and does not intend to
speak on behalf of Microsoft.
Check list for first time
+ MS SBS Technical FAQs:
+ For general MS information and
whitepapers on SBS Deployment issues:
+ For planning and installation:
Please accept opinions as recommendations that at least one person feels
strongly enough to try to get others to agree with. If you don't agree, you
are only forewarned of the concept and that helps too, right?
+ Good and Simple Partition Size
Choose to create a partition of size 4096 and format type of NTFS. When the system finishes loading, you can then create a second partition under Drive Manager to allocate the reset of your space as a data partition.
+ I'm confused or frustrated about.......Booting, installing disk drives
The very best resource for SBS users and disk problems is this one with about ten other links included:
For SCSI and other odd problems and preparations:
+ Set Swap file to at least 256Mb at your first available option
Once the SBS has
finished installing the NT portion of the setup, but before it runs the
setup for SBS Server Suite of Apps (i.e. when you get the first option to
"Shutdown NT for a Reboot Now?"), change the swap file size. Use 256Mb or
1.5x the amount of RAM in the box, which ever is larger. Otherwise you will
get slow performance and virtual memory problem reports. This can be done
later, but for best results, do it before the drive is loaded up.
+ Single partition with SBS on a drive larger than 6G not recommended.
If you are
concerned that you wanted the entire drive as 14G, you don't. If you think a
single partition makes more sense, it doesn't. Separating the system drive
into separate partitions from the user data drives is much smarter. It
solves technical and planning problems down the line.
+ If you think you want a boot partition bigger the 7.8G, you don't.
I leave you to read up on this then follow this advice. Just don't.
+ Need more than 4G system partition.
If you think that you want a boot/system partition larger than 4G and less than 7.8G, you need to pre-partition this drive with an existing installation of NT (likely on another machine or booting from another drive temporarily in this box).
If you think you need more space on the boot/system drive because your user data files and Exchange data all on C: may outgrow this partition at 'only' 4G, then you can choose in the SBS setup when prompted to locate many of these shared folders to the back partition. However, this is only if you create that partition first as well when you are in the floppy disk part of setup creating the first partition. Personally, I finish the install, then create the other partition, then I would just use the wizard to relocate them after finishing the install entirely, but before loading any users.
+ Moving or Splitting NT swap files, Exchange files, user files between partitions
If you have a single drive, or a drive mirror that is partitioned, or a RAID stripe acting as a single physical volume, placement of these various files makes no difference for performance. Just allocate for space planning.
Moving such files
that are shared folders is possible with SBS Console. Moving the Exchange
folders is possible with the Exchange Optimizer. Either can be done after
+ If you think you don't need or want to install all of the SBS programs
You are wrong. You
can disable them later, but install them all. Omitting things in the
installation will haunt you. Uninstalling them is equally dumb. At most,
disable the services.
If you think you want to install without attaching a modem first, you are wrong, you must to have a successful installation.
If you think you want to use an internal modem, you will receive unrelenting harassment from most everyone in this NG every time you post a question about your modem not working as you want. MS may support internals, but few folks here will give an answer that doesn't start with...'you probably should switch to an external modem...'
If you plan to use
only one modem for web, modemshare, RAS, and Fax, you will provide amusement
for everyone but yourself. This is not a beginner's topic likely to be fun.
You will spend more time on this single issue than all other things combined
in the SBS install. If you insist here is the documentation:
If you think that leaving the HCL will be pleasant, you probably like suffering too.
+ No NIC, more than one NIC, or broadband connect to web issues
If you plan to have more than one NIC in the server, you don't want them both in the server during the installation phase. Finish the entire install, then add the 2nd NIC.
If you add a second NIC to the computer, you must check the binding order and place the primary NIC at the top of the binding list for every protocol, disable WINS on the external NIC, make sure that Proxy LAT is updated for knowing where the local addresses in the LAN are and where the external ones are. If you do not do this, a volunteer will be funded by the 'Binding Fool's 12 Step Program" dues to come and beat you over the head with a copy of the SBS 4.5 Resource Kit for posting questions that are cause by bad binding order issues.
If you will use a router, preferred approach is a second NIC for the router.
+ My Network stopped working, I can't browse the server and such쏺P>
First of all, look
at this general KB for help.
Next check the
binding order again. Then:
Check to see that
DHCP is started and running and that there are not errors in the Event Log
I've got Browser
entries in the Event Log that a certain workstation "has forced an election
because it believes that it is the master browser". This is caused by
improper settings on a client workstation. There is documentation on
registry settings to change this with NT workstations or Win9x stations. You
need to disable the setting to become Master Browser or IsDomainMaster key.
If it is a Win95 station, go to the Network Panel and see if File and Printer Sharing is enabled. If it isn't enable it. Then edit the properties for this item. Under the option of Master Browser, set it to disabled. With this done, exit and reboot. If you have not desire to share anything from this computer, then you may go back and remove the File and Printer Sharing after the reboot.
+ My Network is slow, error rates,
computers send faster then they receive data.
Look at virus
scanning software, bad NIC, old NIC drivers, bad binding order.
+ POP3 vs Exchange SMTP
Go here for tons
of information on related issues:
Exchange SMTP mail is preferred, more expensive. POP3 will work. POP3
install after the SBS install is completed entirely. You must download the
POP3 Connector from the MS website, it isn't on the SBS distribution or
upgrade CDs. Find it here,:
POP3 will let you continue to use existing ISP POP3 mailboxes, or to setup a global mailbox for all the users in you office to receive mail as email@example.com . The configuration of the POP3 is integrated with the ICW (Internet Connection Wizard).
Please make sure that you have IMC set for routing "Inbound and Outbound", and turn up logging to maximum before posting questions...we'll just send you back for this.
Setting up the ICW
and internet services:
+ Using Office 2000 Professional instead
of Outlook 2K in the installation process
If you plan to preinstall an entire Office Pro 2k rather than just Outlook, this will chew-up over a Gig of space on the boot/system partition. It isn't completely necessary. There's a Q on this process, or you can just use the CD locally for each machine, there's no real difference in the experience of installation cause you still need the 25digit install code. To install Office Pro 2K, when prompted for the Outlook CD install key in the early part of the SBS install for a key number you still give it the key number from the Outlook CD no matter what. When you are prompted after the 3 SBS disks for the Outlook or Office CD, now you insert the Office Pro CD instead of the Outlook. You will have to modify the configurations according to the Q on Office installs to make the Office download automatically to each station, but this CD swap thing confuses many.
+ Workstation configuration for more than one user
No, you do not have to run setup for users or for software repeatedly for every user at every station. After the first user configures the machine by logging in, then all other users will have complete installations when they log in.
In order for a user login to work correctly, however, every user must have been designated to configure at least one machine in order to create the default login batch file for that user. If you have 10 machines and 10 users, then do each machine with one user. If you have 10 machines and 25 users, then you could use one user to configure each of the 10 machines, but you still must run a 'Configure computer for additional user' process on at least one machine for all of the other 24 users, even if they won't use that specific machine, this is what creates the batch file.
Yes you have to create a setup disk for every user,
yes you could just overwrite the same disk,
yes you can manually setup each computer manually if you want,
yes this is documented,
yes it is recommended to use the disk anyway,
yes it sometimes does not work and requires help manually.
On WIN98 machines, remove Microsoft Family Logon before running the setup disk.
What the client
SBS Fax doesn't forward to more than one user. SBS Fax does not trigger Inbox rules for alerts or redirection automatically. It just doesn't. No. You could look at 3rd party if this is important.
SBS Fax doesn't provide excellent reports.
information on all issues:
+ Remote Access and dialup questions
On the remote
client, disable the NIC in the hardware profile. Include WINS IP for the SBS.
Include a HOSTS and LMHOSTS file specifying at least the SBS server IP and
name with the #PRE file. This is documented in the HOSTS.SAM and LMHOSTS.SAM
files on your client computer. These sample files have the .sam extension,
the working copies you use should have no file extensions. Login into the
remote as the same username as you will use on the SBS, set the station
workgroup the same as the SBS domain.
To allow the remote station to access the Exchange, you simple configure the workstation in the same manner as the local stations. This is done either by hooking the computer on the network, or by manually configuring the software from the SBS CD client's folders.
Most of us recommend using TCP/IP only on this link, though adding Netbios can sometime help, sometimes hurts.
You will not get
better than a 33.6 connection from modem to modem with RAS and analog type
modems. Disabling v.90 or 56K protocols will help make the connections more
reliable, possibly even connect when the default settings don't.
+ Service Packs and WIN2k Compatibility
If you are running
SBS 4.5, MS has intended that all service packs are available to consider
for installation for both NT and the other applications.
NT SP5 is commonly
accepted as not having any particular disadvantages or issues for SBS. I you
are using SBS 4.0 or SBS 4.0a, you really should upgrade to SBS 4.5, not
apply SPs to those older versions.
SBS is not
planning on supporting Win2K anytime soon.
+ Administration and Reinstallation
Use the Console.
Use the Console. If you want to do something the Console does, use the
Console. Once you finish the installation of the SBS software, browse the
entire Console to find out what it does and use it. I guess that about
covers the console issues. Oh, there are these:
Do not move the
shared folders that SBS creates manually without using the console. The
wizard for moving "User Shared Folders" is hidden away in the Online
Documentation pages of the Console. If the console breaks, produces errors
and such, there are three very common reasons. Backup Exec 7.3 overwrote the
MFC42U.DLL and MFC42.DLL files. You must restore the originals from SBS CDs
and place them in the Smallbusiness folder. Second reason is the file
permissions on the shared folders is wrong or the folders are moved,
missing. Third, you have messed with the Administrator password or are not
logged in as the administrator.
administration, don't change the Administrator's password if you can avoid
it. If you must, use the Console Wizard. Don't try to give the Exchange
Administrator a different username. Leave all the SBS administration tasks
under a single username.
administration, Use Pcanywhere or else MS has Netmeeting as an Option. You
will want to download the Netmeeting 3.0 Update, in particular this allows
unattended answer by the host computer.
+ How is SBS different than the standard
Q&A: Migrating, Adding or
Replacing Servers in SBS LAN
Revision 1.1 12/15/1999
Previously titled: "Adding a Second
Server to an SBS LAN: What jobs should it do?"
This is not an official MS technote,
heck, it not officially anything. This describes an issue that occurs with
adding another NT Server to an SBS managed domain, and what jobs the server
could do. This document has not been reviewed or approved by MS or anyone.
This may have some controversial ideas expressed and may even harbor
outright errors. This is a compilation of information to use as you see fit,
not a substitute for smart management of your own situations.
If you have
recommendations, corrections, or additions, please be kind enough to forward
them to me in an HTML format or plain text. Include any technotes you have
reason to believe would help. I'm not really looking to start a newspaper
here or become an investigative reporter. I'm trying to avoid some of us
posting the exact same stuff over and over again.
㯰yright 12/10/99 Prepared by Jeff Middleton of Computer Focus, Inc.
Distribute this freely,
don't misquote me, no warranties or assurance provided for errors or
anything. Don't charge to provide this to anyone. Leave my copyright notice
in the document to retain this as a public document. TMs to their respective
owners. The attachment to this has not been reviewed in any regard by
Microsoft and does not intend to speak on behalf of Microsoft.
Summary of Q&As: (new
questions in Italics)
Another consideration is that we might want to install RAS for users to work from home. Would this be more efficiently installed on SBS, or the second machine? SBS has a 2-modem pool used for proxy and other dial-out applications, with the intention of switching to one modem and DSL for web access. Should I move the RAS activity for these users to another computer, this additional server, for instance?
Q&A on Server Roles with SBS
Beyond what is discussed here, are there other issues related to the topic of a second server that I should consider?
Certainly! This is not intended to exhaust the possible questions. You may want to review the MS knowledge base for keywords like BDC, member server, CALS, license or server.
In addition, check these two locations for more Q&A points that may apply:
The following location provides some design concepts about SBS that might be of interest on this subject:
Connecting or Migrating from NT Server (or reinstall SBS):
Can I migrate an installed configuration from an existing NT Server, SBS Server, SBS Evaluation installation, or a crashed/corrupted SBS installation?
The answer is essentially "No."
For the MS position on migration related issues, check these:
Very little can be brought over from a prior installation for various reasons, mostly, its because MS has acknowledge that it designed SBS to be a "first server" concept for a small company. As flawed as this "vision" may have been, it is further impacted by some designed limitations with SBS, limitations that suit MS marketing and technical goals for the SBS product line, at least as it was originally conceived circa the release of SBS 4.0.
SBS uses a scripted installation from start to finish. This script (and MS licensing) forces the SBS product to the following restrictions:
To be installed from scratch as the PDC of a new domain with a clean Security Account Manager database (SAM), the unique home of the domain security.
The ability to demote SBS to a BDC is removed.
SBS does not support trusts,
Therefore it is not possible to migrate accounts from another domain using trusts, or introduce SBS to an existing domain as a BDC then promote it, nor to operate in conjunction with a foreign domain. Since the SAM is created from scratch, it's not possible to "inherit" an existing domain, even if you are simply replacing the installation of the server within the same office on the same hardware!
This places the most extraordinary emphasis upon making excellent disaster recovery via a tape backup or similar process a very high priority. A reinstallation from scratch with SBS would potentially require extensive reconstruction of the entire domain, including the reinstallation of all BDCs, and the direct loss of all NT Workstation and Server domain user profiles and related resources.
While the filestructure and contents could be migrated, it's a potentially laborious process to maintain users specific file ownership in such a situation (if that's important), and all the shared resources will require modification throughout the LAN. The process would require an Administrator in the new domain to take ownership of all the files, flush the old ownership and permissions (ACLs) for files, folders and shares from the old (dead) domain. To return personal files to the user's ownership, the administrator must then reset the ACLs for the "new" usernames to allow the users to regain ownership of their personal files under their new username identity, and the users must then take ownership of the files accordingly.
SBS only provides a modest "Username Export" process for migrating from another NT or SBS installation. This only saves the typing of the account names, does not preserve the passwords, and does not maintain all the associated information on the users. It does create the Exchange Mailboxes for the users automatically.
With an Exchange Server to migrate, the problems are equally frustrating, but a bit more robustly recovered. The design of Exchange is also intended to use Site to Site migration for redundant backup and recovery, but this is unlikely in an SBS environment. Rather, there are two routes to follow. The simple route is to have all the user mailboxes save to .PST files (using Outlook or a mail client), or even use .OST to preserve the contents. The contents of the Public Folders would need to be preserved in a mailbox as well. Once the new Exchange Server is up an running, simply synchronize the .PST or .OST files with the new "empty" mailbox for that user. There is a tool available with the BackOffice Resource Kit to simplify the export of all mailboxes, if that purchase seems justified.
Alternatively, the Exchange Server databases can be migrated if the servername, site name, and domain name are the same. This is essentially a disaster recovery process. It can be a bit time consuming, intimidating, as well as frustrating to accomplish. The requirement to match the site configuration, as well as exact username identification could well cause one not to bother with this approach.
On the whole, migration into SBS from an existing NT configuration can seem a bit disappointing as compared to the options provided in a full NT Server or BackOffice environment, but since an SBS is typically in a small environment, the manual tasks are not completely overwhelming, just very tedious.
I have another document which may be of interest, it covers some specific issues related to "SID and Profile Issues in Reinstalling a SBS or PDC."
Can I migrate or integrate my SBS with other non-NT environments such as Mac, Novell or Unix/Linux?
Yes, MS has provided some more guidance on this for Mac or Novell.
No, I've not seen anything specifically on Linux or Unix at the time this document is written. However, integration of these is certainly possible, though one would not expect such systems to be SBS clients, more likely resource servers. Documentation available on routine NT and Unix integration would be the most likely course to pursue.
The comment inserted below is directly quoted from the MS deployment document at this link:
Small Business Server
4.5 was designed to run as a single server to support a business with up to
50 connected workstations. Several enterprise-class server applications and
services have been integrated into one solution and tested to work together
on one server. With the right server hardware configuration (discussed later
in this paper), you can run 50 heavy-profile users on a Small Business
Server᳥d machine at one time.
One common misconception
about Small Business Server is that you can only connect one server to a
Small Business Server᳥d network. In fact, you can connect any number of
Windows NT Server᳥d, Novell NetWare, and other servers to the network.
The limitation is that you cannot connect more than one machine running
Small Business Server to a network and that you must set up additional
Windows NT᳥d servers as either Backup Domain Controllers or Member
environments, however, might warrant connecting additional servers to a
Small Business Server᳥d network. For example, several line-of-business
applications are either especially resource intensive and should run on
their own server, or may require a special server. You may also have an
application that relies on a NetWare server, an IBM AS/400, or a variant of
UNIX. In each of these cases, you can continue to use Small Business Server
as your primary user authentication and communications server and easily
connect additional servers to support line-of-business applications."
Can I run my SBS in the same LAN with another SBS, or another domain PDC for a different domain "on the same cable"?
Yes, MS has documented guidance on this too in various places in the deployment information. The major issues relate to configuring the IP addressing, Proxy, and DHCP settings in a compatible manner. Of course, the SBS systems would not allow trusts, therefore the two domains would be uniquely isolated. Only with synchronized usernames and passwords would crossover access by a user be available.
NT Service Pack 5 is required for SBS 4.5 in order to prevent the DHCP server on the SBS from shutting down when it detects the presence of another DHCP server elsewhere. This is covered in this technote:
Should I configure my second server as a BDC for the domain?
The simple answer is probably "No", but there's some room for discussion.
With most NT networks, having a BDC is a very smart disaster recovery preparation step. With SBS, a BDC has significantly less value. Take a look at this KB from MS on the subject:
What is revealed is that with an SBS managed domain, there is no route to get a BDC promoted and take over the job of the SBS entirely, it can only provide logon services.
The double whammy of the BDC is that if you are forced to take the course to introduce a new installation of an SBS into an existing domain, there's no MS approved method to transfer a BDC from another domain into the new SBS managed domain. This is because, with normal NT, one must use the support of "trusts" to accomplish this, but since SBS doesn't support trusts, this path is non-existent. As a result, the only effective way to use a BDC from a foreign domain, even one that had the same domain name, is a task in itself. Either completely reformat the NT Server (former BDC), or to perform a fresh parallel installation of NT onto the same drive, then perform some file ownership and permissions maintenance cleanup. Either way, all of the shares and server configuration must be redone. This is such a significant process, it provides a very strong argument for NOT creating a server as BDC.
If the machine in question is a Windows Terminal Server, I would go as far as to suggest that making that computer a BDC would be very poor judgement because of the additional complexity that configuring a WTS involves as opposed to a simple NT server.
It turns out the adding additional NT Servers to an SBS domain can make a great deal of sense to only use them as member servers, not BDCs.
The only really good instance for having a BDC in an SBS managed domain is if there is a WAN or remote office involved. In this case, the BDC in the remote location can make a great deal of sense. The logic of this follows the common logic for having a BDC in any remote site, something that is discussed with routine multi-site NT installations. There's nothing unusual about the PDC being an SBS server in this instance regarding the wisdom of establishing a BDC in a different site.
We are considering installing a second NT server to act mainly as a file server. It seems to me that this machine should be configured as a BDC so that its files can be accessed even if the SBS machine is down for some reason. Are there any particular pros or cons to this?
Another consideration is that we might want to install RAS for users
to work from home. Would this be more efficiently installed on SBS, or the
second machine? SBS has a 2-modem pool used for proxy and other dial-out
applications, with the intention of switching to one modem and DSL for web
access. Should I move the RAS activity for these users to another computer,
this additional server, for instance?
There is not an absolutely right answer on this issue. There's actually a
significant amount of personal preference, as well a operational priorities
that could impact this decision. Here are few of the most common issues that
might be either unique or new to the SBS mindset.
If you have all the main fileservices (other than the userfolders on the
SBS) now located on the NT fileserver, you will find that you can shutdown
and reboot the SBS almost transparently because your multiuser accounting,
database type programs are not on the SBS anymore. Exchange and Proxy are
forgiving of such a move. The users are temporarily disconnected, but they
Can I install some of the SBS featured applications on the other server?
The simple answer, "No." You cannot "transfer" any of these services or applications to another computer. None of the BackOffice products (Proxy, Exchange, SQL) can be relocated, nor can the server portion of the SBS Fax or Modemsharing.
You can use any of the services that are commonly provided by NT Server, currently including the RAS Server, IIS, as well as the file and print services. If you are serious about establishing BackOffice services on a second computer, this will be a full repurchase of that product, plus all the client licenses that might be required. This is a question that really would deserve discussion with MS if you are not convinced to avoid it from my comments.
As always, my comments on licensing are intended to be helpful interpretations, but not the MS gospel.
One can run the client versions of the SBS software from this secondary server is that serves a valuable purpose.
On tip, if you add an additional server to an SBS environment, you should modify the TEMPLATE.BAT, or at least the USERNAME.BAT files for any users who will logon locally to the second server (from the keyboard) to avoid a series of error messages generated by the logon script. An examination of the TEMPLATE.BAT file reveals that a similar check is performed for the SBS servername that causes the logon script to exit.
If the SBS is down, can my users still logon to the network if I don't provide this additional server in the role of BDC', only as a member server?
Yes, but there are some issues here. First of all, for short periods of time your users will be able to access all the remaining available network resources due to NT providing "cached logins" for the users. What happens is that the NT server remaining will recognize the usernames as long as the cache of usernames remains active on that server. However, over a period of time, or after the reboot of the member server, the cache of names may be lost. At this point, NT workstations can still logon because they retain (in the local user profiles) information that identifies the users as part of the actual domain managed by the SBS. The member server will accept these logons continuously. For Win9x stations, when the cached logons expire, these stations will be denied access to all resources other than those available to "Everyone".
Would adding an NT Server require more Microsoft licenses to be purchased?
Yes, when you add the NT Server, you will have to purchase all the additional licenses for all of the users that will attach to this server. The simple answer is that none of the SBS licenses apply to the CALS require for additional NT Servers. Therefore, you would need to acquire all the NT Server CALS (licenses) you would otherwise expect for the LAN if the SBS and it's collection of related BackOffice services wasn't even present.
This does add some additional expense and that may be an issue, but it's not that expensive in the long run. If having a second server allows your office with 20 users to avoid 2-4 hrs of down time in the network, you probably have recovered the total investment for the server and the licenses.
Would adding an NT Server complicate the backup and filestorage procedures?
Yes, there are some issues here. First of all, to backup a remote server entirely, including the registry to provide a true recovery option for that server, this cannot be done with the native NTbackup software. You will need to look at a 3rd Party product that supports multi-server. While there are options to run a tape backup on each server, or to copy critical files across the network, or just run without the recovery of the remote server's registry, these are not very good practical approaches to the problem.
On the storage side, the biggest issues are these. SBS currently doesn't allow for transferring the default shared folders onto another server. The Exchange and SQL server files are also going to be local to the SBS computer. This means that if you add a fileserver, then you will need to properly consider the storage hardware for both machines, not just the SBS. By this I mean, if you have justified a RAID or mirror configuration on the SBS, then you will likely want to consider the same approach on the fileserver as well. This again can add cost to the decision, but that is just the reality of the situation.
From the standpoint of the user access of the two servers, this is really not a big deal. If you use mapped drives for user access, one can modify the logon scripts to map drives to more than one server just as easily as to the SBS alone. Otherwise, browsing Network Neighborhood works as normal, there's just another server there to be seen.
Can I add a Windows Terminal Server or Citrix Server?
Yes, MS has covered this with their own information.
SBS Information Trail
Where to Find SBS Related
1. Trailheads Summary: Where to Look
SBS Home: The Small Business Server Website
Getting MS Human Support by Phone
Help Yourself: Searching the MS Knowledgebase
SBS Evaluation and Basic Deployment Planning Overview
6. Standard SBS Deployment Tools available for Download
7. Updates, Service Packs, Y2K, Upgrades
Training and Books on SBS Installation, Support, References
White Papers: Detailed Deployment, Installation and Troubleshooting
Information available for FREE!!
This is not an official MS technote, heck, it not officially anything.
This is a compilation of SBS resources, primarily those provide by MS. There
are many MS technotes referenced and embedded below with the occasional
interpretive comment. This document has not been reviewed or approved by MS
or anyone. This may have some controversial ideas expressed and may even
harbor outright errors. This is a compilation of information to use as you
see fit, not a substitute for smart management of your own situations.
If you have recommendations,
corrections, or additions, please be kind enough to forward them to me in an
HTML format or plain text. Include any technotes you have reason to believe
would help. I'm not really looking to start a newspaper here or become an
investigative reporter. I'm trying to avoid some of us posting the exact
same stuff over and over again.
㯰yright 12/03/99 Prepared by Jeff Middleton of Computer Focus, Inc.
Distribute this freely, don't misquote
me, no warranties or assurance provided for errors or anything. Don't charge
to provide this to anyone. Leave my copyright notice in the document to
retain this as a public document. TMs to their respective owners. The
attachment to this has not been reviewed in any regard by Microsoft and does
not intend to speak on behalf of Microsoft.
Summary: Where to Look
There are many sources of information on SBS provided online by Microsoft (aka MS). To my way of thinking, this is part of the challenge, trying to determine where to look for what, when. What really seems to be missing is a single trailhead that provides a top-down starting point for finding 'all things SBS related'.
Therefore, I am providing this summary, not to suggest that this is a totally inclusive summary, but rather the heavily worn trail of common locations to begin research and troubleshooting.
Below are listed the 'top-level' entry points for most all other links included in references throughout this document. This means you could go there and find even more information than is highlighted within this document itself:
Microsoft Smallbusiness Website:
Microsoft Support Online (Knowledgebase):
Micosoft Technet (Knowledgebase and Technical Background Resources):
MS Resource Kits available to review online!! (Part of Technet):
Microsoft Backoffice Website:
Microsoft Direct Access (MS Authorized Channel Site, it's not publicly accessible other than to dealers):
Microsoft Press Resource Link (Publishing Division with Online and Print Resources Available):
(I've omitted links to the MSDN (Developer) and MSP (Solution
Provider) sites because these tend to have more than minimal requirements to
gain access to those resources.)
2. SBS Home: The
Small Business Server Website
The generally best place to start:
If you are an MS dealer, some additional resources are here:
3. Getting MS Human
Support by Phone
Not the only information option, but if you want to talk to someone at
MS for support, hereࡠplace to start:
(SBS 4.5 includes two free telephone tech-support issues for US and
Canada, perhaps in other areas as well. Some restrictions apply, but they're
there to use!)
4. Help Yourself:
Searching the MS Knowledgebase
The MS knowledgebase is the most common resource for identifying a troubleshooting tool, or for uncovering an explanation of a symptom or problem. The 'Q' articles are cross-referenced and use some less than obvious techniques for organization. You can search for words and concepts, but the most common mistake is to search either too broad or too narrow a concept. There are usually 'keywords' listed at the bottom of these documents that are an excellent hint for finding related, but unreferenced KBs.
To Search or for more information on the knowledgebase usage:
Check the online help for how to search with this tool. Personally, I never waste my time with the basic search, I always go to advanced. The following article points out some specific tips, in particular the idea of using the arcane keywords for doing more powerful searching. Similar logic applies for searching any knowledgebase topic.
Windows NT Error & Event Messages Database
This is a really fascinating resource for trapped errors and Event Log
Support Highlights for Small Business Server
This location has trailheads for top requested support on the major components of SBS:
5. SBS Evaluation and
Basic Deployment Planning Overview
Complete Pricing and Licensing:
Product Sheet (General specifications and related pricing list)
Try Before you Buy: Evaluation Copy (non-Upgradeable!!)
Get a Full Functioning Evaluation copy of SBS 4.5 (non-upgradeable) sent to you.
Do not make the mistake of expecting to migrate from this trial
installation. If you purchase an SBS product later, at the current time, you
must wipe out the evaluation product, then reinstall from scratch. It is
possible to preserve the data, but the installation must be redone entirely
Minimum Hardware Requirement/MS Certified Compatible Hardware:
Some additional Deployment planning related info is here too:
Comparison with Full Backoffice Product:
Product Migrating into or away from SBS:
(Don't forget the SBS Readme.doc)
6. Standard SBS
Deployment Tools available for Download (not shipped with SBS CDs)
Downloads for SBS (including older ones for SBS 4.0)
These are popular and SBS 4.5 specific
Client License Disk Converter:
Batch tool streamlines setup by adding multiple users to Small
Business Server 4.5 simultaneously
(SBS Resource Kit sample tool)
Windows NT ZAK, includes utility to push the installation of printers
on NT workstations and servers called con2prn.exe
To use NetMeeting 3.0 with Small Business Server:
Small Business Server 4.5 currently ships with Microsoft NetMeetingﳰan> 2.1 conferencing software. You can Netmeeting 3.0
to get its additional benefits.
Also review this whitepaper:
Updates, Service Packs, Y2K, Upgrades
BackOffice Small Business Server 4.5 Service Pack Compatibility Information
Y2k and service Packs:
Service Pack Deployment:
8. Training and Books
on SBS Installation, Support, References
Best Single reference in print:
Microsoft Small Business Resource Kit (for info on ordering):
SBS 4.5 RK Online Access (full text!!):
4.2 Mb Downloadable Self-Paced Hypertext Course:
Installing and Configuring Microsoft BackOffice Small Business Server
Books identified by MS on SBS:
MS Sponsored Online Bookstore (not just SBS):
(Don't forget the SBS Readme.doc)
9. White Papers:
Detailed Deployment, Installation and Troubleshooting Information available
Generally, with most products, MS gets around to writing whitepapers. Sometimes the audience for such papers is quite obviously the end-user of a product and therefore is quite useful. Othertime it seems the audience is either a technical review committee, developers, MS background references. Whitepapers can range from the really arcane to as fluffy as a press release.
Fortunately, MS took some time with the release of SBS 4.5 to produce some really excellent whitepapers for user and system administrator interest concerning deployment and configuration, something that was badly missing with the initial SBS release. In addition, some targeted papers have been produced by MS explaining specific topics that have either proven troublesome, or are unique to the SBS 'way' of thinking.
I've not included the sales and marketing papers in this group of documents. Generally, I don't find many request to locate these be stated, it's the 'How to..' type documents that need better indexing.
Generally, what is listed below can be found in one of two places. Here's where to find the most current stuff at anytime:
The SBS Website:
The Technet Website:
(Don't forget the SBS Readme.doc)
Proxy server Security - How to close http://www.windowswebsolutions.com/Articles/Index.cfm?ArticleID=8114
Issues with Console on SBS 4.5
Q222531 - Troubleshooting SBS Console Problems:
Q199031 - Unable to Create Shares in Manage Console:
Q226331 - Reinstalling the Small Business Server Console:
Q225101 - Reinstalling the SBS 4.5 Console Deletes All MAPI Profiles from
Q186388 - Restoring the SBS 4.0 Console After Removing and Reinstalling IIS/ASP:
Q236950 - How to Add SBS Top Monthly Support Issues and Microsoft Knowledge
Base Search Page Links to SBS 4.5 Console Home Page:
Q189848 - Computers Disappear from Manage Computer Wizard in Small Business
Q185558 - User Names Missing in Setup Computer and Manage Users Wizards:
Q226028 - Computer Name Is Not Displayed When Setup Computer Wizard Is
Q221223 - Err Msg: "VBScript Runtime Error 800a01ad" in Manage Server
Q192617 - VBScript Errors Running Manage Server Console:
Q178269 - Components Required for SBS Manage Server (Console.exe):
Q218426 - Permissions on Shared Folders Are Not Granted to Existing Files:
Q218115 - User Account Not Displayed in SBS Management Console Connections:
Q218045 - How to Permit Additional Users to Administer the Exchange Server:
Q218048 - Object Not Found Displayed after Many Refreshes in the Console:
Q216775 - SBS: Console User List Empty When Trying to Manage Users:
Q214688 - SBS: How to Troubleshoot Small Business Server Setup Computer
Q214615 - SBS Manage Server Console's Online Guide Find Feature Does Not
Q214550 - PRB: Unable to Manage Share Permissions from SBS Console:
Q206679 - Cannot Modify Shared Folder Permission Through SBS Console:
Q201508 - SBS: Manager Server Console Initiates Dial-Up:
Q196439 - How to Set Down-level Folder Permissions Through SBS Console:
Q189088 - Wizard Was Unable to Read the Permission Information:
Q186286 - SBS Console Does Not Redraw When Moving around Wizard Dialog:
Q184751 - Multiple Console Problems Occur If SBS Setup Is Cancelled:
Q184220 - Small Business Server Console Does Not Update after Adding a New
Q181366 - Running SBS Console Results in Internet Explorer Connection Error:
Q181262 - Shortcuts to the SBS Administrative Console Do Not Work:
Q180409 - Moving Shared Folders on SBS Can Cause Errors:
Q179010 - Setup Computer Wizard Does Not Display Complete User List:
232263 - Small Business Server 4.0/4.5 Top Support Issues:
This site Copyrighted by Susan Bradley, CPA/CITP, MCP, please distribute it as you see fit,
I make no warranties regarding the information contained in the links listed above. Surf at your own risk.