Wintivity ™

Small Business Server 2008 brings a new approach to Remote Web Workplace Connect to Computer connections. This new architecture mandates a default installation of Certificate Services which affects non-domain clients in their ability to connect using the 6.1 version of Terminal Services Client (required for TS Gateway connections).

The following articles explain the new architecture and teach how to distribute certificates to non-domain clients as well as connect those non-domain clients to your domain computer remotely through the new SBS 2008 Remote Web Workplace.

Receiving Certificate Errors When Connecting to Clients/Servers with TS Gateway or Remote Web Workplace on SBS 2008

How Do I Distribute the SBS 2008 Self-Signed SSL Certificate to My Users?

Windows Small Business Server 2008 Client Computer Help

Windows Small Business Server 2008 Technical FAQ

Happy Remote Computing on SBS 2008!

A LESSON LEARNED FROM SEAN DANIELS - SBS PM

The sbsanswerfile.xml can be used, when setting up Small Business Server 2008, to define setup parameters via text string entries. These same parameters may also be defined using a different tool, the OOBE wizard. To reach the OOBE wizard, the sbsanswerfile.xml is bypassed (never placed into the machine) and Small Business Server 2008 setup reaches OOBE (Out of Box Experience wizard) because it doesn’t see the sbsanswerfile.xml during boot/setup.

In the OOBE wizard, the level of specificity is not as detailed as using the sbsanswerfile.xml. A more important difference is that the OOBE wizard “hard codes” certain defaults and predefines certain assumptions about the installation. One of the most important of these entries is the DOMAIN-NAME for the SBS2008 environment.

The “domain name” parameter has brought us to write this article today.

DEFINING PARAMETERS BEFORE BEGINNING SETUP

The SBS Team developed Small Business Server 2008 so that “IF and WHEN” the admin wants to change the default parameters, then an answer file (a text file called sbsanswerfile.xml) must be defined prior to beginning setup. The xml file is then written to a USB drive (or other media) and placed in the machine before placing the SBS setup disk into the server. The OOBE wizard is not used in this case.

In the real world: VAR’s, IT Consultants, MS Partners, etc… often receive OEM boxes with Small Business Server 2008 already partially installed. This creates a quandry because the opportunity to define the answer file and then point SBS setup to sbsanswerfile.xml has already passed.

this circumstance raises the following question?:

How do we still define these settings once setup has already begun and the binaries have already been installed on the drive?

In our scenario (and In the case of most OEM boxes), the first stages of the SBS2008 installation are accomplished by the manufacturer. Therefore, the system launches straight into OOBE and and ultimately the wizard that defines the core SBS settings (text strings).

Since an sbsanswerfile cannot possibly be defined “with our answers” at the manufacturer, and pressing Power ON boots us straight into OOBE, how do we offer the machine the more “flexible and definitive parameter set using sbsanswerfile.xml”?

Sean Daniels emailed the response today:

As long as you

• DO NOT go past the first screen in OOBE
• DO NOT enter any data whatsoever in OOBE (i.e. the SERVER NAME /DOMAIN NAME / etc…)
• SHUT DOWN THE MACHINE immediately

You can still define the sbsanswerfile.xml and still have the machine call it when booting from a powered off state.

This gives you the ability to define specific settings (i.e. SERVERNAME / FULL DOMAIN NAME / etc… ) even though a partial install has already been accomplished at the factory.

How?

• Just grab the SBS Setup disk
• define and save your sbsanswerfile.xml to USB or other media
• place the media in the machine (prior to booting from powered off state)
• boot and wait for SBS setup to locate the sbsanswerfile.xml , enumerate the text strings, and commit your settings automatically

REPEATING “THE VERY IMPORTANT POINT”: do not launch an OEM box into OOBE without first defining the answer file.

What happens if you do start OOBE on an OEM SBS2008 box?

If you continue a SBS2008 install on an OEM Small Business Server 2008 box from OOBE you will irrevocably turn off the only method to explicitly define the setup parameters. Even if you partially begin OOBE and then bail out without writing or saving any data …a complete re-install will be required to change the SBS settings using an sbsanswerfile.xml. Why, because the method that calls to the sbsanswerfile.xml is irrevocably “turned off” (by design) If OOBE is entered or defined on any level.

So what happened in our case?

So there we were, installing a machine on-site that had a partially completed Small Business Server 2008 installation. We didn’t know (yet) the information contained in this article (duh!). Upon receipt of the machine we started the unit and were taken directly into OOBE. Upon arrival at the setup screens for SERVER NAME, DOMAIN NAME, etc… we realized we did not want to accept the defaults and thought “Hey, what about the sbsanswerfile.xml?” So we bailed out and in doing so, turned off the method available to call sbsanswefile.xml. We could no longer make certain changes to the OOBE based install using the sbsanswerfile.xml

