Company web needs a little help in the external link department?

So you have some links in company web that aren't properly resolving externally?

There are some links on companyweb that don't include the domain name, you need to manually modify them, the appears to be the case on standard too.

They can be modified easily at http://companyweb/Lists/Links/AllItems.aspx

 

P.S.  Adding Chad's comments about ISA...

 

Now, for those Premium customers running ISA, you can configure link translation within ISA. As a result, you can have hard-coded internal links on your companyweb site (that point to http://companyweb/<whatever>">http://companyweb/<whatever>). But when you access these links from the outside, ISA will do the heavy lifting for you and automatically translate the links so that http://companyweb is replaced with https://<your.fqdn.com>:444 Way cool :^)

 

Okay it's time to Sharepoint... are you ready?

Chad Gross (SBS-MVP) and Nick Whittome (SBS-MVP) present Windows Sharepoint Services in SBS.

For further resources check out Mark Mulvany’s Blog http://www.swifttrain.com

Susan Bradley has invited you to view a Microsoft Office Live Meeting recording.

View Recording 

Recording Details

    Subject:              SBS Group
    Recording URL:        https://www.livemeeting.com/cc/winserver_usergroup/view
    Recording ID:         MJT5DM
    Attendee Key:         K_9G#$t

There's this little problem with authentication, John....

So John asks if folks are exposing their sharepoint to clients and putting up invoices and stuff up there for clients to look at.

There's one problem.

It's the authentication issue.... you see for those folks to privately get into your Sharepoint and not expose that data to the universe you'd want them to authenticate.

To authenticate takes active directory rights and uses.

To use AD rights and uses takes CALs.

To use CALs means... they gotta be official users on your SBS box.

That's why for many folks wanting to share out Sharepoint to clients, they won't do it on their own SBS box due to the licensing and instead put it on an externally hosted box.

Bottom line...read this past post...and remember that www.mssmallbiz.com is on such an externally hosted sharepoint.

P.S. Happyfunboy reminded me of how we first met and bonded.... over a presentation where someone said access didn't matter...[yeah right, both of us afterwards were like 'He said WHAT about licensing?]

 

While you are installing... do you 'value add'?

Gregg brings up a wonderful point in the blog comments..... do you look for ways to introduce Sharepoint into the firms you install SBS in?

Do you look for ways to help someone learn how to use their SBS box better?  To increase the use in the firm?  I just set up an Excel shared spreadsheet this weekend... one that I knew that I wanted to have better control of the employees use of it... so that one person wouldn't get in the document and lock out all the others and you'd have to buzz them on the phone and tell them to get out of the file.  Yeah, it's the way that most of us small businesses do it, but it sure isn't efficient is it?  So I enabled 'sharing' of the spreadsheet and set up a shared workspace so that the changes are better tracked and updated without having to buzz someone in the office.

...so the next time you install SBS... look around at those dog eared documents tacked up on a bulletin board.... Sharepoint 'em.

So what do you use Sharepoint for?

I use it in my office to share out Word documents that I want to ensure are kept intact and not rewritten over again.  I use it to keep our employee manual and other resources that I tend to go...dang.. now where did I save that?  I put things like instructions to the phone system.  Set up for the Scanner.  Other things that I do ...but infrequently.  Why?

Because the Search box in there that I have from SQL makes it perfect for this.  I can find things.

Stephanie talks about backing up Sharepoint in this blog entry but doesn't make it as clear as I would like, that her instructions allow you to do file by file backup...the Sharepoint is really backed up as a whole each time you backup the server.  So don't worry... the SBS is truly backing up Sharepoint..but as a whole, and thus you have to restore the entire thing.  If you want to be extra paranoid and have a file by file backup, you need to follow her post.

So?

What do you use Sharepoint for?

I screwed myself up

You know the other day when Mr. Murphy visited my firm and the boss didn't have access to CompanyWeb?  Chad thinks I might have done this to myself by cleaning up the Sharepoint templates out of my "Shared Workspace" contact section.  You see I didn't like those templates showing up in my Live Communication Server fed contact list so I took them out... in doing so... we think I broke the wizard template that adds a user automagically to Companyweb.  I'll be setting up a couple of new users and we'll see if this is indeed what I did.

 

What's the difference between WSS - Sharepoint and SBS - Companyweb?

I'm stealing this from an email Chad made about the difference between WSS and “our” Sharepoint: 

Please note, if you have been told that the SBS sharepoint questions should only be answered in the SBS newsgroup, I do have to apologize for our Communities sometimes.  We do tend to be territorial sometimes.

You want to know the difference between WSS Team Site on SBS & the default WSS Team Site  on a straight Win2k3 box?  Here you go:

Document Libraries:

• WSS on Win2k3 includes a ‘Shared Documents’ library.
• WSS on SBS includes a ‘General Documents’ library, ‘Projects’ library, ‘Archived Documents’ library, and a ‘Presentations’ library.

What’s the difference between these libraries?  Nothing.  It’s the exact same result as if you created each of these libraries in WSS on Win2k3 using the default Document Library Template.

Now WSS on SBS also has an Incoming Faxes document library, which as we know integrates with the SBS Shared Fax.  This is a regular document library that has been customized – but only in the sense of customizing the fields.  The SBS Shared Fax does all of the heavy lifting for integrating with WSS – not the other way around.

Photo Libraries –

• WSS on SBS includes a ‘Company Photos’ photo library.  This was created using the default WSS Photo Library template.  Nothing special.
• WSS on Win2k3 does not include any pre-created Photo Libraries.

Lists –

WSS on SBS includes a Help Desk and Vacation Calendar.  WSS on Win2k3 includes a Contacts list and a Tasks list.  So what is the Help Desk?  Nothing but a customized Issues list.  Create a new Issues list, remove the Category, Related Issue and Comment fields.  Add an Assigned To field (lookup on the built-in Users list), a % Complete field (number value in Percent format), a Description field (multiple lines of text / allow HTML content), and a Due Date field (Date/Time).

So what’s the net change?  Besides having a few different items pre-created for us (which are no different than the ‘Shared Documents’, ‘Contacts’ and ‘Issues’ lists pre-created on WSS on Win2k3), we have two custom lists (‘Incoming Faxes’ and ‘Help Desk’) that are saved as templates.  There is ZERO code variance between WSS on SBS and WSS on Win2k3.  As a matter of fact, anyone running WSS on Win2k3 could manually create the exact WSS environment on Win2k3 that we have on SBS – and that would not compromise their ability to get support or complete normal WSS administration tasks include backup and restore.

Web parts and IM

Sarah in the blog comments asks..... I searched your blog for &quot;web part&quot; and didn't find what I was looking for, but I thought I'd ask you anyway....

How safe are non-microsoft webparts for Sharepoint? Do you have any recommended sites for finding these? And specifcally, have you ever heard of an in/out board web part? (Because what SBS2003 company can afford Live Communications Server?)

Well.. you mean this SBS company because I 'caught LCS' on Software assurance but yes, LCS 2005 is WAY too expensive for SBS and honestly... I think WAY too much overkill.

Any Sharepoint webpart is just fine for SBS... for another idea for an internal only IM system

Read Vlad's blog for some ideas...

Vladville - Secure & Affordable IM for Small Business:
http://www.vladville.com/articles/smallbizim.asp

Sharepoint SP2 - revisited

From the mailbag today...

For what it's worth, the KB announcing WSS SP2 does NOT include SBS2003 in the 'Supported Operating Systems' list and when I ran MU on my SBS box, WSS SP2 did NOT show up in the list of available updates. Then again, SP1 does not explicitly specify SBS, either. Still... based on that, SP2 is not getting installed until a SBSized version shows up, or until many other people have successful installs!

 

First off... you won't find 'generic' service packs that explicity say they support SBS when we are just merely the sum of our parts.  If you are expecting any patch for Windows 2003 to say “SBS”, you will have a long wait.  Any patch/;service pack that goes on 'normal' Windows 2003 goes on SBS.  Flat out don't expect a KB or patch to explicitly state SBS unless it's “ONLY” for SBS.

 

