Blog Home  Home RSS 2.0 Atom 1.0 CDF  
Mike Walsh's WSS and more - Saturday, December 13, 2008
 
 Saturday, December 13, 2008

Note: All of the addresses of the KB / Articles - 2007 Products / MS / Non-MS Articles below were valid at the time I added them to the WSS FAQ
site and to this file. I can't guarantee that they still are.

(Items are added to the WSS FAQ throughout the week so you will find new items more quickly by checking at wss.collutions.com or www.wssfaq.com daily.)

From 7th - 13th December 2008

NOTE: Amendment to KB articles: Microsoft are now not amending the date of a KB article if the change made is marked as a version point change (so from 2.2 to 2.3 for instance).
This ought to mean that the amendment made is cosmetic rather than important as important text changes ought to result in a major version change (such as from 2.2 to 3.0).
Because of this change and to avoid unnecessary effort I will in future not amend the listings in the WSS FAQ sites if only a minor version change has taken place.
I will continue to amend both the date and version numbers of major version changes and of course will continue to add all relevant new KB articles that my RSS feeds and other sources give me.

I.1 2007 KB Articles    (*now only one section for WSS and MOSS*)

New

None

Modifed

None


I.b Forefront KB Articles

New or Modified

None

I.c InfoPath 2007 KB Articles

New or Modified

None

I.d SPD 2007 KB Articles

New or Modified

None


II. Articles - 2007 Products  (no longer with all links to articles for other Office 2007 and other 2007 Products)

New

A. Office 2007 Server Products

http://www.endusersharepoint.com/?p=1008

Why Can’t I Easily Port SharePoint Designer Workflow Solutions From One List to Another? Part 1 (EnduserSharePoint.com - Paul Galvin)

9th December 2008 (date added)

http://office.microsoft.com/en-us/help/HA103339651033.aspx

The SharePoint Shepherd's Guide for End Users extract: Create a document workspace from within a document

6th December 2008

http://office.microsoft.com/en-us/sharepointserver/HA103339681033.aspx

The SharePoint Shepherd's Guide for End Users extract: Connect your document to a SharePoint site or workspace

6th December 2008

http://office.microsoft.com/en-us/sharepointserver/HA103347451033.aspx

The SharePoint Shepherd's Guide for End Users extract: Remove a document workspace

6th December 2008

http://technet.microsoft.com/en-us/library/dd335970.aspx

Logging and auditing business data operations using the Business Data Catalog (Updated 4th December 2008)

4th December 2008

http://office.microsoft.com/download/afile.aspx?AssetID=AM103360091033

Poster: Architecture Example - Single School, Single Server

4th December 2008

http://www.devx.com/dotnet/Article/40007

Creating and Deploying SharePoint Solution Files (devx - Joydip Kanjilal)

24th November 2008

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032388934&EventCategory=5&culture=en-US&CountryCode=US

TechNet Webcast: Which Enterprise Search Solution Is Right for My Business? (Level 100) (Mei Lau)

7th November 2008

B. Other Office 2007 products

http://technet.microsoft.com/en-us/library/dd335961.aspx

Configure a dedicated front-end Web server for crawling (Search Server 2008) (updated 4th December 2008)

4th December 2008

http://technet.microsoft.com/en-us/library/dd335962.aspx

Configure a dedicated front-end Web server for crawling by using the user interface (Search Server 2008) (updated 4th December 2008)

4th December 2008

http://technet.microsoft.com/en-us/library/dd335960.aspx

Configure a dedicated front-end Web server for crawling by editing the Hosts file (Search Server 2008) (updated 4th December 2008)

4th December 2008

http://www.sharepointusecases.com/index.php/2008/10/configuring-scopes-in-microsoft-search-server-2008-part-2/

Configuring scopes in Microsoft Search Server 2008 Part 2 (Blog - Toni In)

20th October 2008

http://www.sharepointusecases.com/index.php/2008/10/configuring-scopes-on-microsoft-search-server-2008/

Configuring scopes in Microsoft Search Server 2008 Part 1 (Blog - Toni In)

19th October 2008

C. Other relevant products

None

 

Modified

http://technet.microsoft.com/en-us/library/cc263467.aspx

Deploy software updates for Office SharePoint Server 2007 (Updated 4th December 2008)

4th December 2007 (previous version 12th November 2008)

III WebCasts (+ PodCasts, On-Line courses) for 2007 Products

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032396510&EventCategory=5&culture=en-US&CountryCode=US

MSDN Webcast: SharePoint Products and Technologies for Internet Site Development: Getting Started (Level 100) (Todd S. Baginski, Advaiya)

2nd December 2008

IV WSS v3 FAQ

New

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1631