You might be wondering: Why did we not move forward with the default OOBE install in the first place?

In our case, we bailed out because…. the FULL INTERNAL DOMAIN can not be defined in OOBE and we did not want to use the SBS Development Team’s  “default OOBE choice of .local as the top level domain”. Why… because we had a network full of Macs.

If you are not aware: Small Business Server defines .local as the top level domain (by default) when using the OOBE wizard and their is “NO WAY” to alter a top-level domain in SBS setup except by using the sbsanswerfile.xml

To sum up our story, we irrevocably entered OOBE and clicked next before abandoning the OOBE wizard.

Because we had a “time constraint” on delivery to this client, we needed to finish this install quickly, so we went ahead with the .local top level domain. Alas for our own choice for the full domain name (sigh). We then had to deal with the .local top-level domain issue on Mac.

By the way, about Mac on SBS:

• iPhone and Microsoft Exchange
• Using Apple Macintosh File Systems with Windows Services for Mac
• Networking Windows .local and Apple Macintosh
• screenshots: How Mac Entourage 2008 RPC HTTP uses WebDav to Exchange

Remember, exit OOBE immediately when setting up an SBS 2008 machine from an OEM and you can still define the environment using the sbsanswerfile.xml. Restart clean with the sbsanswerfile.xml on USB . In doing so, you can still have it “your way”.

Thanks seanda

Small Business Server packs a lot of functionality into a single container. As such, keeping track of the settings and parameters associated with SBS functionality can be tricky.

When moving day for files, folders, data stores, MSDE etc… comes around, it is important to know both the configuration (to setup the destination) and how to move the files (to keep settings, parameters, etc… intact).

Microsoft provides a thorough article on the most commonly moved items: databases , User Shared Folders, and Exchange Store. Read more at:

Moving Data Folders for Windows Small Business Server 2003

TechNet article: Moving Data, User Shares and Exchange Store in SBS 2003

also… check out the Windows Small Server 2003 Technical Library for additional information as well as Documentation by Task for Windows Small Business Server 2003.

SBS 2008 and Essential Business Server 2008

Presenters

• Eric Watson - eric.watson[at]microsoft(dot)com
• Dean Paron - dean.paron[at]microsoft(dot)com

NOTES:

• SBS 2008 up to 75 CALS
• EBS 2008 up to 250 CALS

SBS 2008 will have a list of Registrars with which SBS 2008 will automate the process of domain registration while setting up SBS 2008. This domain registrar list will be available publicly soon.

SBS 2008 will come packaged with a One Year subscription to One Care for Server ( a server only Anti-Virus solution to protect SBS 2008). Renewal of the subscription at a cost.

SBS 2008 will integrate with Office Live. Details to follow.

SBS 2008 will NOT offer dual authentication for Remote Web Workplace in SBS 2008. Auth Anvil may be a 3rd party solution at that time.

Trust Relationships still CANNOT be formed with other domains (in either product)

EBS 2008 comes with System Center Essentials. Support for Virtual Machines will exist but not be integrated. System Center Virtual Machine Manger does not run on System Center Essentials.

Will install on either 32bit or 64bit machines.

SBS 2008

• SBS 2008 Standard (one box)
• SBS 2008 Premium (2 boxes)

EBS 2008

• EBS 2008 Standard (3 boxes)
• EBS 2008 Premium (4+ boxes)
• EBS 2008 will have an extensible administration console (3rd party vendors can integrate with the administration tools)

Questions for the Microsoft EBS team regarding future security:

• RWW Cert generated by CEICW on SBS 2003 (publishes FQDN). How is this addressed in SBS 2008 ?
• RWW and Terminal Services in SBS 2003 (cannot use TLS/FIPS in combination with RWW Connect to Server). How is this addressed in SBS 2008 ?

Remote Web Workplace offers a number of helpful links in the Remote Web Workplace portal. Links like Client Help and Ask the Community offer users the ability to seek out their own answers to questions and even (ask for help).

 However, the walkthrough explaining How to Connect Outlook via the Internet exposes some unnecessary information. To be specific, it spells out the SBS computer name and the Internal domain name.

The better practice might not be to have this information exposed to the Internet.

 Google Groups provides some very helpful posts on this subject. It turns out the the registry can be used to disable certain links from the view of Knowledge Workers when visiting the Remote Web Workplace portal.

 check out:

• http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/c043f0ef3df6e66e/7f993539cbea81b1?hl=en&lnk=st&q=Remote+Web+Workplace+disable+KWLinks+Registry#7f993539cbea81b1
• http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/718c07b7f899caad/bc4725275ca8bd82?hl=en&lnk=st&q=Remote+Web+Workplace+disable+KWLinks+Registry#bc4725275ca8bd82