Next, I'll have to check the MU on my own box, but you 'can' install it manually you know.  We will be installing it later on our own machines.

 

Lastly, the SBS Dev team pinged us today in fact that this patch has been tested and approved on SBS boxes. 

 

Bottom line, unless EXPLICITLY stated in the KB that it  'can't' go on SBS, it's approved on our boxes.

 

Update... got a ping that this Sharepoint SP2 “will' be on MU/WU ...just a bit later on.  It just happens to be only on the download site for the time being.  So, for now it's on the Download center but will be on the WU/MU in the future.

 

Again, this IS fully supported on SBS boxes.

Windows Sharepoint Services sp2 released

Bill reminds us that Windows Sharepoint Services sp2 has been released.

Now, keep in mind that ANY service pack for our parts is perfectly fine to put on a SBS box, but I personally am not at home and I won't be testing this yet. 

We do have some special customizations for Sharepoint, so if you'd rather one of us crazies in the newsgroup installed it first, triple checked to ensure that there are no issues with this SP2 on our SBS boxes, I would say you are a wise person.

Installing patches on SBS boxes is only fun for me the wacko SBS patcher.  It's really NOT fun at all if a patch affects the system,even if it's a minor annoyance.  It breaks the confidence of the client in your ability to be their outsourced CIO.  I know many consultants who, if they are traveling, or busy with other projects will wait on service packs like this Service pack.

If you've set up WSUS to pull down service packs and auto apply them, you are indeed a 'bleeding edger'.  Just remember that those of us who are more into control, we don't set up our servers to auto patch anything.

P.S.  I have no idea what will happen if you install Sharepoint SP2 and then attempt to install the SBS 2003 sp1 bundle.

 

So how do you make a drive letter out of Sharepoint?

So after the blog post the other day, people asked how do you map a drive letter from Sharepoint.

Easy... on a workstation give this a try.

Click on My computer, tools, map a drive, pick a drive letter and when the 'browse' box shows up, just put “wack wack” or \\companyweb in the browse box and voila..you get a tree structure of your Sharepoint. 

There's your drive letter.

Now I wack off autodisconnect so the drives don't fall off, but you could probably script this from a login script as well.

So how can you save from Outlook email to Sharepoint directly?

So I have these attachments that I wanted to dump straight into Sharepoint..but they were email attachments in Outlook...so...I asked the gang and Javier said.....

Save it to Sharepoint just like you would save it from any other application.

Right-click on the attachment-> Save As-> type http://companyweb (or https://whatever.company.com:444 if you are doing it externally) on the file name to open the sharepoint site and select the folder you want.

Of course, if you plan to do it more than 1 time-> Either add the folder to Network Places or create a drive letter for Sharepoint.

and then he said....

By the way... 

Since the day I learned from Chad that I could access 
Sharepoint as if it was share or drive letter my VPN usage
 has hit an all time low.
In fact, for the most part I'm not even VPN to clients anymore  :-) 
 
-Javier

Cool!

Office, Sharepoint and Glue

From the mailbag today comes the question.... 

If a user has *only* Office 2000 on their computer (so no Office10 folder, no owssupp.dll file), can they edit documents on the sharepoint website? (The reason there is no Office10 folder is because we never installed Outlook 2003 on this computer for various reasons.) Can I just install the dll into their Office folder, register it and make it work or do I need to upgrade their version of Office?

 

You shouldn't have to adjust any DLL...but keep in mind you'll have only “Good“ not “Better“ or “Best“ experience with Sharepoint. 

 

Buy Office 2003.... Outlook rocks, and the Sharepoint glue integration is worth it [at least I think so]

There's a really good whitepaper that addresses this:

·         File Save Integration – Microsoft Office 2000 provides basic integration with Windows SharePoint Services. Users can open and save files stored on SharePoint sites from their Office 2000 applications and receive alerts in Microsoft Outlook® 2000.

·         Basic Data Integration – Microsoft Office XP provides additional data integration between SharePoint sites and Microsoft Office, so users can export list data to Microsoft Excel 2002 and view properties and metadata for files stored on SharePoint sites.

·         Contextual Integration – Microsoft Office 2003 Editions add rich contextual integration between Microsoft Office and Windows SharePoint Services, integrating SharePoint fully into the business tasks that users perform every day.

Public Folders versus Sharepoint

A question came from the audience about the plans for Public Folders being phased out in favor of Sharepoint.

This came out from a TechEd presentation. 

Should you be concerned..... no I don't think so ... we have plenty of time... besides... Public folder infrastructure has always been a bit sucky anyway.

Sharepoint is the future folks.  And if you aren't playing with it?  Man you should.  I'll be honest with you we're just now starting to roll out Sharepoint to be our data storage for Litigation consulting documents in my office.

If you aren't looking, learning, looking at Sharepoint... man you should.

Ripping out Sharepoint from it's roots

I bought a Dell the other day that has SBS 2003 preinstalled.  Comes in a tower sized unit.  Looks like a Desktop.  My real baby at the office is a big overgrown tower unit as well.  I think that's the problem right there.... they look like a normal desktop.  But they are not.

On a regular basis in the newsgroup I see folks ready to reinstall, flatten, rebuild, yank out.  Heck, even the other day I posted up for later saving ['cause I'm lazy and this is in a way my own personal filing cabinet] a street map to basically go shoot yourself in the foot and rip out Sharepoint and start over.

Somehow I get this feeling if we had some sort of GUI that would show Sharepoint in a flat file database we'd stop a lot more than we do now and stop ripping the dang thing out by it's roots and starting over again.

If your Sharepoint isn't working...check the following... [stealing a post from Chad]... and let's stop ripping out quite so quickly 'eh?  Let's make sure you have backups, you aren't ripping out multiple web sites, you aren't ... just really mucking up big time and instead figure out the real reason why things aren't working.  Here's just one suggestion....

Before you do a complete re-install of the companyweb, check to make sure that your MSSQL\Sharepoint service is running.  Just to be safe, make sure you can stop & restart it successfully.

If the service cannot start - change the logon credentials for that service to use a domain account, then try to start the service.  If the service starts, change the startup credentials back to the default (Local System), then stop & restart the service and you should be good to go . . .

How about we dig around a bit before we go yanking, okay?

Different scenarios to reinstall Companyweb after the SBS 2003 SP1 setup

Once again.... hello?  If you are installing supporting SBS boxes and are NOT a Microsoft partner..why ever not?  Get your buns signed up!

 

From the Partner support group comes the varying ways we can get Sharepoint fixed back up after SP1...now mind you I don't quite understand why folks get Sharepoint mucked up... I've never had to uninstall it and reinstall it...but if it needs it..here's the info that might help..

 

PLEASE BE AWARE THAT IF YOU HAVE LIVE DATA IN YOUR SHAREPOINT, THIS IS PROBABLY NOT TOO WISE OF STEPS TO BE FOLLOWING...WE ONLY PUT IT IN HERE BECAUSE WE'RE LAZY AND WE DON'T WANT TO GOOGLE ALL THE TIME.  IF YOU HAVE LIVE DATA AND YOUR SHAREPOINT FAILED AFTER SP1, YOUR SP1 MAY HAVE FAILED AS WELL SO IT'S WISE TO CALL MICROSOFT PRODUCT SUPPORT SERVICES.  THERE'S A TIME TO BE A DIY'ER AND THERE'S A TIME TO GET HELP. STOP MUCKING AROUND ON YOUR OWN, STOP GOOGLING AND USE THE PROPER RESOURCES.

 

Okay so that's a little harsh ...but I swear people want to flatten this box if it even sneezes funny.  You don't need to flatten and start over... you just need good advice and googling and reading blogs for some of this stuff may not be the wisest move when there are trained Engineers who live and breathe SBS boxes.

 

Bottom line, use your resources wisely and know when to put down the mouse and keyboard, stop googling, and call.  Issues with a service pack are a free call, but even then on a 'non covered call', how much is your time, how much is your firm's time worth?  After all, this is your business right?  There at times you just need to get the credit card out and call Microsoft Product Support Services.

 

