This weekend is going to be all about SharePoint on the blog. To start here’s a handy free downloadable webpart. With it you can easily add an aggregated RSS feed into your sites.
3.1.0.1
Release name is requiredReleased:
Nov 25 2008Updated:
Nov 26 2008 by timheuerDev status:
StableRated:
No ratings yet for this release (Add your own rating)Reviewed:
0 reviewsDownloaded:
341 downloadsWiki link:
[release:19830]Downloads & Files
application, 345K, uploaded Nov 26 – 341 downloads
Categories: SharePoint · Web Links of Note
Several Microsoft applications require databases that utilize the Windows Internal Database aka SQL Server 2005 Embedded Edition. These include WSUS 3.0 and WSS 3.0 (SharePoint Services). The instance is noted by a name of ‘MICROSOFT##SSEE’.
If you ever need to get at the databases contained in the instance you will find that this isn’t conventional. In SQL Server Management Studio UI you must use a named pipe identity in order to connect to this instance. You optionally could also use SQLCMD or OSQL scripts.
***now months later I found this critically important to a SharePoint installation that was using this database instance. What had occurred is that this separate and experimental lab server doesn’t have a regular backup routine; consequently, SQL’s log grows and grows until a backup is made. My _log.ldf file was well over 30GB! Also, the drive was less that 1% from full. So a little Googling and up popped an Experts Exchange thread that had the information embedded – http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_23983391.html With the Express Management Studio GUI and a couple of clicks it was all sorted. 
Lots of space released and I’m wiser for it.
a nice SQL reference: http://blogs.mssqltips.com/forums/t/843.aspx
***editors note***
As I worked through an SBS 2008 migration, the Companyweb migration instructions specify to ONLY open AS ADMINISTRATOR (right click the shortcut) the SQL Server Management Studio Express (SSMSE) before entering the Named Pipe path. DO IT. Trust me, if you don’t you won’t connect to the …##SSEE database.
Categories: Admin Tools & Tips · SQL · SharePoint · WSUS 3.0
Tagged: MICROSOFT##SSEE
Thank you Alpesh Nakar for providing this resource for the PSConfig command line utility. This is deep dive and practical reading for mastering SharePoint 3.0 administration. The actual PSconfig switch information is found in the psconfig.chm Help file (%systemdrive%\Program Files\Common Files\Microsoft Shared\web server extensions\12\Help\1033) and the information is found there at the very last listed topic.
SharePoint: WSS Installation On A DC – PSConfig Goodness
11 Mar, 2007 SharePoint
Using Configuration Wizard without the wizard! That’s right.
This has nothing to do with our installation that we have done so far. However, I think you should know about this very powerful exe file that ships with this version of Windows SharePoint Services v3.
psconfig
details in linked blog post below
Categories: Admin Tools & Tips · SharePoint
Oh if only we could have this as a supported solution. Still this makes the side-by-side installation all the more practical. What is the main gain from having “Companyweb” as the address that resolves to WSS v3 vs. the original v2? You don’t gain any new WSS v3 functionality. What you do get is that any of the SBS embedded links such as the main one in RWW now will take users into WSSv3. This is the meat of the matter.
Chad, you are the man!
Companyweb & Sharepoint v3 – Part 5
a.k.a. - Living on the Edge. Just remember, there’s a reason it’s called the bleeding edge . . . Here’s your warning: In this post I am going to explain configuration changes I made to my own internal production environment to get http://companyweb to point to a new WSS v3 site. This configuration is not supported by Microsoft or myself. If you decide to try to replicate these settings in your environment, you are doing so at your own risk.
OK, let’s recap. We’ve talked about the benefits of Sharepoint v3? Check. We’ve talked about planning what we’re going to move, how we’re going to move it, and what we’re going to have to clean up after the move? Check. We’ve talked about prepping our environment so that WSS v3 search works? Check. We’ve talked about installing WSS v3 and accessing it via a common name? Check. Chad has warned everyone that just because he’s crazy enough to implement a non-supported configuration doesn’t me he’s recommending it or supporting it? Check.
Companyweb & Sharepoint v3 – Part 5 – Aimless Ramblings from a Blithering Lunatic . . .
Categories: RWW · SBS · SharePoint
FYI – I’m putting this on my list of thing to research & explore for 2008. If an “easy” extranet SharePoint site can be made possible, I’m VERY interested and I think many businesses might benefit from this too.
The Extranet Collaboration Toolkit for SharePoint helps enhance security by creating each collaboration site as a SharePoint site collection. This ensures that teams using one collaboration site will not be able to view documents on another site, unless they are explicitly given access. In addition, the toolkit puts all external users in ADAM (Microsoft’s lightweight directory service), rather than in the organization’s primary internal directory.
The benefits for your customers include:
Boosts security. The toolkit allows team members to store and share documents centrally on their organization’s server, instead of e-mailing documents to others across the Internet. And instead of giving VPN access to external team members (therefore granting them access to everything on the internal network), site owners can give external members access to just the team collaboration site.Easy to deploy. Automated tools and step-by-step instructions allow customers to deploy this Solution Accelerator quickly and easily – in as little as two hours, instead of weeks or months without the toolkit.
Easy to use. Once the toolkit is deployed, team members can set up their own SharePoint collaboration sites in minutes. The toolkit’s web-based interface makes it simple for team members to share documents and collaborate with each other across the Internet.
Reduces IT costs and boosts productivity. Project team members can manage sites on their own, freeing up scarce IT resources to focus on higher-return activities.
Thoroughly tested. The toolkit is extensively tested in our labs, and verified by customers and partners under real-world conditions.
The Extranet Collaboration Toolkit for SharePoint is now in Beta and available via MSConnect! To learn more about the toolkit, click here.
Microsoft SharePoint Products and Technologies Team Blog : New Beta Extranet Collaboration Toolkit
Categories: IIS · SharePoint
Tagged: extranet, SharePoint
Sean Daniel The Official SBS Blog SBS Documentation Team blog Susan Bradley Microsoft SBS Community Blog