Thanks Jerry zhao

 The specific Registry Keys are:
HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\KWLinks
HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\AdminLinks

and this break down by Jerry zhao is super helpful

ServerTS
DWORD
0×00000001 (1)
Access Server Desktops

ClientTS
DWORD
0×00000001 (1)
Access Client Desktops

HelpDesk
DWORD
0×00000000 (0)
Monitor Help Desk. 1 = WSS is published. 0 = Not published

STS
DWORD
0×00000000 (0)
Administer internal company web site. 1 = WSS is published. 0 = Not published

PerfReport
DWORD
0×00000000 (0)
View performance report for SBS. 1 = Monitoring is published. 0 = Not published

UsageReport
DWORD
0×00000000 (0)
View usage report for SBS. 1 = Monitoring is published. 0 = Not published

OWA
DWORD
0×00000000 (0)
Use Outlook Web Access. 1 = OWA is published. 0 = Not published

CM
DWORD
0×00000000 (0)
Download Connection Manager

Help
DWORD
0×00000001 (1)
View Client Help

We can also modify the registry keys under
HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\KWLinks
They are used to enable and disable links on Remote Web Workplace Knowledge
Worker Page. 0 = Hide the link. 1 = Show the link.

TS
DWORD
0×00000001 (1)
Access my computer at work

AppTS
DWORD
0×00000001 (1)
Access my company??s application-sharing server

STS
DWORD
0×00000000 (0)
View my company??s internal web site

UsageReport
DWORD
0×00000000 (0)
View usage report for SBS

OWA
DWORD
0×00000000 (0)
Read my company e-mail

CM
DWORD
0×00000000 (0)
Join my remote computer to the network

Help
DWORD
0×00000001 (1)
View Remote Web Workplace help

Small Business Server 2003 makes use of a wizard to join Client Computers and Member Servers to an SBS domain. This wizard is accessed on the Small Business Server from the LAN subnet by typing the IP address of the SBS Domain Controller, a slash, and the word connectcomputer The wizard however can veer off course and not complete the procedure. Troubleshooting this circumstance can be a challenge and today I was in just that position.

Searching for potential solutions lead me to this walkthrough by Jacky Luo at [MSFT] and posted at Google Groups

SBS connectcomputer wizard error

Options

NOTE: the entire post is copied here just in case the content it is ever deleted from the original source. The original post can be viewed here. Thanks

(more…)

Aspiring to the highest “configurability” of SharePoint on SBS. Comments welcome. Thank you.
- - - - - - - - - -
11/15/2006 it’s here! SBS admins/users looking for SharePoint 3.0 RTM version - please go here for a single page of links. The official “side by side” White Paper from MSFT is available for WSS 3.0 with SBS WSS 2.0 already in place. The white paper is the endorsed method.

Windows SharePoint Services 3.0 Release Version download is here

TechNet page about Windows SharePoint Services 3.0 download is here

SBS-WSS3.0 White Paper download is here

The official SBS community is here - good info on adapting WSS 3.0 to SBS as methods evolve.

Please consider Microsoft’s official side by side installation procedure if you want the supported method of installing SharePoint 3.0 on your SBS box. To expand beyond the official options, consider this post. It offers methods outside the scope of the official white paper.

You can monitor for a Green Check here on MSFT technologies generally applicable to SBS.

Refer to this document on migrating the SharePoint instance of WMSDE Companyweb for migration and information on HOW TO BACKUP your WSS 2.0 Companyweb WMSDE config and content DATA. Having these files backed up is essential for restoring Companyweb under all circumstances.

IMPORTANT: To restore your WSS 2.0 Companyweb site… please try this post for guidance: http://blogs.technet.com/edwalt/archive/2006/11/29/removing-wss-3-0-companyweb-upgrade-restoring-wss-2-0-on-sbs-2003.aspx

Please backup your data.

- - - - - - - - - - -

This WSS 3.0 setup method follows a particular order of installing SBS cleanly with the configurability of WSS 3.0 in mind. Please note that SBS Companyweb does function normally after completing this installation method. The Default Web Site applications (i.e. OWA and Remote Web Workplace) are also GO along with all other bundled SBS functionality. Please backup your WSS 2.0 WMSDE instance as outlined above as well as all other data before proceeding. PLEASE NOTE that this is not a supported method of installing WSS 3.0. It does however WORK and with a greater scope of configurable options for SharePoint Services version 3 than any other method for SBS I have read to date - 11/30/2006.

- - - - - - - - - - -