Different scenarios to reinstall Companyweb after the SBS 2003 SP1 setup

 

I. Scenario I - SBS SP1 Standard (with no complete Intranet component

removal)

 

. Problem Description

After SBS 2003 SP1 Standard installation, if Companyweb is uninstalled by

using the 'Remove' feature in SBS Integrated setup; reinstalling the

Intranet component through 'SBS Integrated Setup' will prompt for CD 3:

Insert Windows Small Business Server 2003 Disc 3 or point to location where

Windows Small Business Server Setup files may be found.

 

However, after the original SBS CD3 is inserted and 'OK' is clicked, the

wizard then gives the error: The drive contains a disc for Windows Small

Business Server 2003 with no service packs. When the prompt appears, insert

a disc for Windows Small Business Server 2003 with Service Pack 1.

 

Since the Companyweb (Intranet) installation part is in the SBS SP1 CD2, the

installation cannot proceed.

. Analysis

This is an Intranet component removal by using the 'SBS Integrated setup',

which can be treated as an incomplete Companyweb instance removal. As a

result, the existing WSS MSDE SP4 instance is NOT removed, but the WSS SP1

is removed. When trying to perform the reinstallation of the Intranet

component, the System will try to locate both the original Companyweb

installation bits and the new ones in the SP1.

 

What's Removed:

 Import File wizard

 Fax Routing Extension.

 WSS

 Any folders files created by WSS.

 ISAPI filter

 V-dir

 

What's Not removed:

 MSDE Instance

 Config Database.

 Content Database.

 

. Resolution

1. Start a cmd prompt and change directory to the SP1 download folder (or

the SBS03_SP1 folder on the SBS SP1 PKG_CD2).

2. Type "SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and

press Enter.

3. Specifying a path for the extracted files (such as C:\SBSSP1)

4. Insert the original SBS (non-SP1) Disc 3 into the CDROM.

5. Copy all the folders and the files from the

  :\SBS\CLIENTAPPS\SHAREPT folder to the

C:\SBSSP1\cd3\sbs\clientapps\sharept folder.

6. Run the SBS Integrated setup, and when the setup program prompts for CD3,

point it to the folder created in the previous step.

7. Insert SBS SP1 CD 1, re-install WSS SP1.

8. And then insert SBS SP1 CD 2 to reinstall SBS SP1.

9. Run CEICW once the setup is completed.

 

 

II. Scenario II - SBS SP1 Standard (with complete Intranet component

removal)

 

. Problem Description

Note: The only different from the scenario I is that one uses the steps

outlined in the KB article below to completely remove the Companyweb

(Intranet) component:

 

 829114 How to remove and how to install the Windows Small Business Server

2003

 http://support.microsoft.com/?id=829114

 

After SBS 2003 SP1 Standard installation, one uninstalls the Companyweb by

using the steps outlined in KB 829114; when they try to reinstall the

Intranet component through 'SBS Integrated Setup', they are prompted to

insert the CD 3: Insert Windows Small Business Server 2003 Disc 3 or point

to location where Windows Small Business Server Setup files may be found.

 

However, after the original SBS CD3 is inserted and 'OK' is clicked, the

wizard then gives the error: The drive contains a disc for Windows Small

Business Server 2003 with no service packs. When the prompt appears, insert

a disc for Windows Small Business Server 2003 with Service Pack 1.

 

Since the Companyweb (Intranet) installation part is in the SBS SP1 CD2, the

installation cannot proceed.

 

. Analysis

Since it's a complete removal by using the steps in KB 829114, all the

following components are removed. However, that makes our resolution

relatively easy since all the reinstallation required bits can be found on

the SBS SP1 CD2.

 

What's Removed:

 MSDE Instance

 Config Database.

 Content Database.

 Import File wizard

 Fax Routing Extension.

 WSS

 Any folders files created by WSS.

 ISAPI filter

 V-dir

 

What's Not removed:

 None

 

. Resolution

1. Start a cmd prompt and change directory to the SP1 download folder (or

the SBS03_SP1 folder on the SBS SP1 PKG_CD2).

2. Type "SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and

press Enter.

3. Specifying a path for the extracted files (such as C:\SBSSP1)

4. Run the SBS Integrated setup, and when the setup program prompts for the

CD3, point it to the folder created in the previous step.

5. Insert SBS SP1 CD 1, re-install WSS SP1.

6. And then insert SBS SP1 CD 2 to reinstall SBS SP1.

7. Run CEICW once the setup is completed.

 

 

III.  Scenario III - SBS SP1 Premium (with no complete Intranet component

removal)

 

. Problem Description

After SBS 2003 SP1 Premium installation (both ISA 2004 and SQL SP4 is

installed through SP1 CD3,) one uninstalls the Companyweb by using the

'Remove' feature in SBS Integrated setup; when they try to reinstall the

Intranet component through 'SBS Integrated Setup', they are prompted to

insert the CD 3: Insert Windows Small Business Server 2003 Disc 3 or point

to location where Windows Small Business Server Setup files may be found.

 

However, after the original SBS CD3 is inserted and 'OK' is clicked, the

wizard then gives the error: The drive contains a disc for Windows Small

Business Server 2003 with no service packs. When the prompt appears, insert

a disc for Windows Small Business Server 2003 with Service Pack 1.

 

Since the Companyweb (Intranet) installation part is in the SBS SP1 CD2, the

installation cannot proceed.

. Analysis

 

This is an Intranet component removal by using the 'SBS Integrated setup',

which can be treated as an incomplete Companyeweb instance removal. As a

result, the existing WSS SQL SP4 instance is NOT removed, but the WSS SP1 is

removed. When trying to perform the reinstallation of the Intranet

component, the System will try to locate both the original Companyweb

installation bits and the new ones in the SP1. And since the SQL SP4

instance for WSS is still there, we don't need to re-apply the SQL

installation bits in the SP1 CD3 again.

 

What's Removed:

 Import File wizard

 Fax Routing Extension.

 WSS

 Any folders files created by WSS.

 ISAPI filter

 V-dir

 

What's Not removed:

 SQL Instance

 Config Database.

 Content Database.

 

. Resolution

1. Start a cmd prompt and change directory to the SP1 download folder (or

the SBS03_SP1 folder on the SBS SP1 PKG_CD2).

2. Type "SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and

press Enter.

3. Specifying a path for the extracted files (such as C:\SBSSP1)

4. Insert the original SBS (non-SP1) Disc 3 into the CDROM.

5. Copy all the folders and the files from the

  :\SBS\CLIENTAPPS\SHAREPT folder to the

C:\SBSSP1\cd3\sbs\clientapps\sharept folder.

6. Run the SBS Integrated setup, and when the setup program prompts for the

CD3, point it to the folder created in the previous step.

7. Insert SBS SP1 CD 1, re-install WSS SP1.

8. And then insert SBS SP1 CD 2 to reinstall SBS SP1.

9. Run CEICW once the setup is completed.

 

 

IV. Scenario IV - SBS SP1 Premium (with complete Intranet component removal)

 

. Problem Description

Note: The only different from the scenario III is that one uses the steps

outlined in the KB article below to completely remove the Companyweb

(Intranet) component: '829114 How to remove and how to install the Windows

Small Business Server 2003 - http://support.microsoft.com/?id=829114'.

 

After SBS 2003 SP1 Premium installation (both ISA 2004 and SQL SP4 is

installed through SP1 CD3,) one uninstalls the Companyweb by using the steps

outlined in KB 829114; when they try to reinstall the Intranet component

through 'SBS Integrated Setup', they are prompted to insert the CD 3: Insert

Windows Small Business Server 2003 Disc 3 or point to location where Windows

Small Business Server Setup files may be found.

 

However, after the original SBS CD3 is inserted and 'OK' is clicked, the

wizard then gives the error: The drive contains a disc for Windows Small

Business Server 2003 with no service packs. When the prompt appears, insert