VI.137 SPSRollUpChart WebPart (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1632

VI.138 Navigation Web Parts (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1633

VI.139 SPSExplorer WebParts (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1634

VI.140 Cut Copy / Paste (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1635

VI.141 SPSRollUp (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1636

VI.142 SPSProfessional Site Creation Event Handler (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1637

VI.143 ActionDataBase (commercial - SPSProfessional)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1620

X.234 SmartTools.Charts (codeplex - Jan Tielens)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1621

X.235 ChartPart for SharePoint (codeplex - "wictor")

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1622

X.236 SharePoint PowerGUI Launcher 1.0 (codeplex - "cglessner")

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1623

X.237 Silverlight Blueprint for SharePoint (codeplex - "redmondhockey")

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1624

X.238 SharePoint AJAX RSS Aggregator WebPart (codeplex - Zlatan Dzinic)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1625

X.239 SharePoint RSS Aggregator Web Part (codeplex - Zlatan Dzinic)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1626

X.240 Active Directory Tools For SharePoint (codeplex - Burke Holland)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1627

X.241 Solutionizing for SharePoint (codeplex - "dahlbyk")

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1628

X.242 STSDev 2008 Version 1.1 (codeplex - dmcwee)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1629

X.243 Custom SharePoint Workflow template with Debugging (codeplex - Tobias Lekman)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1630

X.244 Content Type Toolbar v1.2 (free - James Milne)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1638

X.245 SharePoint Language Store (for multi-lingual sites) (codeplex - Chris O'Brien)


Modified

None

V WSSv2 KB Articles (plus SPS 2003 Hot fixes)

New or Modified

None

VI WSSv2 FAQ

New or Modified

None

VII. MS Articles

New or Modified

None

 

12/13/2008 11:14:13 AM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 
 Wednesday, December 10, 2008

It's not that long ago (this http://mikewalsh.bilsimser.com/PermaLink,guid,768c223a-4f27-479e-8f21-cbc822ae2250.aspx is the re-posted version of that post) that I posted about the strange situation that after installing Search Server 2008 Express on top of WSS 3.0, I had a set of search web parts available to me in both the Search Server site and in the (original) WSS 3.0 site but that they weren't able to be added (although listed) in the WSS 3.0 site.

I was documenting every change I made and then checking this and the situation was always the same. Yet I knew that in an identical installation (VM copy) something had "clicked" and suddenly I *could* add web parts in that VM copy's WSS 3.0 site. So I kept making a change and then trying but still nothing.

Well now I don't think I have made any change to the WSS 3.0 system but now I CAN add a search web part to my search results page that is stored in a document library in the WSS 3.0 site.

As far as I can see (and no guarantees on this because I've made such assumptions before and been proved wrong) the only change I have made since I last tried and failed to add a search web part to my search results page is the following.

On the home page (default.aspx) I added in the right-hand-column (above the WSS image) the Advanced Search box. To my surprise that worked.

I then immediately (and I mean that, I "ran") opened the search results page (in a document library in the WSS 3.0 site) and now I could add the Federation Search web part there.

I'm still in a state of shock and what's more important still somewhat disbelieving that that (adding the Advanced Search box) is the only change I've done. What I do remember is that I tried at one time to add the Federation Search web part to default.aspx and it failed and I even have a vague feeling that I've already tried to add just that Advanced Search box to default.aspx and it too failed.

So I'm wondering (and this is a sign of desperation because I don't want to have to do this entire installation again - I ran out of disk space and so I don't have yet another copy of the VM just after the installation of MSSX) whether the fact that my browser (IE7) crashed and I had to re-start it from zero had anything to do with this working now - i.e. some of my earlier server changes made the difference only IE wasn't letting me see them.

Anyway for now, I couldn't care less (which you Americans should note is the correct way to say this phrase :) ) because I'm going to start setting up my Foundation Search page !

 

12/10/2008 11:43:19 AM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 

As all of you will know one of the main advantages of WSS 3.0 (and MOSS 2007) over WSS 2.0 (or SPS 2003) was that users no longer saw things they couldn't do anything with.

This is officially known as "security trimming".

Now search has always had the problem that depending on the rights given to the indexing routine it could well be indexing stuff that you either don't want any non-Administrator to see or - more commonly - that you don't want a particular section of the user population to see.

That of course is where security trimming is supposed to come in. The user's search will filter out from the totality of hits all those documents (or areas of the site) that that particular user isn't allowed to see and will present to him/her only the ones he/she can look at.

That's the theory and in general it works.

But according to the search book's chapter (8) on "Securing your search results" there are some cases where that isn't the case.

One of those is if you have placed the Best Bets web part (which naturally isn't called the "Best Bets" web part - that would be too simple - it's actually called the "Search High Confidence Results" web part) on a page then the "results are not security trimmed".

The reason given is (and I don't understand it but you might) "SharePoint does not place ACLs on best bets, and best bets are shown in their own web part, separated from the search results. (That's a reason?)

Then there's the interesting suggestion that "The easiest way to secure your environment completely is to removed the Best Bets web part from your search page". 

Great. Give us a web part; don't tell us that it's flawed and then in a book most people won't buy recommend not using it. Did I mention in an earlier post that you should buy this book ?

Another case that gets a brief mention in a paragraph in this chapter is the fact that if you have a page that displays a (secured) list through a web part, then if you allow crawling of the page, the contents of the List will be available in the search results even for people who are not allowed to see the list! This just gets worse and worse ...

OK. Let's assume you know not to use the Search High Confidence Results web part and you exclude all pages with web parts containing secure lists, one way of securing data that is totally secure is to use Information Rights Management (IRM), right?

Actually yes, but in Search terms what we want is that people who do have the IRM rights to access the document will see the document in the list of documents returned by their searches and there's a snag there too which again is hidden away in a short section on IRM.  

The details taken from that (p191) are as follows.

Included in Search: You put a document into a SP Library and then make it IRM enabled ("by Sharepoint").

Not included in Search: You IRM enable a document locally and then upload it to a SP document library.

Now I don't know about you but I would have thought that IRM enabling the document before you add it to a SP library ought clearly to be the standard way of doing things as otherwise there is a time gap when the document is available on the SP site but not protected by IRM. Yet if you do that, that document isn't available to *anyone* (even people with rights to look at it) via the SP search routine.

[Later: a comment from Edgar Maucourant "About the IRM part, As far as I know when you enable IRM on a Document Library, all documents are stored unencrypted. When you request a document, SharePoint call the RMS server to encrypt the document and set the appropriate rights for you on the document based on the paramaters defined for the library and your rights. This way any documents are encrypted and secured on demand. I can't see any "time gap" but maybe I miss a point :) " cleared up this presumed problem which was caused by misreading (I prefer to call it poor wording) of the text in the chapter. That text said "the content must be IRM enabled by SharePoint after being put into a SharePoint library" which I took to mean that you upload a document ("content") and then "IRM enable" it (that single document).That to me is a reasonable interpretation of those words, but from Edgar's comment it seems that you first IRM enable the Document Library - and so when you add the document (="content") it's already covered. Maybe they could improve the text in the next printing (if that indeed is the case)!]

Anyway I haven't a clue how I can IRM enable a document that is in a SP library and they don't say so.

The point again is that you shouldn't need to buy a book to get this sort of information presented to you in a clear way (if visible only to people reading every single word of the book). But as it is in the book, again, it just adds to the reasons for buying it.

(However be warned that my usual method of buying a book; putting it on the shelf; and by magic knowing everything that is in it; won't work!)

 

12/10/2008 11:22:56 AM (FLE Standard Time, UTC+02:00)  #    Comments [1]   Other Computer | SharePoint  | 
 Tuesday, December 09, 2008

There have often been questions in the forums about how to upgrade from SPS 2003 to WSS 3.0.

The snappy answer is that you can't, but that's not very helpful so the threads move on to the next level which is how you get the data from SPS 2003 to WSS 3.0.

There are two main routes

- move the data to WSS 2.0 and then upgrade the WSS 2.0 to WSS 3.0

- upgrade the SPS 2003 to MOSS 2007 and then move the data to WSS 3.0.

Both of these options have the same sort of problem, namely that SPS 2003 and MOSS 2007 both have more functionality than the equivalent WSS product so many methods of - in effect - "downgrading" won't work.

My preference is for moving the data to WSS 2.0 because in SPS 2003 there's a clear dividing line between the WSS 2.0 sites "layer" and the SPS "layer" and so the chances are that most "WSS" sites and lists will not contain any SPS functionality and so will be movable.

My next preference is to go right down to the lowest level of saving the data. By this I mean that I don't bother with backup/restores and smigrates but instead do a number of "Save List as Templates"s (with content) to save the data. It's quick, easy and as the lowest common denominator is the most likely in my view to not include any SPS functionality. Anyway, finding out if it does is simple - just try to create a WSS 2.0 list from such a template and if it works, fine. If it doesn't you'll have to use manual methods (typically involving Datasheet View) in order to transfer the *contents* of the List rather than the whole List.

Yesterday as part of the effort of moving content to the new (Mindsharp) hosted v3 WSS FAQ site, I needed to actually do that.

The (German) WSS FAQ site is actually a WSS 2.0 site in SPS 2003. It's a very simple one with nothing there that isn't in normal WSS 2.0 so I wasn't expecting any surprises when I created v2 templates from several of the lists there.

As I only have a v3 site in a VM, I then had to create a WSS 2.0 site from scratch which I haven't done for some time. This of course went into another VM.

The way I did this - and I'm sure the easiest way - was to get hold of the MSDN disk containing iso files for Windows Server 2003 R2. I first installed the product (Standard Edition) from the CD1 iso file and then was able to use the CD2 iso file to install WSS 2.0 (which required a bit of disconnecting/reassigning/connecting of an iso file to the CDROM "device" because that WSS 2.0 wanted access to CD1 but otherwise was straightforward).

Then I added the list templates to the List template gallery and created a list each from each template.

So that was the transfer from SPS 2003 to WSS 2.0 phase over.

The next step was to upgrade that to WSS 3.0.

The first step was to make sure I had done all the pre-requisites so I looked in the Installation view in my WSS FAQ site's "2007 Articles" list and found the TechNet web page starter page for upgrading to WSS 3.0

http://technet2.microsoft.com/windowsserver/WSS/en/library/91046a84-57a1-40cb-a32c-ff3395073dc91033.mspx?mfr=true

(There's also a downloadable version but I didn't want to read it in the bath and I knew that what I needed would be in a couple of web pages only)

I followed the various steps and only noticed a couple of things that didn't apply/work for me.

The first - didn't apply - was that I was told I needed to install WSS 2.0 SP2. I didn't need to because that was already installed when using the WSS 2.0 from Windows Server 2003 *R2* (as it told me after I *did* try to install it!)

The second - didn't work - was the preconfig.exe that I downloaded from the Internet to the VM's harddisk and ran from there as it said I should. Running that gave errors. However the technet web page said that you could also run pre-config after doing the installation of WSS 3.0 and before running the installation wizard (when you would be using a different preconfig.exe that was part of the WSS 3.0 installation). So that's what I did - installed WSS 3.0; exited; ran preconfig.exe from the BIN directory (it was successful) and then looked for and ran the Configuration wizard.

[I should at this stage point out that, before starting the WSS 3.0 installation phase for the upgrade in place, I shutdown the VM and made a copy of the directory. Upgrade-in-place runs are supposed to fail often, although mine never have, and you can't back out from them. Usually you would take a backup but that's stupid if you have a VM - just make either a snapshot before doing the WSS 3.0 installation or do as I did and make a complete copy of the files.]

It all really went like clockwork, though and i never did need that (VM) directory copy.

The final step for me - though not for people moving to a new WSS 3.0 server, who would use the new server for that operation - was to then Save (now v3) List as Template again and again save the result to the hard disk of my client.

So now those Lists which will not change until the new WSS FAQ site is ready for them (the three WSS 2.0 information only lists) are ready to go. I'll make new templates from the Lists with v3 information (WSS 3.0 and MOSS 2007 information) at the very last minute before adding them to the new site.

 

12/9/2008 12:18:49 PM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 
 Monday, December 08, 2008

The Collutions site has been down since last Wednesday and shows no signs at the moment of making it back. Certainly I've heard nothing.

So I'm very grateful to the US training (etc.) company Mindsharp (http://www.mindsharp.com/) for agreeing to provide a v3 (!) site for the WSS FAQ to replace the Collutions one. (i.e. this will be the site that I will be updating in future).

It looks at the moment as if this will be like the German mirror site - i.e. http://www.wssv3faq.com will be a way to get to the site, but the address when you get there will be a Mindsharp one. 

As of today http://www.wssv3faq.com still points to the German site (just as http://www.wssfaq.com does) but I'll point it to the new Mindsharp site as soon as it's up and populated which will hopefully be by next weekend.

12/8/2008 9:11:25 AM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 
 Sunday, December 07, 2008

This needs a bit of an explanation.

A while ago after I discovered that the explanation in my book for how to amend the standard search box in WSS 3.0 (after you had installed Search Server 2008 Express (or MSSX) on top of it) which worked when I did it (in Windows Server 2003) didn't work in an identical installation working in Windows Server 2008, I started investigating how to get it to work in Windows Server 2008 too and eventually succeeded!

Like all good testers, before I made those tests, I took a copy of the VM.

So I now have two VMs which started out as being identical but where in one I've amended the Search locations etc. (which included creating a new search results page) and one where I haven't.

Today I decided to document the process.

There are two main activities.

One is to install a feature which amends the standard search box, but when you do that you need to already have a Search Results page to point the search box at and for that you can either chose to point it at the *MSSX site's* Search results page, or you can create a new one - typically by creating a web part page; storing it in a document library and then amending it by adding in one or more Search web parts.

So I decided to start with that and I created a new Web Parts Page; stored it in the standard "Shared Documents" document library (giving it lots of rows and columns) and then did Edit page so I could add at least one "Federated Search" web part. The set of Search web parts had been added to the installation when I installed MSSX on top of 'WSS 3.0 + SP1'.

At first everything looked fine, when I clicked on "Add a Web Part" I got three sets of Web Parts - "List and Libraries"; "All Web Parts" (both of these are standard WSS 3.0 web parts) and "Search".

The problem however was that when I tried to add any of the web parts in the Search group, I got an error message (usually - but not always - "unable to add selected web part." "Cannot Import this web part".

Now I remembered having exactly this problem the first time around with that other copy of the VM and what then happened was that suddenly (after I had been fiddling around) it cleared and I *could* add search web parts in the WSS 3.0 default site. (Now, too, it's possible to add these parts in the MSSX site).

This was in fact one of the reasons for repeating these actions - to try to see what exactly made the difference and "turned on the switch" allowing me to add Search web parts. Only this time I'd document what I was doing and try adding a search web part after every single action.

The present state of play is that despite all the things I've tried, I still can't add these web parts to the WSS 3.0 site. But there's a key there somewhere, it's just a question of trying to remember allthe things I did last time (which was - horrors - three weeks ago).

Interesting, though, I think you'll agree.

 

P.S. Just to make it quite clear. I have no problems in adding Search parts to the Search site. I can thus create Web Part Pages in the Search site that I can use for the Results from a search done in the default (WSS 3.0) site. The problem is only if I want that Web Part Page to be in the default (WSS 3.0) site. Then the Search parts are listed as available, but aren't.
12/7/2008 5:03:29 PM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 
 Saturday, December 06, 2008

Special Note: The US wss.collutions.com site has been down since Wednesday. I'm frantically making arrangements to find another hoster for that copy of the WSS FAQ site. For now the "German" mirror used in the (FAQ) links below is the only one working. (www.wssfaq.com) If a new US site is found it will use www.wssv3faq.com which until then will go to the same address as www.wssfaq.com)

Note: All of the addresses of the KB / Articles - 2007 Products / MS / Non-MS Articles below were valid at the time I added them to the WSS FAQ
site and to this file. I can't guarantee that they still are.

(Items are added to the WSS FAQ throughout the week so you will find new items more quickly by checking at wss.collutions.com or www.wssfaq.com daily.)

From 30th November - 6th December 2008

NOTE: Amendment to KB articles: Microsoft are now not amending the date of a KB article if the change made is marked as a version point change (so from 2.2 to 2.3 for instance).
This ought to mean that the amendment made is cosmetic rather than important as important text changes ought to result in a major version change (such as from 2.2 to 3.0).
Because of this change and to avoid unnecessary effort I will in future not amend the listings in the WSS FAQ sites if only a minor version change has taken place.
I will continue to amend both the date and version numbers of major version changes and of course will continue to add all relevant new KB articles that my RSS feeds and other sources give me.

I.1 2007 KB Articles    (*now only one section for WSS and MOSS*)

New

None

Modifed

None

I.b Forefront KB Articles

New or Modified

None

I.c InfoPath 2007 KB Articles

New

http://support.microsoft.com/default.aspx?scid=kb;en-us;957306

A hotfix is available to view or print the digitally signed InfoPath 2007 form when the form's digital certificate expires

27th November 2008

Modified

None

I.d SPD 2007 KB Articles

New or Modified

None

II. Articles - 2007 Products  (no longer with all links to articles for other Office 2007 and other 2007 Products)

New

A. Office 2007 Server Products

http://technet.microsoft.com/en-us/magazine/dd297618.aspx

SharePoint Security Accounts (TechNet Mag Jan 2009 - Pav Cherny)

4th December 2008 (date added)

http://www.microsoft.com/downloads/details.aspx?familyid=71a6a448-b655-44aa-bc70-c7f752547046&displaylang=en&tm

Extending SharePoint with Groove Collaboration

25th November 2008

B. Other Office 2007 products

http://technet.microsoft.com/en-us/magazine/dd314383.aspx

Getting Started with Project Server 2007 (TechNet Mag Jan 2009 - Alan Maddison)

4th December 2008 (date added)

C. Other relevant products

None

 

Modified

None

III WebCasts (+ PodCasts, On-Line courses) for 2007 Products

None

IV WSS v3 FAQ

New

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1608

V.182 (Software: Microsoft Office SharePoint Designer 2007 Upgrade)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1609

V.183 (Software: Microsoft Office SharePoint Designer 2007)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1610

V.184 Microsoft Office SharePoint Server 2007 - Collaboration Features - Computer Based Training DVD Rom (BrainStorm Inc) *released*

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1611

V.185 (Software: Microsoft InfoPath 2007)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1612

V.186 Microsoft InfoPath 2007 Training Course (K Alliance) *released*

(ID 1613 and 1614 are "A" copies of courses to get them listed with the products as well [SPD 2007 / InfoPath 2007])

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1615

V.187 Microsoft InfoPath 2007 Quick Reference Card - Handy Durable Tri-Fold MS Info Path 2007 Tip & Tricks Guide. 6 Total Pages. (Brainstorm Inc.) *released*

(ID 1616, 1617, 1618 are "A" copies of courses to get them listed with the products as well)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1619

VII.40A Professional Microsoft Office SharePoint Designer 2007 (Wrox - ISBN  978-0-470-28761-3) - Chapter 1 - Exploring SharePoint Designer

Modified

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1313

V.87 Professional SharePoint 2007 Design (Wrox - Jacob J. Sanford, Randy Drisgill, David Drinkwine, Coskun Cavusoglu) *released*

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1446

V.138 Microsoft SharePoint 2007 Wrox Box: Professional SharePoint 2007 Development, Real World SharePoint 2007, Professional SharePoint 2007 Design & Professional ... 2007 Web Content Management Development (Wrox - various authors) *released*

V WSSv2 KB Articles (plus SPS 2003 Hot fixes)

New or Modified

None

VI WSSv2 FAQ

New or Modified

None

VII. MS Articles

New or Modified

None

12/6/2008 3:37:17 PM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 

Note: All of the addresses of the KB / Articles - 2007 Products / MS / Non-MS Articles below were valid at the time I added them to the WSS FAQ
site and to this file. I can't guarantee that they still are.

(Items are added to the WSS FAQ throughout the week so you will find new items more quickly by checking at wss.collutions.com or www.wssfaq.com daily.)

From 23rd - 29th November 2008

NOTE: Amendment to KB articles: Microsoft are now not amending the date of a KB article if the change made is marked as a version point change (so from 2.2 to 2.3 for instance).
This ought to mean that the amendment made is cosmetic rather than important as important text changes ought to result in a major version change (such as from 2.2 to 3.0).
Because of this change and to avoid unnecessary effort I will in future not amend the listings in the WSS FAQ sites if only a minor version change has taken place.
I will continue to amend both the date and version numbers of major version changes and of course will continue to add all relevant new KB articles that my RSS feeds and other sources give me.

I.1 2007 KB Articles 

New

None

Modifed

http://support.microsoft.com/kb/952167/en-us

Folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in Windows SharePoint Services 3.0 or in SharePoint Server 2007 (ver 5.0)

20th November 2008

http://support.microsoft.com/default.aspx?scid=kb;en-us;957693

Description of the SharePoint Server 2007 hotfix package (Coreserver.msp): October 28, 2008 (ver 2.0)

19th November 2008

I.b Forefront KB Articles

New or Modified

None

I.c InfoPath 2007 KB Articles

New or Modified

None

I.d SPD 2007 KB Articles

New or Modified

None

II. Articles - 2007 Products

New

A. Office 2007 Server Products

** Special Search Server 2008 section **

http://www.codeplex.com/tmt/Release/ProjectReleases.aspx?ReleaseId=19742

View or change content index locations (Search Server 2008) (updated 30th November 2008)

30th November 2008   (probably a mistake and it should have been 30th October ...)

http://www.thesanitypoint.com/archive/2008/11/22/search-federation-part-2-customizing-results-with-sharepoint-designer.aspx

Search Federation Part 2 - Customizing Results with SharePoint Designer (Blog - Woody Windischman)
 
22nd November 2008

http://www.thesanitypoint.com/archive/2008/11/18/search-federation-with-sharepoint-part-1.aspx

Search Federation with SharePoint - Part 1 (Blog - Woody Windischman)
 
18th November 2008

http://technet.microsoft.com/en-us/library/dd255991.aspx

Configure index and query server roles (Search Server 2008) (updated 30th October 2008)

30th October 2008

http://technet.microsoft.com/en-us/library/dd255992.aspx

View the content index location for the index server (Search Server 2008) (updated 30th October 2008)

30th October 2008

http://technet.microsoft.com/en-us/library/dd255995.aspx

View the content index location for a query server (Search Server 2008) (updated 30th October 2008)

30th October 2008

http://technet.microsoft.com/en-us/library/cc825782.aspx

Move site collections to a new database (split a content database) (Search Server 2008) (updated 23rd October 2008)

23rd October 2008

http://technet.microsoft.com/en-us/library/cc706840.aspx

Archive and retrieve content by using Stsadm import and export operations (Search Server 2008) (updated 23rd October 2008)

23rd October 2008

http://technet.microsoft.com/en-us/library/dd181962.aspx

Migrate an SSP to another farm (Search Server 2008) (updated 9th October 2008)

9th October 2008

http://technet.microsoft.com/en-us/library/cc950776.aspx

Security for Federation (Search Server 2008) (updated 9th October 2008)

9th October 2008

http://technet.microsoft.com/en-us/library/cc262507.aspx

Create a custom dictionary (Search Server 2008) (updated 9th October 2008)

9th October 2008

http://technet.microsoft.com/en-us/library/cc262033.aspx

Security considerations for search (Search Server 2008) (updated 9th October 2008)

9th October 2008

http://www.thesanitypoint.com/archive/2008/09/05/the-quote-language-quote-of-advanced-search-part-2.aspx

The "Language" of Advanced Search (Part 2) (Blog - Woody Windischman)
 
5th September 2008

http://www.thesanitypoint.com/archive/2008/09/02/the-quote-language-quote-of-advanced-search-part-1.aspx

The "Language" of Advanced Search (Part 1) (Blog - Woody Windischman)
 
2nd September 2008

http://go.microsoft.com/fwlink/?LinkId=121946&clcid=0x409

Presentation: Understanding and deploying hotfixes, public updates, and service packs (Search Server 2008) (updated 21th August 2008)

21th August 2008

---end of special section for Search Server 2008 ---


http://go.microsoft.com/fwlink/?LinkID=135694&clcid=0x409

Using scripts to automate SharePoint Server 2007 installation

26th November 2008 (date added)

http://blogs.msdn.com/sharepointdesigner/archive/2008/11/25/locking-down-sharepoint-designer.aspx

Locking Down SharePoint Designer (MS TeamBlog)

25th November 2008

http://microsofttech.fr.edgesuite.net/TechEdOnline/Videos/447_high_fix.wmv

TechEd Europe chat on "SharePoint Guidance" from MS Patterns and Practices (Robert Bogue)

23rd November 2008 (date added - there are also .mp4 and .mp3 versions available)

http://technet.microsoft.com/en-us/library/dd263437.aspx

Deploy inter-farm shared services (Updated 20th November 2008)

20th November 2008

http://go.microsoft.com/fwlink/?LinkId=133329&clcid=0x409

Protecting Office SharePoint Server 2007 by using System Center Data Protection Manager (white paper) (Updated 13th November 2008)

13th November 2008

http://technet.microsoft.com/en-us/library/dd278299.aspx

Updatealerttemplates: Stsadm operation (Office SharePoint Server *and* WSS 3.0 - identical articles) (Updated 12th November 2008)

12th November 2008

(as the title above indicates there were two articles one supposedly for MOSS and the other for WSS 3.0. Apart from this the text (which referred only to WSS 3.0 in both) was identical)

https://www.microsoft.com/downloads/details.aspx?FamilyId=1C356D9A-BE11-4BEB-88E7-4EB7141D7F89&displaylang=en

Updates for Microsoft Office SharePoint Designer 2007 Help

11th November 2008

B. Other Office 2007 products

None

C. Other relevant products

http://www.microsoft.com/downloads/details.aspx?familyid=bce7684a-507b-4fc6-bc99-6933cd690cab&displaylang=en&tm

Microsoft Silverlight 2 Software Development Kit Documentation (ver 2.0)

25th November 2008

http://www.microsoft.com/downloads/details.aspx?familyid=66d3e6f5-6902-4fdd-af75-9975aea5bea7&displaylang=en&tm

SQL Server 2008 Upgrade Technical Reference Guide

25th November 2008

Modified

None

III WebCasts (+ PodCasts, On-Line courses) for 2007 Products

http://channel9.msdn.com/posts/VisualStudio/Sharepoint-Development-with-Visual-Studio-2010/

PDC 2008: Sharepoint Development with Visual Studio 2010 (Channel 9 - Reza Chitsaz)

14th November 2008

IV WSS v3 FAQ

New

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1605

X.231 SharePoint Snippets (Workflow Extensions/Custom Workflow Template for Debugging) (MS Code Gallery - Tobias Lekman)

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1606

X.232 Imtech SharePoint A (extended HtmlAnchor control) (codeplex - Waldek Mastykarz, Imtech (NL))

http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1607

X.233 Useful Sharepoint Designer Custom Workflow Activities (codeplex - "unclepaul84" and others)

Modified

None

V WSSv2 KB Articles (plus SPS 2003 Hot fixes)

New or Modified

None

VI WSSv2 FAQ

New or Modified

None

VII. MS Articles

New or Modified

None

12/6/2008 3:29:13 PM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 

You may remember that I had problems because at work on the keyboard there I had specified a password containing "*" in a server system that had first been installed (by no chopice of mine because this was Windows 2008 where the installation of the US version of the operating system will always install the US keyboard leaving you to amend that setting later) with the US keyboard and - guess what, the US keyboard is the one that is valid for the password because the password is asked for before the operating system gets its settings!

Anyway, the problem then was that the "*" on a Finnish keyboard is in a place where there is NO KEY at all in a US keyboard and so it was impossible to find the US keyboard equivalent, because there wasn't one.

Anyway, when I re-installed (I was forced to !) the Operating system I very carefully chose keys that were not on the far right of the keyboard, so there were US keybpard equivalents.

To make it easy for myself - because it didn't seem possible (= wasn't as easy as usual) to say that I wanted a permanent password - I decided to use my usual password but using a ! (shift-1) at the end instead of the * and then it was logical when a new password that I would move along and use Shift-2 (= ").

Then I transfered the VM back to my home machine for the weekend **and I couldn't login**. I naturally tried the old password; the new password; both with Caps On and nothing worked. So I presumed that the problem was in the transfer (which had just made it onto a 16GB USB stick) and I've have to wait until I got back to work.

However, today I had a brainwave (a very small one :) ) and I had a look at a US keyboard. Small Oops the US keyboard's Shift-2 isn't a " but it's a @ (which is my AltGr-2).

So I decided that I had two more possible attempts. To use the @ on my keyboard or to use the key (in fact Ä) on my keyboard that is where the " is located on a US keyboard.

I tried them in order. To no-one's surprise the second one I tried was the right one.

---------------------

So why ? I changed the password using the same kind of keyboard that I used to enter the password later. Why then didn't it work ?

It's obvious really. When I changed the password I was already logged in to the operating system and so the Finnish keyboard was in operation. I did therefore type in AAAA" and that is what the system changed the password to. When however I was asked to login, I was not logged in at that time (:)) and so the US keyboard was in operation hence it wanted me to type in the " on the US keyboard which of course wasn't in the same place.

Small quiz: If the system locks and you need to enter Name and Password to get back in, which password do you write "AAAA and Shift-2" or "AAAA and Ä" ?

(The answer is at the end)

--------------------

You may well call this - not letting you change the keyboard when installing an operating system but only afterwards - a bug.

I'd call it a MASSIVE design error.

Answer: You use "AAAA and Ä". If you had shut down the OS and re-started it you would have needed "AAAA and Shift-2"

... and for some reason when I added this last time the system flipped out completely ...
12/6/2008 3:22:36 PM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 

I recently received two recent Wrox books.

- Professional Microsoft Search - Sharepoint 2007 and Search Server 2008

(Amazon US: http://www.amazon.com/exec/obidos/ASIN/0470279338/heme0f)

- Professional SharePoint 2007 Design

(Amazon US: http://www.amazon.com/exec/obidos/ASIN/047028580X/heme0f)

One major difference between them is that the first deals ONLY with Search. The second on the other hand extends the boundaries of what is "Design" way past anything I would consider to be design and is in fact for me more of a mixed bag of interesting but isolated chapters on a wide range of topics.

Let's start with the first book. It's the first one I have seen on Search (and there is also the MS Press book "Inside the Index and Search engines" which I haven't seen) so it's perhaps fooolhardy to say that if you are at all interested in Search you should buy this one, but I'll say it anyway because it covers everything and more that I could think of.

(Even though the single Search chapter in the Design book had lots of stuff that I couldn't find in the Search book - which I've read all of just over half the chapters but have scanned the rest to look for just that information)

There's really only one thing that jars when reading the book and that is that there were three different people involved in writing it - and it shows. Very roughly speaking there are parts of the book that are at helicopter level (written by Microsoft non-Search specialist is my guess); then there are the parts of the book that think that everything in the product is wonderful (written by Microsoft Search specialist ?) and then there are the chapters and parts of chapters that go into details of real use of the product and are not afraid to say that things don't work as you would expect (written by the one writer who doesn't work for Microsoft is my solid guess).

There's one lovely part where it tells you that there is a "slight complication" that you don't get any search results at all if your site isn't using Kerberos. I spent hours wondering whether this was the non-Microsoft guy being sarcastic or the MS Search guy trying to justify a poor design decision ...

There's also sometimes a curious order to some of the chapters which i imagine is caused by slotting in the work of two or more authors into the same chapter.

So, for instance, the chapter on Federation Search has towards the middle a section with very complicated stuff that is followed by the simplest of all things (clicking on Modify a (Search) Web Part and changing the default values). In any normal, logical order, that very easy section would surely have come very early on in the chapter not right at the end.

But these are minor flaws. I learnt a lot by reading the chapters I have read so far and although I wouldn't give it 5 stars at Amazon, it would be worth a clear 4 and a bit.

Now on to the Design book.

Here you have the impression that they (in this case the four authors) didn't really know half of the time what they were supposed to be writing about. The foreword for instance was written by Heather Solomon and she seemed to think that this was a book about SharePoint Designer.

Well there are a few chapters on SharePoint Designer that's true but there are also chapters on standard MOSS functionality; on Search (see above - that's a really good chapter btw) and on Accessibility for what Microsoft define as the "physically challenged".

There's also an early chapter on designing your SharePoint site by using a very expensive Adobe Product (Photoshop). 

This seems completely mad if you want to sell a lot of copies of a book as most people will not have this Adobe product and will certainly not feel like buying it in order to do the design. Yet the use of this product is even listed on the back cover and although at the start of the chapter there's mention that you can also use other cheaper (or free) products to do the same kind of thing, all they seem to use is that expensive product.

At the moment therefore I'm at a loss as to who ought to buy this book. Should people who want the SPD content buy it instead of a book dedicated to SPD (Hardly)? Should people specialising in Search buy it for the one Search chapter (actually the answer is probably yes, but that answer applies only to serious search specialists)? Should people wanting to know about Accessibility for the physically challenged buy it for that single chapter (imo, No)? Should people wanting information on standard MOSS functionality buy it for those chapters when there are so many other MOSS books out there both for developers and non-developers (I doubt it) ?

In other words whereas the Search book is a slam dunk buy if you want lots of Search information, with this one you'd better look at the Design book closely in a bookshop and decide if enough of it is about things you are interested in. If I were buying, I'd only buy this as a third or fourth (or fifth or sixth or ...) to add to my other more specific books.

P.S. The Amazon web site shows at present four 5 star reviews and one three star one. So far without giving it enough time, I'm inclined to side with the three star reviewer who seems to have expected what Heather Solomon indicated in her foreword, but what she got was - as i've tried to indicate above - something else.

My own Amazon review will have to wait until I've given the book as a lot more time. The Photoshop chapter alone ensures that it won't be getting 5 stars but 4 is still possible if the quality of the other chapters matches the quality of the Search chapter - despite the lack of real focus of the book as a whole.

 

 

 


 

 

12/6/2008 3:20:29 PM (FLE Standard Time, UTC+02:00)  #    Comments [0]   Other Computer | SharePoint  | 
 Friday, December 05, 2008

You may remember that I had problems because at work on the keyboard there I had specified a password containing "*" in a server system that had first been installed (by no chopice of mine because this was Windows 2008 where the installation of the US version of the operating system will always install the US keyboard leaving you to amend that setting later) with the US keyboard and - guess what, the US keyboard is the one that is valid for the password because the password is asked for before the operating system gets its settings!

Anyway, the problem then was that the "*" on a Finnish keyboard is in a place where there is NO KEY at all in a US keyboard and so it was impossible to find the US keyboard equivalent, because there wasn't one.

Anyway, when I re-installed (I was forced to !) the Operating system I very carefully chose keys that were not on the far right of the keyboard, so there were US keybpard equivalents.

To make it easy for myself - because it didn't seem possible (= wasn't as easy as usual) to say that I wanted a permanent password - I decided to use my usual password but using a ! (shift-1) at the end instead of the * and then it was logical when a new password that I would move along and use Shift-2 (= ").

Then I transfered the VM back to my home machine for the weekend **and I couldn't login**. I naturally tried the old password; the new password; both with Caps On and nothing worked. So I presumed that the problem was in the transfer (which had just made it onto a 16GB USB stick) and I've have to wait until I got back to work.

However, today I had a brainwave (a very small one :) ) and I had a look at a US keyboard. Small Oops the US keyboard's Shift-2 isn't a " but it's a @ (which is my AltGr-2).

So I decided that I had two more possible attempts. To use the @ on my keyboard or to use the key (in fact Ä) on my keyboard that is where the " is located on a US keyboard.

I tried them in order. To no-one's surprise the second one I tried was the right one.

---------------------

So why ? I changed the password using the same kind of keyboard that I used to enter the password later. Why then didn't it work ?

It's obvious really. When I changed the password I was already logged in to the operating system and so the Finnish keyboard was in operation. I did therefore type in AAAA" and that is what the system changed the password to. When however I was asked to login, I was not logged in at that time (:)) and so the US keyboard was in operation hence it wanted me to type in the " on the US keyboard which of course wasn't in the same place.

Small quiz: If the system locks and you need to enter Name and Password to get back in, which password do you write "AAAA and Shift-2" or "AAAA and Ä" ?

(The answer is at the end)

--------------------

You may well call this - not letting you change the keyboard when installing an operating system but only afterwards - a bug.

I'd call it a MASSIVE design error.

 

google_ad_client = "pub-7109607934593950"; google_alternate_color = "FFFFFF"; google_color_border = "FFFFFF"; google_ad_width = 468; google_ad_height = 60; google_ad_format = "468x60_as"; google_ad_channel ="2397098682"; //-->

Answer: "AAAA and Ä" because the operating system is running. If you however shut it down and re-start it, *then* you need "AAAA and Shift-2" !