OK…

Some reflections about WSS 3.0 on Small Business Server Premium R2. This brief summary outlines my learning experience in testing SBS with WSS 3.0 while in Beta. These observations eventually motivated this document. ( -OR- ) just scroll down to read the Setup>

1. Installing WSS onto Small Business Server 2003 has very different implications than installing on Windows Server 2003. SBS has lots of built in functionality/is a Domain Controller/runs Exchange locally/comes with WSS 2.0 etc… and that functionality can be affected by how successfully you install/migrate to WSS 3.0.
2. There is an existing Windows SharePoint Services 2.0 installation in SBS “by default” (the Companyweb Team Site). During a Basic installation, WSS must resolve it’s relationship to the WMSDE instance serving the SBS Companyweb Team Site. This occurs in a very limited number of ways when installing in Basic Mode “side by side”.
3. The Single Server Install Method (which uses Basic Mode to install and eventually configure WSS) follows its own course in establishing the SharePoint config and content databases for WSS 3.0. User directed options are basically null. This approach presumes use of SQL 2005 Express and the existing Companyweb WMSDE instance in SBS.

Why have these been challenges for me?

1. With SBS 2003 fully installed, WSS 3.0 setup offers no other option (at least on the install’s I’ve done) than to install in “Basic Mode (side by side -OR- migration)”. The installation of the bits and the configuration runs almost entirely on its own. The Wizard sees SBS 2003 with WSS 2.0 already there (read also WMSDE instance) and makes it’s own choices. Most importantly, installing in Basic mode does not offer the option to establish a New Server Farm which is “very important” because creating a New Server Farm opens up the parameters that make WSS 3.0 configurable and re-configurable.
   • ABOUT BASIC MODE: Most MSFT docs defer to the Single Server method of installation for a single box (makes sense right). Unfortunately this puts WSS 3.0 in the arduous position of having to figure out all of the intricacies of SBS (and with SBS Premium R2… there’s a lot to figure out). This is a challenge because the standard method of installing WSS 3.0 on SBS falls short of maximizing the available options in Small Business Server.
     1. Basic Mode setup with an SBS Single Server: WSS 3.0 must resolve it’s relationship with the WMSDE instances already servicing WSS 2.0. This “auto-pilot” is absent of choices in regard to SQL Server and will borrow from the current instance of WMSDE (migration) -AND/OR- install SQL 2005 Express (side by side). This is the major limitation of installing in Basic Mode: that you CANNOT make use of SQL Server 2005 Workgroup which comes with SBS 2003 Premium R2 -(OR EVEN)- SQL Server 2005 Express Advanced Edition which can be used with SBS 2003 Standard.
     2. Advanced Mode setup with an SBS Single Server: Advanced Mode “is workable” with a single server when that single server is Small Business Server 2003. The way I read the documentation available from Microsoft, Advanced Mode generally implies installing to a Server Farm (aka lots-o-computers). What I’ve found is that Advanced Mode can be utilized on SBS 2003 because the various components prompted for during install actually do exist in SBS Premium and SBS! In short, Advanced Mode has the major upside of allowing you to flexibly link up with all of the great stuff that SBS 2003 offers.
   • ADVANCED MODE - NEW SERVER FARM: The only mode in which SharePoint 3.0 is truly configurable…. this is the means of achieving full utilization of all of your SBS Premium components. Using Advanced Mode (on a single SBS box) and directing WSS to install to a New Server Farm enables the connectivity that makes full use of SBS 2003 with Windows SharePoint Services.
2. About SQL Server Workgroup on SBS 2003 Premium R2: keep in mind that one obvious goal of installing SBS 2003 “Premium R2″ is the use of SQL Server 2005 Workgroup Edition as the database for SharePoint. A significant benefit of “SQL Workgroup” is scalability. The storage that “Workgroup” provides for WSS is unlimited (not so with SQL Express). Advanced Mode installation and New Server Farm configuration offers the Administrator a choice of which SQL instance (ServerName\INSTANCENAME) to use…
   • Anyone running SBS Premium R2 will generally consider SQL Workgroup as an option because it’s… scalable.
   • Migration of the WSS 2.0 WMSDE database and/or a SQL 2000 database is still an option after New Server Farm install. Migration can be accomplished later, one Virtual Server/Web Application at a time -OR- not accomplished at all if that’s your choice.
     • PLEASE NOTE: migrating the MSDE instances for SBS Reporting and WSUS to SQL Server 2005 is not supported on SBS.