a disc for Windows Small Business Server 2003 with Service Pack 1.

 

Since the Companyweb (Intranet) installation part is in the SBS SP1 CD2, the

installation cannot proceed.

 

. Analysis

Since it's a complete removal by using the steps in KB 829114, all the

following components are removed. That makes our resolution relatively easy

since all the reinstallation required bits can be found on the SBS SP1 CD2;

however, you will need to reinstall SQL SP4 to apply to the WSS instance by

using the SBS SP1 CD3.

 

What's Removed:

 SQL Instance

 Config Database.

 Content Database.

 Import File wizard

 Fax Routing Extension.

 WSS

 Any folders files created by WSS.

 ISAPI filter

 V-dir

 

What's Not removed:

 None

 

. Resolution

1. Start a cmd prompt and change directory to the SP1 download folder (or

the SBS03_SP1 folder on the SBS SP1 PKG_CD2).

2. Type "SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and

press Enter.

3. Specifying a path for the extracted files (such as C:\SBSSP1)

4. Run the SBS Integrated setup, and when the setup program prompts for the

CD3, point it to the folder created in the previous step.

5. Insert SBS SP1 CD 1, re-install WSS SP1.

6. And then insert SBS SP1 CD 2 to reinstall SBS SP1.

7. Once the setup for SBS SP1 main bit is completed, insert SBS SP1 CD3 to

install SQL SP4.

8. Run CEICW once the setup is completed.

Stand back please... Sharepoint people are about to drool all over the place....

As Chad said...it's Christmas in July.....or August as the case may be....

Web parts and templates for Sharepoint...all OVER the place...

John Westworth talks about them on his blog on Technet....

Sharepointing yet?  You'd better be by the time SMBnation rolls around...

Need to reinstall Sharepoint after SP1?

Need to reinstall the Sharepoint/intranet post SP1?

Try this:

1. Start a cmd prompt and change directory to the SP1 download folder (or
the SBS03_SP1 folder on PKG_CD2).

2. Type "SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and
press Enter.

3. Specifying a path for the extracted files (such as C:\SBSSP1)

4. Run the SBS Integrated setup, click Next repeatedly until the Component
Selection page is displayed.

5. In the Server Tools list, click Maintenance. In the Intranet list, click
Install.

6. When the setup program prompts for the CD3, point it to the folder
created above.

Sharepoint blogs, you say you want Sharepoint blogs?

I'll be the first to admit that the first thing on my to do list after busy season is really getting into Sharepoint.  After I posted my “Exchange blogs” post the other day someone from the mailbag asked about Sharepoint blogs

So here you go:

http://www.sharepointblogs.com/

http://www.spsfaq.com/blogs.htm

Actually better get.. grab this OPML file and stuck it in newsgator.  Okay SeanDaniel.com today gave us a lesson in RSS... I'm going to one-up him by doing a OPML.  OPML is a way to quickly and easily share your feeds with another person, another computer, etc.  OPML is a file format that can be used to exchange subscription lists between programs that read RSS files, such as feed readers and aggregators. So rather than you clicking and subscribing on each individual RSS feed, you can suck in the 'entire' Sharepoint blog listing in one she-bang.

On a final note.... I would just like to ask does anyone else routinely tend to spell Sharepoint, Sharepoing?  There's something about the g and the t being close that I end up with the wrong keys sometimes....

The ports of SBS

From the mailbag today comes the question from Alex... is there a way to publish Companyweb without opening 444?  And the answer is.... No.  You must have 444 for external access to CompanyWeb [Sharepoint].

SBS bascially requires the following ports:

TCP Port	Service	Description
21	FTP	Enables external and internal file transfer
25	Exchange Server	Enables incoming and outgoing SMTP mail
80 (http://)	IIS	Enables all nonsecure browser access, including: internal access to IIS Webs including the company Web, Windows SharePoint Web, Windows SharePoint administration Web, and server monitoring and usage reports Enables internal access to Exchange by OWA and OMA clients
110	POP3	Enables Exchange to accept incoming POP3 mail
123 (UDP port)	NTP	Enables the system to synchronize time with an external Network Time Protocol (NTP) server
143	IMAP4	Enables Exchange to accept incoming IMAP4-compliant messages
220	IMAP3	Enables Exchange to accept incoming IMAP3-compliant messages
443 (https://)	Outlook	Enables all secure browser access, including external access to Exchange for Outlook 2003, OWA, and OMA clients; required for external access to server monitoring and usage reports
444	Windows Share Point Services	Enables internal and external access to the SharePoint Web
500	IPSec	Enables external VPN connections by using IPSec
1701	L2TP clients	Enables external L2TP VPN connections
1723	PPTP clients	Enables external PPTP VPN connections
3389	Terminal Services	Enables internal and external Terminal Services client connections
4125 (Note: you can change this port in RRAS)	Remote Web Workplace	Enables external OWA access to Exchange, plus internal and external HTTPS access to the client Web site
4500	IPSec	Internet Key Exchange (IKE) Network Address Translation (NAT) traversal

If you need access to Sharepoint .... you MUST go through port 444.  For RRAS, the Sharepoint is automagically enabled if you merely click the box, for ISA they thought we'd be a bit more paranoid so you have to manually publish it.

 

So my Sharepoint hired a few employees

I got Live Communications server 2003 set up in my office and noticed that when I opened Sharepoint that it had “hired” a few people.  I had “Admin template”, “Mobile user template”, and “Power users template” as “contacts” inside of Sharepoint.  Knowing that this would freak out my end users... “who are these people?”, I asked around if there was a way to remove these.

 

Chad who is Sharepoint power user around here said to

 

Open your companyweb | Site Settings | Manage Users.  Check the

templates and then 'Remove Selected Users'

 

Also Chad pointed out... 

 

the Domain Power Users security group is a member of the Sharepoint Administrators group by default.  So if you have any Domain Power Users running around,

they'll still have full access to your companyweb site even if you

remove them from the user list within the site . . .

 

Remember too the BEST Sharepoint integration is with Office 2003.. you might have to “rig“ up some stuff with other Office versions:

Windows SharePoint Services FAQ - Can I simulate "Edit in" functionality

using...:

http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=308

 

As she wipes a tear from her eye

Sniff sniff... as I do my first “send to, as attachment” out of Excel via Outlook, I got my first sidebar box in Outlook that reminded me I'm on my new and improved SBS 2003 box now and we're no longer in Kansas [meaning SBS 2000] anymore!

See that?  That sucker is asking me... do you want to automagically set up a Sharepoint Shared space?  Oooh I'm getting gooseybumpies here.  You know about the document that talks about the best integration that you get is with Office 2003 and Sharepoint [and I would argue SBS 2003]?  Click on that link and see what I mean.

---

About shared attachments

When you send a file as a shared attachment, a Document Workspace site is created for the attachment in the Microsoft Windows SharePoint Services site that you specify. The Document Workspace carries the same name as the attached file.

Note  If you attach more than one file, the Document Workspace carries the name of the first file in the list of attachments.

Members of the Document Workspace

As the sender of the shared attachment, you become the administrator of the Document Workspace, and all the recipients become members of the Document Workspace, where they are members of the contributor site group.

Recipients can open the attachment, or they can follow the link that is added automatically to the message. The link goes to the home page of the Document Workspace, where a copy of the e-mail attachment is stored in the Shared Documents library.

Document updating

If the e-mail attachment is a document or Single File Web Page (MHTML) from Microsoft Office Word 2003, Microsoft Office Excel 2003, Microsoft Office PowerPoint 2003, a document from Microsoft Office Visio 2003, or an XML file from Word or Excel, members of the Document Workspace can open and work on their own copy of the attachment while the Microsoft Office program that they're using to edit the document periodically gets updates from the Document Workspace. Members can also save their changes to the Document Workspace copy.

---

Mondo kewl, huh!

The RSS feed is connected to the Sharepoint that is connected to the customer that is connected to..

Tim Barrett posted in the comment section a really kewl idea that I just had to pull up to the front blog.

Here's the idea. 

• You, the IT pro do a blog [blogger.com is free] of tips, tricks, announcements, happenings of interest to your customer.
• You set up a Sharepoint feed reader on your client's Sharepoint that suck in RSS feeds
• You subscribe your client to your feed
• Your client now gets announcments from you, not spam filtered, not stopped by email issues
• Your client now has a direct communication link from you

So what do you need to accomplish this?  Most of the ingredients you already have or are to be had for free

• Start a blog
• Free ones are at Blogger.com
• For pay ones are at Movabletype
• If you have SQL server you can do a .Text blog
• Radio Userland is a long time blog engine
• Sharepoint included in your SBS 2003
• Smilinggoat.net feed reader
• Drop a web part on that Sharepoint that displays your RSS feed
• Remember that Newsgator has a “post to blog“ feature so that you don't even need to go to the blog to post

Remember if the client is behind ISA you will need to add proxy info:

There are two ways you can use this web part within

your proxy server.  The first is to set your proxy

configuration in the Portal's web.config file:

 

<system.net>

    <defaultProxy>

      <proxy proxyaddress="server:port" bypassonlocal="true" />

    </defaultProxy>

  </system.net>

 

The second option is to configure the proxy server

settings on the web part.  In SHARED VIEW, the proxy

server/port settings are enabled for you to enter them.

And Nick found the command that adds the webpart to your sharepoint, but I also stuck the bat file here

C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\STSADM.EXE" -o addwppack -filename "C:\Program Files\Smiling Goat\FeedReader\SmilingGoat.FeedReader.cab" -globalinstall -force

Nick also sent me his Front page part that can be used to easily import [and it still has his firm name on it :-).  I'll ping him to double check to see if I've forgotten anything.  I know he had to walk me through a few steps... the main one being that batch file he did for me. [still needs to be easier for us non coders/admin types in my opinion]

Anne also has a service where she sets up Business blogs for folks, gives the person a tutorial on how they work, etc. if you still aren't convinced that blogs are a business tool.  It's a realtively inexpensive way to get a leg up in how the process of “blogging” works. 

It's funny because for a while when Anne and I would go nutcase over blogs, some of our geek counterparts were rolling their eyes. There are some even saying that if you don't have RSS.. that they just don't listen to you. 

So check out adding RSS to your client's Sharepoint!

When is a date not a date?

For those of you in the world that are not MM/DD/YY but backwards [well to me anyway], you do know that Company web has it's “own“ date settings, don't you?

Thanks to Kevin for posting this

Check out http://companyweb, Site Settings, Go to Site Administration link, 
Change regional settings link.

SharePoint.
    > Site Settings
        > "Go to Site Administration"
            > Management and Statistics
                    > "Change regional settings".

Gavin says check out the Sharepoint Guide

Gavin pings and says “have you checked out the Sharepoint useage and admin guide”....ummm no I haven't...... “it's a good document”

Check it out folks!

This compiled help file provides searchable, up-to-date information about using and managing sites based on Microsoft Windows SharePoint Services technology. The topics covered in this file include the following:

• Basic concepts
• Viewing information
• Sharing files and documents
• Sharing information
• Deleting information
• Organizing meetings
• Customizing lists and pages
• Customizing sites
• Customizing pages by using Web Parts
• Managing permissions and security
• Managing sites and settings
• Troubleshooting
• Reference

The content in this file is different from the content you can find in a Windows SharePoint Services site when you click Help. This content has been updated to correct errors, add information, and be easier to browse.

Missed the Sharepoint Live Meeting last week? No Problem!

Eric L sends the email today that they've put the recording of the Sharepoint up on the MSSmallbiz web site.  Kewlamundo!

Thank you to all of you who attended the Windows SharePoint Services LiveMeeting session we presented last week.  Since that session, we have received several requests for this information once available, so here it is.  The PDF& PPT versions of the 10/13 Windows SharePoint Services LiveMeeting that was presented by Brad Billison and Eric Ligman are now available along with the information regarding how to view the recorded version of the session in the "LiveMeetings" section of the http://www.mssmallbiz.com site:

 

http://www.mssmallbiz.com/LiveMeetings/Forms/AllItems.aspx

 

Thank you and have a great day,  [1]

 

Eric Ligman

Small Business Manager - U.S. Central Region

Enabling millions of small businesses and partners to realize their full potential

[1]  He's so polite isnt' he?  :-) 

Are you Sharepointing?

SBS 2003 is a year old and one of the parts of the box that I don't think we've played with enough is Sharepoint.  Harry made this point in his “Happy Birthday SBS” email yesterday.  Scoble says that O'Reillys' books on Sharepoint are the top sellers.  When Chad showcased his “poor man's” CRM at SMBnation people just started to see the concept and what you can do with Sharepoint.

As Scoble says:  “The impulse to create is strong. The impulse to share is strong. The impulse to consume is strong.”

So here's my personal take of what we need that came out of SMBnation to help us “bamm“ up Sharepoint as Emeril would say:

1.  We need consumables for the end user that are like “sound bites“  that make Sharepoint into easy how tos.  Right now most of the documentation out there is all aimed at the designer NOT the end user.  Don't forget that you need to TRAIN the end user how to use this technology.

2.  We need a Infopath that is a “runtime“ version.  What's that you ask?  One of the coolest additional tools that you can use as an additional feature is the program called Infopath.  This of it as a “standardization tool to help you “suck“ in data and information.  But you have to BUY the product to use it.  The SBS folks at SMBnation need a “runtime“ or bundle version that can run via a web app so that it does not need to be installed locally.  If you are in a situation where you forgot to install it, you can't use the power of it.

3.  We need a better centralized place for finding web parts and other “cool stuff“.  Right now it's a lot of word of mouth and blog linking that makes us find this stuff.  SmilingGoat and Sid Weber's Playground  I found via blog links or word of mouth.  Make it easier for me to find this cool stuff.

4.  Where's your Sharepoint Community page and advertisement of RSS feeds?   The official home page of Windows Sharepoint services is there.... where's the community link?  I know that Mike Walsh is a tireless Sharepoint MVP, yet where the page that can point me to his site?  “I“ know that it's located here but how would anyone else know that?

5.  Sharepoint blogs.  Advertise them more!  And again, I need a Sharepoint blog that focuses on the END USER and their needs.

• Mike Walsh's blog
• Sharepoint Thoughts
• Listing of Sharepoint Bloggers
• More Bloggers on Sharepoint from Laura J
  • Amanda Murphy
  • Arpans' Weblog
  • DevHawk (Category)
  • Drewby (rss)
  • Eric Legault
  • Frank Fischer (in German) (rss)
  • Jan Tielen (rss)
  • Jim Edelen (rss)
  • JohnWe's Sharepoint Blog (rss)
  • Lamont Harrington (rss)
  • Patrick Tisseghem (rss)
  • Point2Share (Daniel McPherson) (rss)
  • Random Ramblings...
  • RandomElements Blog
  • SharePointBlogs.com (rss)
  • Stramit's Blog
  • Tangible Thoughts (rss)
  • Tim Heuer (rss)

So what about you?  What do YOU need to “bamm” up Sharepoint for you?

If after applying the Sharepoint SP1 service pack you are getting HTTP 500 or 0x80040E14 error

Follow this guidance:

841216 - "0x80040E14" or "HTTP 500" error message when you connect to your Windows SharePoint Services Web site after you install a Windows SharePoint Services service pack:
http://support.microsoft.com/?id=841216

If they ever ask for my Amazon.com book purchases....

If they ever ask to see my Amazon.com book purchases they are going to see hacker books, computer books, and my latest purchases... a bunch of Sharepoint books.  I just finished an online training class and definitely my interest was peaked and definitely demanded that money be spent at the “book store”.

Remember that the SBS sharepoint [aka companyweb] is pretty much the same as “normal“ Windows Sharepoint Server with the following exceptions:

SBS sets up the WSS, it sets up the virtual server, configures the sites, add the users automagically.

It has custom lists, content unique to SBS -- for example -- it has Help Desk and Vacation calendar as a custom list

It has an import file wizard that allows bulk import of folder structures.

It has a part that works with MS fax server that can auto route incoming faxes to a WSS fax document library.

That's about it folks.... other than that the technology of WSS inside SBS is the same as "normal" WSS.

So the books I ordered are:

Amazon.com: Books: Microsoft SharePoint 2003 Unleashed (Unleashed):
http://www.amazon.com/exec/obidos/tg/detail/-/0672326167/102-6920567-9875324?%5Fencoding=UTF8&v=glance
Amazon.com: Books: Microsoft SharePoint: Building Office 2003 Solutions:
http://www.amazon.com/exec/obidos/tg/detail/-/1590593383/102-6920567-9875324?%5Fencoding=UTF8&v=glance
Amazon.com: Books: Microsoft SharePoint Products and Technologies Resource Kit (Pro - Resource Kit):
http://www.amazon.com/exec/obidos/tg/detail/-/073561881X/102-6920567-9875324?%5Fencoding=UTF8&v=glance

....so I'm looking for a "beginners guide to Sharepoint in the SBS platform"....

....and either I'm blind or not googling properly... we do have our MVP friend Mike Walsh's site that is specficially WSS, Home - WSS FAQ: http://wss.collutions.com/default.aspx but now I'm searching for webcasts [under the theory a picture is worth a 1,000 words] and finding a lot on Sharepoint PORTAL server but not on WSS.

I found this blog, but it lists SPS not WSS.  MSDN has some stuff, but no pictures.

AH HA... this might just be what I'm looking for... I found this on the Sharepoint customization site.  But I think there still needs to be more content specifically “for” Sharepoint on SBS.  We do have a couple of unique things.  So far I haven't found any “basic” documentation on the web that helps a newbie get a handle on it.

I'll keep looking....

We've declared it a national day of celebration on behalf of Eliot Sennett

My fellow SBS MVP buddy Eliot Sennett has a killer sense of humor and writes.....

OK - this must be old news for everyone else out there, but it took me
days to figure out. So, if everyone already knows it, just laugh at me.
 
Mike Walsh - this is a proposed addendum to your WSS site document 55.1
(WSS FAQ  Alerts aren't working even if the Timer Service...).
 
Here's the problem - you subscribe to a WSS site (configure an alert)
and you don't get it. Everything I found on this issue dealt with the
WSS Timer Service - either the account running the service lacked
permissions to the content or the service stopped or blah blah blah. 
Anyway, there is another possible cause.
 
By default, WSS configures the email server settings with the "from" 
address as blank. There are a million firewalls, spam filters, and other
similar things that automatically block email with blank sender
addresses. If you pop in even a fake email address in the server's
"from" address in the WSS email configuration page, alerts start
working.
 
I'm extremely proud of myself for figuring this out, because the last
time I figured out something technical, people were still arguing the
relative merits of VisiCalc vs Lotus 1-2-3. Please record this day in
your calendars and send email to your political leaders suggesting that
it become a national holiday in whatever nation you are living. Thank
you.
 
Eliot Sennett
Level Two

... oooh I'm feeling the power...are you?

oooh...guys... can we start to see the power of Sharepoint now?  Robert Scoble points to a tool that could post from Outlook into a place on Sharepoint... basically blog post into Sharepoint.  Think of how much faster you can do a “firm announcement” if you could just drag it and it would autopost up to Sharepoint?

Moving SBS 2003 Data Folders

Moving SBS 2003 Data Folders - These folders include: Users Shared Folders,
the Windows SharePointT Services and Monitoring databases, Exchange
databases and log files, Sent Faxes folder, and ClientApps shared folder.

This document provides step-by-step instructions for moving each of the
data folders for Windows Small Business Server 2003. You can choose to move
one or all of the data folders. For example, you can choose to move only
the Users Shared Folders and no other data folders. Additionally, it is not
necessary to move the data folders in the order presented in this document.
For example, you can choose to move the Exchange databases and log files on
one day and then the Users Shared Folders on another. However, it is
strongly recommended that you always complete and verify a full backup
before moving any data folders.

Download it here:

http://download.microsoft.com/download/1/1/6/11671e4d-fb21-489c-870f-db36fd21a7d2/SBS_MoveDataFolders.DOC

[Thanks Marie for that info!]

Sharepoint KB articles of interest

837849 - How to add an icon to Windows SharePoint Services to represent Adobe PDF documents that are stored in document libraries:
http://support.microsoft.com/?kbid=837849

825513 - How to use the SharePoint Administrator to upgrade to FrontPage 2002 server extensions on Windows Server 2003:
http://support.microsoft.com/?kbid=825513

839048 - "Could not instantiate control SharePoint:ProjectProperty" error message when you view a Windows SharePoint Services Web page:
http://support.microsoft.com/?kbid=839048

And another, this might be interesting.....

I have a RSS feed that monitors the Microsoft download site and here is another one of those, hmmm .... this looks interesting... let be blogify it for later and deal with it later in the month.  :-)

[SBS has Sharepoint you know]

The Document Library Event Handler Toolkit (EventHandlerToolkit.exe) download introduces developers to the Microsoft® Windows® SharePoint™ Services list events feature for document libraries.

http://www.microsoft.com/downloads/details.aspx?familyid=4b2c2f1b-d74a-482a-903a-45bb44c5dec4

Adding RSS feeds into your sharepoint site

http://weblogs.asp.net/exchange/archive/2004/03/24/95530.aspx

Take a look at the Exchange team blog for instructions on adding RSS feeds into your Sharepoint!

Are you getting an error referring to #50070: Unable to connect to the database STS_Config?

From a post in the newsgroups....

“Based on my research, this problem could be caused because the SharePoint
Timer Service failed to contact the SharePoint database while the SBS is
rebooting. In SBS 2003, the SharePoint Timer Services is used to send
notifications and performs scheduled tasks of WSS. It needs to access the
SharePoint database when starting. Since the Veritas Backup exec software
is installed on the server box and several backup exec related services
have started during the reboot, these services could cause the SharePoint
database from being mounted in a timely manner, thus, causing the problem
to occur.

I reproduced this problem in my test machine. After the MSSQL$SHAREPOINT
service has stopped, this error message will be logged in the application
log. You may now try to manually start this service to see if the problem
will still occur.

1. Start-->Run-->Type 'services.msc' (without the quotation marks) and
press Enter.

2. In the Services console, stop the 'SharePoint Timer Services'. Check the
status of the 'MSSQL$SHAREPOINT' service, make sure it has been started and
then restart the 'SharePoint Timer Services'. The problem should be
resolved.

If there is no problem with the manually service startup, we can set a
service dependent of the SharePoint Timer Service. Please try the following
steps:

1. Start-->Run-->Type 'Regedit' (without the quotation marks) and press
Enter.

2. In the registry editor, navigate to the following registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

3. Right-click the blank area in the right panel, click
'New'-->'Multi-String Value'.

4. Input the value name 'DependOnService' (without the quotation marks) and
then double-click the newly created value. In the value data area, type
'MSSQL$SHAREPOINT' and click 'OK'.

5. Close the registry editor and reboot the server box.“

Are faxes not opening right on your SBS 2003?

If your faxes are not opening right, it's probably because Quicktime was loaded up. Try uninstalling Quicktime or the following steps:

1. Save a .TIF file on the Desktop.
2. Right click on the .TIF file, move to Open With, and then select Choose Program.
3. Select Windows Picture and Fax Viewer from the list. 
NOTE: Place a check mark from Always use the selected program to open this kind of file. 
4. Click OK to open the photo image with Windows Picture and Fax Viewer. 
5. Close this window, and then test if this problem is solved.

Take a look at these:

319196 OFFXP: Cannot Preview Scanned TIFF File in Windows Picture and Fax Viewer
http://support.microsoft.com/?id=319196
329270 You Cannot View TIFF Images Using Windows Picture and Fax Viewer
http://support.microsoft.com/?id=329270

An option put forth by Kevin W. in the newsgroups is to load alternative TIF viewer programs:

Check out:
http://www.alternatiff.com/  or http://phoenix.gov/tiffview.html

Gavin reports that alternatiff has lots more options for viewing and he's considering loading this up on all his installs.

 

Wanting more training on Sharepoint?

Download details: SharePoint™ Developers' Conference 2003:
http://www.microsoft.com/downloads/details.aspx?familyid=d5bd33cb-4a0c-45c6-9bd3-091470db7943&displaylang=en

If you've tried EVERYTHING and still can't get Company web installed through Windows Update.....

Try this:

1. Check the file versions of C:\Program Files\Common Files\System\Ole 
DB\oledb32.dll and oledb32r.dll.

The oledb32.dll file and oledb32r.dll file should be 2.80.1022.0 in a 
default install of SBS 2003.  If one file is this version and one file is 
not, you only need to perform the rest of the steps for the file that is 
the improper version.

2. Get the 2.80.1022.0 version of the oledb32.dll and oledb32r.dll files.  
 You can get these files by expanding them from the SBS 2003 CD #1:\i386 
folder.

3. Delete the C:\winnt\system32\dllcache\oledb32.dll and oledb32r.dll. 
Place a copy of the 
2.80.1022.0 version of oledb32.dll and oledb32r.dll in the 
C:\winnt\system32\dllcache folder.

4. Rename the C:\Program Files\Common Files\System\Ole DB\oledb32.dll file 
and oledb32r.dll file.
Place a copy of the 2.80.1022.0 version of oledb32.dll and oledb32r.dll in 
this folder.

5. Register the updated oledb32.dll and oledb32r.dll file using the 
following command.
regsvr32 C:\Program Files\Common Files\System\Ole DB\oledb32.dll 
regsvr32 C:\Program Files\Common Files\System\Ole DB\oledb32r.dll 

6.  Reinstall the Intranet using SBS setup (if you have the updated CD #3) 
or by running SBS WSS patch 832880. 

If you purchased your SBS2k3 prior to February....

You need to make sure you have a replacement cdrom 3 [the Sharepoint cdrom]

You can order the cdrom from this site:

Windows Small Business Server 2003 CD3:
https://microsoft.order-4.com/sbsrtmcd/

When it comes, don't worry that it says “Premium” ... It's the same “bits” as standard.  I looks like this:

http://www.sbslinks.com/cd3.htm

If you already have begun to load your SBS and you don't have this cdrom, don't worry, just go to Windows Update and your patch fix will be downloaded and you will be good to go.

 

Sharepoint slow to load when first opening it up? Tweak it!

You can speed up the launching of the Companyweb site by changing the IIS
Application Pool.

Go to IIS Manager
Open the Application Pools
Right click on the DefaultAppPool and go to properties
Go to the Performance Tab
Uncheck the top box - shutdown worker processes after being idle.

http://www.sbslinks.com/AppPool.htm

Sharepoint patch failing?

 If your installation of the Sharepoint patch keeps failing, look in the KB832880.log and see if you have the following:

The procedure entry point GetTextExtentPointI could not be located in the
dynamic link library msdart.dll.

1) You will need to get the 2.80.1022.0 version of the oledb32.dll file.

   You can get this file by expanding it from the SBS 2003 CD #1:\i386
folder to a temporary directory expand d:\i386\oledb32.dl_ c:\temp\oledb32.dll

2. Delete the %systemroot%\system32\dllcache\oledb32.dll and place a copy of
the 2.80.1022.0 version of oledb32.dll in the %systemroot%\system32\dllcache
folder.

3. Rename the C:\Program Files\Common Files\System\Ole DB\oledb32.dll file
and place a copy of the 2.80.1022.0 version of oledb32.dll in this folder.

4. Register the updated oledb32.dll file using the following command.
regsvr32 C:\Program Files\Common Files\System\Ole DB\oledb32.dll

5.  Reinstall the SBS WSS patch 832880.

Flat file backup of Sharepoint

Generally, if we restore an individual SharePoint file, we need to have a
file-based backup image of your SharePoint documents. As I know, there are
two ways to perform file-based backup for your SharePoint database. For
your convenience, I included the methods below:

Method 1. Use NTBackup.

=====================

According to our test, we can map the folders under \\companyweb as network
drives now. Thus, we can use NTBackup to back up or restore the files in
these folders (network drives) directly. To do so, please follow the steps
below:

1. Map the \\Companyweb\Foldername folder as a network drive

2. Run NTBackup and back up the network drive.

3. When you need to restore one file in this folder, simply run NTBackup to
restore

Method 2. Use Stsadm.exe.

=====================

If you have enabled the recovery of SharePoint files, you can recover a
file or list item by restoring the entire site from a backup to a subsite
of http://companyweb, selecting the file or list item that you want to
restore, extracting it, and uploading it to its original location. To
enable the recovery of individual SharePoint files, please use the
following procedure:

1. Click Start, click Control Panel, click Scheduled Tasks, and then click
Add Scheduled Task.

2. Click Next on the first page of the Scheduled Task Wizard.

3. Click Browse, go to %SystemDrive%\Program Files\Common Files\Microsoft
Shared\Web server extensions\60\Bin, and then double-click Stsadm.exe.

4. Select how often you want this task to run, and then click Next.

5. Select the time you want to run the schedule, and then click Next.

6. Enter administrator credentials, and then click Next.

7. Select the Open advanced properties when I click finish check box, and
then click Finish.

8. On the Task tab in the dialog box that appears, in the Run box, type
"%SystemDrive%\Program files\Common files\Microsoft shared\Web server
extensions\60\Bin\Stsadm.exe" -o backup -url http://Companyweb -filename
target path -overwrite, where target path is where you save the backup of
your internal Web site. Click OK. You must type the quotation marks.

If you have enabled this before, you can follow the steos below to restore
the missing files:

1. Click Start, click Command Prompt, and then type "%SystemDrive%\Program
files\Common files\Microsoft shared\Web server
extensions\60\Bin\Stsadm.exe" -o createsiteinnewdb -url
http://companyweb/sites/RestoredSite -ownerlogin DOMAIN\administrator
-owneremail administrator@DOMAIN.local -databasename STS_RESTORE, where
DOMAIN is your server domain and administrator@DOMAIN.local is your
administrator¡¯s e-mail address. Include the quotation marks as part of the
path. Press ENTER.

2. Type "%SystemDrive%\Program files\Common files\Microsoft shared\Web
server extensions\60\Bin\Stsadm.exe" -o restore -url
http://Companyweb/Sites/Restoredsite -filename target path -overwrite,
where target path is the location where you chose to save your SharePoint
backup. Include the quotation marks as part of the path. Press ENTER.

3. Open Internet Explorer, and in the address bar, type
http://Companyweb/Sites/Restoredsite. The site that appears is the same as
your company Web site.

4. In the restored site, navigate to the missing file.

5. Right-click the file, select Save Target As, and then select a location
to which to save the file.

6. Repeat steps 4 and 5 for all missing files.

7. Open your company Web site, navigate to the location where the missing
files should be, and then on the SharePoint toolbar, click Upload Document.

NOTE: The second method is provided in the SBS Server help. You can find
this by the following steps:

1. Open Server Management.

2. Click Standard Management->Backup.

3. Click Restore Sharepoint files in the right pane.

However, if you have not performed either method above to enable file-based
backup, I am afraid that we may have to restore the entire database.

Put RSS feeds into your Sharepoint site

SharePoint Component Details:
http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a=336

Publishing Sharepoint through ISA

 Making Companyweb available via RWW with ISA installed.

NOTE: If ISA isn't installed, it all works through the CIECW, no further
configuration required.

NOTE: Run the CEICW first to create a certificate.

1. Create a new protocol definition for Inbound TCP/444

Go to ISA -> Policy Elements -> Protocol Definitions. Create a protocol
definition called "Companyweb Inbound" (Port number: 444, Type: TCP,
Direction: Inbound)

2. Create a Server Publishing rule to publish the new protocol.

Go to ISA -> Server Publishing Rules, create a rule called "Publish
Companyweb". Specify the internal and external IP, set it to apply to
"Companyweb Inbound" and Any Request.

3. Assign the FQDN cert to the companyweb with SSL port set to 444

Go to IIS -> Companyweb Properties. Directory Security tab. Click Server
Certificate -> Assign an existing certificate. Next, you should have 2
different certs available. One is the FQDN, the other is
Publishing.domain.local. Pick the FQDN and continue. Set the SSL port to 444
and next all the way.

4. Do the regedits for the sharepoint links you want to display in RWW.

HLKM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\KWLinks\STS to
1
HLKM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\AdminLinks\STS
to 1
HLKM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\AdminLinks\Help
Desk to 1

5. Type "iisreset" at a command prompt.
6. Restart ISA Server Control.
7. From a remote location, verify you can telnet to FQDN on port 444.

So if you created your certificate server.domain.com, then server.domain.com
must be reachable from the internet. If all you have is a fixed ip address,
then create your certificate using the ip. "123.456.789". Then telnet to
123.456.789 444 to verify. If this doesn't work, go back to the top and try
again, starting with the ciecw to create a certificate.

8. Connect to RWW and you should see the SharePoint links.

NOTE: If your remote client happens to also be behind an ISA server, you're
not done.

ISA does not allow HTTPS traffic on port 444 by default. Opening the packet
filters should not change the behavior since that only affects server based
communications. Your client is behind ISA and will be using the protocol
rules and if the HTTP Redirector is enabled it will also use the
site&content rule for its HTTPS requests. You need to follow the
instructions on the following article (change the port range to 444,444) on
the ISA server.

283284 Blank Page or Page Cannot Be Displayed When You View SSL Sites

http://support.microsoft.com/?id=283284

Now officially documented here:

838304 - How to publish http://Companyweb to the Internet by using ISA Server 2000 on a server that is running Windows Small Business Server 2003, Premium Edition: 
http://support.microsoft.com/?kbid=838304

If you can't get Sharepoint installed - reset your clock.

833019 - You Receive an Error Message When You Install Windows SharePoint Services, Create a New Content Database, or Provision a New Virtual Server:
http://support.microsoft.com/?id=833019

SYMPTOMS
If you try to install Microsoft Windows SharePoint Services by using the default settings after November 24, 2003, you receive the following error message:

Metadata manifest 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin\sqmcfg.dll' does not exist or has invalid signature. (Error code: 2779).  If you try to provision a new virtual server or you try to create a new content database when you are running Windows SharePoint Services by using Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE) after November 24, 2003, you receive the following error message:

Metadata manifest 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin\sqmsto.dll' does not exist or has invalid signature. (Error code: 2779).  Note By default, SQL Server 2000 Desktop Engine (Windows) (WMSDE) is installed when you choose Typical Install during the installation of Windows SharePoint Services.

CAUSE
This problem is caused by code that verifies the signatures of the dynamic-link libraries (DLL) that are installed with Windows SharePoint Services. An error in the verification algorithm does not permit the signatures of the DLLs to be verified. All installations of Windows SharePoint Services experience this behavior after November 24, 2003.

WORKAROUND
To work around this problem, temporarily set the date in the Date and Time Properties dialog box to a date that is between May 24, 2002 and November 23, 2003. If you receive the error messages that are described in the "Symptoms" section when you try to install Windows SharePoint Services by using the default settings, follow these steps:
Remove Windows SharePoint Services.
Set the date in the Date and Time Properties dialog box to a date that is between May 24, 2002 and November 23, 2003.

Note You may have to temporarily disable the Windows Time service if it has been enabled. Install Windows SharePoint Services again by using the same options. Set the date in the Date and Time Properties dialog box back to the current date and time, and then restart the Windows Time service if appropriate.  If you receive the error messages that are described in the "Symptoms" section when you try to provision a new virtual server or when you try to create a new content database, follow these steps:
Set the date in the Date and Time Properties dialog box to a date that is between May 24, 2002 and November 23, 2003.

Note You may have to temporarily disable the Windows Time service if it has been enabled.  Try to provision the virtual server or to create the new content database again, and then verify your results.  Set the date in the Date and Time Properties dialog box back to the current date and time, and then restart the Windows Time service if appropriate.  Note If you receive the following message during this process, close your Internet browser, and then start the Internet browser again:   The security validation for this page has timed out.

STATUS
Microsoft is researching this problem and will post more information in this article when the information becomes available. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION
This problem does not apply to Windows SharePoint Services deployments that use Microsoft SQL Server 2000 for data storage. It also does not affect Windows SharePoint Services sites that have already been provisioned.

 

UPDATE - DON'T RESET YOUR CLOCK - JUST INSTALL IT AS IS AND THEN GO TO WINDOWS UPDATE AND GET THE PATCH

To Reinstall Sharepoint

If you have RTM, let's try this
1. Remove Intranet using sbs setup
2. Remove MSDE SharePoint from Add/Remove Program
3. Delete Program Files\Microsoft SQL Server\MSSQL$SharePoint\ and
HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Intranet
4. Delete Companyweb from IIS if it is still there.
5. Rerun SBS setup to put back Intranet.

Enabling Full Text Searches in Sharepoint by upgrading to SQL

 

To enable full text search you will need to do the following..

1) Upgrade the SharePoint named instance of SQL to full SQL Server 2000.. 
be sure that you install/add Full-Text Search.. (listed in the steps in the 
premiuminstallsteps.htm on the Premium cd)
2)  Once SQL Server the named instance is upgraded and service packed, then 
go to Start/Administrative Tools/SharePoint Central Administration  scroll 
down to the Component Configuration section and click on the Configure 
full-text search link.  Then click the checkbox to enable full-text search 
and index component..

Once that is done if you then go back to the companyweb site then you 
should see a text box in the upper right corner of the page (with a 
magnifying glass icon to the left.. ) to enter your search criteria.

Guide for installing, configuring, managing, and maintaining Windows SharePoint Services

http://www.microsoft.com/downloads/details.aspx?familyid=a637eff6-8224-4b19-a6a4-3e33fa13d230

Is your Sharepoint a big sluggish on first launch?

 You can speed up the launching of the Companyweb site by changing the IIS
Application Pool.

Go to IIS Manager
Open the Application Pools
Right click on the DefaultAppPool and go to properties
Go to the Performance Tab
Uncheck the top box - shutdown worker processes after being idle.

Sharepoint Template for the Legal Industry

http://www.microsoft.com/downloads/details.aspx?familyid=da1655fd-54c0-4ffc-8bcc-abe02741bda7

Build a Windows SharePoint Services Site using a pre-designed Windows SharePoint Template.

Hosting Sharepoint on your SBS to be viewed by external users

http://www.microsoft.com/downloads/details.aspx?familyid=b51dcb25-0c63-4561-b981-9a3c860b9f15

This document provides information about how to configure Microsoft® Windows® Small Business Server 2003 to host a new Windows SharePoint™ Services Web site that can be used by people outside your local network.

Sharepoint template for Human Resources

Download details: Windows SharePoint Services Template Package- Human Resources:
http://www.microsoft.com/downloads/details.aspx?familyid=df912cc2-0fd2-4f59-b116-1aa053ca8ada&displaylang=en

Build a Windows SharePoint Services Site using a pre-designed Windows SharePoint Template - Finance

http://www.microsoft.com/downloads/details.aspx?familyid=7e706976-2ba1-4aa0-a987-e1ae1e7cc99c

Build a Windows SharePoint Services Site using a pre-designed Windows SharePoint Template - Real Estate

http://www.microsoft.com/downloads/details.aspx?familyid=335b314e-408e-4662-8543-1fec9d1837ca

Build a Windows SharePoint Services Site using a pre-designed Windows SharePoint Template - Hospital

http://www.microsoft.com/downloads/details.aspx?familyid=ce57107f-e0fb-499b-9f41-d813a14823c8

Build a Windows SharePoint Services Site using a pre-designed Windows SharePoint Template.