3. Microsoft’s “official side by side method”: WSS 3.0 Basic installation offers a “side by side with SBS WSS 2.0″ option. My personal experience is that this approach simply does not provide a “configurable” WSS 3.0 to SBS owners. In the past during Beta, other blogs I’ve browsed confirmed various trials in how WSS 3 oriented itself to the WSS 2.0 WMSDE even using the side by side approach. The short story is that I’ve observed some wacky stuff in WSS3 Beta on SBS. I would hope those things to be resolved now that we’re at RTM. I understand that migration is no longer an officially supported option and that cleans up some of it, however, there is still the primary issue of configurability which leads directly back to the ADVANCED MODE AND NEW SERVER FARM approach.
4. About IIS and SBS as Domain Controller: learn how to secure IIS on a Domain Controller here.

“HELPFUL INFORMATION” - Let’s here it for those Blogs! I must tip my hat to the following people who, among many others, paved the way during Beta. This post would not exist without them and the fact that this information was available in advance of the methods eventually posted on TechNet. Their info and my own falling down “a lot” eventually got me here. PLEASE NOTE: The current best single page of links on setup that I know of today is here: MSDN - Announcing the RTW of WSS and Office SharePoint Server 2007

• Steve Smith - installing MOSS 2007 beta 2 TR
• Rob Garrett - Beta 2 installation
• Rob Garrett - Beta 2 TR installation
• Joris Poelmans - installing WSS 3.0 Beta 2 TR
• “Microsoft” TechNet how to install WSS 3.0
• “Microsoft” Server Farm Method of Deploying Windows SharePoint Services

- - - - - - - - - - -

Please note: this post contains my own personal upgrade path and is not endorsed or supported by Microsoft. Consult all current documentation at www.microsoft.com prior to any installation and/or upgrade of Microsoft software. The following installation procedure contains no warranties and conveys no rights.

- - - - - - - - - - -

How to: CLEAN install Small Business Server 2003 - WSS 3.0 - Standard/Premium Technologies - R2 Technologies

To describe the installation method I have used successfully in a few sentences (both SBS 2003 PREMIUM R2 and SBS STANDARD):

1. Install SBS 2003 CLEAN (this translates to core Windows Server 2003 components) - reboot. Continue setup of (Domain Controller, Active Directory and IIS components ONLY) - one more reboot - when the box comes back up asking to continue Setup, click Cancel (”for now”) and STOP at this point.
2. Install .net 3.0 Framework then install WSS 3.0 bits ONLY. Choose advanced installation, front end web server… because we’re going to create new Server Farm later (yes on one box). Once the bits are on board… STOP… DO NOT CONFIGURE the SharePoint installation (i.e. DO NOT RUN THE CONFIGURATION WIZARD).
3. Grab SBS disk one. Install the remaining SBS components (Companyweb - WSS 2.0/Exchange/Fax Services/etc…). This will include all setup disks (2, 3, 4 and Outlook) and all components.
4. Run Windows Update.
5. Install SQL Server 2005 (SBS Premium owners) -OR- SQL Server Express Advanced Edition (SBS Standard Owners). **Please note: if you’re installing SQL Express, you’ll need SQL Server Management Studio Express to graphically manage your service accounts for SQL Server Express.
6. Establish your Security accounts for SharePoint (at least 3 service accounts - SQL/SEARCH/CRAWL… more for individual Web Apps)
7. Finally - launch the SharePoint Configuration Wizard and configure your installation. Everything in WSS and SBS will work. You can orient WSS to the Account for SQL /Search/(Email pending) etc… and even reconfigure WSS 3.0 in the future. Companyweb and Default Web Applications definitely work as well as all bundled SBS applications.

STEP 1 - Clean installation of SBS Core Components

IN MY EXPERIENCE, SUCCESSFULLY INSTALLING A “CONFIGURABLE” WSS3 ON SBS REQUIRES A CLEAN AND “INITIALLY PARTIAL” INSTALLATION OF SBS 2003 - THIS IS THE ONLY WAY TO ACCESS THE FULL PALETTE OF CONFIGURABLE OPTIONS AVAILABLE IN SHAREPOINT SERVICES I HAVE FOUND.

Perform a clean install of Windows Small Business Server 2003 SP1, including the Domain Controller, Active Directory and IIS components

• Insert SBS 2003 SP1 Disk 1. Begin setup.
• Install Windows Server 2003 components. Server restarts.
• Install any needed drivers (motherboard chipset, NIC, etc…). Restart server.
• Continue SBS installation completing default setup of Domain Controller, Active Directory and IIS. The SBS Server will ask to restart one more time. Allow this but when it comes back up and looks to continue setup (ends disk 1 and soon asks for disk 2: Exchange) - - STOP!… DO NOT install the next set of components (Exchange, Fax Service, Companyweb etc…). Stop the setup at this point and move to Step 2.

STEP 2 - Install .net 3.0 Framework

Install net 3.0 Framework RTM version .

Restart Server.

Step 3 - Install WSS 3.0 RTM Version (SharePoint)

Windows SharePoint Services 3.0 Release Version can be downloaded here

This is much simpler “fortunately” then it was in beta (YEAH!). Simply download the software and start the setup.

IMPORTANT STEPS

1. Install the SharePoint bits using Advanced mode
2. On the Server Type tab, click Web Front End
3. Install the WSS 3.0 bits ONLY and then STOP!!!. DO NOT run the SharePoint Configuration wizard. This will be done later after SQL Server (Workgroup or Express Advanced) has been installed

Shut down the Server. Power off. Boot OS

Notes: we are essentially following the Simple Farm deployment (Windows SharePoint Services 3.0) guidelines here. Look this up on TechNet under Windows SharePoint Services 3.0 technology. Please note that anyone wanting a configurable SharePoint 3.0 on SBS must completely ignore guidelines to install on a stand-alone computer. To repeat this essential point again: New Server Farm installation is the sole key to opening up SharePoint’s Configuration options. That includes a SINGLE SBS stand-alone computer.

To explain: we are borrowing steps from New Server Farm guidelines but not following the guidelines verbatim because we are installing on SBS. We have not yet installed SQL Server 2005 (Workgroup or Express) which we definitely need and will eventually install. At this point in time we don’t configure SharePoint 3.0 because our SQL instance is not yet there and that means there is no config and content database to point our SharePoint configuration to. FIRST - we must complete the Small Business Server installation. The reason - because SBS prefers not to see any other SQL instances already installed when completing it’s default setup (read… I’ve tried it!!). We first make room for SBS to finish installing it’s default components. This negates any confusion in configuring it’s MSDE 2000 instances. SBS goes first, installs “MSDE for Reporting Services” and “WMSDE for SharePoint 2.0″ and finishes setup according it’s design. Only after SBS has completed setup of all disks (2, 3, 4 and Outlook) will we continue and install SQL Server 2005. From this point forward we can pursue the general goals of the Server Farm installation method, set up our Security Accounts and finally configure Windows SharePoint Services 3.0. SBS likes this much better than installing SQL 2005 early or configuring WSS before SBS has first finished doing it’s thing! Remember… New Server Farm installation method using Advanced / Web Front End.

NOTE: Consider reading the New Server Farm Installation method thoroughly. it’s available at Technet here.

Reminder… if you haven’t already done so please Shut Down the Server. Power off. Boot OS.

Step 4 - Complete Setup of SBS 2003 SP1 Components

Once you have confirmed Advanced Mode installation of the bits is complete, move on to installing all remaining Small Business Server 2003 SP1 components. This includes all SBS disks. You will be prompted for disk 2, 3, 4 and Outlook.

• Insert SBS Setup Disk 1 and choose auto play (follow the instructions) -OR- double click the Setup Icon on your desktop
• You will be prompted to select SBS components
• Install the full array of SBS functionality including (Exchange/Companyweb/Fax Services/Reporting/etc…)

This completes the setup of the Standard SBS components as specified by you, the Administrator. All of Small Business Server’s standard functionality can be installed. The Companyweb WSS 2.0 team site will work as well the MSDE instances used by SBS reporting services and for R2 installs, WSUS.

Restart server.

Step 5 - Windows Update

One more time…. once all components are installed, please restart the Server.

Go to Windows Update and install all updates to SBS 2003 SP1. This is a good opportunity for a refreshment, “lots” of Security Updates.

Restart server.

Step 6 - Establish the Security Accounts for SharePoint

1. SQL Account for Config and Content database - AND - Central Administration Account
2. Search Account
3. Crawl and Indexing Account
4. Service Accounts for individual Web Applications

For information on Security account requirements please read Plan for administrative and service accounts [Windows SharePoint Services

To paraphrase this guide: in order to deploy Windows SharePoint Services 3.0 in a server farm environment you will need the following security accounts:

A user account that you can use to install Windows SharePoint Services 3.0 and run the SharePoint Products and Technologies Configuration Wizard. This account must be:

1. A domain user account.
2. A member of the Administrators group on each of your front-end servers.
3. A member of the SQL Server Logins, which grants login access to your SQL Server instance.
4. A member of the SQL Server Database Creator (dbcreator) server role, which grants permission to create and alter databases.
5. A member of the SQL Server Security Administrators server role, which grants permission to manage server logins.

Also establish

1. A unique domain user account that you can specify as the Windows SharePoint Services 3.0 service account. This user account is used to access your SharePoint configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator server role, and the SQL Server Security Administrators server role. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.
2. A unique domain user account under which the Windows SharePoint Services Search service can run. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.
3. A unique domain user account that is used to crawl content on your sites and create indexes. It is recommended that you follow the principle of least privilege and select a unique user account that cannot modify content and does not have administrative rights on your front-end servers or on your back-end database servers. This user account will be added to the Web application Full Read policy for your farm.
4. A unique domain user account that acts as the application pool identity for your site collection’s Web application. It is recommended that you follow the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers.

Step 7 - Disable Internet Explorer pop up blocker

1. You need to disable the Internet Explorer Pop up blocker to avoid any issues with the SharePoint 3.0 configuration screens.

• • Launch Internet Explorer
  • Go to Tools – Internet Options – Privacy
  • Un Check the Block Pop-ups
  • Also make sure pop up blocker is disabled in any other browser add on bars you may have.

Step 8 - Installing SQL Server 2005 for Workgroups

The most helpful document I’ve found on SBS and SQL Workgroup is here - Installing SQL Server 2005 WorkGroup Edition. Give this a thorough read as it addresses installation, migration and more regarding SQL Server 2005 for SBS.

OPTION 1 - SBS 2003 Premium

My personal preference for installing SQL Server 2005 Workgroup on SBS is to:

1. Install the default instance of SQL Server
2. Install a second instance (in a mirrored drive/directory of your choice) that is solely for use by Windows SharePoint Services
3. Add the Primary config/content database account described above under Logins for SQL.
4. Grant that account both database creator (dbcreator) and security administrator (security admin) rights under Server Roles
5. Running the SharePoint Configuration Wizard (next step) completes granting the other Security Accounts access to SQL.

The preceding assumes the availability of SQL Server 2005 Workgroup (which comes with SBS Premium R2). Obviously for those running SBS 2003 Standard or SBS Premium prior to R2, SQL Server 2005 Workgroup is not a freely available option.

- - - - - - - - - - -

OPTION 2 - SBS 2003 Standard (using SQL Server 2005 Express Advanced Edition)

You can also install SQL Server 2005 Express Advanced Edition and achieve the full functionality described in this post. First, download SQL Server 2005 Express Advanced Edition here. Install both SQL Server 2005 Express Advanced and the SQL Management Studio Express. You can then use the Management Studio to add access to SQL for your SharePoint 3.0 config and content database accounts exactly as described in Step 6 above (Step 6 Security Accounts). There you have it… SharePoint Lite!

There are two important limitations with SQL Server Express that you should be aware of regarding scalability:

1. SQL Server Express has a maximum database size of 4GB
2. SQL Server Express can only be configured to use a maximum of 1GB of RAM

You can review a SQL Server 2005 Features Comparison here. If you are thinking of scaling out your WSS installation, you may want to make preparations for the purchase of SQL 2005.

Step 9 - Configure Windows SharePoint Services 3.0

… here we are at last.

* reprinted without permission from TechNet Simple Farm deployment (Windows SharePoint Services 3.0)

Run the SharePoint Products and Technologies Configuration Wizard

1. On the Welcome to SharePoint Products and Technologies page, click Next.

2. Click Yes in the dialog box that notifies you that some services might need to be restarted during configuration.

3. On the Connect to a server farm page, click No, I want to create a NEW SERVER FARM, and then click Next.

4. In the Specify Configuration Database Settings dialog box, in the Database server box, type the name of the computer that is running SQL Server.

5. Type a name for your configuration database in the Database name box, or use the default database name. The default name is “SharePoint_Config”.

6. In the User name box, type the user name of the server farm account. (Be sure to type the user name in the format DOMAIN\username.)

Important:

This account is the server farm account and is used to access your SharePoint configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator server role, and the SQL Server Security Administrators server role. The user account that you specify as the service account must be a domain user account, but it does not need to be a member of any specific security group on your Web servers or your back-end database servers. We recommend that you follow the principle of least privilege and specify a user account that is not a member of the Administrators group on your Web servers or your back-end servers.

7. In the Password box, type the user’s password, and then click Next.

8. On the Configure SharePoint Central Administration Web Application page, select the Specify port number check box and type a port number if you want the SharePoint Central Administration Web application to use a specific port, or leave the Specify port number check box cleared if you do not care which port number the SharePoint Central Administration Web application uses.

9. On the Configure SharePoint Central Administration Web Application dialog box, do one of the following:

• If you want to use NTLM authentication (the default), click Next.

• If you want to use Kerberos authentication, click Negotiate (Kerberos), and then click Next.

Note:

In most cases, you should use the default setting (NTLM). Use Negotiate (Kerberos) only if Kerberos authentication is supported in your environment. Using the Negotiate (Kerberos) option requires you to configure a Service Principal Name (SPN) for the domain user account. To do this, you must be a member of the Domain Admins group. For more information, see How to configure a Windows SharePoint Services virtual server to use Kerberos authentication and how to switch from Kerberos authentication back to NTLM authentication (http://go.microsoft.com/fwlink/?LinkID=76570&clcid=0×409).

10. On the Completing the SharePoint Products and Technologies Configuration Wizard page, click Next.

11. On the Configuration Successful page, click Finish.

The SharePoint Central Administration Web site home page opens.

Premium Technologies and R2 Technologies upgrade

STEPS 10, 11 and so on…

Documents to download/read prior to installing SBS 2003 Premium R2 Technologies upgrade.

SBSR2GettingStarted.doc

• Installing SQL Server 2005 WorkGroup Edition in Windows Small Business Server 2003 R2
• Installing ISA Server 2004 in Windows Small Business Server 2003 R2
• Installing Exchange Server 2003 Service Pack 2
• How to install the Windows Small Business Server 2003 R2 Technologies

If you are installing Windows SBS 2003 R2 Premium Edition, it is recommended that you install the Premium Technologies before you install the Windows SBS 2003 R2 Technologies.

For step-by-step instructions on how to install the Windows SBS 2003 R2 Premium Technologies, insert Premium Technologies Disc 1.

Additional notes: Upgrading Exchange Server 2003 to SP2

Exchange Intelligent Message Filter (IMF) version 1 (v1) must be uninstalled before installing Exchange Server SP2. Exchange Server 2003 SP2 is a prerequisite for the Windows SBS 2003 R2 Technologies. Exchange Server 2003 SP2 automatically installs Exchange IMF version 2 (v2). If you have already installed Exchange IMF v1 on your server, you must uninstall it before installing Exchange Server SP2.

Please read How to install the Windows Small Business Server 2003 R2 Technologies

You may also read the Exchange Server 2003 Service Pack 2 Release Notes prior to installation of the Exchange 2003 Service Pack 2 update.

---

… in closing:

For those interested in MOSS 2007 see SharePointBlogs.com. There are volumes of information and links to Webcasts on upgrading to MOSS 2007.

For those migrating from SPS 2003 to MOSS 2007 please check out SharePoint Farmers Almanac as well as the blogs listed above. At Almanac, MSMVP Shane Young teaches this stuff and has carefully applied his experience to an upgrade path for those migrating from SPS 2003 to MOSS 2007 (post 10/2/2006).

ABOUT SBS and the migration of SQL 2000 instances and the SBS WMSDE instance: There are a lot of working installations of SBS 2003 in place that are likely just fine the way they are. In other words: “if it ain’ t broke…. ” . Please remember the official side by side white paper which puts WSS 3.0 on your Small Business Server without disturbing anything.

I was speaking with a well regarded consultant a few weeks ago (after SBS Premium R2 released) who shared that a colleague had attempted a migration of a sizable SQL 2000 database to SQL 2005. The migration did not quite achieve expectations. She offered certain cautions to me. In my reading, I browsed across these Microsoft documents that may help those targeting migration:

1. Instructions on how to Migrate a SharePoint Instance of SQL Server 2000. That same general link (mentioned earlier in this post) is here and applies to anyone running SBS and seeking to migrate the SharePoint WMSDE or SQL Server 2000 instance to SQL 2005 Workgroup. I have completed this migration personally and fortunately in my shot at it, Companyweb migrated to SQL Server 2005 Workgroup Edition perfectly.
2. There is also this knowledge base article with warnings and workarounds regarding SBS and SQL 2000: http://support.microsoft.com/kb/920899
3. RECENT UPDATE! - Please note the official white paper states that Gradual upgrade and/or In place upgrade (MIGRATION) is NOW UNSUPPORTED. Please go to the official SBS blog to read about it here: Companyweb 2.0 migration through the install of WSS 3.0 is unsupported.

Thank you.

End of post.

- - - - - - - - - - -

Thanks for dropping by. I hope the information is useful and informative to you. This of course is not the last stop on the WSS/SBS road. Please let me know how I can improve the post. I’m not beyond correction. If accurately placed, a helpful nudge (or shove) is accepted thankfully. Recently, I’ve made an effort to tidy up the outline. I’ve also focused on linking to a foundation of reference material with which you can research and draw your own conclusions. Please let me know what you find.

I’m very thankful. This technology is running for me now in a way I could not have presumed without daring to try. What I’ve learned is that by patiently pressing on and waiting upon those good gifts that come from above, I accomplish more in faith then by intellect alone. I hope your goals for SharePoint are faithful ones as well.

May His face shine upon you.

to the glory of God

---